From owner-freebsd-hackers Sun Aug 9 00:03:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19653 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 00:03:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19645 for ; Sun, 9 Aug 1998 00:03:45 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id PAA23987; Sun, 9 Aug 1998 15:01:53 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id PAA00669; Sun, 9 Aug 1998 15:02:27 +0800 Message-Id: <199808090702.PAA00669@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG cc: dg@root.com, jobaldwi@vt.edu, grog@lemis.com Subject: Re: AMD-specific kernel code (was: How long a wait?) In-reply-to: Your message of "Sat, 08 Aug 1998 23:49:51 MST." <199808090649.XAA23702@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 15:02:27 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The effect on CPU performance is also noticable: here are "make > >world" times: > > > >Without write allocate: > > > >real 106m58.441s > >user 63m0.960s > >sys 20m25.035s > > > >With write allocate: > > > >real 114m16.402s > >user 69m41.733s > >sys 17m54.862s > > It looks like something that should be a tunable knob of some sort. I tend to have processes that compute for a considerable period of time, which may benefit, but Joe Average's make world clearly won't. Try it as a option in the config file, or yet another flag to the npx device, or (best possible) a sysctl flag, so that one may turn it off & on as required while the system is up. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 9 00:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20635 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 00:15:14 -0700 (PDT) (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 AAA20630 for ; Sun, 9 Aug 1998 00:15:10 -0700 (PDT) (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 QAA06259; Sun, 9 Aug 1998 16:44:44 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA11299; Sun, 9 Aug 1998 16:44:37 +0930 (CST) Message-ID: <19980809164437.C11095@freebie.lemis.com> Date: Sun, 9 Aug 1998 16:44:37 +0930 From: Greg Lehey To: dg@root.com Cc: John Baldwin , FreeBSD Hackers Subject: Re: AMD-specific kernel code (was: How long a wait?) References: <19980809160829.A11214@freebie.lemis.com> <199808090649.XAA23702@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808090649.XAA23702@implode.root.com>; from David Greenman on Sat, Aug 08, 1998 at 11:49:51PM -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 Saturday, 8 August 1998 at 23:49:51 -0700, David Greenman wrote: >> The effect on CPU performance is also noticable: here are "make >> world" times: >> >> Without write allocate: >> >> real 106m58.441s >> user 63m0.960s >> sys 20m25.035s >> >> With write allocate: >> >> real 114m16.402s >> user 69m41.733s >> sys 17m54.862s >> >> These were only a rough test (I had other stuff running at the same >> time), but in practice this normally only makes about 1 minute >> difference. I'd guess that the difference *is* real. Obviously there >> must be a reason for enabling or disabling this behaviour, and I'd >> guess that write allocation is most effective when one process is >> using much CPU time. 'make world' starts thousands of short-lived >> process, and may thus be the worst-case scenario. In this connection, >> it's also interesting to note that system time was down and user time >> was up with write allocation. >> >> I have patches available. Does anybody want to commit them? > > Based on the above performance numbers, I'd say no - they appear to be > a pessimization. If they were always like that, I'd agree. But as I said, I think it depends on the application, and I'm prepared to believe that long-running servers could benefit significantly. Still, that's not proven. I've put the patches on ftp://ftp.lemis.com/pub/AMD-write-allocate-patch. They relate to today's -CURRENT. How about some other people grabbing them and trying them out? Greg -- See complete headers for address 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 Sun Aug 9 08:37:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26742 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 08:37:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26737 for ; Sun, 9 Aug 1998 08:37:52 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 2.02 #1) id 0z5XXC-0007Pb-00 for freebsd-hackers@freebsd.org; Sun, 9 Aug 1998 17:37:26 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id RAA00285 for ; Sun, 9 Aug 1998 17:32:29 +0200 (SAT) Date: Sun, 9 Aug 1998 17:32:27 +0200 (SAT) From: Peter van Heusden To: freebsd-hackers@FreeBSD.ORG Subject: EXA 8200 tape drive on FreeBSD? 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 I'm trying to get a EXA 8200 tape drive working on FreeBSD. It is detected fine by the kernel during startup, and I can do a 'mt status' on it, with the following results: Present Mode: Density = 0x00 Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3.136-1986 Blocksize = 512 bytes Mode 2: Density = X3.39-1986 Blocksize variable Mode 3: Density = X3.54-1986 Blocksize variable However, I cannot write to it at all - even after a 'mt erase', I get the following: bash# mt rewind bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 dd: /dev/nrst0: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.082043 secs (0 bytes/sec) bash# with the console showing the following message: st0: oops not queued My system details are as follows: OS: FreeBSD 2.2.6 System: 486 DX 4 120, NCR 53c810 SCSI controller (with 3 disk drives - Conner CFP1080S, Seagate ST12400N and ST32155N as well as the tape drive - disks are on ids 0, 1, 4, tape is on 6), 24 mb RAM. Is there anything else I can try to get this thing working, or should I just give up on it? Thanks, Peter -- Peter van Heusden | Its the 90's, and collective action is STILL cool! pvh@leftside.wcape.school.za | Get active in your union today! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 9 13:29:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20332 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 13:29:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA20327 for ; Sun, 9 Aug 1998 13:29:48 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA29735 (5.67b/IDA-1.5); Sun, 9 Aug 1998 22:21:45 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA00829; Sun, 9 Aug 1998 20:17:46 +0200 (CEST) From: Wilko Bulte Message-Id: <199808091817.UAA00829@yedi.iaf.nl> Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: from Peter van Heusden at "Aug 9, 98 05:32:27 pm" To: pvh@leftside.wcape.school.za (Peter van Heusden) Date: Sun, 9 Aug 1998 20:17:46 +0200 (CEST) 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 Peter van Heusden wrote... > I'm trying to get a EXA 8200 tape drive working on FreeBSD. It is detected > fine by the kernel during startup, and I can do a 'mt status' on it, with > the following results: > > Present Mode: Density = 0x00 Blocksize variable > ---------available modes--------- > Mode 0: Density = 0x00 Blocksize variable > Mode 1: Density = X3.136-1986 Blocksize = 512 bytes > Mode 2: Density = X3.39-1986 Blocksize variable > Mode 3: Density = X3.54-1986 Blocksize variable > > However, I cannot write to it at all - even after a 'mt erase', I get the > following: > [del] > My system details are as follows: > > OS: FreeBSD 2.2.6 > System: 486 DX 4 120, NCR 53c810 SCSI controller (with 3 disk drives - > Conner CFP1080S, Seagate ST12400N and ST32155N as well as the tape drive > - disks are on ids 0, 1, 4, tape is on 6), > 24 mb RAM. > Is there anything else I can try to get this thing working, or should I > just give up on it? Well, not that it solves your problem, but I also have a 8200 on a ncr810 and that one works. Has done so for years. More specific it has firmware: Aug 7 22:17:20 yedi /kernel: (ncr1:3:0): "EXABYTE EXB-8200 2687" type 1 removable SCSI 1 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 Sun Aug 9 14:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23383 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 14:01:18 -0700 (PDT) (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 OAA23378 for ; Sun, 9 Aug 1998 14:01:12 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40495>; Mon, 10 Aug 1998 07:00:26 +1000 Date: Mon, 10 Aug 1998 07:00:37 +1000 From: Peter Jeremy Subject: NPX configuration after exec() To: hackers@FreeBSD.ORG Message-Id: <98Aug10.070026est.40495@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The NPX (x87) is initialised with a configuration word of 0x1272 (sys/i386/include/npx.h __BDE_NPXCW__). The comment associated with this states: * Later I will want the IEEE default of all exceptions masked. See the * 0.0 math manpage for why this is better. The 0.1 math manpage is empty. Whilst I'm uncertain of the references to 0.0 and 0.1, math(3M) does include some comments which imply that libm is designed to function correctly with all exceptions masked. Are there any plans to change the configuration word to 0x127f as implied in this comment? 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 Sun Aug 9 15:01:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28317 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 15:01:00 -0700 (PDT) (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 PAA28306 for ; Sun, 9 Aug 1998 15:00:58 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA22990; Sun, 9 Aug 1998 15:00:32 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd022985; Sun Aug 9 15:00:29 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA20417; Sun, 9 Aug 1998 15:00:22 -0700 (MST) From: Terry Lambert Message-Id: <199808092200.PAA20417@usr04.primenet.com> Subject: Re: C and static initialization with unions To: mike@smith.net.au (Mike Smith) Date: Sun, 9 Aug 1998 22:00:22 +0000 (GMT) Cc: jdp@polstra.com, rivers@dignus.com, hackers@FreeBSD.ORG In-Reply-To: <199808082206.PAA02145@antipodes.cdrom.com> from "Mike Smith" at Aug 8, 98 03:06:45 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've had (several) run-ins with const poisoning trying to port a large > third-party codebase. It's sufficiently bogus to require -traditional > to build, and I expect not too novel in that regard. I have a number of programs which I like to use, but which I do not want to become the maintainer of (for one thing, I don't have a huge FTP server and can't offer cvsup, etc.). These programs do things like modify declared strings (on the assumption that they will be stored in data section, not code section, what with them being data, and all...). They also do things like modify variables in signal handlers and in subfunctions of functions that also use the variable. Without the -traditional flag, this would require the use of the "volatile" keyword. Other examples exist, including the use of int arguments to implement varaddic functions, and casting to char * instead of void * for opaque conversion. Sure, it's be nice if there were three of me (;-)) and I could do all this and the stuff that I want to do as well, but there aren't, and I can't. > If we support compilation of K&R application code, we should attempt to > make sure that system headers function correctly in that regard. Yes, please. 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 Aug 9 15:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28490 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 15:02:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28484 for ; Sun, 9 Aug 1998 15:02:30 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA21838 for hackers@freebsd.org; Sun, 9 Aug 1998 18:05:13 -0400 From: Bill Paul Message-Id: <199808092205.SAA21838@skynet.ctr.columbia.edu> Subject: Yet another XL driver update To: hackers@FreeBSD.ORG Date: Sun, 9 Aug 1998 18:05:12 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I put yet another update of the 3Com Etherlink XL driver at www.freebsd.org/~wpaul/3Com. This version has changes to fix support for 100baseT4 cards and fixes a small bug in the TX error recovery. I'm hoping to commit the 3.0 driver to -current by the end of next week, but I'm still concerned that there may be problems in some configurations. I've have a couple people report problems with performance but lack of followups has made it hard to me to know if these problems are still present. I'm interested mainly in the following: - I have received some reports of spotty transmission performance or 'transmission error' messages. I made a mistake in the code that tries to recover from some of these errors (I wasn't resetting the upload list pointer correctly) which should be fixed now. I'm interested to know if transmission problems persist, particularly with 10Mbps links on slow machines. This applies to all supported cards (3c900, 905 and 905B). - I haven't yet been able to fix the problem with one particular 3c900 COMBO card. This card appears to initialize correctly but refuses to do DMA. The 3c900 card that I have works properly and I haven't been able to remotely debug the problem. If you have a 3c900 card that probes correctly but doesn't appear to transmit and receive, and which does work corretly with the vx driver (which doesn't use DMA), then I'd like to know. Without any other evidence, I'm nearly convinced that this is a hardware problem with this one card. If you have a problem, please let me know. Tell me the type of system you're using, the type of card you have, the version of FreeBSD, and a _DETAILED_ description of the problem, along with a way to reproduce the failure, if at all possible. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 9 17:55:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20876 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 17:55:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20871 for ; Sun, 9 Aug 1998 17:55:21 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-112.camalott.com [208.229.74.112]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA05437; Sun, 9 Aug 1998 19:56:11 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA02641; Sun, 9 Aug 1998 18:36:54 -0500 (CDT) (envelope-from joelh) Date: Sun, 9 Aug 1998 18:36:54 -0500 (CDT) Message-Id: <199808092336.SAA02641@detlev.UUCP> To: freebsd-hackers@FreeBSD.ORG Subject: Boot code From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From /sys/i386/boot/biosboot/boot.c: /* * Be paranoid and make doubly sure that the input buffer is empty. */ if (loadflags & (RB_DUAL | RB_SERIAL)) init_serial(); Is this worth the bytes? (The only thing that would have frobbed loadflags at this point is getbootdev, and it calls init_serial() if it sets either flag. This is what I see, but more eyes checking me would be welcome.) Are we even concerned about saving bytes in boot2, or is that no longer a concern? While I'm at it, the stack is reset when the kernel is loaded, so I don't need to worry about adding variables to boot(), do I? While I'm at it, I'm adding code to allow all flags to be specified in boot.config. The idea is that if flags are specified from the keyboard, they override everything (except RB_SERIAL, RB_DUAL, and RB_PROBEKBD) from boot.config. Anybody have a problem with this? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 9 20:01:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01001 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 20:01:17 -0700 (PDT) (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 UAA00996 for ; Sun, 9 Aug 1998 20:01:16 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from phoenix.phoenixos.com (pool-207-205-242-59.atln.grid.net [207.205.242.59]) by camel14.mindspring.com (8.8.5/8.8.5) with ESMTP id WAA20483; Sun, 9 Aug 1998 22:59:52 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.2 [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: <19980808182200.E14475@freebie.lemis.com> Date: Sun, 09 Aug 1998 23:00:24 -0400 (EDT) Organization: Virginia Tech From: John Baldwin To: Greg Lehey Subject: RE: AMD-specific kernel code (was: How long a wait?) Cc: FreeBSD Hackers , John Baldwin , dg@root.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Aug-98 Greg Lehey wrote: > (following up to -hackers) > > On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >> >> I just looked at the patch. Other than some KNF style bugs, it seems >> okay. >> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >> be committing it. >> If it could get wider circulation - perhaps by posting a note to hackers >> asking for testers, then I think there would be less hesitation in getting >> it committed. > > I've grabbed the code and will try it out and report. > > Greg One note, I just found out that this will only work on on certain chipsets (I think Intel Triton TX, but I could be wrong, so don't quote me on that.) John Baldwin -- jobaldwi@vt.edu -- jbaldwin@freedomnet.com -- ---- http://www.freedomnet.com/~jbaldwin/ ---- "I waited for the Lord on high/I waited and He heard my cry." - Petra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 9 20:04:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01308 for freebsd-hackers-outgoing; Sun, 9 Aug 1998 20:04:13 -0700 (PDT) (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 UAA01303 for ; Sun, 9 Aug 1998 20:04:10 -0700 (PDT) (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 MAA08721; Mon, 10 Aug 1998 12:33:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA14853; Mon, 10 Aug 1998 12:33:41 +0930 (CST) Message-ID: <19980810123341.X11095@freebie.lemis.com> Date: Mon, 10 Aug 1998 12:33:41 +0930 From: Greg Lehey To: John Baldwin Cc: FreeBSD Hackers , John Baldwin , dg@root.com Subject: Re: AMD-specific kernel code (was: How long a wait?) References: <19980808182200.E14475@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Baldwin on Sun, Aug 09, 1998 at 11:00:24PM -0400 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 Sunday, 9 August 1998 at 23:00:24 -0400, John Baldwin wrote: > On 08-Aug-98 Greg Lehey wrote: >> (following up to -hackers) >> On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >>> >>> I just looked at the patch. Other than some KNF style bugs, it seems >>> okay. >>> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >>> be committing it. >>> If it could get wider circulation - perhaps by posting a note to hackers >>> asking for testers, then I think there would be less hesitation in getting >>> it committed. >> >> I've grabbed the code and will try it out and report. > > One note, I just found out that this will only work on on certain chipsets (I > think Intel Triton TX, but I could be wrong, so don't quote me on that.) As the title indicates, this specific tweak only works on AMD K5 stepping 4 and above, and all AMD K6s. I've posted a followup. Greg -- See complete headers for address 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 Mon Aug 10 01:52:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03683 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 01:52:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03568 for ; Mon, 10 Aug 1998 01:51:55 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 2.02 #1) id 0z5nA4-0006vW-00; Mon, 10 Aug 1998 10:18:36 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id KAA01384; Mon, 10 Aug 1998 10:18:01 +0200 (SAT) Date: Mon, 10 Aug 1998 10:18:00 +0200 (SAT) From: Peter van Heusden Reply-To: Peter van Heusden To: Wilko Bulte cc: freebsd-hackers@FreeBSD.ORG Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: <199808091817.UAA00829@yedi.iaf.nl> 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, 9 Aug 1998, Wilko Bulte wrote: > > Well, not that it solves your problem, but I also have a 8200 on a ncr810 > and that one works. Has done so for years. > > More specific it has firmware: > > Aug 7 22:17:20 yedi /kernel: (ncr1:3:0): "EXABYTE EXB-8200 2687" type 1 > removable SCSI 1 Thanks for the info. Mine gives a slightly different dmesg output: (ncr0:6:0): "EXABYTE EXB-8200 253G" type 1 removable SCSI 1 So, its a slightly different model, maybe with an older firmware (are firmware upgrades possible on these drives?) However, since it is a similar model, I was wondering what you do to use a tape. The tape I'm trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt erase' before using the tape. Peter -- Peter van Heusden | Its the 90's, and collective action is STILL cool! pvh@leftside.wcape.school.za | Get active in your union today! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 01:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04320 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 01:56:36 -0700 (PDT) (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 BAA04310; Mon, 10 Aug 1998 01:56:32 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id KAA21585; Mon, 10 Aug 1998 10:55:19 +0200 (MET DST) Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Mon, 10 Aug 1998 10:55:19 +0200 (MET DST) Mime-Version: 1.0 To: "Matthew D. Fuller" Cc: dg@root.com, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Does this mean we have another breakin? References: <199808072337.RAA13808@lariat.lariat.org> <199808080135.SAA00798@implode.root.com> <19980808013456.49685@futuresouth.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 am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Aug 1998 10:55:18 +0200 In-Reply-To: "Matthew D. Fuller"'s message of "Sat, 8 Aug 1998 01:34:56 -0500" Message-ID: Lines: 8 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 BAA04313 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" writes: > On sendmail on one machine (sendmail -q run out of cron) and on Why do you do that? Doesn't 'sendmail -bd -qxx' do the job? 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 Aug 10 01:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04440 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 01:57:33 -0700 (PDT) (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 BAA04412 for ; Mon, 10 Aug 1998 01:57:25 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id KAA21679; Mon, 10 Aug 1998 10:56:51 +0200 (MET DST) Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Mon, 10 Aug 1998 10:56:50 +0200 (MET DST) Mime-Version: 1.0 To: Chris Timmons Cc: hackers@FreeBSD.ORG Subject: Re: cvsup.freebsd.org down for a few 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 am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Aug 1998 10:56:50 +0200 In-Reply-To: Chris Timmons's message of "Sat, 8 Aug 1998 06:02:44 -0700 (PDT)" Message-ID: Lines: 8 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 BAA04431 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Timmons writes: > ... site power outage. "Use the mirror, Luke" ;) 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 Aug 10 02:03:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05937 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 02:03:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05896 for ; Mon, 10 Aug 1998 02:03:29 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA04280 for ; Mon, 10 Aug 1998 02:03:05 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100903.CAA04280@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: can not fork... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 02:03:04 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Plenty of swap space: {hasty} swapinfo Device 512-blocks Used Avail Capacity Type /dev/sd0s1b 262144 94096 167792 36% Interleaved {hasty} sysctl kern.maxproc kern.maxproc: 500 {root} telnet rah Trying 209.133.7.234... Connected to rah.star-gate.com. Escape character is '^]'. FreeBSD (rah.star-gate.com) (ttyp3) login: hasty Password: Last login: Mon Aug 10 00:02:45 from 192.100.81.124 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 Justice, n.: A decision in your favor. {hasty} man vi Formatting page, please wait...Cannot fork Failed. Error executing formatting or display command. system command exited with status 512 Cannot fork Error executing formatting or display command. system command exited with status 512 No manual entry for vi {hasty} setenv DISPLAY :0.0 {hasty} man vi Formatting page, please wait...Cannot fork /usr/bin/groff:fatal error: fork: Resource temporarily unavailable Failed. Error executing formatting or display command. system command exited with status 512 Cannot fork /usr/bin/groff:fatal error: fork: Resource temporarily unavailable Error executing formatting or display command. system command exited with status 512 No manual entry for vi ============================ vmstat -m Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 69 187 48283 1280 0 32 273 9839 119520 640 4777 64 5020 1636 3806591 320 205 128 1312 14208 133289 160 12387 256 141 51 1856 80 0 512 4273 47 384705 40 318 1K 264 148 23053 20 862 2K 48 22 610 10 250 4K 14 2 3328 5 0 8K 9 10 367 5 199 16K 9 0 9 5 0 32K 1 0 2 5 0 128K 0 0 37 5 0 Memory usage type by bucket size Size Type(s) 16 shm, sysctl, soname, ether_multi, routetbl, pcb, proc, devbuf, DEVFS mount, temp 32 mkdir, freefile, dirrem, indirdep, freefrag, sysctl, diradd, bmsafemap, soname, in_multi, ether_multi, pgrp, subproc, routetbl, pcb, newblk, vnodes, ifaddr, devbuf, temp, kld 64 allocindir, shm, allocdirect, lockf, file, session, routetbl, pcb, pagedep, namecache, proc, ifaddr, devbuf, DEVFS name, temp 128 VM pgdata, freeblks, soname, zombie, file desc, routetbl, inodedep, namecache, vnodes, cred, ZONE, ttys, ifaddr, DEVFS node, temp 256 VM pgdata, Export Host, file desc, subproc, routetbl, newblk, NFS daemon, NFS srvsock, vnodes, proc, devbuf 512 VM pgdata, ioctlops, FFS node, UFS mount, BIO buffer, NFS daemon, devbuf, mount, temp 1K VM pgdata, BIO buffer, NQNFS Lease, devbuf, temp 2K VM pgdata, UFS mount, BIO buffer, pcb, ttys, devbuf, mbuf 4K VM pgdata, ioctlops, UFS mount, pagedep, devbuf, temp 8K indirdep, VM pgdata, MSDOSFS mount, devbuf, temp 16K UFS ihash, inodedep, NFS hash, ISOFS mount, devbuf 32K VM pgdata, namecache 128K VM pgdata Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mkdir 0 0K 9K 15768K 1748 0 0 32 freefile 0 0K 231K 15768K 11001 0 0 32 dirrem 0 0K 271K 15768K 11641 0 0 32 indirdep 0 0K 105K 15768K 626 0 0 32,8K allocindir 0 0K 28K 15768K 7986 0 0 64 freefrag 0 0K 9K 15768K 7109 0 0 32 shm 1 1K 1K 15768K 8 0 0 16,64 VM pgdata 568 137K 420K 15768K 1039 0 0 128,256,512,1K,2K,4K,8K,32K,128K sysctl 0 0K 1K 15768K 5020 0 0 16,32 allocdirect 1 1K 112K 15768K 27559 0 0 64 freeblks 1 1K 919K 15768K 11156 0 0 128 diradd 0 0K 71K 15768K 11777 0 0 32 bmsafemap 1 1K 2K 15768K 1907 0 0 32 lockf 2 1K 1K 15768K 12252 0 0 64 Export Host 2 1K 1K 15768K 2 0 0 256 soname 18 1K 1K 15768K 16495 0 0 16,32,128 in_multi 4 1K 1K 15768K 4 0 0 32 ether_multi 14 1K 1K 15768K 14 0 0 16,32 ioctlops 0 0K 4K 15768K 6 0 0 512,4K zombie 0 0K 1K 15768K 34000 0 0 128 file 204 13K 16K 15768K 2826917 0 0 64 session 27 2K 2K 15768K 1026 0 0 64 pgrp 35 2K 2K 15768K 1963 0 0 32 file desc 63 9K 10K 15768K 34069 0 0 128,256 subproc 73 6K 7K 15768K 35517 0 0 32,256 FFS node 4226 2113K 2144K 15768K 384515 0 0 512 UFS mount 15 29K 29K 15768K 15 0 0 512,2K,4K BIO buffer 282 309K 419K 15768K 13807 0 0 512,1K,2K routetbl 51 7K 14K 15768K 378 0 0 16,32,64,128,256 pcb 37 5K 5K 15768K 2774 0 0 16,32,64,2K UFS ihash 1 16K 16K 15768K 1 0 0 16K newblk 1 1K 1K 15768K 35546 0 0 32,256 inodedep 2 17K 1192K 15768K 41251 0 0 128,16K pagedep 1 4K 52K 15768K 2781 0 0 64,4K NQNFS Lease 1 1K 1K 15768K 1 0 0 1K NFS daemon 5 3K 3K 15768K 5 0 0 256,512 NFS srvsock 2 1K 1K 15768K 2 0 0 256 NFS hash 1 16K 16K 15768K 1 0 0 16K MSDOSFS mount 1 8K 8K 15768K 1 0 0 8K ISOFS mount 1 16K 16K 15768K 1 0 0 16K namecache 4493 313K 414K 15768K 934003 0 0 64,128,32K vnodes 56 7K 24K 15768K 1271 0 0 32,128,256 cred 22 3K 5K 15768K 4027 0 0 128 ZONE 17 3K 3K 15768K 17 0 0 128 proc 7 1K 1K 15768K 8 0 0 16,64,256 ttys 481 64K 64K 15768K 1339 0 0 128,2K ifaddr 17 2K 2K 15768K 17 0 0 32,64,128 devbuf 101 166K 166K 15768K 161 0 0 16,32,64,256,512,1K,2K,4K,8K,16K DEVFS mount 1 1K 1K 15768K 1 0 0 16 mount 7 4K 4K 15768K 7 0 0 512 DEVFS name 265 17K 17K 15768K 305 0 0 64 DEVFS node 243 31K 31K 15768K 283 0 0 128 mbuf 1 2K 2K 15768K 1 0 0 2K temp 80 6K 15K 15768K 38288 0 0 16,32,64,128,512,1K,4K,8K kld 1 1K 1K 15768K 1 0 0 32 Memory Totals: In Use Free Requests 3324K 2505K 4521650 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 03:07:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14462 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 03:07:03 -0700 (PDT) (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 DAA14441 for ; Mon, 10 Aug 1998 03:07:00 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id MAA02096; Mon, 10 Aug 1998 12:06:10 +0200 (MET DST) Date: Mon, 10 Aug 1998 12:06:08 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Peter van Heusden cc: Wilko Bulte , freebsd-hackers@FreeBSD.ORG Subject: Re: EXA 8200 tape drive on FreeBSD? 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 > So, its a slightly different model, maybe with an older firmware > (are firmware upgrades possible on these drives?) However, since it is a > similar model, I was wondering what you do to use a tape. The tape I'm > trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt > erase' before using the tape. Take a safe bet and use a 90m tape before anything else. I know that 160m tapes are aproblem in anything before the 8505XL drives and after that they were still not very reliable. The update of the EPROM involves opening it up and being able to burn an EPROM. I'll send you the web page of exabyte separately: http://www.exabyte.com/suppserv/techsupp/8mm/fullhigh/ Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 03:21:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16570 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 03:21:26 -0700 (PDT) (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 DAA16548 for ; Mon, 10 Aug 1998 03:21:21 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 18041 invoked by uid 1001); 10 Aug 1998 10:20:53 +0000 (GMT) To: hasty@rah.star-gate.com Cc: hackers@FreeBSD.ORG Subject: Re: can not fork... In-Reply-To: Your message of "Mon, 10 Aug 1998 02:03:04 -0700" References: <199808100903.CAA04280@rah.star-gate.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, 10 Aug 1998 12:20:53 +0200 Message-ID: <18039.902744453@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Plenty of swap space: > {hasty} swapinfo > Device 512-blocks Used Avail Capacity Type > /dev/sd0s1b 262144 94096 167792 36% Interleaved > {hasty} sysctl kern.maxproc > kern.maxproc: 500 You haven't given enough info - you could still be bumping against login.conf limits. I ended up having to increase maxproc-cur for the "root" and "default" entries quite a bit, on a 2.2.6 system. 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 Aug 10 03:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17886 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 03:28:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cam.grad.kiev.ua (grad-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17733 for ; Mon, 10 Aug 1998 03:27:58 -0700 (PDT) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (localhost [127.0.0.1]) by cam.grad.kiev.ua (8.8.8/8.8.5) with ESMTP id NAA13146; Mon, 10 Aug 1998 13:25:36 +0300 (EEST) Message-ID: <35CECA9E.F1FF8548@Shevchenko.Kiev.UA> Date: Mon, 10 Aug 1998 13:25:34 +0300 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: Amancio Hasty CC: hackers@FreeBSD.ORG Subject: Re: can not fork... References: <199808100903.CAA04280@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > .... > FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 > Justice, n.: > A decision in your favor. > {hasty} man vi > Formatting page, please wait...Cannot fork > Failed. > Error executing formatting or display command. > system command exited with status 512 > Cannot fork > login.conf what is you ulimit ? -- @= //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 Aug 10 08:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23097 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 08:47:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles176.castles.com [208.214.165.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23092 for ; Mon, 10 Aug 1998 08:47:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA12270; Mon, 10 Aug 1998 08:45:54 -0700 (PDT) Message-Id: <199808101545.IAA12270@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: hackers@FreeBSD.ORG Subject: Re: can not fork... In-reply-to: Your message of "Mon, 10 Aug 1998 02:03:04 PDT." <199808100903.CAA04280@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 08:45:54 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > {root} telnet rah > Trying 209.133.7.234... > Connected to rah.star-gate.com. > Escape character is '^]'. No problem forking for telnetd. > > FreeBSD (rah.star-gate.com) (ttyp3) > > login: hasty > Password: > Last login: Mon Aug 10 00:02:45 from 192.100.81.124 > Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 > The Regents of the University of California. All rights reserved. > > FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 No problem forking for login. > Justice, n.: > A decision in your favor. No problem forking for your shell, or fortune. > {hasty} man vi > Formatting page, please wait...Cannot fork No problem forking for man, but problems with the pager. At this point, 'limit' and 'ps x | wc -l' would be educational. > vmstat -m ... Nothing suspicious in here. -- \\ 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 Aug 10 09:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27648 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 09:26:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27587 for ; Mon, 10 Aug 1998 09:25:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA01769; Mon, 10 Aug 1998 09:25:29 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808101625.JAA01769@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: can not fork... In-reply-to: Your message of "Mon, 10 Aug 1998 08:45:54 PDT." <199808101545.IAA12270@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 09:25:29 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My old limits: {hasty} limit cputime unlimited filesize unlimited datasize 32768 kbytes stacksize 16384 kbytes coredumpsize unlimited memoryuse unlimited descriptors 256 memorylocked 20480 kbytes maxproc 32 {hasty} ps -x | wc -l 24 My new limits: {hasty} limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 49152 kbytes coredumpsize unlimited memoryuse unlimited descriptors 256 memorylocked 20480 kbytes maxproc 64 I just bumped up my login class xuser: xuser:\ :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ :cputime=4h:\ :datasize=64M:\ :stacksize=32M:\ :filesize=32M:\ :memoryuse=120M:\ :openfiles=256:\ :maxproc=64:\ :tc=standard: and increased maxusers to 64 in my kernel config file. I think what I will do next is decreased my limits and repeat the same experiment . I usually don't run much in my system USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND hasty 1703 0.0 0.0 404 280 p4 R+ 9:19AM 0:00.00 ps -xuaw root 1 0.0 0.0 496 180 ?? Is 7:18PM 0:00.13 /sbin/init -- root 2 0.0 0.0 0 0 ?? DL 7:18PM 0:00.05 (pagedaemon) root 3 0.0 0.0 0 0 ?? DL 7:18PM 0:00.00 (vmdaemon) root 4 0.0 0.0 0 0 ?? DL 7:18PM 0:01.95 (syncer) root 28 0.0 0.0 204 68 ?? Is 7:18PM 0:00.00 adjkerntz -i root 83 0.0 0.0 796 396 ?? Ss 2:18AM 0:00.25 syslogd root 89 0.0 0.0 1756 1292 ?? Is 2:18AM 0:00.46 named -b /etc/namedb/named.conf daemon 94 0.0 0.0 780 304 ?? Is 2:18AM 0:00.00 portmap root 102 0.0 0.0 460 228 ?? Is 2:18AM 0:00.00 mountd root 105 0.0 0.0 316 140 ?? Is 2:18AM 0:00.01 nfsd: master (nfsd) root 109 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server (nfsd) root 110 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server (nfsd) root 111 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server (nfsd) root 112 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server (nfsd) root 113 0.0 0.0 262944 316 ?? Is 2:18AM 0:00.00 rpc.statd root 128 0.0 0.0 836 380 ?? Is 2:18AM 0:00.13 inetd root 130 0.0 0.0 952 380 ?? Is 2:18AM 0:00.81 cron root 134 0.0 0.0 808 420 ?? Is 2:18AM 0:00.01 lpd root 137 0.0 0.0 1192 576 ?? Ss 2:18AM 0:00.28 sendmail: accepting connections on port 25 (sendmail) root 158 0.0 0.0 760 340 ?? Ss 2:18AM 0:01.89 moused -p /dev/mouse -t x10mouseremote msql 172 0.0 0.0 1048 464 con- I+ 2:18AM 0:01.54 /usr/local/bin/msql2d root 186 0.0 0.0 1296 640 ?? Is 2:18AM 0:00.00 /usr/local/sbin/smbd -D root 188 0.0 0.0 1160 684 ?? Ss 2:18AM 0:00.46 /usr/local/sbin/nmbd -D root 193 0.0 0.0 1152 576 ?? Is 2:18AM 0:00.74 /usr/local/sbin/sshd hasty 217 0.0 0.0 1360 940 v0 Is 2:18AM 0:00.13 -tcsh (tcsh) root 218 0.0 0.0 796 416 v1 Is+ 2:18AM 0:00.01 /usr/libexec/getty Pc ttyv1 root 219 0.0 0.0 796 416 v2 Is+ 2:18AM 0:00.01 /usr/libexec/getty Pc ttyv2 hasty 223 0.0 0.0 456 236 v0 I+ 2:18AM 0:00.02 /bin/csh /usr/local/bin/sx 16 hasty 224 0.0 0.0 1688 600 v0 I+ 2:18AM 0:00.02 /usr/X11R6/bin/xinit -- /usr/X11R6/bin/Xwrapper :0 -gamma 1.5 -bpp 16 root 225 0.0 0.0 14152 12384 ?? S 2:18AM 5:12.93 /usr/X11R6/bin/Xwrapper :0 -gamma 1.5 -bpp 16 (XF86_SVGA) hasty 228 0.0 0.0 492 156 v0 I 2:18AM 0:00.01 sh /home/hasty/.xinitrc hasty 229 0.0 0.0 2044 1148 v0 I 2:18AM 0:00.06 xconsole root 231 0.0 0.0 3052 2184 v0 S 2:18AM 0:02.64 xterm -e tcsh hasty 233 0.0 0.0 1720 984 v0 S 2:18AM 0:00.87 fvwm95-2 hasty 234 0.0 0.0 1376 440 v0 S 2:18AM 0:00.03 /usr/X11R6/lib/X11/fvwm95-2/FvwmAuto 9 6 .fvwm2rc95 0 8 300 hasty 237 0.0 0.0 1496 696 v0 S 2:18AM 0:00.08 /usr/X11R6/lib/X11/fvwm95-2//FvwmButtons 10 5 .fvwm2rc95 0 8 hasty 238 0.0 0.0 1564 776 v0 S 2:18AM 0:00.27 /usr/X11R6/lib/X11/fvwm95-2//FvwmTaskBar 12 5 .fvwm2rc95 0 8 hasty 240 0.0 0.0 2036 1172 v0 S 2:18AM 0:04.82 xclock hasty 241 0.0 0.0 500 160 v0 I 2:18AM 0:00.00 /bin/sh -c nice -16 xload -fg red -nolabel -bg grey60 -update 5 -geom hasty 242 0.0 0.0 2148 1292 v0 SN 2:18AM 0:01.10 xload hasty 243 0.0 0.0 1492 688 v0 S 2:18AM 0:00.11 /usr/X11R6/lib/X11/fvwm95-2//FvwmPager 14 5 .fvwm2rc95 0 8 0 0 hasty 244 0.0 0.0 1344 920 p0 Is 2:18AM 0:00.10 -csh (tcsh) hasty 246 0.0 0.0 32176 27064 p0 S 2:18AM 31:41.40 netscape hasty 247 0.0 0.0 13424 3084 p0 I 2:18AM 0:00.22 (dns helper) (netscape) hasty 263 0.0 0.0 920 512 p0 I+ 2:28AM 0:00.84 telnet rah root 264 0.0 0.0 864 456 ?? Is 2:28AM 0:00.62 telnetd hasty 265 0.0 0.0 1364 1008 p2 Is 2:28AM 0:00.22 -tcsh (tcsh) hasty 1041 0.0 0.0 8916 8380 v0 S 8:31AM 0:34.78 /usr/local/bin/wish8.0 -f /usr/local/bin/exmh hasty 1424 0.0 0.0 3828 2988 v0 I 8:32AM 0:01.00 /usr/local/bin/wish8.0 -f /usr/local/bin/exmh-bg exmh /usr/local/lib/ root 1686 0.0 0.0 2436 1748 v0 S 9:12AM 0:00.17 xterm hasty 1687 0.0 0.0 1348 976 p4 Ss 9:12AM 0:00.11 -tcsh (tcsh) hasty 1695 0.0 0.0 5444 4992 v0 S 9:14AM 0:00.26 ispell -a -S hasty 1699 0.0 0.0 820 556 p2 I+ 9:16AM 0:00.02 more -e /etc/login.conf root 0 0.0 0.0 0 0 ?? DLs 7:18PM 0:00.02 (swapper) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 09:56:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01179 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 09:56:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01103 for ; Mon, 10 Aug 1998 09:56:04 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA06870; Mon, 10 Aug 1998 09:55:37 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808101655.JAA06870@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: can not fork... In-reply-to: Your message of "Mon, 10 Aug 1998 08:45:54 PDT." <199808101545.IAA12270@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 09:55:37 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks Mike , I think it was a limit problem in my system. I can't seem to reproduce the problem after switching from the default login class to my modified "xuser" class. xuser:\ :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ :cputime=4h:\ :datasize=64M:\ :stacksize=32M:\ :filesize=32M:\ :memoryuse=120M:\ :openfiles=256:\ :maxproc=64:\ :tc=standard: Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 10:16:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03996 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 10:16:22 -0700 (PDT) (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 KAA03990 for ; Mon, 10 Aug 1998 10:16:21 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id KAA12031 for hackers@FreeBSD.ORG; Mon, 10 Aug 1998 10:14:24 -0700 (PDT) (envelope-from dhw) Date: Mon, 10 Aug 1998 10:14:24 -0700 (PDT) From: David Wolfskill Message-Id: <199808101714.KAA12031@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: CAP vs netatalk for Appletalk/printing support In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 7 Aug 1998 15:53:39 -0400 >From: Garance A Drosihn >I notice the ports collection includes both CAP and netatalk, and >that kernel changes have been made for netatalk to take advantage >of. I was wondering if most FreeBSD'ers prefer netatalk over CAP. Not sure about FreeBSDers, but I'll mention that a fairly large company I did some consulting sysadmin work for uses CAP for access to printers. (The company in question was moving its Mountain View Facility to downtown San Jose; I participated in part of that move near the beginning of my tenure there. They use *lots* of printers....) Thus, it's conceivable that keeping CAP functional would make FreeBSD more attractive to such a company than failing to keep it functional would. (During the time I was there, they did not make any use of FreeBSD that I know of; I mostly did Solaris 2 & SunOS administration, with the occasional IRIX, AIX, Digital UNIX, or HPUX system.) One datum, 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 Mon Aug 10 12:28:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20204 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 12:28:29 -0700 (PDT) (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 MAA20199 for ; Mon, 10 Aug 1998 12:28:27 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id PAA05095 for ; Mon, 10 Aug 1998 15:28:04 -0400 (EDT) Date: Mon, 10 Aug 1998 15:28:03 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Question about routine getblk() 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, getblk() tries to get a buffer with specified size of physical memory allocated to it. I got two questions about this routine: (1) The given size could be greater than the optimial size contained in the mount structure. The comment says "this happens on mount points". Why is the case? (2) If the buffer is in the core, we check for size inconsistancies. Why should this happen and why should we be conservative on metadata. Any help is appreciated. -------------------------------------------------- | 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 Aug 10 14:47:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05749 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 14:47:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05744 for ; Mon, 10 Aug 1998 14:47:12 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA23316; Mon, 10 Aug 1998 17:46:19 -0400 (EDT) (envelope-from luoqi) Date: Mon, 10 Aug 1998 17:46:19 -0400 (EDT) From: Luoqi Chen Message-Id: <199808102146.RAA23316@lor.watermarkgroup.com> To: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Question about routine getblk() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, getblk() tries to get a buffer with specified size > of physical memory allocated to it. I got two questions > about this routine: > > (1) The given size could be greater than the optimial size contained in > the mount structure. The comment says "this happens on mount points". > Why is the case? The size you were talking about was the block size of the file system, it is used to translate starting blkno to a vm offset. For a mount point covered by another file system, the correct block size should be coming from the fs that is covering this vnode, but vp->v_mount still points to the fs being covered, and block size for these two fs could be different. > > (2) If the buffer is in the core, we check for size inconsistancies. Why > should this happen and why should we be conservative on metadata. I'm not sure about this one. Maybe it happens when a frag is extended to a full block? > > Any help is appreciated. > > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 16:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13735 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 16:00:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13710; Mon, 10 Aug 1998 16:00:23 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id BAA13025; Tue, 11 Aug 1998 01:00:01 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id AAA01830; Tue, 11 Aug 1998 00:40:02 +0200 (CEST) X-Face: " Date: Tue, 11 Aug 1998 00:40:02 +0200 From: Stefan Esser To: Peter van Heusden , freebsd-hackers@FreeBSD.ORG Cc: Stefan Esser Subject: Re: EXA 8200 tape drive on FreeBSD? Mail-Followup-To: Peter van Heusden , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Peter van Heusden on Sun, Aug 09, 1998 at 05:32:27PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-09 17:32 +0200, Peter van Heusden wrote: > However, I cannot write to it at all - even after a 'mt erase', I get the > following: > > bash# mt rewind > bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 > dd: /dev/nrst0: Input/output error > 1+0 records in > 0+0 records out > 0 bytes transferred in 0.082043 secs (0 bytes/sec) > bash# Did you try shorter transfers (less than 64KB blocks) ? I seem to remember, that the EXABYTE 8200 was limited to less than 64KB per block (i.e. 63KB works, but 64KB doesn't). Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 16:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13788 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 16:00:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13763; Mon, 10 Aug 1998 16:00:42 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id BAA13041; Tue, 11 Aug 1998 01:00:03 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA01717; Mon, 10 Aug 1998 23:36:11 +0200 (CEST) X-Face: " Date: Mon, 10 Aug 1998 23:36:10 +0200 From: Stefan Esser To: Bill Paul , hackers@FreeBSD.ORG Cc: Stefan Esser Subject: Re: Yet another XL driver update Mail-Followup-To: Bill Paul , hackers@FreeBSD.ORG References: <199808092205.SAA21838@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808092205.SAA21838@skynet.ctr.columbia.edu>; from Bill Paul on Sun, Aug 09, 1998 at 06:05:12PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-09 18:05 -0400, Bill Paul wrote: > - I haven't yet been able to fix the problem with one particular > 3c900 COMBO card. This card appears to initialize correctly > but refuses to do DMA. The 3c900 card that I have works properly This could be due to the MASTER_ENABLE bit not being set in the PCI configuration space COMMAND register. The PCI code in 2.2.x used to set that bit whenever a port or memory map was registered, but the code in 3.0 doesn't, since the bus-master functionality should be enabled last. The PCI BIOS will often set the master enable bit, but may leave the board alone, on that particular system ... To check out that possibility, have the owner of that failing card do a "pciconf -r" of the COMMAND register and check bit 2 (value 4): it should be set to 1 to have DMA support enabled. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 16:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14120 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 16:02:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Altitude.CAM.ORG (Altitude.CAM.ORG [198.168.100.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14099; Mon, 10 Aug 1998 16:02:30 -0700 (PDT) (envelope-from intmktg@cam.org) Received: from cam.org (here@Dialup-614.HIP.CAM.ORG [199.84.45.109]) by Altitude.CAM.ORG (8.8.4/8.8.4) with ESMTP id TAA03547; Mon, 10 Aug 1998 19:02:07 -0400 (EDT) Message-ID: <35CF7AA0.208CBEBA@cam.org> Date: Mon, 10 Aug 1998 18:56:32 -0400 From: Marc Tardif X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG CC: freebsd-questions@FreeBSD.ORG Subject: semop syscall trouble 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 trying to use the semop(), but the program stalls right at that system call. I'm using 2.2.5 with SYSVSHM, SYSVSEM, SYSVMSG compiled in the kernel. Following is part of my code as well as the last couple lines from ktrace: dbms.c static void semcall(sid, op) int sid; int op; { struct sembuf sb; sb.sem_num = 0; sb.sem_op = op; sb.sem_flg = 0; if (semop(sid, &sb, 1) == -1) syserr("semop"); } ktrace.out 232 dbms CALL semsys(0x2,0x10001,0xefbfdc24,0x1,0) 232 dbms PSIG SIGINT SIG_DFL SIGINT SIG_DFL is obviously where I Ctrl-C to leave the stalled program. Any insight would be greatly appreciated. Thanks in advance, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 16:41:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20464 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 16:41:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from send101.yahoomail.com (send101.yahoomail.com [205.180.60.87]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA20459 for ; Mon, 10 Aug 1998 16:41:24 -0700 (PDT) (envelope-from lc001@yahoo.com) Message-ID: <19980810234032.23291.rocketmail@send101.yahoomail.com> Received: from [139.87.242.56] by send101.yahoomail.com; Mon, 10 Aug 1998 16:40:32 PDT Date: Mon, 10 Aug 1998 16:40:32 -0700 (PDT) From: "L.C." Subject: Does FreeBSD support not symmetrical processors? 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 If not, which UNIX systems may support? Thanks, L.C. _________________________________________________________ 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 Mon Aug 10 17:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29727 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 17:36:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29627; Mon, 10 Aug 1998 17:35:52 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-52.HiWAAY.net [208.147.148.52]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id TAA15472; Mon, 10 Aug 1998 19:35:28 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA00818; Mon, 10 Aug 1998 19:35:25 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199808110035.TAA00818@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Esser cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: EXA 8200 tape drive on FreeBSD? In-reply-to: Message from Stefan Esser of "Tue, 11 Aug 1998 00:40:02 +0200." <19980811004002.C1778@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 19:35:25 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Esser writes: > On 1998-08-09 17:32 +0200, Peter van Heusden w > rote: > > However, I cannot write to it at all - even after a 'mt erase', I get the > > following: > > > > bash# mt rewind > > bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 > > dd: /dev/nrst0: Input/output error > > 1+0 records in > > 0+0 records out > > 0 bytes transferred in 0.082043 secs (0 bytes/sec) > > bash# > > Did you try shorter transfers (less than 64KB blocks) ? > > I seem to remember, that the EXABYTE 8200 was limited to > less than 64KB per block (i.e. 63KB works, but 64KB doesn't). "bs=64" spells out 64 byte blocks, not 64k. "bs=64k" would be 64k. There might be a problem with the block being too small. :-) SGI Irix defaults to 128k blocks on Exabyte 8mm drives, including the 8200. Its FreeBSD that won't (can't) do more than 64k. As others have mentioned, when a new (new to you) Exabyte drive acts flaky its time to flash the EEPROMs or burn new EPROMs for the old 8200. I too have a new-to-me 8200 that ID's, rewinds, retensions, ejects, and all that good stuff. But doesn't work. If new EPROMs don't fix it, then its junk. That too is standard failure mode for an Exabyte. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 17:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29956 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 17:37:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA29945; Mon, 10 Aug 1998 17:37:28 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA23576; Mon, 10 Aug 1998 20:40:13 -0400 From: Bill Paul Message-Id: <199808110040.UAA23576@skynet.ctr.columbia.edu> Subject: Re: Yet another XL driver update To: se@FreeBSD.ORG (Stefan Esser) Date: Mon, 10 Aug 1998 20:40:12 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <19980810233610.A1555@mi.uni-koeln.de> from "Stefan Esser" at Aug 10, 98 11:36:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Stefan Esser had to walk into mine and say: > On 1998-08-09 18:05 -0400, Bill Paul wrote: > > - I haven't yet been able to fix the problem with one particular > > 3c900 COMBO card. This card appears to initialize correctly > > but refuses to do DMA. The 3c900 card that I have works properly > > This could be due to the MASTER_ENABLE bit not being > set in the PCI configuration space COMMAND register. > The PCI code in 2.2.x used to set that bit whenever > a port or memory map was registered, but the code in > 3.0 doesn't, since the bus-master functionality should > be enabled last. The PCI BIOS will often set the master > enable bit, but may leave the board alone, on that > particular system ... > > To check out that possibility, have the owner of that > failing card do a "pciconf -r" of the COMMAND register > and check bit 2 (value 4): it should be set to 1 to > have DMA support enabled. I thought about that; the xl_attach() routine explicitly sets the bus master enable, port enable and memory map enable bits in the PCI command register, and checks to make sure they were turned on successfully, otherwise it prints an error. The card is this guy: pci0:14:0: class=0x020000 card=0x00000000 chip=0x900110b7 rev=0x00 hdr=0x00 The PCI command register should be at offset 4 according to /sys/pci/pcireg.h. pciconf says: snarf# pciconf -r pci0:14:0 4 0x02000107 Looks like everything's turned on to me. This is really a case of "nothing's wrong, but nothing works." I can't find anything in the diag or status registers to indicate why DMA might not be working. This machine has two other bus master ethernet adapters in it, a 3c905B and a ThunderLAN-based card, and both of those seem to be doing DMA correctly. My understanding, which is somewhat limited, is that you can have both PCI bus master and PCI slave slots in a machine; a card that has to do bus master DMA must be placed in a bus master slot in order to work correctly. At first I thought that maybe the user had put the card in a slave slot, but he swears to me that the 3c905B card worked perfectly in the same slot earlier. Like I said, I'm tempted to blame this on a defective card. I've gotten one other report today on a 3c900-TP and 3c900-COMBO that both seem to work fine. It's just very curious because the card will work with the vx driver, which is only different in this case in that it doesn't use the DMA packet transfer mechanism. The engineer in me is having a hard time figuring out how just that one part of the adapter could fail, particularly when the DMA engine is inside the ASIC along with the transmit and receive circuitry and other pieces that that seem to be working fine. I usually think of a chip failure as something that would wipe out the whole ASIC, not just part of it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 18:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12045 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 18:59:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12038 for ; Mon, 10 Aug 1998 18:59:44 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.1/8.9.0) id UAA17242; Mon, 10 Aug 1998 20:59:11 -0500 (CDT) To: hackers@FreeBSD.ORG Subject: Re: can not fork... References: <199808101655.JAA06870@rah.star-gate.com> From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 10 Aug 1998 20:59:11 -0500 In-Reply-To: Amancio Hasty's message of "Mon, 10 Aug 1998 09:55:37 -0700" Message-ID: <87soj45le8.fsf@couatl.uchicago.edu> Lines: 13 X-Mailer: Gnus v5.6.22/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty writes: > Tnks Mike , I think it was a limit problem in my system. I can't How about the standard login.conf have only an entry that is unlimited (or root and default, both unlimited or whatever), and then comments on how to introduce the limits so the people who need this feature can add it easily and the people who don't never need to know about it? -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 20:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22474 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 20:26:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from brooklyn.slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22464 for ; Mon, 10 Aug 1998 20:26:50 -0700 (PDT) (envelope-from pfm@brooklyn.slack.net) Received: from localhost (pfm@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id XAA25114; Mon, 10 Aug 1998 23:33:52 -0400 (EDT) Date: Mon, 10 Aug 1998 23:33:52 -0400 (EDT) From: Patrick McAndrew To: Greg Lehey cc: John Baldwin , FreeBSD Hackers , John Baldwin , dg@root.com Subject: Re: AMD-specific kernel code (was: How long a wait?) In-Reply-To: <19980810123341.X11095@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 Mon, 10 Aug 1998, Greg Lehey wrote: > On Sunday, 9 August 1998 at 23:00:24 -0400, John Baldwin wrote: > >>> I just looked at the patch. Other than some KNF style bugs, it seems > >>> okay. > >>> I don't have any AMD K5/K6 machines, however, so I can't test it and won't > >>> be committing it. I missed the first part of this thread, is this patch for AMD K6 processors (does it utilitze their RISC core (or whatever it is))? Where can i get info and the patch? How stable is it? ================================================== Patrick McAndrew, Nashua, NH pfm@slack.net CES, Inc. XNS, Inc. FreeBSD, NetBSD, Unixware 7, Solaris 2.5 "I'd change the world, but I don't have the source code" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 10 20:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24741 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 20:39:52 -0700 (PDT) (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 UAA24735 for ; Mon, 10 Aug 1998 20:39:49 -0700 (PDT) (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 NAA12355; Tue, 11 Aug 1998 13:09:13 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA21297; Tue, 11 Aug 1998 13:09:11 +0930 (CST) Message-ID: <19980811130910.Q20188@freebie.lemis.com> Date: Tue, 11 Aug 1998 13:09:10 +0930 From: Greg Lehey To: Patrick McAndrew Cc: John Baldwin , FreeBSD Hackers , John Baldwin , dg@root.com Subject: Re: AMD-specific kernel code (was: How long a wait?) References: <19980810123341.X11095@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Patrick McAndrew on Mon, Aug 10, 1998 at 11:33:52PM -0400 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, 10 August 1998 at 23:33:52 -0400, Patrick McAndrew wrote: > On Mon, 10 Aug 1998, Greg Lehey wrote: > >> On Sunday, 9 August 1998 at 23:00:24 -0400, John Baldwin wrote: >>>>> I just looked at the patch. Other than some KNF style bugs, it seems >>>>> okay. >>>>> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >>>>> be committing it. > > I missed the first part of this thread, is this patch for AMD K6 > processors (does it utilitze their RISC core (or whatever it is))? It's a relatively small patch which enables write allocation. This is a modified way of handling pending writes when the cache line is not in L1 cachec: instead of a normal write cycle, it performs a burst read cycle of 32 bytes into L1 cache, and merges the write data into the cache. This wins when there are lots of local references, and loses when there are not (because reading the cache line takes longer than most writes). > Where can i get info and the patch? Info is in an AMD application note: http://www.amd.com/K6/k6docs/pdf/21326d.pdf. The patches are at ftp://ftp.lemis.com/pub/AMD-write-allocate-patch. > How stable is it? I've been running it for two days. It just sets a processor register according to the documentation, so I don't see much room for instability. The only question is, is it worth it? I found about a 5% degradation in performance when building a world. Others have claimed 15% improvement in web servers. Given the nature of the fix (which has to be enabled via the kernel option CPU_AMD_WT_ALLOC), there's no conflict in that. I'm thinking of finding a way to enable it on the fly. I'd be very interested to hear how other people fare with it. Greg -- See complete headers for address 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 Mon Aug 10 21:16:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01161 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 21:16:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01120 for ; Mon, 10 Aug 1998 21:15:59 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-97.HiWAAY.net [208.147.148.97]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id XAA26025; Mon, 10 Aug 1998 23:15:34 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA00917; Mon, 10 Aug 1998 19:42:33 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199808110042.TAA00917@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "L.C." cc: hackers@FreeBSD.ORG From: David Kelly Subject: Re: Does FreeBSD support not symmetrical processors? In-reply-to: Message from "L.C." of "Mon, 10 Aug 1998 16:40:32 PDT." <19980810234032.23291.rocketmail@send101.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 19:42:33 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "L.C." writes: > If not, which UNIX systems may support? SGI does some flavor of NUMA. Start at http://www.sgi.com/. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 02:50:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08122 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 02:50:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sliphost37.uni-trier.de (rzppp-055.uni-trier.de [136.199.4.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08104 for ; Tue, 11 Aug 1998 02:50:44 -0700 (PDT) (envelope-from blank@sliphost37.uni-trier.de) Received: (from blank@localhost) by blank.uni-trier.de (8.9.1/8.9.1) id LAA00298 for hackers@freebsd.org; Tue, 11 Aug 1998 11:48:15 +0200 (CEST) (envelope-from blank) Message-ID: <19980811114815.A292@uni-trier.de> Date: Tue, 11 Aug 1998 11:48:15 +0200 From: Sascha Blank To: hackers@FreeBSD.ORG Subject: No more CTM ports-cur deltas? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-PGP-Fingerprint: 26 FD 71 B5 48 12 42 91 10 1C 4F 74 70 48 6F 89 X-Operating-System: FreeBSD 3.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, it looks like the CTM delta production for "ports-cur" has silently stopped on August 8th with #2443. Since then neither my private mailbox nor ctm.freebsd.org have received any further ports-cur deltas. Whoever is currently responsible for CTM may please have a look at it. -- Sascha Blank | FreeBSD - Student and System Administrator | that's where you want to go today! at the University of Trier, Germany | mailto:blank@fox.uni-trier.de | See http://www.freebsd.org for details To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 05:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23438 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 05:20:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thanatos.clara.net (thanatos.clara.net [195.8.69.60]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA23429 for ; Tue, 11 Aug 1998 05:20:50 -0700 (PDT) (envelope-from "[name]"@pcp.clara.net) Received: (qmail 20182 invoked from network); 11 Aug 1998 12:20:21 -0000 Received: from du-029-0313.claranet.co.uk (HELO atlantis.mail) (195.8.88.59) by mail.clara.net with SMTP; 11 Aug 1998 12:20:21 -0000 To: hackers@FreeBSD.ORG Message-Id: <980811132115.n0002911.pcp@mail.clara.net> References: <199808102147.OAA05756@hub.freebsd.org> From: Mark Chapman <[name]@pcp.clara.net> Reply-To: Mark Chapman Organization: Paul Chapman Partnership Subject: Re: freebsd-hackers-digest V4 #215 X-Mailer: atlantis mail 32 Date: Tue, 11 Aug 98 13:21:15 GMT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please please stop sending me these I don't want them any more!!!. > >freebsd-hackers-digest Monday, August 10 1998 Volume 04 : Number 215 > > > >In this issue: >Re: EXA 8200 tape drive on FreeBSD? >NPX configuration after exec() >Re: C and static initialization with unions >Yet another XL driver update >Boot code >RE: AMD-specific kernel code (was: How long a wait?) >Re: AMD-specific kernel code (was: How long a wait?) >Re: EXA 8200 tape drive on FreeBSD? >Re: Does this mean we have another breakin? >Re: cvsup.freebsd.org down for a few >can not fork... >Re: EXA 8200 tape drive on FreeBSD? >Re: can not fork... >Re: can not fork... >Re: can not fork... >Re: can not fork... >Re: can not fork... >Re: CAP vs netatalk for Appletalk/printing support >Question about routine getblk() >Re: Question about routine getblk() > >---------------------------------------------------------------------- > >Date: Sun, 9 Aug 1998 20:17:46 +0200 (CEST) >From: Wilko Bulte >Subject: Re: EXA 8200 tape drive on FreeBSD? > >As Peter van Heusden wrote... > >> I'm trying to get a EXA 8200 tape drive working on FreeBSD. It is detected >> fine by the kernel during startup, and I can do a 'mt status' on it, with >> the following results: >> >> Present Mode: Density = 0x00 Blocksize variable >> ---------available modes--------- >> Mode 0: Density = 0x00 Blocksize variable >> Mode 1: Density = X3.136-1986 Blocksize = 512 bytes >> Mode 2: Density = X3.39-1986 Blocksize variable >> Mode 3: Density = X3.54-1986 Blocksize variable >> >> However, I cannot write to it at all - even after a 'mt erase', I get the >> following: >> > >[del] > >> My system details are as follows: >> >> OS: FreeBSD 2.2.6 >> System: 486 DX 4 120, NCR 53c810 SCSI controller (with 3 disk drives - >> Conner CFP1080S, Seagate ST12400N and ST32155N as well as the tape drive >> - disks are on ids 0, 1, 4, tape is on 6), >> 24 mb RAM. > >> Is there anything else I can try to get this thing working, or should I >> just give up on it? > >Well, not that it solves your problem, but I also have a 8200 on a ncr810 >and that one works. Has done so for years. > >More specific it has firmware: > >Aug 7 22:17:20 yedi /kernel: (ncr1:3:0): "EXABYTE EXB-8200 2687" type 1 >removable SCSI 1 > >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 > >------------------------------ > >Date: Mon, 10 Aug 1998 07:00:37 +1000 >From: Peter Jeremy >Subject: NPX configuration after exec() > >The NPX (x87) is initialised with a configuration word of 0x1272 >(sys/i386/include/npx.h __BDE_NPXCW__). The comment associated with >this states: > * Later I will want the IEEE default of all exceptions masked. See the > * 0.0 math manpage for why this is better. The 0.1 math manpage is empty. > >Whilst I'm uncertain of the references to 0.0 and 0.1, math(3M) does >include some comments which imply that libm is designed to function >correctly with all exceptions masked. > >Are there any plans to change the configuration word to 0x127f as implied >in this comment? > >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 > >------------------------------ > >Date: Sun, 9 Aug 1998 22:00:22 +0000 (GMT) >From: Terry Lambert >Subject: Re: C and static initialization with unions > >> I've had (several) run-ins with const poisoning trying to port a large >> third-party codebase. It's sufficiently bogus to require -traditional >> to build, and I expect not too novel in that regard. > >I have a number of programs which I like to use, but which I do not >want to become the maintainer of (for one thing, I don't have a >huge FTP server and can't offer cvsup, etc.). > >These programs do things like modify declared strings (on the assumption >that they will be stored in data section, not code section, what with >them being data, and all...). > >They also do things like modify variables in signal handlers and in >subfunctions of functions that also use the variable. Without the >- -traditional flag, this would require the use of the "volatile" >keyword. > >Other examples exist, including the use of int arguments to >implement varaddic functions, and casting to char * instead >of void * for opaque conversion. > >Sure, it's be nice if there were three of me (;-)) and I could >do all this and the stuff that I want to do as well, but there >aren't, and I can't. > > >> If we support compilation of K&R application code, we should attempt to >> make sure that system headers function correctly in that regard. > >Yes, please. > > > 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 > >------------------------------ > >Date: Sun, 9 Aug 1998 18:05:12 -0400 (EDT) >From: Bill Paul >Subject: Yet another XL driver update > >Today I put yet another update of the 3Com Etherlink XL driver at >www.freebsd.org/~wpaul/3Com. This version has changes to fix support >for 100baseT4 cards and fixes a small bug in the TX error recovery. > >I'm hoping to commit the 3.0 driver to -current by the end of next >week, but I'm still concerned that there may be problems in some >configurations. I've have a couple people report problems with >performance but lack of followups has made it hard to me to know >if these problems are still present. I'm interested mainly in the >following: > >- - I have received some reports of spotty transmission performance > or 'transmission error' messages. I made a mistake in the code > that tries to recover from some of these errors (I wasn't resetting > the upload list pointer correctly) which should be fixed now. > I'm interested to know if transmission problems persist, > particularly with 10Mbps links on slow machines. This applies > to all supported cards (3c900, 905 and 905B). > >- - I haven't yet been able to fix the problem with one particular > 3c900 COMBO card. This card appears to initialize correctly > but refuses to do DMA. The 3c900 card that I have works properly > and I haven't been able to remotely debug the problem. If you > have a 3c900 card that probes correctly but doesn't appear to > transmit and receive, and which does work corretly with the > vx driver (which doesn't use DMA), then I'd like to know. > Without any other evidence, I'm nearly convinced that this is > a hardware problem with this one card. > >If you have a problem, please let me know. Tell me the type of >system you're using, the type of card you have, the version of FreeBSD, >and a _DETAILED_ description of the problem, along with a way to >reproduce the failure, if at all possible. > >- -Bill > >- -- >============================================================================= >- -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu >Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" >============================================================================= > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Sun, 9 Aug 1998 18:36:54 -0500 (CDT) >From: Joel Ray Holveck >Subject: Boot code > >From /sys/i386/boot/biosboot/boot.c: > > /* > * Be paranoid and make doubly sure that the input buffer is empty. > */ > if (loadflags & (RB_DUAL | RB_SERIAL)) > init_serial(); > >Is this worth the bytes? (The only thing that would have frobbed >loadflags at this point is getbootdev, and it calls init_serial() if >it sets either flag. This is what I see, but more eyes checking me >would be welcome.) > >Are we even concerned about saving bytes in boot2, or is that no >longer a concern? While I'm at it, the stack is reset when the kernel >is loaded, so I don't need to worry about adding variables to boot(), >do I? > >While I'm at it, I'm adding code to allow all flags to be specified in >boot.config. The idea is that if flags are specified from the >keyboard, they override everything (except RB_SERIAL, RB_DUAL, and >RB_PROBEKBD) from boot.config. Anybody have a problem with this? > >Happy hacking, >joelh > >- -- >Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > 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 > >------------------------------ > >Date: Sun, 09 Aug 1998 23:00:24 -0400 (EDT) >From: John Baldwin >Subject: RE: AMD-specific kernel code (was: How long a wait?) > >On 08-Aug-98 Greg Lehey wrote: >> (following up to -hackers) >> >> On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >>> >>> I just looked at the patch. Other than some KNF style bugs, it seems >>> okay. >>> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >>> be committing it. >>> If it could get wider circulation - perhaps by posting a note to hackers >>> asking for testers, then I think there would be less hesitation in getting >>> it committed. >> >> I've grabbed the code and will try it out and report. >> >> Greg > >One note, I just found out that this will only work on on certain chipsets (I >think Intel Triton TX, but I could be wrong, so don't quote me on that.) > >John Baldwin >- -- jobaldwi@vt.edu -- jbaldwin@freedomnet.com -- > ---- http://www.freedomnet.com/~jbaldwin/ ---- >"I waited for the Lord on high/I waited and He heard my cry." - Petra > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Mon, 10 Aug 1998 12:33:41 +0930 >From: Greg Lehey >Subject: Re: AMD-specific kernel code (was: How long a wait?) > >On Sunday, 9 August 1998 at 23:00:24 -0400, John Baldwin wrote: >> On 08-Aug-98 Greg Lehey wrote: >>> (following up to -hackers) >>> On Thursday, 6 August 1998 at 23:44:39 -0700, David Greenman wrote: >>>> >>>> I just looked at the patch. Other than some KNF style bugs, it seems >>>> okay. >>>> I don't have any AMD K5/K6 machines, however, so I can't test it and won't >>>> be committing it. >>>> If it could get wider circulation - perhaps by posting a note to hackers >>>> asking for testers, then I think there would be less hesitation in getting >>>> it committed. >>> >>> I've grabbed the code and will try it out and report. >> >> One note, I just found out that this will only work on on certain chipsets (I >> think Intel Triton TX, but I could be wrong, so don't quote me on that.) > >As the title indicates, this specific tweak only works on AMD K5 >stepping 4 and above, and all AMD K6s. > >I've posted a followup. > >Greg >- -- >See complete headers for address 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 > >------------------------------ > >Date: Mon, 10 Aug 1998 10:18:00 +0200 (SAT) >From: Peter van Heusden >Subject: Re: EXA 8200 tape drive on FreeBSD? > >On Sun, 9 Aug 1998, Wilko Bulte wrote: > >> >> Well, not that it solves your problem, but I also have a 8200 on a ncr810 >> and that one works. Has done so for years. >> >> More specific it has firmware: >> >> Aug 7 22:17:20 yedi /kernel: (ncr1:3:0): "EXABYTE EXB-8200 2687" type 1 >> removable SCSI 1 > >Thanks for the info. Mine gives a slightly different dmesg output: > >(ncr0:6:0): "EXABYTE EXB-8200 253G" type 1 removable SCSI 1 > >So, its a slightly different model, maybe with an older firmware >(are firmware upgrades possible on these drives?) However, since it is a >similar model, I was wondering what you do to use a tape. The tape I'm >trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt >erase' before using the tape. > >Peter >- -- >Peter van Heusden | Its the 90's, and collective action is STILL cool! >pvh@leftside.wcape.school.za | Get active in your union today! > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: 10 Aug 1998 10:55:18 +0200 >From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) >Subject: Re: Does this mean we have another breakin? > >"Matthew D. Fuller" writes: >> On sendmail on one machine (sendmail -q run out of cron) and on > >Why do you do that? Doesn't 'sendmail -bd -qxx' do the job? > >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 > >------------------------------ > >Date: 10 Aug 1998 10:56:50 +0200 >From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) >Subject: Re: cvsup.freebsd.org down for a few > >Chris Timmons writes: >> ... site power outage. > >"Use the mirror, Luke" ;) > >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 > >------------------------------ > >Date: Mon, 10 Aug 1998 02:03:04 -0700 >From: Amancio Hasty >Subject: can not fork... > >Plenty of swap space: >{hasty} swapinfo >Device 512-blocks Used Avail Capacity Type >/dev/sd0s1b 262144 94096 167792 36% Interleaved >{hasty} sysctl kern.maxproc >kern.maxproc: 500 > > >{root} telnet rah >Trying 209.133.7.234... >Connected to rah.star-gate.com. >Escape character is '^]'. > >FreeBSD (rah.star-gate.com) (ttyp3) > >login: hasty >Password: >Last login: Mon Aug 10 00:02:45 from 192.100.81.124 >Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 > The Regents of the University of California. All rights reserved. > >FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 >Justice, n.: > A decision in your favor. >{hasty} man vi >Formatting page, please wait...Cannot fork >Failed. >Error executing formatting or display command. >system command exited with status 512 >Cannot fork >Error executing formatting or display command. >system command exited with status 512 >No manual entry for vi >{hasty} setenv DISPLAY :0.0 >{hasty} man vi >Formatting page, please wait...Cannot fork >/usr/bin/groff:fatal error: fork: Resource temporarily unavailable >Failed. >Error executing formatting or display command. >system command exited with status 512 >Cannot fork >/usr/bin/groff:fatal error: fork: Resource temporarily unavailable >Error executing formatting or display command. >system command exited with status 512 >No manual entry for vi > >============================ > >vmstat -m >Memory statistics by bucket size >Size In Use Free Requests HighWater Couldfree > 16 69 187 48283 1280 0 > 32 273 9839 119520 640 4777 > 64 5020 1636 3806591 320 205 > 128 1312 14208 133289 160 12387 > 256 141 51 1856 80 0 > 512 4273 47 384705 40 318 > 1K 264 148 23053 20 862 > 2K 48 22 610 10 250 > 4K 14 2 3328 5 0 > 8K 9 10 367 5 199 > 16K 9 0 9 5 0 > 32K 1 0 2 5 0 >128K 0 0 37 5 0 > >Memory usage type by bucket size >Size Type(s) > 16 shm, sysctl, soname, ether_multi, routetbl, pcb, proc, devbuf, > DEVFS mount, temp > 32 mkdir, freefile, dirrem, indirdep, freefrag, sysctl, diradd, > bmsafemap, soname, in_multi, ether_multi, pgrp, subproc, routetbl, > pcb, newblk, vnodes, ifaddr, devbuf, temp, kld > 64 allocindir, shm, allocdirect, lockf, file, session, routetbl, pcb, > pagedep, namecache, proc, ifaddr, devbuf, DEVFS name, temp > 128 VM pgdata, freeblks, soname, zombie, file desc, routetbl, inodedep, > namecache, vnodes, cred, ZONE, ttys, ifaddr, DEVFS node, temp > 256 VM pgdata, Export Host, file desc, subproc, routetbl, newblk, > NFS daemon, NFS srvsock, vnodes, proc, devbuf > 512 VM pgdata, ioctlops, FFS node, UFS mount, BIO buffer, NFS daemon, > devbuf, mount, temp > 1K VM pgdata, BIO buffer, NQNFS Lease, devbuf, temp > 2K VM pgdata, UFS mount, BIO buffer, pcb, ttys, devbuf, mbuf > 4K VM pgdata, ioctlops, UFS mount, pagedep, devbuf, temp > 8K indirdep, VM pgdata, MSDOSFS mount, devbuf, temp > 16K UFS ihash, inodedep, NFS hash, ISOFS mount, devbuf > 32K VM pgdata, namecache >128K VM pgdata > >Memory statistics by type Type Kern > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > mkdir 0 0K 9K 15768K 1748 0 0 32 > freefile 0 0K 231K 15768K 11001 0 0 32 > dirrem 0 0K 271K 15768K 11641 0 0 32 > indirdep 0 0K 105K 15768K 626 0 0 32,8K > allocindir 0 0K 28K 15768K 7986 0 0 64 > freefrag 0 0K 9K 15768K 7109 0 0 32 > shm 1 1K 1K 15768K 8 0 0 16,64 > VM pgdata 568 137K 420K 15768K 1039 0 0 >128,256,512,1K,2K,4K,8K,32K,128K > sysctl 0 0K 1K 15768K 5020 0 0 16,32 > allocdirect 1 1K 112K 15768K 27559 0 0 64 > freeblks 1 1K 919K 15768K 11156 0 0 128 > diradd 0 0K 71K 15768K 11777 0 0 32 > bmsafemap 1 1K 2K 15768K 1907 0 0 32 > lockf 2 1K 1K 15768K 12252 0 0 64 > Export Host 2 1K 1K 15768K 2 0 0 256 > soname 18 1K 1K 15768K 16495 0 0 16,32,128 > in_multi 4 1K 1K 15768K 4 0 0 32 > ether_multi 14 1K 1K 15768K 14 0 0 16,32 > ioctlops 0 0K 4K 15768K 6 0 0 512,4K > zombie 0 0K 1K 15768K 34000 0 0 128 > file 204 13K 16K 15768K 2826917 0 0 64 > session 27 2K 2K 15768K 1026 0 0 64 > pgrp 35 2K 2K 15768K 1963 0 0 32 > file desc 63 9K 10K 15768K 34069 0 0 128,256 > subproc 73 6K 7K 15768K 35517 0 0 32,256 > FFS node 4226 2113K 2144K 15768K 384515 0 0 512 > UFS mount 15 29K 29K 15768K 15 0 0 512,2K,4K > BIO buffer 282 309K 419K 15768K 13807 0 0 512,1K,2K > routetbl 51 7K 14K 15768K 378 0 0 16,32,64,128,256 > pcb 37 5K 5K 15768K 2774 0 0 16,32,64,2K > UFS ihash 1 16K 16K 15768K 1 0 0 16K > newblk 1 1K 1K 15768K 35546 0 0 32,256 > inodedep 2 17K 1192K 15768K 41251 0 0 128,16K > pagedep 1 4K 52K 15768K 2781 0 0 64,4K > NQNFS Lease 1 1K 1K 15768K 1 0 0 1K > NFS daemon 5 3K 3K 15768K 5 0 0 256,512 > NFS srvsock 2 1K 1K 15768K 2 0 0 256 > NFS hash 1 16K 16K 15768K 1 0 0 16K >MSDOSFS mount 1 8K 8K 15768K 1 0 0 8K > ISOFS mount 1 16K 16K 15768K 1 0 0 16K > namecache 4493 313K 414K 15768K 934003 0 0 64,128,32K > vnodes 56 7K 24K 15768K 1271 0 0 32,128,256 > cred 22 3K 5K 15768K 4027 0 0 128 > ZONE 17 3K 3K 15768K 17 0 0 128 > proc 7 1K 1K 15768K 8 0 0 16,64,256 > ttys 481 64K 64K 15768K 1339 0 0 128,2K > ifaddr 17 2K 2K 15768K 17 0 0 32,64,128 > devbuf 101 166K 166K 15768K 161 0 0 >16,32,64,256,512,1K,2K,4K,8K,16K > DEVFS mount 1 1K 1K 15768K 1 0 0 16 > mount 7 4K 4K 15768K 7 0 0 512 > DEVFS name 265 17K 17K 15768K 305 0 0 64 > DEVFS node 243 31K 31K 15768K 283 0 0 128 > mbuf 1 2K 2K 15768K 1 0 0 2K > temp 80 6K 15K 15768K 38288 0 0 >16,32,64,128,512,1K,4K,8K > kld 1 1K 1K 15768K 1 0 0 32 > >Memory Totals: In Use Free Requests > 3324K 2505K 4521650 > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Mon, 10 Aug 1998 12:06:08 +0200 (MET DST) >From: Nick Hibma >Subject: Re: EXA 8200 tape drive on FreeBSD? > > > So, its a slightly different model, maybe with an older firmware > > (are firmware upgrades possible on these drives?) However, since it is a > > similar model, I was wondering what you do to use a tape. The tape I'm > > trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt > > erase' before using the tape. > >Take a safe bet and use a 90m tape before anything else. I know that >160m tapes are aproblem in anything before the 8505XL drives and after >that they were still not very reliable. > >The update of the EPROM involves opening it up and being able to burn an >EPROM. > >I'll send you the web page of exabyte separately: > > http://www.exabyte.com/suppserv/techsupp/8mm/fullhigh/ >Nick > > >- -- >building: 27A >address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy >tel.: +39 332 78 9549 >fax.: +39 332 78 9185 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Mon, 10 Aug 1998 12:20:53 +0200 >From: sthaug@nethelp.no >Subject: Re: can not fork... > >> Plenty of swap space: >> {hasty} swapinfo >> Device 512-blocks Used Avail Capacity Type >> /dev/sd0s1b 262144 94096 167792 36% Interleaved >> {hasty} sysctl kern.maxproc >> kern.maxproc: 500 > >You haven't given enough info - you could still be bumping against >login.conf limits. > >I ended up having to increase maxproc-cur for the "root" and "default" >entries quite a bit, on a 2.2.6 system. > >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 > >------------------------------ > >Date: Mon, 10 Aug 1998 13:25:34 +0300 >From: Ruslan Shevchenko >Subject: Re: can not fork... > >Amancio Hasty wrote: >> >> .... >> FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 >> Justice, n.: >> A decision in your favor. >> {hasty} man vi >> Formatting page, please wait...Cannot fork >> Failed. >> Error executing formatting or display command. >> system command exited with status 512 >> Cannot fork >> > > login.conf > > what is you ulimit ? > > >- -- > @= > //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 > >------------------------------ > >Date: Mon, 10 Aug 1998 08:45:54 -0700 >From: Mike Smith >Subject: Re: can not fork... > >> >> {root} telnet rah >> Trying 209.133.7.234... >> Connected to rah.star-gate.com. >> Escape character is '^]'. > >No problem forking for telnetd. > >> >> FreeBSD (rah.star-gate.com) (ttyp3) >> >> login: hasty >> Password: >> Last login: Mon Aug 10 00:02:45 from 192.100.81.124 >> Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> >> FreeBSD 3.0-CURRENT (STAR-GATE) #28: Wed Jul 29 01:01:13 PDT 1998 > >No problem forking for login. > >> Justice, n.: >> A decision in your favor. > >No problem forking for your shell, or fortune. > >> {hasty} man vi >> Formatting page, please wait...Cannot fork > >No problem forking for man, but problems with the pager. > >At this point, 'limit' and 'ps x | wc -l' would be educational. > >> vmstat -m >... > >Nothing suspicious in here. > >- -- >\\ 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 > >------------------------------ > >Date: Mon, 10 Aug 1998 09:25:29 -0700 >From: Amancio Hasty >Subject: Re: can not fork... > >My old limits: > >{hasty} limit >cputime unlimited >filesize unlimited >datasize 32768 kbytes >stacksize 16384 kbytes >coredumpsize unlimited >memoryuse unlimited >descriptors 256 >memorylocked 20480 kbytes >maxproc 32 >{hasty} ps -x | wc -l > 24 > >My new limits: >{hasty} limit >cputime unlimited >filesize unlimited >datasize 524288 kbytes >stacksize 49152 kbytes >coredumpsize unlimited >memoryuse unlimited >descriptors 256 >memorylocked 20480 kbytes >maxproc 64 > > >I just bumped up my login class xuser: > >xuser:\ > :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ > :cputime=4h:\ > :datasize=64M:\ > :stacksize=32M:\ > :filesize=32M:\ > :memoryuse=120M:\ > :openfiles=256:\ > :maxproc=64:\ > :tc=standard: >and increased maxusers to 64 in my kernel config file. > >I think what I will do next is decreased my limits and repeat the >same experiment . > >I usually don't run much in my system > >USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND >hasty 1703 0.0 0.0 404 280 p4 R+ 9:19AM 0:00.00 ps -xuaw >root 1 0.0 0.0 496 180 ?? Is 7:18PM 0:00.13 /sbin/init -- >root 2 0.0 0.0 0 0 ?? DL 7:18PM 0:00.05 (pagedaemon) >root 3 0.0 0.0 0 0 ?? DL 7:18PM 0:00.00 (vmdaemon) >root 4 0.0 0.0 0 0 ?? DL 7:18PM 0:01.95 (syncer) >root 28 0.0 0.0 204 68 ?? Is 7:18PM 0:00.00 adjkerntz -i >root 83 0.0 0.0 796 396 ?? Ss 2:18AM 0:00.25 syslogd >root 89 0.0 0.0 1756 1292 ?? Is 2:18AM 0:00.46 named -b >/etc/namedb/named.conf >daemon 94 0.0 0.0 780 304 ?? Is 2:18AM 0:00.00 portmap >root 102 0.0 0.0 460 228 ?? Is 2:18AM 0:00.00 mountd >root 105 0.0 0.0 316 140 ?? Is 2:18AM 0:00.01 nfsd: master >(nfsd) >root 109 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server >(nfsd) >root 110 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server >(nfsd) >root 111 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server >(nfsd) >root 112 0.0 0.0 296 88 ?? I 2:18AM 0:00.00 nfsd: server >(nfsd) >root 113 0.0 0.0 262944 316 ?? Is 2:18AM 0:00.00 rpc.statd >root 128 0.0 0.0 836 380 ?? Is 2:18AM 0:00.13 inetd >root 130 0.0 0.0 952 380 ?? Is 2:18AM 0:00.81 cron >root 134 0.0 0.0 808 420 ?? Is 2:18AM 0:00.01 lpd >root 137 0.0 0.0 1192 576 ?? Ss 2:18AM 0:00.28 sendmail: >accepting connections on port 25 (sendmail) >root 158 0.0 0.0 760 340 ?? Ss 2:18AM 0:01.89 moused -p >/dev/mouse -t x10mouseremote >msql 172 0.0 0.0 1048 464 con- I+ 2:18AM 0:01.54 >/usr/local/bin/msql2d >root 186 0.0 0.0 1296 640 ?? Is 2:18AM 0:00.00 >/usr/local/sbin/smbd -D >root 188 0.0 0.0 1160 684 ?? Ss 2:18AM 0:00.46 >/usr/local/sbin/nmbd -D >root 193 0.0 0.0 1152 576 ?? Is 2:18AM 0:00.74 >/usr/local/sbin/sshd >hasty 217 0.0 0.0 1360 940 v0 Is 2:18AM 0:00.13 -tcsh (tcsh) >root 218 0.0 0.0 796 416 v1 Is+ 2:18AM 0:00.01 >/usr/libexec/getty Pc ttyv1 >root 219 0.0 0.0 796 416 v2 Is+ 2:18AM 0:00.01 >/usr/libexec/getty Pc ttyv2 >hasty 223 0.0 0.0 456 236 v0 I+ 2:18AM 0:00.02 /bin/csh >/usr/local/bin/sx 16 >hasty 224 0.0 0.0 1688 600 v0 I+ 2:18AM 0:00.02 >/usr/X11R6/bin/xinit -- /usr/X11R6/bin/Xwrapper :0 -gamma 1.5 -bpp 16 >root 225 0.0 0.0 14152 12384 ?? S 2:18AM 5:12.93 >/usr/X11R6/bin/Xwrapper :0 -gamma 1.5 -bpp 16 (XF86_SVGA) >hasty 228 0.0 0.0 492 156 v0 I 2:18AM 0:00.01 sh >/home/hasty/.xinitrc >hasty 229 0.0 0.0 2044 1148 v0 I 2:18AM 0:00.06 xconsole >root 231 0.0 0.0 3052 2184 v0 S 2:18AM 0:02.64 xterm -e tcsh >hasty 233 0.0 0.0 1720 984 v0 S 2:18AM 0:00.87 fvwm95-2 >hasty 234 0.0 0.0 1376 440 v0 S 2:18AM 0:00.03 >/usr/X11R6/lib/X11/fvwm95-2/FvwmAuto 9 6 .fvwm2rc95 0 8 300 >hasty 237 0.0 0.0 1496 696 v0 S 2:18AM 0:00.08 >/usr/X11R6/lib/X11/fvwm95-2//FvwmButtons 10 5 .fvwm2rc95 0 8 >hasty 238 0.0 0.0 1564 776 v0 S 2:18AM 0:00.27 >/usr/X11R6/lib/X11/fvwm95-2//FvwmTaskBar 12 5 .fvwm2rc95 0 8 >hasty 240 0.0 0.0 2036 1172 v0 S 2:18AM 0:04.82 xclock >hasty 241 0.0 0.0 500 160 v0 I 2:18AM 0:00.00 /bin/sh -c nice >- -16 xload -fg red -nolabel -bg grey60 -update 5 -geom >hasty 242 0.0 0.0 2148 1292 v0 SN 2:18AM 0:01.10 xload >hasty 243 0.0 0.0 1492 688 v0 S 2:18AM 0:00.11 >/usr/X11R6/lib/X11/fvwm95-2//FvwmPager 14 5 .fvwm2rc95 0 8 0 0 >hasty 244 0.0 0.0 1344 920 p0 Is 2:18AM 0:00.10 -csh (tcsh) >hasty 246 0.0 0.0 32176 27064 p0 S 2:18AM 31:41.40 netscape >hasty 247 0.0 0.0 13424 3084 p0 I 2:18AM 0:00.22 (dns helper) >(netscape) >hasty 263 0.0 0.0 920 512 p0 I+ 2:28AM 0:00.84 telnet rah >root 264 0.0 0.0 864 456 ?? Is 2:28AM 0:00.62 telnetd >hasty 265 0.0 0.0 1364 1008 p2 Is 2:28AM 0:00.22 -tcsh (tcsh) >hasty 1041 0.0 0.0 8916 8380 v0 S 8:31AM 0:34.78 >/usr/local/bin/wish8.0 -f /usr/local/bin/exmh >hasty 1424 0.0 0.0 3828 2988 v0 I 8:32AM 0:01.00 >/usr/local/bin/wish8.0 -f /usr/local/bin/exmh-bg exmh /usr/local/lib/ >root 1686 0.0 0.0 2436 1748 v0 S 9:12AM 0:00.17 xterm >hasty 1687 0.0 0.0 1348 976 p4 Ss 9:12AM 0:00.11 -tcsh (tcsh) >hasty 1695 0.0 0.0 5444 4992 v0 S 9:14AM 0:00.26 ispell -a -S >hasty 1699 0.0 0.0 820 556 p2 I+ 9:16AM 0:00.02 more -e >/etc/login.conf >root 0 0.0 0.0 0 0 ?? DLs 7:18PM 0:00.02 (swapper) > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Mon, 10 Aug 1998 09:55:37 -0700 >From: Amancio Hasty >Subject: Re: can not fork... > >Tnks Mike , I think it was a limit problem in my system. I can't >seem to reproduce the problem after switching from the default >login class to my modified "xuser" class. > >xuser:\ > :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ > :cputime=4h:\ > :datasize=64M:\ > :stacksize=32M:\ > :filesize=32M:\ > :memoryuse=120M:\ > :openfiles=256:\ > :maxproc=64:\ > :tc=standard: > > Amancio > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Mon, 10 Aug 1998 10:14:24 -0700 (PDT) >From: David Wolfskill >Subject: Re: CAP vs netatalk for Appletalk/printing support > >>Date: Fri, 7 Aug 1998 15:53:39 -0400 >>From: Garance A Drosihn > >>I notice the ports collection includes both CAP and netatalk, and >>that kernel changes have been made for netatalk to take advantage >>of. I was wondering if most FreeBSD'ers prefer netatalk over CAP. > >Not sure about FreeBSDers, but I'll mention that a fairly large company >I did some consulting sysadmin work for uses CAP for access to printers. >(The company in question was moving its Mountain View Facility to >downtown San Jose; I participated in part of that move near the >beginning of my tenure there. They use *lots* of printers....) > >Thus, it's conceivable that keeping CAP functional would make FreeBSD >more attractive to such a company than failing to keep it functional >would. (During the time I was there, they did not make any use of >FreeBSD that I know of; I mostly did Solaris 2 & SunOS administration, >with the occasional IRIX, AIX, Digital UNIX, or HPUX system.) > >One datum, >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 > >------------------------------ > >Date: Mon, 10 Aug 1998 15:28:03 -0400 (EDT) >From: zhihuizhang >Subject: Question about routine getblk() > >Hi, getblk() tries to get a buffer with specified size >of physical memory allocated to it. I got two questions >about this routine: > >(1) The given size could be greater than the optimial size contained in >the mount structure. The comment says "this happens on mount points". >Why is the case? > >(2) If the buffer is in the core, we check for size inconsistancies. Why >should this happen and why should we be conservative on metadata. > >Any help is appreciated. > > >- -------------------------------------------------- >| 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 > >------------------------------ > >Date: Mon, 10 Aug 1998 17:46:19 -0400 (EDT) >From: Luoqi Chen >Subject: Re: Question about routine getblk() > >> Hi, getblk() tries to get a buffer with specified size >> of physical memory allocated to it. I got two questions >> about this routine: >> >> (1) The given size could be greater than the optimial size contained in >> the mount structure. The comment says "this happens on mount points". >> Why is the case? >The size you were talking about was the block size of the file system, >it is used to translate starting blkno to a vm offset. For a mount point >covered by another file system, the correct block size should be coming >from the fs that is covering this vnode, but vp->v_mount still points to >the fs being covered, and block size for these two fs could be different. > >> >> (2) If the buffer is in the core, we check for size inconsistancies. Why >> should this happen and why should we be conservative on metadata. >I'm not sure about this one. Maybe it happens when a frag is extended to >a full block? >> >> Any help is appreciated. >> >> >> -------------------------------------------------- >> | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | >> | Dept. of Computer Science, SUNY at Binghamton | >> -------------------------------------------------- >> >- -lq > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >End of freebsd-hackers-digest V4 #215 >************************************* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 05:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25940 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 05:54:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from magc.cd.2573.savbank.ru (h26.216.elnet.msk.ru [194.190.216.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25771 for ; Tue, 11 Aug 1998 05:54:08 -0700 (PDT) (envelope-from mag@h26.216.elnet.msk.ru) Received: from magc.cd.2573.savbank.ru (magc.cd.2573.savbank.ru [172.16.201.254]) by magc.cd.2573.savbank.ru (8.8.5/8.8.5) with ESMTP id QAA26831 for ; Tue, 11 Aug 1998 16:56:09 +0400 Message-ID: <35D03F68.69837C2A@magc.cd.2573.savbank.ru> Date: Tue, 11 Aug 1998 16:56:08 +0400 From: MAG X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Question about shutdown Content-Type: multipart/alternative; boundary="------------22F7B703E7D4E24EA4134DCD" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------22F7B703E7D4E24EA4134DCD Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit I have written an UPS monitor daemon. But I cannot decide where the "Turn the UPS power off" command must be (I tryed /etc/rc.shutdown, but the filesystems were improperly dismounted, reboot, halt and shutdown commands do not call /etc/rc.shutdown, etc...). Who can help me? -- MAG --------------22F7B703E7D4E24EA4134DCD Content-Type: text/html; charset=koi8-r Content-Transfer-Encoding: 7bit     I have written an UPS monitor daemon. But I cannot decide where the "Turn the UPS power off" command
must be (I tryed /etc/rc.shutdown, but the filesystems were improperly dismounted, reboot, halt and shutdown
commands do not call /etc/rc.shutdown, etc...).
    Who can help me? 
-- 
MAG
  --------------22F7B703E7D4E24EA4134DCD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 06:11:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27477 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 06:11:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27472 for ; Tue, 11 Aug 1998 06:11:29 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.8.8/8.8.8) with SMTP id JAA02389; Tue, 11 Aug 1998 09:11:42 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 11 Aug 1998 09:11:41 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Bill Paul cc: hackers@FreeBSD.ORG Subject: about XL driver In-Reply-To: <199808110040.UAA23576@skynet.ctr.columbia.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 the newest versions (as of yesterday) seem to deliver quite impressive performance, (ftp over 100mbit full duplex) 60410655 bytes received in 7.75 seconds (7.43 MB/s) (while playing mp3) 60410655 bytes received in 6.67 seconds (8.63 MB/s) (mostly idle) irix seems to be able to get like 11.5 MB/s (between 2 irix boxes) is this hardware or software? (linux on the other hand is about the same speed as freebsd) (this is a download to MFS an mount and into /dev/null gets about the same performance, the first one is while playing an mp3 (on a PII300)) Great job, the driver seems to be quite solid, thank you. Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Tue Aug 11 06:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01093 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 06:40:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01081 for ; Tue, 11 Aug 1998 06:40:09 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id GAA25902 for ; Tue, 11 Aug 1998 06:39:44 -0700 (PDT) Message-Id: <199808111339.GAA25902@mailgate.cadence.com> Received: from unknown(194.32.96.136) by mailgate.cadence.com via smap (mjr-v1.2) id xma902842781.025879; Tue, 11 Aug 98 06:39:42 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: freebsd-hackers@FreeBSD.ORG Date: Tue, 11 Aug 1998 14:39:19 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Network stack assumptions Reply-to: dmlb@ragnet.demon.co.uk X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of interest can theFreeBSD network stack support network interfaces which provide both connection orientated and connection less protocols? Take a look at www.homerf.org and www.bluetooth.com. I'm under NDA as Symbionics (my employer and one of the Core Companies) is overseeing parts of the SWAP specification writing and I'm writing specs (and hopefully designing) for RFICs to go in these things. Both of these systems offer isochronous data on connection orientated streams for voice and LAN (802.11 style for SWAP) connectionless streams for data. Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 07:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06613 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 07:29:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06465 for ; Tue, 11 Aug 1998 07:28:18 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id QAA11493; Tue, 11 Aug 1998 16:23:37 +0200 (CEST) Date: Tue, 11 Aug 1998 16:25:57 +0200 From: Stefan Bethke To: MAG cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown Message-ID: <927784.3111841557@d254.promo.de> In-Reply-To: <35D03F68.69837C2A@magc.cd.2573.savbank.ru> Originator-Info: login-token=Mulberry:01Qdh6oLRM3wbgR6BG3QH+ X-Mailer: Mulberry Demo (MacOS) [1.4.0a8, s/n Evaluation] 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 On Die, 11. Aug 1998 16:56 Uhr +0400 MAG wrote: > I have written an UPS monitor daemon. But I cannot decide where the > "Turn the UPS power off" command must be (I tryed /etc/rc.shutdown, > but the filesystems were improperly dismounted, reboot, halt and shutdown > commands do not call /etc/rc.shutdown, etc...). You need to shut down power from within the kernel. I did just this a few months back, but were to lazy to put up the sources somewhere. I'll try to dig it up later today... Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 07:31:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07000 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 07:31:19 -0700 (PDT) (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 HAA06993 for ; Tue, 11 Aug 1998 07:31:12 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 5337 invoked by uid 1001); 11 Aug 1998 14:30:46 +0000 (GMT) To: bright@hotjobs.com Cc: wpaul@skynet.ctr.columbia.edu, hackers@FreeBSD.ORG Subject: Re: about XL driver In-Reply-To: Your message of "Tue, 11 Aug 1998 09:11:41 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 11 Aug 1998 16:30:46 +0200 Message-ID: <5335.902845846@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the newest versions (as of yesterday) seem to deliver quite impressive > performance, > (ftp over 100mbit full duplex) > 60410655 bytes received in 7.75 seconds (7.43 MB/s) (while playing mp3) > 60410655 bytes received in 6.67 seconds (8.63 MB/s) (mostly idle) > > irix seems to be able to get like 11.5 MB/s (between 2 irix boxes) is this > hardware or software? (linux on the other hand is about the same speed as > freebsd) It would be interesting to see what you can get with ttcp or NetPerf. FreeBSD is perfectly capable of saturating a 100 Mbps Ethernet segment using either Intel Pro 100/B or DEC 21140 based NICs. 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 Tue Aug 11 08:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14756 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:05:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14625 for ; Tue, 11 Aug 1998 08:04:40 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id LAA10281; Tue, 11 Aug 1998 11:02:52 -0400 (EDT) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Tue, 11 Aug 1998 11:02:51 -0400 (EDT) From: "Bruce M. Walter" To: MAG cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown In-Reply-To: <35D03F68.69837C2A@magc.cd.2573.savbank.ru> 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 written an UPS monitor daemon. But I cannot decide where the > "Turn the UPS power off" command > must be (I tryed /etc/rc.shutdown, but the filesystems were improperly > dismounted, reboot, halt and shutdown > commands do not call /etc/rc.shutdown, etc...). > Who can help me? I've written one myself as well... There was a discussion several months back on hackers regarding this, and the answer is: Not where you'd think ;) Actually, to sum up that discussion, there is a flag that gets passed into reboot (RB_POWEROFF... see man 2 reboot) which, when received, should shutdown and poweroff the machine. There is no built-in kernel support for this, although I believe the APM stuff interfaces for ATX boards. My package has a driver component as well as a userland daemon. On bootup, the driver installs a callback function (via at_shutdown) which sends the poweroff signal to the UPS if reboot gets called with RB_POWEROFF. If powerfail is detected during boot, it goes into a tight loop (checking for user intervention) to prevent bootup. This is what needs to happen in the case of intermittant power loss. Once the system boots, the monitor daemon runs and queries the driver for the UPS status, also making that status available via a TCP port in case you need to link several systems off a single UPS. I had submitted patches (kern/5863) which corrected the function of the halt/reboot -p commands and also prioritized and added a third kernel callout function list which gets called after all of the other drivers spin-down stuff is called (namely the DPT driver which uses the second shutdown callout list to sync the array... Very bad to poweroff during that, take my word) I don't believe any interest was shown, so I just run the patches here. Currently I support all of the GenPower cables, APC BackUPS and Pro devices and a TrippLite or two if IIRC. My code is languishing due to lack of interest outside my office, but you're more than welcome to see what I've got. It works well here, and I'd love someone else to use it. The code is at: ftp://ftp.fortean.com/pub/bupsd/backupsd-1.1.tar.gz It's still pretty rough package-wise, but once it's built it's solid. - Bruce ========================================================== || Bruce M. Walter || 426 South Dawson Street || || Principal || Raleigh, NC 27601 USA || || NIXdesign Group, Inc. || Tel: 919.829.4908 || || Concept + Code || Fax: 919.829.4993 || ========================================================== || BSD Unix -- It's not just a job, it's a way of life! || ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 08:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17742 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:19:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17712 for ; Tue, 11 Aug 1998 08:19:43 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id IAA20455; Tue, 11 Aug 1998 08:19:14 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with SMTP id IAA17248; Tue, 11 Aug 1998 08:19:13 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id IAA08564; Tue, 11 Aug 1998 08:16:37 -0700 To: grog@lemis.com Cc: hackers@FreeBSD.ORG Subject: Re: AMD-specific kernel code (was: How long a wait?) In-Reply-To: Your message of "Tue, 11 Aug 1998 13:09:10 +0930" <19980811130910.Q20188@freebie.lemis.com> References: <19980811130910.Q20188@freebie.lemis.com> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980811081637E.thomma@baynetworks.com> Date: Tue, 11 Aug 1998 08:16:37 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg, I tried K6 write-allocation patch last night. Here is the result of make buidlworld (about 10 days old) PA-2007, K6-300(75MHz x 4.5), IBM UW 4(9ES)/NCR875. 2856.7 999.0 1:04:53.13 98.8% 826+918k 36516+37325io 3263pf (without patch) 2827.3 970.7 1:05:01.36 97.3% 832+923k 41049+40435io 3217pf (with patch) Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 08:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21934 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:38:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21846 for ; Tue, 11 Aug 1998 08:38:13 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id RAA12256; Tue, 11 Aug 1998 17:34:45 +0200 (CEST) Date: Tue, 11 Aug 1998 17:37:05 +0200 From: Stefan Bethke To: dmlb@ragnet.demon.co.uk cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Network stack assumptions Message-ID: <1184714.3111845825@d254.promo.de> In-Reply-To: <199808111339.GAA25902@mailgate.cadence.com> Originator-Info: login-token=Mulberry:01sL+QwyMz9SlPLrZpTOgU X-Mailer: Mulberry Demo (MacOS) [1.4.0a8, s/n Evaluation] 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, On Die, 11. Aug 1998 14:39 Uhr +0000 Duncan Barclay wrote: > Out of interest can theFreeBSD network stack support network > interfaces which provide both connection orientated and connection > less protocols? > > Take a look at www.homerf.org and www.bluetooth.com. I'm under > NDA as Symbionics (my employer and one of the Core Companies) is > overseeing parts of the SWAP specification writing and I'm writing > specs (and hopefully designing) for RFICs to go in these things. > > Both of these systems offer isochronous data on connection orientated > streams for voice and LAN (802.11 style for SWAP) connectionless > streams for data. That definitly sounds interesting. You might want to be a bit more specific about your questions, however. Also, there are probably some people on this list who can comment on these issues far better than me. FreeBSD contains both an API for network communications, sockets. Sockets is the predominantly used API for network communications in most Unix systems and has been ported to many other platforms. Because FreeBSD is based on 4.4BSD, its implementation is based on the very reference implementation for sockets. The sockets model includes a number of categories for communication protocols. Also, if you were to implement a new protocol suite, it probably would be easy to extend these as neccessary (the current models are obviously based on the capabilities TCP/IP provides). FreeBSD also includes network protocol suite implementations, namely TCP/IP. Again, the implentation is based on 4.4BSD, which is considered the reference implementation (more appropiatly, one might consider the Net/3 release as the reference; Net/3 found its way into the 4.4BSD release). Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 08:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24074 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:51:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA24069 for ; Tue, 11 Aug 1998 08:51:41 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA24486; Tue, 11 Aug 1998 11:54:10 -0400 From: Bill Paul Message-Id: <199808111554.LAA24486@skynet.ctr.columbia.edu> Subject: Re: Some errors in XL driver ? To: bazilio@monitord.vrn.ru (Vasily V. Grechishnikov) Date: Tue, 11 Aug 1998 11:54:08 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <000301bdc51e$d7798cc0$0a64a8c0@baz_station.monitord.vrn.ru> from "Vasily V. Grechishnikov" at Aug 11, 98 03:54:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Vasily V. Grechishnikov had to walk into mine and say: > Hi ! > Today I had to test 3C905 NIC. After downloading XL driver > from www.freebsd.org/~/wpaul I had strange results. NIC detection > and autonegotiation works fine but some performance problem > occured - 380-400Kb/s at 10Mbps. After looking at network > statistic I saw very high Ierrs count. Here netstat -ni from my > test box running 2.2.7-RELEASE after downloading 12MB > file from local ftp. Whats happen ? > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll > xl0 1500 00.a0.24.4d.c3.3b 9305 1757 4113 0 > 0 > xl0 1500 192.168.100 192.168.100.245 9305 1757 4113 0 > 0 Aieeee! I think I found the cause of this problem. The autonegotiation code is setting the modes incorrectly. Please try to fix this using one of the following methods: - Force the card to 10mbps/half-duplex mode using the following command: # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex This is just to see if setting the mode correctly clears up the problem. If so, do one of the next to things. - Apply the following patch to if_xl.c, recompile your kernel, and reboot: --- if_xl.c 1998/08/11 02:13:59 1.33 +++ if_xl.c 1998/08/11 15:26:28 @@ -796,13 +796,13 @@ ability & PHY_ANAR_10BTFULL) { ifm->ifm_media = IFM_ETHER|IFM_10_T|IFM_FDX; media &= ~PHY_BMCR_SPEEDSEL; - media &= ~PHY_BMCR_DUPLEX; + media |= PHY_BMCR_DUPLEX; printf("(full-duplex, 10Mbps)\n"); } else if (advert & PHY_ANAR_10BTHALF && ability & PHY_ANAR_10BTHALF) { ifm->ifm_media = IFM_ETHER|IFM_10_T|IFM_HDX; media &= ~PHY_BMCR_SPEEDSEL; - media |= PHY_BMCR_DUPLEX; + media &= ~PHY_BMCR_DUPLEX; printf("(half-duplex, 10Mbps)\n"); } - Download a new copy of if_xl.c from www.freebsd.org/~wpaul/3Com, recompile your kernel and reboot. As you can see, I transposed a couple of lines: the chip is detecting the right modes, but the code later sets the duplex mode incorrectly. I'm not sure how this crept in, but it explains the poor performance at 10Mbps: if you set the duplex bit incorrectly, the card behaves very strangely. I didn't notice this initially because the machine I use for 10Mbps testing has a 3c900 card, which does not have a PHY, hance the autoneg code is never used. The other code in xl_setmode_mii() which manually sets the chip modes gets this right, which is why setting the mode manually works. I apologize for this stupid mistake; that's what I get for not doing proper testing. Naturally, at 100Mbps, which is what my 3c905B test machines were set for, it works right. [chop] > dmesg output (disabled XL_USEIOSPACE), else if this variable > defined we has supplement warning xl0: command never completed!: [chop] This I want to know more about. It anybody else sees this, please let me know. Try to show me where the warning appears and whether or not it affects the operation of the NIC. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 08:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25141 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:56:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25127 for ; Tue, 11 Aug 1998 08:56:46 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id IAA02273; Tue, 11 Aug 1998 08:55:53 -0700 (PDT) Message-Id: <199808111555.IAA02273@mailgate.cadence.com> Received: from unknown(194.32.96.136) by mailgate.cadence.com via smap (mjr-v1.2) id xma902850942.002228; Tue, 11 Aug 98 08:55:42 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: Stefan Bethke Date: Tue, 11 Aug 1998 16:55:12 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Network stack assumptions Reply-to: dmlb@ragnet.demon.co.uk CC: freebsd-hackers@FreeBSD.ORG In-reply-to: <1184714.3111845825@d254.promo.de> References: <199808111339.GAA25902@mailgate.cadence.com> X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > On Die, 11. Aug 1998 14:39 Uhr +0000 Duncan Barclay > wrote: > > > Out of interest can theFreeBSD network stack support network > > interfaces which provide both connection orientated and connection > > less protocols? > > > > Take a look at www.homerf.org and www.bluetooth.com. I'm under > > NDA as Symbionics (my employer and one of the Core Companies) is > > overseeing parts of the SWAP specification writing and I'm writing > > specs (and hopefully designing) for RFICs to go in these things. > > > > Both of these systems offer isochronous data on connection orientated > > streams for voice and LAN (802.11 style for SWAP) connectionless > > streams for data. > > That definitly sounds interesting. You might want to be a bit more > specific about your questions, however. Also, there are probably > some people on this list who can comment on these issues far better > than me. Okay, can the kernel cope with a device hanging off a USB port or integrated into the motherboard or a PCI card which provides wireless LAN capabilities with mutliple protocols running on it? Asynchronous data is 802.11 style, isochronous data is DECT sytle for SWAP, can't remember the protocols for Bluetooth. They will support a number of concurrent voice calls between handsets/apps software on your PC along with LAN activity (i.e. wireless printing from your laptop). In some instances the FreeBSD box will have to be a some form of controller which manages the routing of the network. [tutorial snipped]. Sorry, I meant the device driver and network stack framework! > > Stefan > Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 08:58:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25324 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 08:58:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25300 for ; Tue, 11 Aug 1998 08:57:53 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id LAA10776; Tue, 11 Aug 1998 11:56:24 -0400 (EDT) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Tue, 11 Aug 1998 11:56:24 -0400 (EDT) From: "Bruce M. Walter" To: Bill Fumerola cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown 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 > Would you like me to submit this to the FreeBSD ports collection? Since I developed it specifically for FreeBSD, I had hoped it would eventually find it's way into the system in some capacity. The problems with adding it to the ports collection are twofold: 1) It requires a kernel patch to perform "safe" shutdowns... This is because of the way other drivers use the at_shutdown interface and these patches should first be part of the system. Even if nothing ever comes of my code, the capacity still exists for a program to assume it can poweroff when it really can't. 2) I've not got the time to really polish this code right now. I'd love for it to be an ongoing project for which I can offer all of the resources for it's continued development. Unfortunately my current workload prohibits my direct involvement for a little while longer. (aint that always the case :) When I have more time, I'll see if I can't clean it up a bit. In the meantime, if anyone wants to hack on, please let me know. I can offer coordination and repository services while I'm to busy to hack. - Bruce ========================================================== || Bruce M. Walter || 426 South Dawson Street || || Principal || Raleigh, NC 27601 USA || || NIXdesign Group, Inc. || Tel: 919.829.4908 || || Concept + Code || Fax: 919.829.4993 || ========================================================== || BSD Unix -- It's not just a job, it's a way of life! || ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 09:53:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02225 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 09:53:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02215 for ; Tue, 11 Aug 1998 09:53:49 -0700 (PDT) (envelope-from stefan@promo.de) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by relay.xlink.net (8.8.8/8.8.7) with ESMTP id SAA54132 for ; Tue, 11 Aug 1998 18:53:20 +0200 Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id SAA12750; Tue, 11 Aug 1998 18:42:47 +0200 (CEST) Date: Tue, 11 Aug 1998 18:45:07 +0200 From: Stefan Bethke To: MAG cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown Message-ID: <1430421.3111849907@d254.promo.de> In-Reply-To: <927784.3111841557@d254.promo.de> Originator-Info: login-token=Mulberry:01NYFc0qj1wTjU8IJ40arg X-Mailer: Mulberry Demo (MacOS) [1.4.0a8, s/n Evaluation] 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 On Die, 11. Aug 1998 16:25 Uhr +0200 Stefan Bethke wrote: > I did just this a few months back, but were to lazy to put up the sources > somewhere. I'll try to dig it up later today... http://www.freebsd.org/~stb/dumb_ups-0.01.tar.gz Its defenitly rough around the edges, but is works. Have fun, Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 10:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08626 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 10:55:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08603 for ; Tue, 11 Aug 1998 10:55:17 -0700 (PDT) (envelope-from eranian@cello.hpl.hp.com) Received: from cello.hpl.hp.com (cello.hpl.hp.com [15.4.89.103]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id KAA18568 for ; Tue, 11 Aug 1998 10:54:48 -0700 (PDT) Received: (from eranian@localhost) by cello.hpl.hp.com (8.7.1/8.7.1) id KAA01432 for hackers@FreeBSD.ORG; Tue, 11 Aug 1998 10:54:47 -0700 (PDT) From: Stephane Eranian Message-Id: <199808111754.KAA01432@cello.hpl.hp.com> Subject: Loosing socket options on new connections... In-Reply-To: <199808102147.OAA05756@hub.freebsd.org> from freebsd-hackers-digest at "Aug 10, 98 02:47:17 pm" To: hackers@FreeBSD.ORG Date: Tue, 11 Aug 1998 10:54:47 -0700 (PDT) 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, I recently notice that when you get a new connection on a listen socket the flags for the "master socket" simply vanish from the cloned socket (service socket). This is really annoying for flags like TCP_NODELAY, ie TF_NODELAY (ie user-settable flags via setsockopt()). It seems that all other systems that I've tested do the correct thing, ie all non BSD4.4-Lite2 based system. The faulty line seems to be in netinet/tcp_input.c (whatever version): tp->t_flags |= tp0->t_flags & (TF_NOPUSH|TF_NOOPT); tp->t_flags is set to zero in tcp_newtcpcb(). if tp0 has TF_NODELAY set, you loose it ! It seems that some flags must disappear whereas some other must be kept. Any thoughts about that ? +--------------------------------------------------------------------+ | Ste'phane ERANIAN | Email eranian@hpl.hp.com | | Hewlett-Packard Laboratories | | | 1501, Page Mill Road MS 1U-15 | | | Palo Alto, CA 94303-096 | | | USA | | | Tel : (650) 857-7174 | | | Fax : (650) 857-5548 | | +--------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 11:32:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13447 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 11:32:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA13440 for ; Tue, 11 Aug 1998 11:32:48 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA20270 (5.67b/IDA-1.5); Tue, 11 Aug 1998 19:58:51 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA04987; Tue, 11 Aug 1998 11:24:57 +0200 (CEST) From: Wilko Bulte Message-Id: <199808110924.LAA04987@yedi.iaf.nl> Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: from Peter van Heusden at "Aug 10, 98 10:18:00 am" To: pvh@leftside.wcape.school.za Date: Tue, 11 Aug 1998 11:24:57 +0200 (CEST) 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 Peter van Heusden wrote... > On Sun, 9 Aug 1998, Wilko Bulte wrote: > > > > > Well, not that it solves your problem, but I also have a 8200 on a ncr810 > > and that one works. Has done so for years. > > > > More specific it has firmware: > > > > Aug 7 22:17:20 yedi /kernel: (ncr1:3:0): "EXABYTE EXB-8200 2687" type 1 > > removable SCSI 1 > > Thanks for the info. Mine gives a slightly different dmesg output: > > (ncr0:6:0): "EXABYTE EXB-8200 253G" type 1 removable SCSI 1 > > So, its a slightly different model, maybe with an older firmware > (are firmware upgrades possible on these drives?) However, since it is a Slightly different firmware, the model is the same. You can upgrade the firmware, it is a 2 EPROM swap. One EPROM contains the servo code, it is (in my case) conveniently (...) located below the head drum. The other EPROM is on the scsi interface board of the Exabyte. See www.exabyte.com for the firmware. NOte that the servo code and scsi f/w need to be 'matched', not every combination works according to Exabyte. > similar model, I was wondering what you do to use a tape. The tape I'm > trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt > erase' before using the tape. I do nothing special, not even an erase. 112m tapes should be OK as they use 'm myself. 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 Tue Aug 11 11:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13591 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 11:33:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA13578 for ; Tue, 11 Aug 1998 11:33:15 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA20380 (5.67b/IDA-1.5); Tue, 11 Aug 1998 19:59:02 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00492; Tue, 11 Aug 1998 19:37:45 +0200 (CEST) From: Wilko Bulte Message-Id: <199808111737.TAA00492@yedi.iaf.nl> Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: from Nick Hibma at "Aug 10, 98 12:06:08 pm" To: nick.hibma@jrc.it Date: Tue, 11 Aug 1998 19:37:45 +0200 (CEST) Cc: pvh@leftside.wcape.school.za, 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 Nick Hibma wrote... > > So, its a slightly different model, maybe with an older firmware > > (are firmware upgrades possible on these drives?) However, since it is a > > similar model, I was wondering what you do to use a tape. The tape I'm > > trying to use is an Exabyte 112m tape, and as I said before, I tried a 'mt > > erase' before using the tape. > > Take a safe bet and use a 90m tape before anything else. I know that 112m he wrote.. > 160m tapes are aproblem in anything before the 8505XL drives and after > that they were still not very reliable. 160m are not supported in 8200 drives. They might even spit 'm out 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 Tue Aug 11 11:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13826 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 11:34:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13821 for ; Tue, 11 Aug 1998 11:34:38 -0700 (PDT) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54] helo=demios.scl.ameslab.gov) by mailhub.scl.ameslab.gov with smtp (Exim 1.90 #1) for hackers@freebsd.org id 0z6JBd-0002y6-00; Tue, 11 Aug 1998 13:30:21 -0500 Date: Tue, 11 Aug 1998 13:34:13 -0500 (CDT) From: Guy Helmer To: hackers@FreeBSD.ORG Subject: sysctl.3 and sysctl.8 man pages changes 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'm working on documenting a number of the sysctl variables which are not mentioned in the sysctl.3 or sysctl.8 man pages. In general, should the useful sysctl variables that are likely to remain (variables explicitly defined in sysctl.h, vm_param.h, tcpvar.h, et. al) be briefly mentioned in sysctl.8 and fully explained in sysctl.3? It seems like that was the intent of the way the pages were structured... Guy Helmer Guy Helmer, Graduate Student, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 12:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17877 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 12:00:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17862 for ; Tue, 11 Aug 1998 12:00:26 -0700 (PDT) (envelope-from bright@bright.fx.genx.net) Received: (from bright@localhost) by bright.fx.genx.net (8.8.8/8.8.8) id PAA27216; Tue, 11 Aug 1998 15:00:39 -0500 (EST) (envelope-from bright) From: Alfred Perlstein Message-Id: <199808112000.PAA27216@bright.fx.genx.net> Subject: Re: about XL driver In-Reply-To: <199808111847.MAA00560@harmony.village.org> from Warner Losh at "Aug 11, 1998 12:47:53 pm" To: imp@village.org (Warner Losh) Date: Tue, 11 Aug 1998 15:00:39 -0500 (EST) 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 > In message Alfred Perlstein writes: > : 60410655 bytes received in 6.67 seconds (8.63 MB/s) (mostly idle) > : irix seems to be able to get like 11.5 MB/s (between 2 irix boxes) is this > : hardware or software? (linux on the other hand is about the same speed as > : freebsd) > > Full Duplex vs half duplex? > i'm quite sure it's all full duplex. all tests are: transfer from irix -> irix transfer from irix -> freebsd transfer from irix -> linux -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 12:04:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18347 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 12:04:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18337 for ; Tue, 11 Aug 1998 12:04:28 -0700 (PDT) (envelope-from bright@bright.fx.genx.net) Received: (from bright@localhost) by bright.fx.genx.net (8.8.8/8.8.8) id PAA27235; Tue, 11 Aug 1998 15:04:48 -0500 (EST) (envelope-from bright) From: Alfred Perlstein Message-Id: <199808112004.PAA27235@bright.fx.genx.net> Subject: Re: KERNFS and MFS In-Reply-To: from Snob Art Genre at "Aug 11, 1998 2: 6:15 pm" To: ben@rosengart.com Date: Tue, 11 Aug 1998 15:04:48 -0500 (EST) 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 > On Mon, 10 Aug 1998, Alfred Perlstein wrote: > > > 2 ideas: > > > > add mfs to sysinstall options (visible so as to encourage use for /tmp) > > the reason is that it can provide a huge speed increase if used properly > > I've been wanting to set this up for a while; could you perhaps mail me > your fstab? That's all I should need, right? heh, wasn't able to figure out the format in fstab so i have a "hack" in rc.local: echo 'mounting mfs /tmp.' mount_mfs -s 160000 -o nosuid,nodev /dev/wd0s3b /tmp /dev/wd0s3b is my swap partition. if anyone would document this better..... i'd appreciate knowing a "real" way to do this. thanks. Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 12:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21910 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 12:33:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA21886 for ; Tue, 11 Aug 1998 12:33:39 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0z6Jzl-0004l4-00; Tue, 11 Aug 1998 12:22:09 -0700 Date: Tue, 11 Aug 1998 12:22:09 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Stephane Eranian cc: hackers@FreeBSD.ORG Subject: Re: Loosing socket options on new connections... In-Reply-To: <199808111754.KAA01432@cello.hpl.hp.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, 11 Aug 1998, Stephane Eranian wrote: > Hi, > > I recently notice that when you get a new connection on a listen > socket the flags for the "master socket" simply vanish from the cloned > socket (service socket). This is really annoying for flags like > TCP_NODELAY, ie TF_NODELAY (ie user-settable flags via setsockopt()). The traditional behaviour (not just FreeBSD) has been that only SO_DEBUG, SO_DONTROUTE, SO_KEEPALIVE, SO_LINGER, SO_OOBINLINE, SO_RCVBUF and SO_SNDBUF are inherited. A program shouldn't expect others to be inherited, although this is somewhat ill-defined by the specs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 13:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28847 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 13:30:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA28723; Tue, 11 Aug 1998 13:29:49 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA25949 (5.67b/IDA-1.5); Tue, 11 Aug 1998 21:42:02 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA01048; Tue, 11 Aug 1998 20:16:58 +0200 (CEST) From: Wilko Bulte Message-Id: <199808111816.UAA01048@yedi.iaf.nl> Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: <199808110035.TAA00818@nospam.hiwaay.net> from David Kelly at "Aug 10, 98 07:35:25 pm" To: dkelly@hiwaay.net (David Kelly) Date: Tue, 11 Aug 1998 20:16:58 +0200 (CEST) Cc: se@FreeBSD.ORG, pvh@leftside.wcape.school.za, 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 David Kelly wrote... > Stefan Esser writes: > > On 1998-08-09 17:32 +0200, Peter van Heusden w > > rote: > > > However, I cannot write to it at all - even after a 'mt erase', I get the > > > following: > > > > > > bash# mt rewind > > > bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 > > > dd: /dev/nrst0: Input/output error > > > 1+0 records in > > > 0+0 records out > > > 0 bytes transferred in 0.082043 secs (0 bytes/sec) > > > bash# On mine: su-2.01# dd if=/kernel of=/dev/nrst1 bs=64 count=1024 1024+0 records in 1024+0 records out 65536 bytes transferred in 5.187031 secs (12635 bytes/sec) su-2.01# Why you want to use 64 byte blocks escapes me because: su-2.01# dd if=/kernel of=/dev/nrst1 bs=64k count=1024 17+1 records in 17+1 records out 1176833 bytes transferred in 11.385549 secs (103362 bytes/sec) A 8200 native speed is something like 240kb/sec if I remember well. 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 Tue Aug 11 13:30:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28897 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 13:30:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA28840; Tue, 11 Aug 1998 13:30:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA25941 (5.67b/IDA-1.5); Tue, 11 Aug 1998 21:42:00 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA00917; Tue, 11 Aug 1998 20:11:47 +0200 (CEST) From: Wilko Bulte Message-Id: <199808111811.UAA00917@yedi.iaf.nl> Subject: Re: EXA 8200 tape drive on FreeBSD? In-Reply-To: <199808110035.TAA00818@nospam.hiwaay.net> from David Kelly at "Aug 10, 98 07:35:25 pm" To: dkelly@hiwaay.net (David Kelly) Date: Tue, 11 Aug 1998 20:11:46 +0200 (CEST) Cc: se@FreeBSD.ORG, pvh@leftside.wcape.school.za, 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 David Kelly wrote... > Stefan Esser writes: > > On 1998-08-09 17:32 +0200, Peter van Heusden w > > rote: > > > However, I cannot write to it at all - even after a 'mt erase', I get the > > > following: > > > > > > bash# mt rewind > > > bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 > > > dd: /dev/nrst0: Input/output error > > > 1+0 records in > > > 0+0 records out > > > 0 bytes transferred in 0.082043 secs (0 bytes/sec) > > > bash# > > > > Did you try shorter transfers (less than 64KB blocks) ? > > > > I seem to remember, that the EXABYTE 8200 was limited to > > less than 64KB per block (i.e. 63KB works, but 64KB doesn't). > > "bs=64" spells out 64 byte blocks, not 64k. "bs=64k" would be 64k. > > There might be a problem with the block being too small. :-) > > SGI Irix defaults to 128k blocks on Exabyte 8mm drives, including the > 8200. Its FreeBSD that won't (can't) do more than 64k. I think the 8200 uses 1 kB blocks itself by default. > As others have mentioned, when a new (new to you) Exabyte drive acts > flaky its time to flash the EEPROMs or burn new EPROMs for the old 8200. > I too have a new-to-me 8200 that ID's, rewinds, retensions, ejects, and > all that good stuff. But doesn't work. If new EPROMs don't fix it, then > its junk. That too is standard failure mode for an Exabyte. Exabytes are not the most robust of devices yes.. _ ______________________________________________________________________ | / 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 Tue Aug 11 13:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00428 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 13:40:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00422 for ; Tue, 11 Aug 1998 13:40:53 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id QAA01613; Tue, 11 Aug 1998 16:40:25 -0400 (EDT) Date: Tue, 11 Aug 1998 16:40:24 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: KERNFS and MFS In-Reply-To: <199808112004.PAA27235@bright.fx.genx.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 think I've got it: /dev/sd0b /tmp mfs rw,-s=131072 0 0 /dev/sd1b /usr/obj mfs rw,-s=524288 0 0 Now I'm just wondering if I should leave these mounted async, per the default, or whether I should try to get softupdates running on them. Is that possible, and would it make sense? On Tue, 11 Aug 1998, Alfred Perlstein wrote: > heh, wasn't able to figure out the format in fstab so i have a "hack" > in rc.local: > > echo 'mounting mfs /tmp.' > mount_mfs -s 160000 -o nosuid,nodev /dev/wd0s3b /tmp > > /dev/wd0s3b is my swap partition. > > if anyone would document this better..... i'd appreciate knowing a "real" way to do this. > > thanks. > Alfred > Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 13:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01457 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 13:46:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01363 for ; Tue, 11 Aug 1998 13:45:59 -0700 (PDT) (envelope-from eranian@cello.hpl.hp.com) Received: from cello.hpl.hp.com (cello.hpl.hp.com [15.4.89.103]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id NAA29902; Tue, 11 Aug 1998 13:45:23 -0700 (PDT) Received: (from eranian@localhost) by cello.hpl.hp.com (8.7.1/8.7.1) id NAA16194; Tue, 11 Aug 1998 13:45:22 -0700 (PDT) From: Stephane Eranian Message-Id: <199808112045.NAA16194@cello.hpl.hp.com> Subject: Re: Loosing socket options on new connections... In-Reply-To: from Marc Slemko at "Aug 11, 98 12:22:09 pm" To: marcs@znep.com (Marc Slemko) Date: Tue, 11 Aug 1998 13:45:22 -0700 (PDT) Cc: 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 > On Tue, 11 Aug 1998, Stephane Eranian wrote: > > > Hi, > > > > I recently notice that when you get a new connection on a listen > > socket the flags for the "master socket" simply vanish from the cloned > > socket (service socket). This is really annoying for flags like > > TCP_NODELAY, ie TF_NODELAY (ie user-settable flags via setsockopt()). > > The traditional behaviour (not just FreeBSD) has been that only SO_DEBUG, > SO_DONTROUTE, SO_KEEPALIVE, SO_LINGER, SO_OOBINLINE, SO_RCVBUF and > SO_SNDBUF are inherited. > > A program shouldn't expect others to be inherited, although this is > somewhat ill-defined by the specs. I don't think it is really the good behavior or you have many bogus Oses out there: like Linux, HPUX9/10/11 ... (not to say that they are the best, but). By the way, what is the specs you refering to ? +--------------------------------------------------------------------+ | Ste'phane ERANIAN | Email eranian@hpl.hp.com | | Hewlett-Packard Laboratories | | | 1501, Page Mill Road MS 1U-15 | | | Palo Alto, CA 94303-096 | | | USA | | | Tel : (650) 857-7174 | | | Fax : (650) 857-5548 | | +--------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 13:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02747 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 13:52:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02719; Tue, 11 Aug 1998 13:52:41 -0700 (PDT) (envelope-from volf@oasis.IAEhv.nl) Received: from oasis.IAEhv.nl (uucp@localhost) by news.IAEhv.nl (8.8.8/1.63) with IAEhv.nl; pid 24101 on Tue, 11 Aug 1998 20:52:14 GMT; id UAA24101 efrom: volf@oasis.IAEhv.nl; eto: UNKNOWN Received: from LOCAL (volf@localhost) by avalon.oasis.IAEhv.nl (8.8.8/1.63); pid 914 on Tue, 11 Aug 1998 20:51:07 GMT; id UAA00914 efrom: volf; eto: UNKNOWN From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199808112051.UAA00914@avalon.oasis.IAEhv.nl> Subject: File permissions in CVS tree obtained using CTM To: freebsd-hackers@FreeBSD.ORG Date: Tue, 11 Aug 1998 22:51:07 +0200 (CEST) Cc: wosch@FreeBSD.ORG, volf@oasis.IAEhv.nl (Frank Volf) 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 Hi, After a discussion with Wolfram Schneider I was wondering about the following: It appears that the CVS tree has some perl scripts (typically in the www subtree) with the execute permissions on. People that use CVSUP to update a local copy of the CVS tree, seem to preserve these permissions on their local CVS copy. However, I use CTM to obtain a copy of the CVS tree, and in my case the permissions are not preserved (in fact, all files in my CVS tree have file mode 664). I'm wondering if this is a problem in my setup (e.g. I have set the wrong umask or something) or that this is a generic problem with CTM? A more theoretical question would be: can we safely rely on the file permissions on the CVS tree, or should we take precautions (in this case use the Makefile to set execute permissions on the checkout files, before running them). Regards, Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 14:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07264 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 14:21:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07256 for ; Tue, 11 Aug 1998 14:21:47 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA14076 for ; Tue, 11 Aug 1998 17:21:22 -0400 (EDT) Date: Tue, 11 Aug 1998 17:21:19 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: hackers@FreeBSD.ORG Subject: Re: KERNFS and MFS In-Reply-To: <199808112004.PAA27235@bright.fx.genx.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'm having a problem with MFS: now that I've switched /usr/obj and /tmp over, I can't seem to make it through a make world: --- tclsh --- cc -O2 -I/usr/obj/usr/src/tmp/usr/include/tcl -I/usr/obj/usr/src/tmp/usr/include -o tclsh tclAppInit.o -ltcl -lm *** Signal 11 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error The console has a message from the swap pager suggesting that 190 MB isn't enough. Also a message from the kernel telling me that sh exited on signal 11. Now, I have two swap partitions of 98 megs apiece, with /tmp on one and /usr/obj on the other. I suppose my MFS filesystems shouldn't be more than 98 megs (I have /usr/obj at 256 megs now, which is what I believe the problem is)? That won't be large enough for /usr/obj, of course. Is there any workaround besides repartitioning with a larger swap area, or going back to a standard /usr/obj? Also, does anyone know how compiling without -pipe interacts with MFS? I wonder if MFS is faster or slower than piping. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 14:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08567 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 14:28:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08550 for ; Tue, 11 Aug 1998 14:28:11 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id RAA00614 for ; Tue, 11 Aug 1998 17:25:33 -0400 (EDT) (envelope-from billf@jade.chc-chimes.com) Date: Tue, 11 Aug 1998 17:25:33 -0400 (EDT) From: Bill Fumerola To: freebsd-hackers@FreeBSD.ORG Subject: Re: ident2 (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 Just a little background, I'm trying to port a program called 'ident2' which allows for passthrough ident for those who run ip masq. and also allows userland control of ident replys (optionally). Linux tracks things differently then FreeBSD so perhaps you could read the message I got from the author of the program and help me/him out a bit, as it seems to be over my head. ---------- Forwarded message ---------- Date: Tue, 11 Aug 1998 15:54:13 -0400 (EDT) From: Michael Bacarella To: Bill Fumerola Subject: Re: ident2 > I gotta run so this is going to be brief. > > I am a FreeBSD porting type person. Your program cores when it's run by > inetd in freebsd, I don't know if you knew this. > > Aug 10 22:52:41 jade in.ident2[6926]: error reading /proc/net/tcp: No such > file or directory > Aug 10 22:52:41 jade /kernel: pid 6926 (ident2), uid 0: exited on signal > 11 > > I'm using tcpd (tcp wrappers) to run it, and I haven't checked if that > makes a difference. but I KNOW there is no '/proc/net' in freebsd. Ah yes, it currently won't work with FreeBSD since it doesn't store connection information in /proc/net. If you want that kind of information you'd have to thumb through /dev/kmem. I have no idea how to do this, (well, I have some idea, but I need to find the correct offset to do it from. If you could figure out how to get the offset for TCP/IP connections, I could write a port). Other than that, not much I can do. --Michael Bacarella To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 14:43:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10841 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 14:43:30 -0700 (PDT) (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 OAA10836 for ; Tue, 11 Aug 1998 14:43:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01186; Tue, 11 Aug 1998 14:40:42 -0700 (PDT) Message-Id: <199808112140.OAA01186@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dmlb@ragnet.demon.co.uk cc: Stefan Bethke , freebsd-hackers@FreeBSD.ORG Subject: Re: Network stack assumptions In-reply-to: Your message of "Tue, 11 Aug 1998 16:55:12 -0000." <199808111555.IAA02273@mailgate.cadence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Aug 1998 14:40:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, can the kernel cope with a device hanging off a USB port or > integrated into the motherboard or a PCI card which provides wireless > LAN capabilities with mutliple protocols running on it? Not as it stands, no. By this I mean that we have no protocol support for these devices, however the infrastructure is there to handle this. > Asynchronous data is 802.11 style, isochronous data is DECT sytle for > SWAP, can't remember the protocols for Bluetooth. They will support a > number of concurrent voice calls between handsets/apps software on > your PC along with LAN activity (i.e. wireless printing from your > laptop). We would need extra code to handle these protocols. > In some instances the FreeBSD box will have to be a some form of > controller which manages the routing of the network. > > [tutorial snipped]. Sorry, I meant the device driver and network > stack framework! Device drivers, no. Networking infrastructure, yes. -- \\ 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 Aug 11 16:02:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23210 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 16:02:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23180 for ; Tue, 11 Aug 1998 16:02:12 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA25098 for hackers@freebsd.org; Tue, 11 Aug 1998 19:04:58 -0400 From: Bill Paul Message-Id: <199808112304.TAA25098@skynet.ctr.columbia.edu> Subject: PCI BIOSes and power management To: hackers@FreeBSD.ORG Date: Tue, 11 Aug 1998 19:04:57 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question which I'm somebody familiar with PCI issues might be able to answer. I recently ran into an unusual problem with the 3c905B driver. The 905B (unlike the 905) supports power management. There's a 'CapID' register in the PCI register space of the 3c905B ASIC which indicates that the device supports power manament, and there are also Power Management Control and Power Management Status registers. The 3c905B supports a couple of different power states: D0 'full power' mode; normal NIC operating mode D1 'light sleep' mode D2 Partial power down (still responds to PCI config accesses) D3(hot) Full power down state (loses PCI config info) D3(cold) Power off state (i.e. card unplugged or system turned off) When the NIC is in the D3(hot) state, it loses all of its PCI configuration settings except the value of the power state register. The NIC responds to PCI configuration accesses so that the power mode can be changed back to D0 for normal operation. My understanding is that the PCI BIOS is supposed to set the device back to the D0 state prior to configuring it. Normally I wouldn't care about this, however the Lose95/98/NT 3c905B drivers appear to place the NIC in the D3(hot) state during shutdown. This can cause the following sequence of events: - User has a dual-boot system with Lose95/98/NT and FreeBSD installed. - User boots Lose95/98/NT and fiddles for a while. - User gets tired of listening to disk thrash and selects 'Shutdown and restart' from the Shutdown menu. - Lose95/98/NT places 3c905B NIC in D3(hot) power down state. - Machine warm boots. - PCI BIOS goes out and starts configuring PCI devices. - PCI BIOS, apparently not being clever enough to know how to deal with power management capable devices, fails to set the NIC back to the D0 state. - PCI BIOS tries to configure adapter but fails because the NIC doesn't preserve PCI config data in the D3(hot) state. - System finishes its startup regimen, brings up boot mangler prompt. - User selects FreeBSD, kernel loads and probes for devices. - XL driver detects a card, but pukes with the following error: xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 36 int a irq 10 on pci0:9:0 mapreg[10] type=1 addr=0000d400 size=0080. mapreg[14] type=0 addr=e6000000 size=0080. xl0: chip is in D3 power mode -- setting to D0 int line register not set by bios xl0: couldn't map interrupt The 'setting to D0' message comes from the driver trying to set the card back to a usable state, which it can do, however it's still not properly configured. Now that the chip is back in the D0 state, warm booting again will allow the PCI BIOS to correctly configure the NIC. Cold booting the system would also fix the problem. My question is: is it possible to get the card programmed correctly during the attach routine, and if so, how? I don't see any way to get the BIOS to reconfigure the device once the OS is running, and I don't think the driver is supposed to do it. Does anybody know the correct way to deal with this? It's a minor problem as long as you don't mind cold starting your machine after running an M$ operating system, or if you don't run one to begin with, but I'd like to find a way to solve this if possible. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 16:18:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25333 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 16:18:29 -0700 (PDT) (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 QAA25321 for ; Tue, 11 Aug 1998 16:18:26 -0700 (PDT) (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 IAA15006; Wed, 12 Aug 1998 08:47:56 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id IAA24967; Wed, 12 Aug 1998 08:47:41 +0930 (CST) Message-ID: <19980812084741.G22754@freebie.lemis.com> Date: Wed, 12 Aug 1998 08:47:41 +0930 From: Greg Lehey To: Tamiji Homma Cc: hackers@FreeBSD.ORG Subject: Re: AMD-specific kernel code (was: How long a wait?) References: <19980811130910.Q20188@freebie.lemis.com> <19980811081637E.thomma@baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980811081637E.thomma@baynetworks.com>; from Tamiji Homma on Tue, Aug 11, 1998 at 08:16:37AM -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 Tuesday, 11 August 1998 at 8:16:37 -0700, Tamiji Homma wrote: > Greg, > > I tried K6 write-allocation patch last night. Here is the result > of make buidlworld (about 10 days old) > > PA-2007, K6-300(75MHz x 4.5), IBM UW 4(9ES)/NCR875. > > 2856.7 999.0 1:04:53.13 98.8% 826+918k 36516+37325io 3263pf (without patch) > 2827.3 970.7 1:05:01.36 97.3% 832+923k 41049+40435io 3217pf (with patch) Interesting. You get less CPU time in both user and system, yet slightly longer compile times. Strange. I still don't think that make world is the best test of this facility. It would be nice to see something more like the "web server" scenario. Greg -- See complete headers for address 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 Aug 11 17:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04842 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 17:12:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from the.oneinsane.net (gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04835 for ; Tue, 11 Aug 1998 17:12:46 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id RAA16395 for freebsd-hackers@freebsd.org; Tue, 11 Aug 1998 17:12:04 -0700 (PDT) Message-ID: <19980811171204.A16317@oneinsane.net> Date: Tue, 11 Aug 1998 17:12:04 -0700 From: "Ron 'The Insane One' Rosson" To: freebsd-hackers@FreeBSD.ORG Subject: Re: EXA 8200 tape drive on FreeBSD? Mail-Followup-To: freebsd-hackers@freebsd.org References: <199808110035.TAA00818@nospam.hiwaay.net> <199808111811.UAA00917@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808111811.UAA00917@yedi.iaf.nl>; from Wilko Bulte on Tue, Aug 11, 1998 at 08:11:46PM +0200 X-Operating-System: FreeBSD the.oneinsane.net 2.2.6-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The below is hwat I use without problem. We also have one attatched to a ncr controller as well. Try this to see if your 8200 works tar -cvf - . |dd of=/dev/rst0 bs=10k Here is what my dmesg has. ahc0 rev 1 int a irq 9 on pci0:18:0 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs (ahc0:5:0): "EXABYTE EXB-8200 2618" type 1 removable SCSI 1 On Tue, Aug 11, 1998 at 08:11:46PM +0200, Wilko Bulte wrote: > As David Kelly wrote... > > Stefan Esser writes: > > > On 1998-08-09 17:32 +0200, Peter van Heusden w > > > rote: > > > > However, I cannot write to it at all - even after a 'mt erase', I get the > > > > following: > > > > > > > > bash# mt rewind > > > > bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 > > > > dd: /dev/nrst0: Input/output error > > > > 1+0 records in > > > > 0+0 records out > > > > 0 bytes transferred in 0.082043 secs (0 bytes/sec) > > > > bash# > > > > > > Did you try shorter transfers (less than 64KB blocks) ? > > > > > > I seem to remember, that the EXABYTE 8200 was limited to > > > less than 64KB per block (i.e. 63KB works, but 64KB doesn't). > > > > "bs=64" spells out 64 byte blocks, not 64k. "bs=64k" would be 64k. > > > > There might be a problem with the block being too small. :-) > > > > SGI Irix defaults to 128k blocks on Exabyte 8mm drives, including the > > 8200. Its FreeBSD that won't (can't) do more than 64k. > > I think the 8200 uses 1 kB blocks itself by default. > > > As others have mentioned, when a new (new to you) Exabyte drive acts > > flaky its time to flash the EEPROMs or burn new EPROMs for the old 8200. > > I too have a new-to-me 8200 that ID's, rewinds, retensions, ejects, and > > all that good stuff. But doesn't work. If new EPROMs don't fix it, then > > its junk. That too is standard failure mode for an Exabyte. > > Exabytes are not the most robust of devices yes.. > > _ ______________________________________________________________________ > | / 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 -- -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 17:12:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04848 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 17:12:56 -0700 (PDT) (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 RAA04826; Tue, 11 Aug 1998 17:12:42 -0700 (PDT) (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 JAA15199; Wed, 12 Aug 1998 09:42:16 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA25142; Wed, 12 Aug 1998 09:42:15 +0930 (CST) Message-ID: <19980812094215.L22754@freebie.lemis.com> Date: Wed, 12 Aug 1998 09:42:15 +0930 From: Greg Lehey To: Wilko Bulte , David Kelly Cc: se@FreeBSD.ORG, pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG Subject: Re: EXA 8200 tape drive on FreeBSD? References: <199808110035.TAA00818@nospam.hiwaay.net> <199808111816.UAA01048@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808111816.UAA01048@yedi.iaf.nl>; from Wilko Bulte on Tue, Aug 11, 1998 at 08:16:58PM +0200 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, 11 August 1998 at 20:16:58 +0200, Wilko Bulte wrote: > As David Kelly wrote... >> Stefan Esser writes: >>> On 1998-08-09 17:32 +0200, Peter van Heusden w >>> rote: >>>> However, I cannot write to it at all - even after a 'mt erase', I get the >>>> following: >>>> >>>> bash# mt rewind >>>> bash# dd if=/kernel of=/dev/nrst0 bs=64 count=1024 >>>> dd: /dev/nrst0: Input/output error >>>> 1+0 records in >>>> 0+0 records out >>>> 0 bytes transferred in 0.082043 secs (0 bytes/sec) >>>> bash# > > On mine: > > su-2.01# dd if=/kernel of=/dev/nrst1 bs=64 count=1024 > 1024+0 records in > 1024+0 records out > 65536 bytes transferred in 5.187031 secs (12635 bytes/sec) > su-2.01# > > Why you want to use 64 byte blocks escapes me because: > > su-2.01# dd if=/kernel of=/dev/nrst1 bs=64k count=1024 > 17+1 records in > 17+1 records out > 1176833 bytes transferred in 11.385549 secs (103362 bytes/sec) > > A 8200 native speed is something like 240kb/sec if I remember well. Right. Measuring something as small as a kernel is not a good way to measure Exabyte speed, because the things spend an eternity to decide whether they're going to start or not. Greg -- See complete headers for address 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 Aug 11 18:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14570 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 18:06:44 -0700 (PDT) (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 SMTP id SAA14549 for ; Tue, 11 Aug 1998 18:06:38 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from (ragnet.demon.co.uk) [158.152.46.40] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0z6PMc-0003Co-00; Wed, 12 Aug 1998 01:06:07 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0z6O5u-0004EF-00; Wed, 12 Aug 1998 00:44:46 +0100 Message-ID: X-Mailer: XFMail 1.2 [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: <199808112140.OAA01186@dingo.cdrom.com> Date: Wed, 12 Aug 1998 00:44:46 +0100 (BST) From: Duncan Barclay To: Mike Smith Subject: Re: Network stack assumptions Cc: freebsd-hackers@FreeBSD.ORG, Stefan Bethke Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Aug-98 Mike Smith wrote: >> Okay, can the kernel cope with a device hanging off a USB port or >> integrated into the motherboard or a PCI card which provides wireless >> LAN capabilities with mutliple protocols running on it? > > Not as it stands, no. By this I mean that we have no protocol support > for these devices, however the infrastructure is there to handle this. Good, I brought it up as there was a section in the SWAP spec. where mumble company said their new OS doesn't have this capability. >> Asynchronous data is 802.11 style, isochronous data is DECT sytle for >> SWAP, can't remember the protocols for Bluetooth. They will support a >> number of concurrent voice calls between handsets/apps software on >> your PC along with LAN activity (i.e. wireless printing from your >> laptop). > > We would need extra code to handle these protocols. Sure, I don't know how the voice stuff is meant to work from the point of view of a computer as one end of a call. >> In some instances the FreeBSD box will have to be a some form of >> controller which manages the routing of the network. >> >> [tutorial snipped]. Sorry, I meant the device driver and network >> stack framework! > > Device drivers, no. Networking infrastructure, yes. Well as the spec. isn't finished for SWAP no has anything anyway, Bluetooth is a bit different as there is a complete spec. from one of the core companies, but this is likely to change as more people get involved. These technologies aren't going to hit the streets for a couple of years yet and as they are literally industry standards who knows how "Open" they will be. Lets hope that we don't get into an I2O situtation. Duncan > -- > \\ 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 --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 19:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28883 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 19:30:13 -0700 (PDT) (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 TAA28794 for ; Tue, 11 Aug 1998 19:30:05 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA07017; Tue, 11 Aug 1998 19:29:40 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd006996; Tue Aug 11 19:29:34 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA05799; Tue, 11 Aug 1998 19:29:31 -0700 (MST) From: Terry Lambert Message-Id: <199808120229.TAA05799@usr01.primenet.com> Subject: Re: Question about shutdown To: mag@h26.216.elnet.msk.ru (MAG) Date: Wed, 12 Aug 1998 02:29:31 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <35D03F68.69837C2A@magc.cd.2573.savbank.ru> from "MAG" at Aug 11, 98 04:56:08 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 have written an UPS monitor daemon. But I cannot decide where the > "Turn the UPS power off" command > must be (I tryed /etc/rc.shutdown, but the filesystems were improperly > dismounted, reboot, halt and shutdown > commands do not call /etc/rc.shutdown, etc...). > Who can help me? The correct place is the kernel, unless you have a time delay. For UPS's designed to work with user space daemons, there is typically a time argument, ie: "PWROFF 60" -- shut off power 60 seconds after I give you this command. One way to fake the kernel doing the job at the right time in rc.shutdown: 1) Shutdown all the processes, like shutdown will want to do anyway. 2) Unmount all the FS's except /. 3) remount / as read-only 4) sync the crap out of things (in fact, 3 sync's are required as of the soft updates code, since the dependency graph can be three deep; it may also be worthwhile to wait 40 seconds to allow the syncd to empty the soft clocked I/O queue). 5) Power the ups off. Only FS's mounted read/write will be dirty (which should mean "none of them"). NB: Your ups control code will have to live in /sbin or /bin, since /usr was unmounted. You may also have to modify shutdown to refuse to shutdown if your cwd is not root, since your shell may hold an FS open otherwise (standard unmount is not as forceful as the shutdown, which will give up attempting to write after a while, and simply discard dirty buffers). 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 Aug 11 19:38:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00652 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 19:38:00 -0700 (PDT) (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 TAA00640 for ; Tue, 11 Aug 1998 19:37:58 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA11061; Tue, 11 Aug 1998 19:37:33 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd011014; Tue Aug 11 19:37:27 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA06284; Tue, 11 Aug 1998 19:37:15 -0700 (MST) From: Terry Lambert Message-Id: <199808120237.TAA06284@usr01.primenet.com> Subject: Re: Question about shutdown To: walter@fortean.com (Bruce M. Walter) Date: Wed, 12 Aug 1998 02:37:15 +0000 (GMT) Cc: billf@chc-chimes.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Bruce M. Walter" at Aug 11, 98 11:56:24 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 > 1) It requires a kernel patch to perform "safe" shutdowns... This is > because of the way other drivers use the at_shutdown interface and > these patches should first be part of the system. Even if nothing > ever comes of my code, the capacity still exists for a program to > assume it can poweroff when it really can't. If I remember correctly, this patch was to specify that your driver got called last. I think the more correct way to do this would be to call all of the shutdowns once, with (arg & ~RB_POWEROFF), then again with RB_POWEROFF only (presuming arg & RB_POWEROFF == RB_POWEROFF). Alternately, there needs to be an "at_powerdown()", seperate from the "at_shutdown()". I have no idea how you would, without a timer, resolve the UPS vs. APM powerdown issues... 8-(. My gut feeling is that it's important to power the UPS down because of ATX having a slow drain to support the soft poweron power supply (ATX have two supplies in one case). On the other hand, "suspend to disk" needs the APM called, which means suspending the UPS daemon... 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 Aug 11 19:43:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02208 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 19:43:52 -0700 (PDT) (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 TAA02175 for ; Tue, 11 Aug 1998 19:43:40 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA23957; Tue, 11 Aug 1998 19:43:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd023887; Tue Aug 11 19:43:04 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA06610; Tue, 11 Aug 1998 19:43:02 -0700 (MST) From: Terry Lambert Message-Id: <199808120243.TAA06610@usr01.primenet.com> Subject: Re: KERNFS and MFS To: ben@rosengart.com Date: Wed, 12 Aug 1998 02:43:01 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Aug 11, 98 05:21:19 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 console has a message from the swap pager suggesting that 190 MB > isn't enough. Also a message from the kernel telling me that sh exited > on signal 11. This is the "you've been out of swap, now you must restart things" bug. It is definitely a bug, since you are no longer out of swap. > Also, does anyone know how compiling without -pipe interacts with MFS? > I wonder if MFS is faster or slower than piping. Pipe is faster; it avoids the VFS code. 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 Aug 11 19:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03478 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 19:52:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03471 for ; Tue, 11 Aug 1998 19:52:19 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id WAA07251; Tue, 11 Aug 1998 22:51:47 -0400 (EDT) Date: Tue, 11 Aug 1998 22:51:46 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: KERNFS and MFS In-Reply-To: <199808120243.TAA06610@usr01.primenet.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, 12 Aug 1998, Terry Lambert wrote: > > The console has a message from the swap pager suggesting that 190 MB > > isn't enough. Also a message from the kernel telling me that sh exited > > on signal 11. > > This is the "you've been out of swap, now you must restart things" bug. > > It is definitely a bug, since you are no longer out of swap. What's also definitely a bug is the way sendmail died on signal 11 about every fifteen minutes thereafter, until I killed it normally and restarted it. > > Also, does anyone know how compiling without -pipe interacts with MFS? > > I wonder if MFS is faster or slower than piping. > > Pipe is faster; it avoids the VFS code. Thanks. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 11 21:38:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17472 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 21:38:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p139.tfs.net [139.146.210.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17450 for ; Tue, 11 Aug 1998 21:38:12 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id XAA12411 for freebsd-hackers@freebsd.org; Tue, 11 Aug 1998 23:37:35 -0500 (CDT) From: Jim Bryant Message-Id: <199808120437.XAA12411@unix.tfs.net> Subject: solaris is free. To: freebsd-hackers@FreeBSD.ORG Date: Tue, 11 Aug 1998 23:37:34 -0500 (CDT) 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 haven't seen any traffic on this list concerning this, but this is interesting. sun, the day before yesterday has made solaris for both x86 and sparc free [shipping and handling like $10], for personal use. see the sun web page for info, and follow up to this message on -chat. 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 Tue Aug 11 21:42:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18187 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 21:42:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn1-tnt13-3.detroit.mi.ameritech.net [199.179.188.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18159 for ; Tue, 11 Aug 1998 21:42:11 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id AAA01625 for ; Wed, 12 Aug 1998 00:41:40 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35D11D02.BEBAEFD5@ameritech.net> Date: Wed, 12 Aug 1998 00:41:38 -0400 From: Adam McDougall X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: KERNFS and MFS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't it true that a mount_mfs never releases the memory allocated by writing files inside a mfs? This seemed to be the case when I used to use it for /tmp, and I stopped using it because it would continue to bog things down even after the files were erased from it. Remounting the partition, however, released the memory. Snob Art Genre wrote: > > I think I've got it: > > /dev/sd0b /tmp mfs rw,-s=131072 0 0 > /dev/sd1b /usr/obj mfs rw,-s=524288 0 0 > > Now I'm just wondering if I should leave these mounted async, per the > default, or whether I should try to get softupdates running on them. Is > that possible, and would it make sense? > > On Tue, 11 Aug 1998, Alfred Perlstein wrote: > > > heh, wasn't able to figure out the format in fstab so i have a "hack" > > in rc.local: > > > > echo 'mounting mfs /tmp.' > > mount_mfs -s 160000 -o nosuid,nodev /dev/wd0s3b /tmp > > > > /dev/wd0s3b is my swap partition. > > > > if anyone would document this better..... i'd appreciate knowing a "real" way to do this. > > > > thanks. > > Alfred > > > > Ben > > "You have your mind on computers, it seems." > > 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 Aug 12 00:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09316 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 00:30:44 -0700 (PDT) (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 AAA09309 for ; Wed, 12 Aug 1998 00:30:42 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA06271; Wed, 12 Aug 1998 09:30:01 +0200 (MET DST) Date: Wed, 12 Aug 1998 09:29:57 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Greg Lehey cc: Tamiji Homma , hackers@FreeBSD.ORG Subject: Re: AMD-specific kernel code (was: How long a wait?) In-Reply-To: <19980812084741.G22754@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 > > 2856.7 999.0 1:04:53.13 98.8% 826+918k 36516+37325io 3263pf (without patch) > > 2827.3 970.7 1:05:01.36 97.3% 832+923k 41049+40435io 3217pf (with patch) > > Interesting. You get less CPU time in both user and system, yet > slightly longer compile times. Strange. slow disk... Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 00:32:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09731 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 00:32:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09711 for ; Wed, 12 Aug 1998 00:32:36 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA22393 for ; Wed, 12 Aug 1998 09:32:10 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA25850 for ; Wed, 12 Aug 1998 09:32:10 +0200 (MET DST) Received: (qmail 4276 invoked by uid 666); 12 Aug 1998 07:30:08 -0000 Message-ID: <19980812093008.A4232@hal.mpn.cp.philips.com> Date: Wed, 12 Aug 1998 09:30:08 +0200 From: Jos Backus To: Tor.Egge@fast.no Cc: hackers@FreeBSD.ORG Subject: Re: system shitdown using mount References: <199806101453.QAA09941@pat.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199806101453.QAA09941@pat.idi.ntnu.no>; from Tor.Egge@fast.no on Wed, Jun 10, 1998 at 04:53:44PM +0200 X-Files: The Truth is out there! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Tor, all, On Wed, Jun 10, 1998 at 04:53:44PM +0200, Tor.Egge@fast.no wrote: > /mnt was locked while ffs_mount tried to lookup /mnt/foo. This probably > caused a panic in ufs_lock, since a recursive lock on /mnt was not expected. > > This behavior is also present in 3.0-CURRENT. I'm using the following > patch (for 3.0-CURRENT), after having made a similar mistake with > the mount command (I forgot to specify the '-t null' option). [patch elided] I am trying to move my FreeBSD partition from sd1 to sd0. Before applying this patch, when creating the slice and labeling and newfsing it using sysinstall the system would die with a 'locking against myself' type panic. Upon inspection the slice definition would be OK but the label would be invalid (I tried this using a boot floppy, too). Therefore I wasn't able to proceed any further with the migration. However, after applying this patch, the label at least survives the ensuing 'vrele: negative ref cnt' panic (sys/kern/vfs_subr.c(1348))), and while the filesystems apparently aren't set up properly (fsck complains about a bad magic number in the superblock), I can newfs the partitions without problems. So it looks like I will be able to migrate to sd0 after all *grin* Of course, I guess the panic happening is Bad Thing. If there's anything I can do to help fix this problem, please let me know. I can summon it at will :) In the meantime, thank you for the patch! Groetjes, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 00:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12288 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 00:49:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA12280 for ; Wed, 12 Aug 1998 00:49:21 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z6VeS-0004kY-00; Wed, 12 Aug 1998 01:48:56 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id BAA05604; Wed, 12 Aug 1998 01:50:24 -0600 (MDT) Message-Id: <199808120750.BAA05604@harmony.village.org> To: jbryant@unix.tfs.net Subject: Re: solaris is free. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Aug 1998 23:37:34 CDT." <199808120437.XAA12411@unix.tfs.net> References: <199808120437.XAA12411@unix.tfs.net> Date: Wed, 12 Aug 1998 01:50:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808120437.XAA12411@unix.tfs.net> Jim Bryant writes: : sun, the day before yesterday has made solaris for both x86 and sparc : free [shipping and handling like $10], for personal use. Is it personal use or educational use? My reading of the pages earlier in the week suggested the latter. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 00:58:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13875 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 00:58:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles196.castles.com [208.214.165.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13858 for ; Wed, 12 Aug 1998 00:58:31 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA01257; Wed, 12 Aug 1998 00:56:35 -0700 (PDT) Message-Id: <199808120756.AAA01257@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Duncan Barclay cc: Mike Smith , freebsd-hackers@FreeBSD.ORG, Stefan Bethke Subject: Re: Network stack assumptions In-reply-to: Your message of "Wed, 12 Aug 1998 00:44:46 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 00:56:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 11-Aug-98 Mike Smith wrote: > >> Okay, can the kernel cope with a device hanging off a USB port or > >> integrated into the motherboard or a PCI card which provides wireless > >> LAN capabilities with mutliple protocols running on it? > > > > Not as it stands, no. By this I mean that we have no protocol support > > for these devices, however the infrastructure is there to handle this. > > Good, I brought it up as there was a section in the SWAP spec. where mumble > company said their new OS doesn't have this capability. Our stack is designed for multiple protocols, and the infrastructure exists for connection-oriented and connectionless application interfaces. > These technologies aren't going to hit the streets for a couple of years yet and > as they are literally industry standards who knows how "Open" they will be. Lets > hope that we don't get into an I2O situtation. Indeed; I expect these standards to go somewhere. -- \\ 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 Aug 12 01:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16068 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 01:09:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA16061 for ; Wed, 12 Aug 1998 01:09:30 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0z6VwY-00021s-00; Wed, 12 Aug 1998 01:07:38 -0700 Date: Wed, 12 Aug 1998 01:07:38 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Warner Losh cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: <199808120750.BAA05604@harmony.village.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 Perhaps better taken to -chat? On Wed, 12 Aug 1998, Warner Losh wrote: > In message <199808120437.XAA12411@unix.tfs.net> Jim Bryant writes: > : sun, the day before yesterday has made solaris for both x86 and sparc > : free [shipping and handling like $10], for personal use. > > Is it personal use or educational use? My reading of the pages > earlier in the week suggested the latter. Both. Universities can get site license for educational stuff, users can get free copies for "non-commercial" stuff. The license terms for the non-commercial use are at: http://www.sun.com/developers/promoterms.html The relevant part: 1. License to Use. Sun grants to you a non-exclusive and non-transferable license to use the accompanying software and documentation and any error corrections provided by Sun (collectively "Software") for non-commercial purposes only. "Non-commercial" means personal and not use for commercial gain or in connection with business operations (such as MIS or other internal business systems). Note that this is only free in the sense that you can buy it for a low cost from Sun. You don't get source. You don't get the ability to give copies to other people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 01:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21708 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 01:47:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21696 for ; Wed, 12 Aug 1998 01:47:01 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id BAA16644; Wed, 12 Aug 1998 01:46:14 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980812014614.B16463@mooseriver.com> Date: Wed, 12 Aug 1998 01:46:14 -0700 From: Josef Grosch To: Marc Slemko , Warner Losh Cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. Reply-To: jgrosch@mooseriver.com References: <199808120750.BAA05604@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Marc Slemko on Wed, Aug 12, 1998 at 01:07:38AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 12, 1998 at 01:07:38AM -0700, Marc Slemko wrote: > Perhaps better taken to -chat? > > On Wed, 12 Aug 1998, Warner Losh wrote: > > > In message <199808120437.XAA12411@unix.tfs.net> Jim Bryant writes: > > : sun, the day before yesterday has made solaris for both x86 and sparc > > : free [shipping and handling like $10], for personal use. > > > > Is it personal use or educational use? My reading of the pages > > earlier in the week suggested the latter. > > Both. > > Universities can get site license for educational stuff, users can get > free copies for "non-commercial" stuff. > > The license terms for the non-commercial use are at: > > http://www.sun.com/developers/promoterms.html > > The relevant part: > > 1. License to Use. Sun grants to you a non-exclusive and > non-transferable license to use the accompanying software and > documentation and any error corrections provided by Sun (collectively > "Software") for non-commercial purposes only. "Non-commercial" means > personal and not use for commercial gain or in connection with business > operations (such as MIS or other internal business systems). > > Note that this is only free in the sense that you can buy it > for a low cost from Sun. > > You don't get source. > > You don't get the ability to give copies to other people. My guess is that Sun is beginning to feel the heat from FreeBSD and Linux. Last time I looked very few people we running Solaris on X86. Mayby they are starting to worry about all those older Sparc's running NetBSD. Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 02:07:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24507 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 02:07:32 -0700 (PDT) (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 CAA24502 for ; Wed, 12 Aug 1998 02:07:28 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id LAA09209; Wed, 12 Aug 1998 11:06:29 +0200 (MET DST) Date: Wed, 12 Aug 1998 11:06:25 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Josef Grosch cc: FreeBSD hackers mailing list Subject: Re: solaris is free. In-Reply-To: <19980812014614.B16463@mooseriver.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 > > Note that this is only free in the sense that you can buy it > > for a low cost from Sun. > > > > You don't get source. > > > > You don't get the ability to give copies to other people. > > My guess is that Sun is beginning to feel the heat from FreeBSD and > Linux. Last time I looked very few people we running Solaris on X86. Mayby > they are starting to worry about all those older Sparc's running NetBSD. To be honest, x86 SOlaris has always been a bit a forgotten child in the Sun family. Sun likes to ship complete systems they can reliably support. Giving supports to PC weenies is not one of their favourite hobbies. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 02:08:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24580 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 02:08:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24568 for ; Wed, 12 Aug 1998 02:07:54 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id JAA02426; Wed, 12 Aug 1998 09:07:23 GMT (envelope-from didier@omnix.net) Date: Wed, 12 Aug 1998 11:07:23 +0200 (CEST) From: Didier Derny To: support@yard.de cc: hackers@FreeBSD.ORG Subject: network problem with FreeBSD/Yard (yardnetd) 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, I've a strange problem with yard. A/ Symptoms/Investigation ------------------------- 1/ I was using yard with ESQL without yardnetd and everything worked fine. 2/ I started using DBI::YARD in perl (requires the use of yardnetd) then everything went wrong (I suppose that this problem is the same than for the odbc delay in september/october 1997). 3/ While using Yard from Perl on a very large and badly designed database, I'm only able to read 1 row /s even on a pentium II, with fasts disks. Everything was ok on the sql side, nothing in the logs except that Yard was extremely slow. 4/ I started to check everything in the Yard configuration to see if there was dome deadlock or lack of resources... Nothing! then I started to think that it was a network problem, so I checked everything on the BSD side (lo0). It worked fine. my conclusion was that yardnetd and perl/dbi were waiting each other due to a timeout somewhere. nothing in perl/dbi:yard. 5/ I started to check in the "demon book" "BSD 4.4 design and implementation" and discovered on pages 470/471 that the ACK could be delayed to avoid sending empty or almost empty packet. (the book was saying "bottom of page 471" that X11 was setting the TCP_NODELAY option to avoid this delay). 6/ I checked in freebsd (3.0 may) how I could disable this mechanism. I played with sysctl -a and discovered a ...ack_delayed=1 parameter and tried to put it to 0. (then everything worked fined with yard and the 8000 records database was (read/reorganized/reinserted) in a few seconds when it took hours before. 7/ I'm not using 3.0 at the office but 2.2.5 where this parameter is not present. so I made an awful hack replacing DELACK by ACKNOW in tcp_input.c and tcp_output.c. I got the same result and yard work. B/ Solution ? ------------- 1/ I suppose that a setsockopt(socket... TCP_NODELAY..) would have the same result for the yard application if it was inserted in the yard code ? 2/ what are the implication of setting ...ack_delayed=0 for the system ? 3/ What should I say to Yard to have this problem solved ? I hope that Yard will be able to sove this problem quickly, Yard is a very reliable and efficient database. Thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 02:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26854 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 02:22:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nighthawk.iti.gov.sg (nighthawk.iti.gov.sg [192.122.131.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA26785 for ; Wed, 12 Aug 1998 02:22:26 -0700 (PDT) (envelope-from joerg@krdl.org.sg) Received: (from mailer@localhost) by nighthawk.iti.gov.sg (8.6.11/8.6.11) id RAA29325; Wed, 12 Aug 1998 17:33:16 +0800 Received: from mailhub.iti.gov.sg(192.122.132.132) by nighthawk.iti.gov.sg via smap (V1.3) id sma029321; Wed Aug 12 17:33:06 1998 Received: (from joerg@localhost) by iti.gov.sg (8.8.8/8.8.5) id RAA12020; Wed, 12 Aug 1998 17:13:00 +0800 (SGT) Message-ID: <19980812171259.39906@krdl.org.sg> Date: Wed, 12 Aug 1998 17:12:59 +0800 From: Joerg Micheel To: jgrosch@mooseriver.com Cc: Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. References: <199808120750.BAA05604@harmony.village.org> <19980812014614.B16463@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980812014614.B16463@mooseriver.com>; from Josef Grosch on Wed, Aug 12, 1998 at 01:46:14AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 12, 1998 at 01:46:14AM -0700, Josef Grosch wrote: > > My guess is that Sun is beginning to feel the heat from FreeBSD and > Linux. Last time I looked very few people we running Solaris on X86. Mayby > they are starting to worry about all those older Sparc's running NetBSD. But too late. There was a proposal by Larry Wall back at the beginning of the 1990's to free SunOS source to prevent splitting of the R&D community into all these niches, but in vain. Still interesting reading, from a historical point of view. I need to see whether I still have the copy around somewhere. Joerg -- Joerg B. Micheel Email: SingAREN Technology Center Phone: +65 7705577 Kent Ridge Digital Labs (pron: curdle) Fax: +65 7795966 11 Science Park Road Pager: +65 96016020 Singapore Science Park II Plan: Troubleshooting ATM 117685 Singapore Networks and Applications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 02:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28422 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 02:30:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28375 for ; Wed, 12 Aug 1998 02:30:18 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id CAA17053; Wed, 12 Aug 1998 02:29:37 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980812022936.A16972@mooseriver.com> Date: Wed, 12 Aug 1998 02:29:37 -0700 From: Josef Grosch To: Nick Hibma Cc: FreeBSD hackers mailing list Subject: Re: solaris is free. Reply-To: jgrosch@mooseriver.com References: <19980812014614.B16463@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Wed, Aug 12, 1998 at 11:06:25AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 12, 1998 at 11:06:25AM +0200, Nick Hibma wrote: > > > Note that this is only free in the sense that you can buy it > > > for a low cost from Sun. > > > > > > You don't get source. > > > > > > You don't get the ability to give copies to other people. > > > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > they are starting to worry about all those older Sparc's running NetBSD. > > To be honest, x86 SOlaris has always been a bit a forgotten child in the > Sun family. Given the speed of Solaris on x86 I'm not surprised. When I was contracting at Sun earlier this year I went around installing FreeBSD on machines that were running Solaris. Even hard core Sun people were surprised at how much faster FreeBSD ran. > Sun likes to ship complete systems they can reliably > support. Giving supports to PC weenies is not one of their favourite > hobbies. Yes, Sun is used to having decent hardware. The dirty secret in this industry is that PC manufacturers have been getting away with murder for years. Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 02:44:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01269 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 02:44:09 -0700 (PDT) (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 CAA01264 for ; Wed, 12 Aug 1998 02:44:05 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id LAA10307 for ; Wed, 12 Aug 1998 11:43:39 +0200 (MET DST) Date: Wed, 12 Aug 1998 11:43:35 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: solaris is free. (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 > > Sun likes to ship complete systems they can reliably > > support. Giving supports to PC weenies is not one of their favourite > > hobbies. > > Yes, Sun is used to having decent hardware. The dirty secret in this > industry is that PC manufacturers have been getting away with murder for > years. We use here a RIP (a Rack with Inexpensive Pentium's). If one machine is loaded, you just move on to the next... I am at the moment logged into five of them. 2 internal networks. IF that is not fast enough we spend another 1000 ECU on another ethernet card and there we go again... Lovely way of working. Only installing the buggers is a bitch. But then again, you just by an extra in case you break one... Nah, I've done Solaris and I've done FreeBSD. FreeBSD is a lot more fun because it runs on cheaper hardware. Solaris sucks when installing software. Not a lot of people use packages. In contrast, nothing compares to the quality of the /usr/ports directory. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 04:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18059 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 04:47:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsd.synx.com (rt.synx.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA17983 for ; Wed, 12 Aug 1998 04:46:58 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn [192.1.1.241]) by bsd.synx.com (8.6.12/8.6.12) with ESMTP id MAA01217; Wed, 12 Aug 1998 12:44:03 +0100 Message-Id: <199808121144.MAA01217@bsd.synx.com> Date: Wed, 12 Aug 1998 13:43:58 +0200 (CEST) From: Remy NONNENMACHER Reply-To: remy@synx.com Subject: Re: network problem with FreeBSD/Yard (yardnetd) To: didier@omnix.net cc: support@yard.de, hackers@FreeBSD.ORG 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 On 12 Aug, Didier Derny wrote: > Hi, > > I've a strange problem with yard. > ..... > B/ Solution ? > ------------- > > 1/ I suppose that a setsockopt(socket... TCP_NODELAY..) > would have the same result for the yard application if it was > inserted in the yard code ? > no, TCP_NODELAY allows your local stack to immediatly send packets to peer without waiting for a ack. It's also called the Nagle algo. It is intented for applications sending a lot of small packets. Delaying send in this case is good since it allows the local stack to accumulate data and build bigger pakets. > 2/ what are the implication of setting ...ack_delayed=0 for the system ? > Delayed ack is the exact opposite. It allows the receiving side to delay acking received packets with the hope that a flowing back data (like a response to a query) would transports a piggy-backed ack. > 3/ What should I say to Yard to have this problem solved ? > Delayed ack and nagle are two solutions that must *NEVER* be face to face !!. Many programs uses TCP_NODELAY to turn off Nagle. In the worst case, (Nagle and delayed ack on, and depending on the behaviour of the flow), you can have each send delayed and each ack delayed. This means that your wonderfull 100Mb/s switched network can work as low as 1kb/s !!. Many programs uses the TCP_NODELAY to turn off Nagle. It's sufficient for communications where the receiving side immediatly send back a data packet. This doesn't correctly solves the problem for a one direction flow case. ack-delayed=0 using sysctl (or a '#define TCP_ACK_HACK' at beginning of tcp_input.c for old versions of 3.0) will turn off delayed ack. Even with Nagle on at the other side, this will greatly help since packet sending delaying will be limited only by the (flowing back ack) network roundtrip. The best performance is achieved this a carefull selection of what side uses what algorithm depending on the typical data flow. You can safely turn all two off if you have no problem of amount of packets exchanged. Only remember that delayed ack and Nagle off means that every packet will mostly generate an empty ack one. this can easily double the number of exchanges. As a rule of thumb, Nagle is interesting when you have very small packets flowing on one direction (ie: a badly written program that do a lot of small write()) and delayed-ack is interesting when the receiving side immediatly sends back a data packet in response (ie: an encapsulated protocol). Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 05:12:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20333 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 05:12:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20327 for ; Wed, 12 Aug 1998 05:12:39 -0700 (PDT) (envelope-from aflundi@lundin.abq.nm.us) Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.8.8/1.2.3) with ESMTP id GAA08805 for ; Wed, 12 Aug 1998 06:12:14 -0600 (MDT) Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.8.8/8.8.5) id GAA29528 for freebsd-hackers@freebsd.org; Wed, 12 Aug 1998 06:11:33 -0600 (MDT) Date: Wed, 12 Aug 1998 06:11:33 -0600 (MDT) From: Alan Lundin Message-Id: <199808121211.GAA29528@lundin.abq.nm.us.> In-Reply-To: Joerg Micheel "Re: solaris is free." (Aug 12, 5:12pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 12, 5:12pm, Joerg Micheel wrote: > Subject: Re: solaris is free. > > On Wed, Aug 12, 1998 at 01:46:14AM -0700, Josef Grosch wrote: > > > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > they are starting to worry about all those older Sparc's running NetBSD. > > But too late. There was a proposal by Larry Wall back at the beginning of the ^^^^^^^^^^ Opps! Larry McVoy > 1990's to free SunOS source to prevent splitting of the R&D community into all > these niches, but in vain. He was trying to get Sun to adopt Linux and do the GPL/OpenSource thing. He quit and went to SGI when Sun execs turned him down. --alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 06:25:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26683 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 06:25:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aries.fortean.com (aries.fortean.com [209.42.229.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26678 for ; Wed, 12 Aug 1998 06:25:27 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by aries.fortean.com (8.8.8/8.8.8) with SMTP id JAA16458; Wed, 12 Aug 1998 09:23:34 -0400 (EDT) (envelope-from walter@fortean.com) X-Authentication-Warning: aries.fortean.com: walter owned process doing -bs Date: Wed, 12 Aug 1998 09:23:33 -0400 (EDT) From: "Bruce M. Walter" To: Terry Lambert cc: billf@chc-chimes.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown In-Reply-To: <199808120237.TAA06284@usr01.primenet.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 > If I remember correctly, this patch was to specify that your driver > got called last. > > I think the more correct way to do this would be to call all of the > shutdowns once, with (arg & ~RB_POWEROFF), then again with RB_POWEROFF > only (presuming arg & RB_POWEROFF == RB_POWEROFF). This is certainly a better idea than prioritizing the lists... I had thought that prioritization of shutdown callouts might be useful for other things, but practically it's not. There's still no way to insure a specific callout executes last. > Alternately, there needs to be an "at_powerdown()", seperate from the > "at_shutdown()". I have no idea how you would, without a timer, > resolve the UPS vs. APM powerdown issues... 8-(. This was the primary reason I was 'pro-priorities'... IIRC, there are no flag bits left in the RB_* constants. Separating UPS and APM powerdown flags (and the above idea of spinning through the lists twice) should do the trick. I'll see what I can come up with. > My gut feeling is that it's important to power the UPS down because of > ATX having a slow drain to support the soft poweron power supply (ATX > have two supplies in one case). On the other hand, "suspend to disk" > needs the APM called, which means suspending the UPS daemon... On a side note, some UPS devices will not honor a powerdown request unless a powerfail is in effect. - Bruce ========================================================== || Bruce M. Walter || 426 South Dawson Street || || Principal || Raleigh, NC 27601 USA || || NIXdesign Group, Inc. || Tel: 919.829.4908 || || Concept + Code || Fax: 919.829.4993 || ========================================================== || BSD Unix -- It's not just a job, it's a way of life! || ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 06:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26829 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 06:27:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26824 for ; Wed, 12 Aug 1998 06:27:03 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id IAA19996; Wed, 12 Aug 1998 08:24:01 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id IAA17606; Wed, 12 Aug 1998 08:24:00 -0500 (CDT) Message-ID: <19980812082400.24443@mcs.net> Date: Wed, 12 Aug 1998 08:24:00 -0500 From: Karl Denninger To: jgrosch@mooseriver.com Cc: Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. References: <199808120750.BAA05604@harmony.village.org> <19980812014614.B16463@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980812014614.B16463@mooseriver.com>; from Josef Grosch on Wed, Aug 12, 1998 at 01:46:14AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 12, 1998 at 01:46:14AM -0700, Josef Grosch wrote: > My guess is that Sun is beginning to feel the heat from FreeBSD and > Linux. Last time I looked very few people we running Solaris on X86. Mayby > they are starting to worry about all those older Sparc's running NetBSD. Frankly, FreeBSD + Afterstep on a Pentium Pro 200 makes a damn nice workstation; I prefer it over Solaris. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 07:22:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02355 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 07:22:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as2-p93.tfs.net [139.146.205.93] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02343 for ; Wed, 12 Aug 1998 07:22:22 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id JAA20058; Wed, 12 Aug 1998 09:21:36 -0500 (CDT) From: Jim Bryant Message-Id: <199808121421.JAA20058@unix.tfs.net> Subject: Re: solaris is free. In-Reply-To: <19980812022936.A16972@mooseriver.com> from Josef Grosch at "Aug 12, 98 02:29:37 am" To: jgrosch@mooseriver.com Date: Wed, 12 Aug 1998 09:21:35 -0500 (CDT) 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: > On Wed, Aug 12, 1998 at 11:06:25AM +0200, Nick Hibma wrote: > > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > > they are starting to worry about all those older Sparc's running NetBSD. > > > > To be honest, x86 SOlaris has always been a bit a forgotten child in the > > Sun family. > > Given the speed of Solaris on x86 I'm not surprised. When I was contracting > at Sun earlier this year I went around installing FreeBSD on machines that > were running Solaris. Even hard core Sun people were surprised at how much > faster FreeBSD ran. take note that in paragraph 2 of the license, it is stated: ---------- you will not use the Software for these purposes. You may not publish or provide the results of any benchmark or comparison tests run on Software to any third party without the prior written consent of Sun. No right, title or interest in or ---------- maybe this has something to do with what you were saying about the performance... anyhow, i still see this as a promising move by sun. it could really drop the cost of new low-budget development. it could also boost sparc sales. the way i read the license, it doesn't stop wannabe developers from developing new apps. apps that can be migrated to the large scale with merely a recompile. it is also the first serious commercial threat to nt, but judgement on that i will reserve for a future date. 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 Wed Aug 12 07:43:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04408 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 07:43:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from snitterly.nanoteq.co.za (snitterly.nanoteq.co.za [196.37.90.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04401 for ; Wed, 12 Aug 1998 07:43:37 -0700 (PDT) (envelope-from edebruin@iname.com) Received: from iname.com (mossie.nanoteq.co.za [196.37.91.6]) by snitterly.nanoteq.co.za (8.8.3/8.8.3) with ESMTP id QAA02821 for ; Wed, 12 Aug 1998 16:48:04 GMT Message-ID: <35D1C5E1.3C33DB61@iname.com> Date: Wed, 12 Aug 1998 16:42:09 +0000 From: eT X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: developing device drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greets, Thanks to all the guys out there who are so willing to help. One day when I'm big I want to be like you guys :) I have read 'Writing a Unix Device driver 2nd edition' and have read 'FreeBSD device driver's guide' and I now need to take the plunge and start developing/coding. I was wondering if there was a way to develop & test & debug a device driver before linking it into the kernel .. i know it sorta doesn't make sense, but as i said i was wondering... Another Q: I'm writing a PCI character device driver and i was wondering which if_xx.c in /usr/src/sys/pci would be a good template/example. Anyways, my first posting :) so go easy on me... eT -- Etienne de Bruin E-mail: edebruin@iname.com OR edebruin@netscape.net WWW: http://listen.to/eT Forcefully advancing the Kingdom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 07:44:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04549 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 07:44:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tig.com.au (mail.tig.com.au [209.76.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04542 for ; Wed, 12 Aug 1998 07:44:29 -0700 (PDT) (envelope-from z2172268@student.unsw.edu.au) Received: from student.unsw.edu.au (p39-max2.syd.ihug.com.au [207.214.7.103]) by tig.com.au (8.8.8/8.7.3) with ESMTP id AAA10620; Thu, 13 Aug 1998 00:43:15 +1000 (EST) Message-ID: <35D1A991.26389012@student.unsw.edu.au> Date: Thu, 13 Aug 1998 00:41:21 +1000 From: chris/reman X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: Nick Hibma CC: Josef Grosch , FreeBSD hackers mailing list Subject: Re: solaris is free. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > To be honest, x86 SOlaris has always been a bit a forgotten child in the > Sun family. Sun likes to ship complete systems they can reliably > support. Giving supports to PC weenies is not one of their favourite > hobbies. Thats funny, because the uni. where I am at (UNSW, Sydney) the comp sci labs were originally running (and still is) a mix of decstations and labtams running SunOS, when they redid their workstations upstairs they bought p200's and stuck x86 SunOS on them, weird eh. Personally I would have saved the money bought cheaper workstations and stuck linux or freebsd on them, but what can you do when your only an undergrad, and your uni purchasing scheme is up $h*t creek. Then again I spose they were going for tried and tested, (insert remark about tired and bested here) regards, chris -- Christopher Day E-Mail the_reman@hotmail.com Homepage http://www.geocities.com/TimesSquare/Lair/1218 when the rain/when the children reign/keep your conscience in the dark melt the statues in the park - Fall On Me, REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 10:18:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00243 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 10:18:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00193 for ; Wed, 12 Aug 1998 10:18:45 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id MAA03203; Wed, 12 Aug 1998 12:16:38 -0400 (EDT) Date: Wed, 12 Aug 1998 12:16:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Warner Losh cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: <199808120750.BAA05604@harmony.village.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 Wed, 12 Aug 1998, Warner Losh wrote: > In message <199808120437.XAA12411@unix.tfs.net> Jim Bryant writes: > : sun, the day before yesterday has made solaris for both x86 and sparc > : free [shipping and handling like $10], for personal use. > > Is it personal use or educational use? My reading of the pages > earlier in the week suggested the latter. And when I'd tried to experiment with it (being a student at the University of Maryland) they required a PO from the University before they'd sell a copy. At least then, it was very much a sham. > > Warner > > 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 Wed Aug 12 10:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04667 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 10:39:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04662 for ; Wed, 12 Aug 1998 10:39:10 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id LAA19215; Wed, 12 Aug 1998 11:37:55 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Wed, 12 Aug 1998 11:37:55 -0600 (MDT) From: Brett Taylor To: Karl Denninger cc: jgrosch@mooseriver.com, Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: <19980812082400.24443@mcs.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 Hi, On Wed, 12 Aug 1998, Karl Denninger wrote: > > Frankly, FreeBSD + Afterstep on a Pentium Pro 200 makes a damn nice > workstation; I prefer it over Solaris. I second that (as I sit at the same type of machine also w/ AS running)! :-) Brett ************************************************************* Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ "The bicycle is the most civilized conveyance known to man. Other forms of transport grow daily more nightmarish. Only the bicycle remains pure in heart." - Iris Murdoch, "The Red and the Green" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 10:54:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07267 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 10:54:26 -0700 (PDT) (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 KAA07255 for ; Wed, 12 Aug 1998 10:54:21 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HHQZZNIJ; Wed, 12 Aug 98 17:53:55 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980812195146.00908a50@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 12 Aug 1998 19:51:46 +0200 To: freebsd-hackers@FreeBSD.ORG From: Marius Bendiksen Subject: solaris is free, ehrm.. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I quote a sentence from the original message: >see the sun web page for info, and follow up to this message on -chat. Let's move this thread elsewhere. It doesn't belong in FreeBSD-hackers.. --- 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 Wed Aug 12 10:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07825 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 10:58:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from charon.npc.net (vtk6000.npc.net [199.15.61.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07780 for ; Wed, 12 Aug 1998 10:58:03 -0700 (PDT) (envelope-from mikej@finall.com) Received: from exchange.finall.com (exchange-gw.finall.com [10.0.158.37]) by charon.npc.net (8.9.1/8.8.8) with SMTP id NAA23697 for ; Wed, 12 Aug 1998 13:57:34 -0400 (EDT) (envelope-from mikej@finall.com) Received: by exchange.finall.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BDC5F8.D629B220@exchange.finall.com>; Wed, 12 Aug 1998 13:55:17 -0400 Message-ID: From: "Jung, Michael" To: "'freebsd-hackers@freebsd.org'" Subject: Multisegment NIC Card Date: Wed, 12 Aug 1998 13:55:16 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 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'm trying to determine what multi port network cards are supported under any version of FreeBSD like the Intel Pro 100/Dual Port Server Adapter or the Adaptec Quartet64. Thanks --mikej Michael Jung NPC, Inc. mjung@npc.net mikej@finall.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 11:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11830 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 11:18:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11808 for ; Wed, 12 Aug 1998 11:18:05 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 2.02 #1) id 0z6fSm-0002FF-00 for freebsd-hackers@freebsd.org; Wed, 12 Aug 1998 20:17:32 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id UAA00507 for ; Wed, 12 Aug 1998 20:08:53 +0200 (SAT) Date: Wed, 12 Aug 1998 20:08:52 +0200 (SAT) From: Peter van Heusden Reply-To: Peter van Heusden To: freebsd-hackers@FreeBSD.ORG Subject: Moving ahead with LDAP 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 After a frustrating meeting with a local PHB, I've decided to try and put some more structured involvement into making FreeBSD easily manageable via a browser-like UI (as discussed on freebsd-hackers 2 months ago under the subject 'Adding a new user interface to FreeBSD'). As discussed then, LDAP might be a good tool to store configuration info in. The existing port of the UMich LDAP server, is, however sadly inadaquate. I have applied all patches I know of (Terry Lambert's collection from Critical Angle and elsewhere, as well as the patches forthcoming from freebsd-hackers), and created an updated port including the patches (and notified past (and possible future) port maintainers) but that still leaves UMich LDAP at LDAP v.2. Thus, I am interested in knowing who might want to work on moving ahead with better LDAP support on FreeBSD, with the intention of putting together and implementing a plan to get working LDAP v.3. So, who is interested? Peter -- Peter van Heusden | Its the 90's, and collective action is STILL cool! pvh@leftside.wcape.school.za | Get active in your union today! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 13:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01201 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 13:06:15 -0700 (PDT) (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 NAA01103 for ; Wed, 12 Aug 1998 13:06:01 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA21934 for ; Wed, 12 Aug 1998 16:05:28 -0400 (EDT) Date: Wed, 12 Aug 1998 16:05:27 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: Some buffer questions 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, It seems to me that there are two kinds of buffers: phyical buffers and (normal?) buffers. Both use the structure buf to describe them. Normal buffers are further divided into VMIO and non-VMIO. Can any one explain these classifications to me? Any help is appreciated. -------------------------------------------------- | 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 Wed Aug 12 13:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01807 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 13:08:34 -0700 (PDT) (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 NAA01783 for ; Wed, 12 Aug 1998 13:08:30 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id NAA21735 for freebsd-hackers@freebsd.org; Wed, 12 Aug 1998 13:06:21 -0700 (PDT) (envelope-from dhw) Date: Wed, 12 Aug 1998 13:06:21 -0700 (PDT) From: David Wolfskill Message-Id: <199808122006.NAA21735@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Anyone useing an ADIC FastStor tape changer successfully? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just received an ADIC FastStor tape drive & changer; trying to use the "ch" driver on a 2.2.6-RELEASE system, and running into oddnesses & some problems. "chio status " & "chio params" seem to work OK, as does moving a cartridge from a slot to the drive ("chio move slot 0 drive 0"). However, trying to move a cartridge from the drive to a slot fails, with an "Invalid argument": > chio params /dev/ch0: 7 slots, 1 drive, 1 picker /dev/ch0: current picker: 0 > chio status picker 0: slot 0: slot 1: slot 2: slot 3: slot 4: slot 5: slot 6: drive 0: > chio move drive 0 slot 0 chio: /dev/ch0: CHIOMOVE: Invalid argument > tail -1 /var/log/messages Aug 12 12:47:00 shrimp /kernel: ch0(ahc1:6:0): ILLEGAL REQUEST asc:3b,90 Vendor Specific ASCQ I'm prowling through chio.c, ch.c, & related sources, but short-circuiting the search would be heartily appreciated. Oh -- one other thing that I noticed that seemed a little odd. The unit responds to an "mt offl" command by effectively offlinging the drive all right, but doesn't eject the cartridge from the drive (let alone put it back in its slot or load the next cartridge). Maybe I'm just confused, as this is my first experience with DLT equipment; my 4mm DDS stacker at home responds nicely to "mt offl".... :-} Tips & hints welcome.... Thanks, 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 Wed Aug 12 13:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08026 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 13:46:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07983 for ; Wed, 12 Aug 1998 13:46:09 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id UAA23699; Wed, 12 Aug 1998 20:45:37 GMT (envelope-from didier@omnix.net) Date: Wed, 12 Aug 1998 22:45:37 +0200 (CEST) From: Didier Derny To: Remy NONNENMACHER cc: support@yard.de, hackers@FreeBSD.ORG Subject: Re: network problem with FreeBSD/Yard (yardnetd) In-Reply-To: <199808121144.MAA01217@bsd.synx.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, 12 Aug 1998, Remy NONNENMACHER wrote: > > no, TCP_NODELAY allows your local stack to immediatly send packets to > peer without waiting for a ack. It's also called the Nagle algo. > It is intented for applications sending a lot of small packets. Delaying > send in this case is good since it allows the local stack to accumulate > data and build bigger pakets. > I did some testing with the ...ack_delayed=1 (not modified) and with the TCP_NODELAY forced in tcp_output.c (horrible hack) I obtained the same result and the database was really fast so, TCP_NODELAY could at least be a work around if Yard compiled a version of their program with this flag set. (actually the database is unusable 1 raw/s [without any hack]) but I'm not sure if it's the best solution By the way, I aslo did some testing with tcpblast on the loopback with ...ack_delayed=1 and without my awful hack on TCP_NODELAY I get a repeateable 30Mbs/s with ..ack_delayed=0 or the hack I get a very irregular result going from 2 to 30 Mb/s -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 13:56:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09652 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 13:56:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09634 for ; Wed, 12 Aug 1998 13:56:36 -0700 (PDT) (envelope-from conrad@apple.com) Received: from mailgate.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id NAA29288 for ; Wed, 12 Aug 1998 13:51:03 -0700 Received: from scv1.apple.com (scv1.apple.com [17.128.100.139]) by mailgate.apple.com (mailgate.apple.com2.0.15) with ESMTP id for ; Wed, 12 Aug 1998 13:48:46 -0700 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv1.apple.com (8.8.5/8.8.5) with ESMTP id NAA22010 for ; Wed, 12 Aug 1998 13:48:45 -0700 X-Sender: conrad@mail.apple.com Message-Id: MIME-Version: 1.0 Date: Wed, 12 Aug 1998 13:48:43 -0700 To: freebsd-hackers@FreeBSD.ORG From: Conrad Minshall Subject: DVD & UDF Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone worked on DVD support for BSD? Particularly the UDF filesystem over writable DVD formats such as DVD-RAM. Currently I'm porting non-unix based UDF code into unix and if there are any *BSD (no Linux) UDF prototypes they could prove educational. Thanks, -- Conrad Minshall mailto:conrad@apple.com If "conrad@apple.com" doesn't work, try using rad@acm.org. Picon viewable at: http://facesaver.usenix.org/faces/h/49/4974.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 14:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12664 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 14:16:18 -0700 (PDT) (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 OAA12659 for ; Wed, 12 Aug 1998 14:16:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA00425; Wed, 12 Aug 1998 14:13:38 -0700 (PDT) Message-Id: <199808122113.OAA00425@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter van Heusden cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Moving ahead with LDAP In-reply-to: Your message of "Sat, 12 Aug 1998 20:08:52 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 14:13:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The existing port of the UMich LDAP server, is, however sadly inadaquate. > I have applied all patches I know of (Terry Lambert's collection from > Critical Angle and elsewhere, as well as the patches forthcoming from > freebsd-hackers), and created an updated port including the patches > (and notified past (and possible future) port maintainers) but that still > leaves UMich LDAP at LDAP v.2. This seems to parallel work that was being done by another party whose name has been eaten by my mailer (Giao, you know who you are). > Thus, I am interested in knowing who might want to work on moving ahead > with better LDAP support on FreeBSD, with the intention of putting > together and implementing a plan to get working LDAP v.3. > > So, who is interested? Are there any portable LDAPv3 servers available? Is the UMich server at a developmental dead-end? -- \\ 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 Aug 12 14:17:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12887 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 14:17:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sequoia.lituus.fr (dij8-159.abo.wanadoo.fr [193.252.183.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12879 for ; Wed, 12 Aug 1998 14:17:32 -0700 (PDT) (envelope-from root@smtp.wanadoo.fr) Received: (from root@localhost) by sequoia.lituus.fr (8.9.1/8.8.8) id XAA00420; Wed, 12 Aug 1998 23:01:35 +0200 (CEST) (envelope-from root) Date: Wed, 12 Aug 1998 23:01:35 +0200 (CEST) Message-Id: <199808122101.XAA00420@sequoia.lituus.fr> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Peter van Heusden Cc: freebsd-hackers@FreeBSD.ORG Subject: Moving ahead with LDAP In-Reply-To: References: X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter van Heusden writes: > After a frustrating meeting with a local PHB, I've decided to try and put > some more structured involvement into making FreeBSD easily manageable via > a browser-like UI (as discussed on freebsd-hackers 2 months ago under the > subject 'Adding a new user interface to FreeBSD'). As discussed then, LDAP > might be a good tool to store configuration info in. > > The existing port of the UMich LDAP server, is, however sadly inadaquate. > I have applied all patches I know of (Terry Lambert's collection from > Critical Angle and elsewhere, as well as the patches forthcoming from > freebsd-hackers), and created an updated port including the patches > (and notified past (and possible future) port maintainers) but that still > leaves UMich LDAP at LDAP v.2. > > Thus, I am interested in knowing who might want to work on moving ahead > with better LDAP support on FreeBSD, with the intention of putting > together and implementing a plan to get working LDAP v.3. > > So, who is interested? > Just my 2 eurocents but does a software like "cfengine" (/usr/ports/sysutils/cfengine) could be more adapted than something like LDAP ? I quote the "cfengine" doc : "Cfengine is a tool for setting up and maintaining BSD and System-5-like operating system optionnally attached to a TCP/IP network". Stephane Legrand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 14:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14217 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 14:23:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from chouette.inria.fr (chouette.inria.fr [138.96.24.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14201 for ; Wed, 12 Aug 1998 14:23:20 -0700 (PDT) (envelope-from Emmanuel.Duros@sophia.inria.fr) Received: by chouette.inria.fr (8.8.8/8.8.5) id XAA03579; Wed, 12 Aug 1998 23:22:54 +0200 (MET DST) Date: Wed, 12 Aug 1998 23:22:54 +0200 (MET DST) Message-Id: <199808122122.XAA03579@chouette.inria.fr> From: Emmanuel Duros To: freebsd-hackers@FreeBSD.ORG Subject: Allocating memory in a network device driver Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am currently writing a network device driver and I need clarification on how to allocate memory. I have seen in many device drivers allocating memory in the following way: u_char *buf; buf = malloc( BUFSIZ, M_DEVBUF, M_NOWAIT); Do we get the same result with : ? u_char buf[BUFSIZ]; In fact I have not found much documentation on the malloc function used in device driver. Can anyone point me to some ? I wonder what the M_DEVBUF, M_NOWAIT,... parameters are exactly for. Thanks a lot Emmanuel Duros To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 14:32:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16362 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 14:32:16 -0700 (PDT) (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 OAA16211 for ; Wed, 12 Aug 1998 14:32:07 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id QAA24936; Wed, 12 Aug 1998 16:31:30 -0500 (CDT) (envelope-from dan) Message-ID: <19980812163130.A24645@emsphone.com> Date: Wed, 12 Aug 1998 16:31:30 -0500 From: Dan Nelson To: David Wolfskill , freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone useing an ADIC FastStor tape changer successfully? References: <199808122006.NAA21735@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: <199808122006.NAA21735@pau-amma.whistle.com>; from "David Wolfskill" on Wed Aug 12 13:06:21 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 (Aug 12), David Wolfskill said: > Just received an ADIC FastStor tape drive & changer; trying to use > the "ch" driver on a 2.2.6-RELEASE system, and running into oddnesses > & some problems. > > "chio status " & "chio params" seem to work OK, as does moving a > cartridge from a slot to the drive ("chio move slot 0 drive 0"). > > However, trying to move a cartridge from the drive to a slot fails, > with an "Invalid argument": Depending on how smart/dumb the changer is, you may have to eject the tape from the drive before the autoloader will see it. Like: chio move slot 0 drive 0 tar cv / mt offline chio move drive 0 slot 0 the Exabyte 10h autoloader is like that, although I believe both of our DLT autoloaders (ADIC and Overland Data) are smart enough to eject the tape automatically when asked (and automatically clean the drive when needed too). -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 Wed Aug 12 14:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18690 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 14:46:59 -0700 (PDT) (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 OAA18666 for ; Wed, 12 Aug 1998 14:46:45 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id OAA22098 for freebsd-hackers@freebsd.org; Wed, 12 Aug 1998 14:44:29 -0700 (PDT) (envelope-from dhw) Date: Wed, 12 Aug 1998 14:44:29 -0700 (PDT) From: David Wolfskill Message-Id: <199808122144.OAA22098@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone useing an ADIC FastStor tape changer successfully? In-Reply-To: <19980812163130.A24645@emsphone.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sending this reply to -hackers because my original message went to -hackers (rather than -hardware, as I had intended). Apologies for the confusion on my part; hope it's useful for someone. >Date: Wed, 12 Aug 1998 16:31:30 -0500 >From: Dan Nelson >In the last episode (Aug 12), David Wolfskill said: [stuff about ADIC > FastStor tape changer] >Depending on how smart/dumb the changer is, you may have to eject the >tape from the drive before the autoloader will see it. Like: >chio move slot 0 drive 0 >tar cv / >mt offline >chio move drive 0 slot 0 >the Exabyte 10h autoloader is like that, although I believe both of our >DLT autoloaders (ADIC and Overland Data) are smart enough to eject the >tape automatically when asked (and automatically clean the drive when >needed too). Amazing...! That's what it took: > chio move slot 6 drive 0 > chio status picker 0: slot 0: slot 1: slot 2: slot 3: slot 4: slot 5: slot 6: drive 0: > chio move drive 0 slot 6 chio: /dev/ch0: CHIOMOVE: Invalid argument > mt -f /dev/rst2 offl > chio move drive 0 slot 6 > chio status picker 0: slot 0: slot 1: slot 2: slot 3: slot 4: slot 5: slot 6: drive 0: Somehow, on realizing this is what makes it work, I'm reminded of first learning that the star-tipped rod scares the bird.... (*) Thanks, Dan.... Now I need to get amanda set up to use this.... :-} * Ref. to "Adventure," in case that's not obvious. "You are at the end of a road, near a small brick building...." 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 Wed Aug 12 15:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26826 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 15:47:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beelzebubba.sysabend.org (beelzebubba.sysabend.org [209.48.124.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26819 for ; Wed, 12 Aug 1998 15:47:16 -0700 (PDT) (envelope-from grail@beelzebubba.sysabend.org) Received: (from grail@localhost) by beelzebubba.sysabend.org (8.8.5/8.8.5) id SAA18819; Wed, 12 Aug 1998 18:46:33 -0400 (EDT) Message-ID: <19980812184633.A18658@beelzebubba.sysabend.org> Date: Wed, 12 Aug 1998 18:46:33 -0400 From: Giao Nguyen To: Mike Smith , Peter van Heusden Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Moving ahead with LDAP Mail-Followup-To: Mike Smith , Peter van Heusden , freebsd-hackers@FreeBSD.ORG References: <199808122113.OAA00425@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199808122113.OAA00425@dingo.cdrom.com>; from Mike Smith on Wed, Aug 12, 1998 at 02:13:38PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith said: > > This seems to parallel work that was being done by another party whose > name has been eaten by my mailer (Giao, you know who you are). Damn he's persistent :) > Are there any portable LDAPv3 servers available? Is the UMich server > at a developmental dead-end? In the exact order asked. I can't think of any except for UMich* and I hope not. There will be some significant ripping aparts to get it to v3 and it'll require some significant chunks of work. I've reached the same state as Peter (well, except for the port part. I haven't put together the files for that, but it's not v3 yet so what's the point?). I am lagging behind in where and how the code is fully laid out. However, God willing I'll be caught up in a few weeks. It's always useful to talk your manager into getting you involved in projects that has your interest. I swear nothing is as boring as web enabling . Giao * By available I assume that you mean "freely available". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 15:49:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27171 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 15:49:02 -0700 (PDT) (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 PAA27166 for ; Wed, 12 Aug 1998 15:49:01 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA02938; Wed, 12 Aug 1998 15:48:36 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002934; Wed Aug 12 15:48:24 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA09142; Wed, 12 Aug 1998 15:48:23 -0700 (PDT) From: Archie Cobbs Message-Id: <199808122248.PAA09142@bubba.whistle.com> Subject: Re: Allocating memory in a network device driver In-Reply-To: <199808122122.XAA03579@chouette.inria.fr> from Emmanuel Duros at "Aug 12, 98 11:22:54 pm" To: Emmanuel.Duros@sophia.inria.fr (Emmanuel Duros) Date: Wed, 12 Aug 1998 15:48:23 -0700 (PDT) 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 Emmanuel Duros writes: > I am currently writing a network device driver and I need clarification > on how to allocate memory. > > I have seen in many device drivers allocating memory in the following > way: > > u_char *buf; > buf = malloc( BUFSIZ, M_DEVBUF, M_NOWAIT); > > Do we get the same result with : ? > > u_char buf[BUFSIZ]; The kernel malloc works just like the libc malloc .. man malloc(3). The extra arguments are the type (you must specify the same type when you free() the memory) and whether or not it's OK to put the current process to sleep in order to get the memory. If you say M_WAITOK, then malloc() never fails but may put the process to sleep. If you say M_NOWAIT, then it may fail but will not put the process to sleep. In general, M_NOWAIT is required for any code running during an interrupt (ie, the current process should not be put to sleep), otherwise M_WAITOK is ok. -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 Wed Aug 12 15:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29349 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 15:59:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA29319 for ; Wed, 12 Aug 1998 15:59:22 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40696(1)>; Wed, 12 Aug 1998 15:58:54 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Wed, 12 Aug 1998 15:58:40 -0700 To: Didier Derny cc: support@yard.de, hackers@FreeBSD.ORG Subject: Re: network problem with FreeBSD/Yard (yardnetd) In-reply-to: Your message of "Wed, 12 Aug 98 02:07:23 PDT." Date: Wed, 12 Aug 1998 15:58:31 PDT From: Bill Fenner Message-Id: <98Aug12.155840pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message you write: >1/ I suppose that a setsockopt(socket... TCP_NODELAY..) > would have the same result for the yard application if it was > inserted in the yard code ? It depends on exactly what the problem is. There's a common problem which is caused by sending several small packets in a row; the Nagle algorithm (and sender silly window syndrome avoidance) say that you may not send one small packet when another small packet is outstanding. If the other end delays its ack, then your small packets stay outstanding for a long time. Turning off Nagle and sender SWS avoidance (by setting TCP_NODELAY) prevents this from happening. >2/ what are the implication of setting ...ack_delayed=0 for the system ? Traffic on interactive TCP sessions (e.g. telnet, rlogin, ssh) will approximately double, since the client will send a keystroke that you typed and the server will ACK it, and then the server will send another packet with the echoed keystroke. With delayed acks, the ACK piggybacks on the echoed keystroke. >3/ What should I say to Yard to have this problem solved ? Ask them to set TCP_NODELAY? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 16:02:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00148 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:02:36 -0700 (PDT) (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 QAA29981 for ; Wed, 12 Aug 1998 16:02:20 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA07500; Wed, 12 Aug 1998 16:01:48 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd007412; Wed Aug 12 16:01:42 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA11514; Wed, 12 Aug 1998 16:01:33 -0700 (MST) From: Terry Lambert Message-Id: <199808122301.QAA11514@usr05.primenet.com> Subject: Re: solaris is free. To: joerg@krdl.org.sg (Joerg Micheel) Date: Wed, 12 Aug 1998 23:01:32 +0000 (GMT) Cc: jgrosch@mooseriver.com, marcs@znep.com, imp@village.org, jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980812171259.39906@krdl.org.sg> from "Joerg Micheel" at Aug 12, 98 05:12:59 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > they are starting to worry about all those older Sparc's running NetBSD. If they were selling SunOS for $10 instead of Solaris, then you might have a point. I think there is a lot of Sun hardware running NetBSD because people are nostalgic for the feel of the old SunOS. > But too late. There was a proposal by Larry Wall back at the beginning > of the 1990's to free SunOS source to prevent splitting of the R&D > community into all these niches, but in vain. > > Still interesting reading, from a historical point of view. I need to see > whether I still have the copy around somewhere. I think you mean Larry McVoy, back in 1994. He tried to get Sun to release SunOS 4.x source code under GPL. I think Larry believes he got burned by Sun when they killed SunOS in favor of Solaris, and mistakenly believes that GPL would have somehow prevented that (ignoring the fact that Sun gets most of its revenue from software, not hardware, and that SunOS, being derived from UCB licensed code, can't be licensed under GPL because of the GPL's "no other restrictions" clause conflicting with the UCB "calim credit" clause). Others have commented that Larry's perceived GPL fanatacism has colored his outlook in a number of areas, perhps including the LMBench microbenchmark suite favoring GPL'ed OS's over non-GPL'ed OS's... 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 Aug 12 16:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02550 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:20:20 -0700 (PDT) (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 QAA02525 for ; Wed, 12 Aug 1998 16:20:15 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA11576; Wed, 12 Aug 1998 16:19:48 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd011430; Wed Aug 12 16:19:36 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA12391; Wed, 12 Aug 1998 16:19:33 -0700 (MST) From: Terry Lambert Message-Id: <199808122319.QAA12391@usr05.primenet.com> Subject: Re: Moving ahead with LDAP To: pvh@leftside.wcape.school.za Date: Wed, 12 Aug 1998 23:19:32 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Peter van Heusden" at Aug 12, 98 08:08:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After a frustrating meeting with a local PHB, I've decided to try and put > some more structured involvement into making FreeBSD easily manageable via > a browser-like UI (as discussed on freebsd-hackers 2 months ago under the > subject 'Adding a new user interface to FreeBSD'). As discussed then, LDAP > might be a good tool to store configuration info in. > > The existing port of the UMich LDAP server, is, however sadly inadaquate. > I have applied all patches I know of (Terry Lambert's collection from > Critical Angle and elsewhere, as well as the patches forthcoming from > freebsd-hackers), and created an updated port including the patches > (and notified past (and possible future) port maintainers) but that still > leaves UMich LDAP at LDAP v.2. > > Thus, I am interested in knowing who might want to work on moving ahead > with better LDAP support on FreeBSD, with the intention of putting > together and implementing a plan to get working LDAP v.3. > > So, who is interested? Kurt D. Zeilenga (Kurt@Boolean.Net) just recently announced on the LDAP list that his company is hosting a publically accessable repository for LDAP developement, via anoncvs. The repository is available now for testing only, and if you want access to the test server, he wants you to send him a short email describing yourself (programmer, manager, user, tester, etc.) and the platforms (hw vendor, OS, etc.) you can test. I've been considering doing something similar, but the server setup overhead and the lack of time to commit to a v3 implementation by myself has held me back. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 16:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03429 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:25:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA03381 for ; Wed, 12 Aug 1998 16:25:31 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA26825 for hackers@freebsd.org; Wed, 12 Aug 1998 19:28:14 -0400 From: Bill Paul Message-Id: <199808122328.TAA26825@skynet.ctr.columbia.edu> Subject: More XL driver fixes To: hackers@FreeBSD.ORG Date: Wed, 12 Aug 1998 19:28:13 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You know the drill. I uploaded yet another version of the Etherlink XL driver to www.freebsd.org/~wpaul/3Com. This update fixes the following multicast bugs: - The second for(;;) statement in xl_calchash() was wrong. I'm so damn accustomed to typing "for(i = 0; i < foo; i++)" that my brain failed so switch gears when I moved from i to j. - The patch I applied to xl_setmulti() to turn off multicast reception if acpcom.ac_multicnt was 0 worked okay for 2.2.x but not for 3.0. The multicast code in 3.0 is different and ac_multicnt is never updated. - The 3Com manual states that 3c905B adapters have a 64-bit multicast hash filter, and that future ASIC revisions will have a 256-bit filter instead. As it happens, there are already ASICs with 256-bit filters out there; I know because I've got one. Previously I was masking the upper 2 bits of the hash value thinking that only 6 bits were needed. Now I supply all 8 bits to the NIC; it will ignore bits that it doesn't need. Today I found out that there are some Dell Latitude laptop machines with embedded 3c905B-TX adapters. If anybody has one of these, I'd like to know if the driver works properly. The one person who's talked to me about these things so far says that on his laptop, the driver blows up because it gets a value from the media options register that it wasn't expecting. Supposedly, when he does a "boot: -v" on his machine, he gets a message that says: xl0: media options word: e100 On the 3c905B, the media options register is loaded from the EEPROM (with earlier 3c90x NICs the value is hard-wired). According to the manual, there are 4 possible values that may be encoded in the EEPROM depending on the adapter (TP, TX, T4 and FX) none of which are anywhere close to e100. (You can see the media options bit definitions in if_xlreg.h. Look for XL_MEDIAOPT_*.) I am not sure why this person's system comes up with this value. My suspicion is that either the EEPROM contents are corrupted somehow, or Dell has reprogrammed the EEPROM with their own custom values. It's also possible that this is just a bit combination that isn't documented in the 3Com manual. If you have such a laptop machine and the driver panics in ifmedia_set() for you, please try the following patch: *** if_xl.c 1998/08/11 15:26:56 1.27 --- if_xl.c 1998/08/12 15:21:26 *************** *** 1291,1296 **** --- 1291,1317 ---- printf("xl%d: media options word: %x\n", sc->xl_unit, sc->xl_media); + /* XXXXXX WARNING! THIS IS A HACK! WARNING! XXXXXX */ + /* + * Read the media options word directly from the EEPROM. The + * value printed here and the value shown above should match, + * otherwise something is seriously wrong. Note: only the 3c905B + * has the media options data loaded from the EEPROM. Earlier + * cards have the media options register set by physically + * latching pins on the controller chip when the adapter is + * manufactured. + */ + #define XL_EE_MEDIAOPT 0x19 + xl_read_eeprom(sc, (char *)&sc->xl_media, XL_EE_MEDIAOPT, 1, 0); + printf("xl%d: media options word from EEPROM: %x\n", + sc->xl_unit, sc->xl_media); + /* + * The media options word for a 3c905B-TX adapter is + * supposed to be 0x000A. Force it here for a test. + */ + sc->xl_media = 0x000a; + /* XXXXXX WARNING! THIS IS A HACK! WARNING! XXXXXX */ + xl_read_eeprom(sc, (char *)&sc->xl_xcvr, XL_EE_ICFG_0, 2, 0); sc->xl_xcvr &= XL_ICFG_CONNECTOR_MASK; sc->xl_xcvr >>= XL_ICFG_CONNECTOR_BITS; This patch changes the attach routine so that it checks the value of the EEPROM location from which the media options register is loaded so that it can be compared with the value in read from the register itself. It also forces the media type to XL_MEDIAOPT_BT|XL_MEDIAOPT_BTX, which is supposed to be the correct default for a 3c905B-TX. YOU SHOULD ONLY USE THIS PATCH IF YOU HAVE A 3c905B! Don't use it with a 3c905 or 3c900 because it will muck up the media detection routine! -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 16:28:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04215 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:28:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04195 for ; Wed, 12 Aug 1998 16:28:46 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id QAA25510; Wed, 12 Aug 1998 16:10:30 -0700 (PDT) Message-Id: <199808122310.QAA25510@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert Cc: joerg@krdl.org.sg (Joerg Micheel), jgrosch@mooseriver.com, marcs@znep.com, imp@village.org, jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 12 Aug 1998 16:10:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Aug 1998 23:01:32 +0000 (GMT) Terry Lambert wrote: > If they were selling SunOS for $10 instead of Solaris, then you > might have a point. I think there is a lot of Sun hardware running > NetBSD because people are nostalgic for the feel of the old SunOS. More like: They have these good old workhorse machines, and they want to run an OS that doesn't suck, in constrast to SunOS and Solaris. If I wanted the nostalgia of running SunOS, I'd run SunOS. (Hey, I still have a machine that runs 4.2BSD...) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 16:41:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05772 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:41:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05766 for ; Wed, 12 Aug 1998 16:40:57 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-109.camalott.com [208.229.74.109]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA16331; Wed, 12 Aug 1998 18:41:15 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA03303; Wed, 12 Aug 1998 18:38:57 -0500 (CDT) (envelope-from joelh) Date: Wed, 12 Aug 1998 18:38:57 -0500 (CDT) Message-Id: <199808122338.SAA03303@detlev.UUCP> To: jgrosch@mooseriver.com CC: marcs@znep.com, imp@village.org, jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG In-reply-to: <19980812014614.B16463@mooseriver.com> (message from Josef Grosch on Wed, 12 Aug 1998 01:46:14 -0700) Subject: Re: solaris is free. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808120750.BAA05604@harmony.village.org> <19980812014614.B16463@mooseriver.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My guess is that Sun is beginning to feel the heat from FreeBSD and > Linux. Last time I looked very few people we running Solaris on X86. Mayby > they are starting to worry about all those older Sparc's running NetBSD. Why would they care? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 12 16:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06220 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:43:45 -0700 (PDT) (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 QAA06214 for ; Wed, 12 Aug 1998 16:43:43 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA19885; Wed, 12 Aug 1998 16:43:18 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd019864; Wed Aug 12 16:43:13 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA13385; Wed, 12 Aug 1998 16:43:10 -0700 (MST) From: Terry Lambert Message-Id: <199808122343.QAA13385@usr05.primenet.com> Subject: Re: Moving ahead with LDAP To: mike@smith.net.au (Mike Smith) Date: Wed, 12 Aug 1998 23:43:10 +0000 (GMT) Cc: pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808122113.OAA00425@dingo.cdrom.com> from "Mike Smith" at Aug 12, 98 02:13:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any portable LDAPv3 servers available? Is the UMich server > at a developmental dead-end? The list was very dead for a long time, until I kicked it back in March or thereabouts. After that, a number of Linux people beat on me after getting my patches until I looked at their problems and fixed them. Basically, before I came along, the code was in very poor shape and had some bad assumptions about threading and select(2)'s first argument, etc.. After I took all of the Critical Angle patches and integrated them, fixed the dbm backend namespace bug, and fixed the threads and select assumptions, the code started working on about 8 platforms (SGI uses Draft 4 pthreads too). Since then, the Linux guys have gone nuts... there is a Linux specific LDAP WWW site dedicated to doing an LDAP-based Linux parameter store. Ah, to be a student and get back half my day again while scholarships and grants paid my way... ;-). Anyway, it appears that many of the UMICH people have gone on to commercial pastures, where they have a bit of a vested interest in keeping the patches hard to apply and the protocol one or more revisions out of step. I don't hold out much hope for the Linux effort; the people involved are enthusiastic, but were posting such things as "how do I fix this ``sys_errlist'' compile problem?" and generally stumbling over gdbm not woking, but the Berkely dbm working, and making the same errors about threading models that the original authors made (threading is considered preemptive if a blocking select() will result in a context switch, but they were tagging pthreads as being non-preemptive, and buzz-looping as a result). I'd like to see a serious effort at a commercially usable v3 server implementation (hopefully carrying forward under the UMich license or a UCB style project license for independently developed pieces and the agregation of the new and the old). I'm not sure the boolean.net repository promotes this; mostly because I'm not that sure that the UMich code is capable of evolving into a v3 server. 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 Aug 12 16:51:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07352 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 16:51:17 -0700 (PDT) (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 QAA07347 for ; Wed, 12 Aug 1998 16:51:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01146; Wed, 12 Aug 1998 16:49:08 -0700 (PDT) Message-Id: <199808122349.QAA01146@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: PCI BIOSes and power management In-reply-to: Your message of "Tue, 11 Aug 1998 19:04:57 EDT." <199808112304.TAA25098@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 16:49:08 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a question which I'm somebody familiar with PCI issues might > be able to answer. I recently ran into an unusual problem with the > 3c905B driver. The 905B (unlike the 905) supports power management. > There's a 'CapID' register in the PCI register space of the 3c905B > ASIC which indicates that the device supports power manament, and > there are also Power Management Control and Power Management Status > registers. This is actually more of an ACPI issue; you can obtain the ACPI standard from www.teleport.com/~acpi. > The 3c905B supports a couple of different power states: > > D0 'full power' mode; normal NIC operating mode > D1 'light sleep' mode > D2 Partial power down (still responds to PCI config accesses) > D3(hot) Full power down state (loses PCI config info) > D3(cold) Power off state (i.e. card unplugged or system turned off) > > When the NIC is in the D3(hot) state, it loses all of its PCI > configuration settings except the value of the power state register. > The NIC responds to PCI configuration accesses so that the power mode > can be changed back to D0 for normal operation. My understanding is > that the PCI BIOS is supposed to set the device back to the D0 state > prior to configuring it. > > Normally I wouldn't care about this, however the Lose95/98/NT 3c905B > drivers appear to place the NIC in the D3(hot) state during shutdown. This seems to violate the ACPI spec, although it's notably thin on the ground when it comes to talking about restarts. Section 3.2 says "Computers that support legacy BIOS power management interfaces boot in the Legacy state and transition to the Working state when an ACPI OS loads." > This can cause the following sequence of events: > > - User has a dual-boot system with Lose95/98/NT and FreeBSD installed. > - User boots Lose95/98/NT and fiddles for a while. > - User gets tired of listening to disk thrash and selects 'Shutdown > and restart' from the Shutdown menu. > - Lose95/98/NT places 3c905B NIC in D3(hot) power down state. > - Machine warm boots. > - PCI BIOS goes out and starts configuring PCI devices. > - PCI BIOS, apparently not being clever enough to know how to deal > with power management capable devices, fails to set the NIC back > to the D0 state. It may also be that the BIOS is not getting it right. If you're using NT4.0 and Win95 of the non-OSR2 variety, you may also not have an ACPI BIOS. I presume that Win95/NT will recognise the adapter OK when they restart? > - PCI BIOS tries to configure adapter but fails because the NIC > doesn't preserve PCI config data in the D3(hot) state. > - System finishes its startup regimen, brings up boot mangler prompt. > - User selects FreeBSD, kernel loads and probes for devices. > - XL driver detects a card, but pukes with the following error: > > xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 36 int a irq 10 on pci0:9:0 > mapreg[10] type=1 addr=0000d400 size=0080. > mapreg[14] type=0 addr=e6000000 size=0080. > xl0: chip is in D3 power mode -- setting to D0 > int line register not set by bios > xl0: couldn't map interrupt > > The 'setting to D0' message comes from the driver trying to set the card > back to a usable state, which it can do, however it's still not properly > configured. Now that the chip is back in the D0 state, warm booting again > will allow the PCI BIOS to correctly configure the NIC. Cold booting the > system would also fix the problem. > > My question is: is it possible to get the card programmed correctly > during the attach routine, and if so, how? I don't see any way to > get the BIOS to reconfigure the device once the OS is running, and We don't support this because (for whatever reason) we don't use the BIOS-provided routines for enumeration and configuration. We should be able to do this. > I don't think the driver is supposed to do it. Does anybody know the > correct way to deal with this? It's a minor problem as long as you > don't mind cold starting your machine after running an M$ operating > system, or if you don't run one to begin with, but I'd like to find > a way to solve this if possible. What you're effectively doing here is trying to deal with a hot-inserted PCI card, and we don't have any infrastructure in place to support that. You might want to talk to Stefan in case he has any neat ideas. -- \\ 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 Aug 12 18:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15716 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 18:23:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m67.whistle.com [207.76.205.67]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA15589 for ; Wed, 12 Aug 1998 18:21:45 -0700 (PDT) (envelope-from terry@lambert.org) Date: Wed, 12 Aug 1998 18:21:45 -0700 (PDT) From: terry@lambert.org Message-Id: <199808130121.SAA15589@hub.freebsd.org> to: hackers@FreeBSD.ORG To: hackers@FreeBSD.ORG Subject: lists dead? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Majordomo not responding? -- Terry Lambert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 18:26:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16229 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 18:26:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16218 for ; Wed, 12 Aug 1998 18:26:27 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA02535; Wed, 12 Aug 1998 18:26:18 -0700 (PDT) Message-Id: <199808130126.SAA02535@implode.root.com> To: Emmanuel Duros cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Allocating memory in a network device driver In-reply-to: Your message of "Wed, 12 Aug 1998 23:22:54 +0200." <199808122122.XAA03579@chouette.inria.fr> From: David Greenman Reply-To: dg@root.com Date: Wed, 12 Aug 1998 18:26:18 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Do we get the same result with : ? > > u_char buf[BUFSIZ]; No. That would allocate a large amount of kernel stack space which is precious and must not be wasted. -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 Aug 12 19:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20299 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 19:04:35 -0700 (PDT) (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 TAA20294 for ; Wed, 12 Aug 1998 19:04:28 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA21212; Thu, 13 Aug 1998 11:33:27 +0930 (CST) Message-Id: <199808130203.LAA21212@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: chris/reman cc: Nick Hibma , Josef Grosch , FreeBSD hackers mailing list Subject: Re: solaris is free. In-reply-to: Your message of "Thu, 13 Aug 1998 00:41:21 +1000." <35D1A991.26389012@student.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 11:33:27 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thats funny, because the uni. where I am at (UNSW, Sydney) the comp sci labs > originally running (and still is) a mix of decstations and labtams running Su > when they redid their workstations upstairs they bought p200's and stuck x86 > SunOS on them, weird eh. Personally I would have saved the money bought chea > workstations and stuck linux or freebsd on them, but what can you do when you > only an undergrad, and your uni purchasing scheme is up $h*t creek. > Then again I spose they were going for tried and tested, (insert remark about > tired and bested here) At least when your uni decided to upgrade to SOlaris they bought new hardware! When I was at uni (a few months ago) they where running Solaris on Sparc 10's :( They got 2 E450's just as I left tho.. bastards ;) --------------------------------------------------------------------- |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 Aug 12 19:11:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21095 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 19:11:17 -0700 (PDT) (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 TAA21089 for ; Wed, 12 Aug 1998 19:11:13 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA21306; Thu, 13 Aug 1998 11:40:37 +0930 (CST) Message-Id: <199808130210.LAA21306@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Emmanuel Duros cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Allocating memory in a network device driver In-reply-to: Your message of "Wed, 12 Aug 1998 23:22:54 +0200." <199808122122.XAA03579@chouette.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 11:40:37 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In fact I have not found much documentation on the malloc function used > in device driver. Can anyone point me to some ? I wonder what the > M_DEVBUF, M_NOWAIT,... parameters are exactly for. There exists a manpage for the kernel malloc under -current in section 9. (It basically repeats what Archie said :) --------------------------------------------------------------------- |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 Aug 12 19:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21510 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 19:13:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (libya-197.ppp.hooked.net [206.169.227.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21505 for ; Wed, 12 Aug 1998 19:13:38 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id TAA01536; Wed, 12 Aug 1998 19:14:03 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 12 Aug 1998 19:14:03 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Karl Denninger cc: jgrosch@mooseriver.com, Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: <19980812082400.24443@mcs.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 On Wed, 12 Aug 1998, Karl Denninger wrote: > On Wed, Aug 12, 1998 at 01:46:14AM -0700, Josef Grosch wrote: > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > they are starting to worry about all those older Sparc's running NetBSD. > > Frankly, FreeBSD + Afterstep on a Pentium Pro 200 makes a damn nice > workstation; I prefer it over Solaris. Ahh replace AS with KDE, and you've got a better workstation ;) Anyhow, I think Solaris still has some advantages over FreeBSD, including better SMP, and support for a better C++ compiler (nearly anything is better than gcc 2.7.2). Still not worth 20 bucks tho ;) - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD 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 Wed Aug 12 20:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28275 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 20:09:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28255 for ; Wed, 12 Aug 1998 20:09:38 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA07267; Wed, 12 Aug 1998 22:09:06 -0500 (EST) (envelope-from toor) Message-Id: <199808130309.WAA07267@dyson.iquest.net> Subject: Re: Some buffer questions In-Reply-To: from zhihuizhang at "Aug 12, 98 04:05:27 pm" To: bf20761@binghamton.edu Date: Wed, 12 Aug 1998 22:09:06 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 said: > > Hi, > > It seems to me that there are two kinds of buffers: phyical buffers and > (normal?) buffers. Both use the structure buf to describe them. Normal > buffers are further divided into VMIO and non-VMIO. Can any one explain > these classifications to me? > I wrote the code, so can be pretty definitive: The "VMIO" buffer cache code (it is a misnomer actually), is meant to try to buffer data with file VM objects as being the memory supply rather than anonymous VM objects. This automatically allows for coherency between mmap and file I/O. The "physical" buffers are mostly temporary kernel mappings with I/O request info. They are segregated from the buffer cache, since they are used for I/O requests that are not buffer cache related. Mostly, they are used for raw disk I/O or certain kinds of VM operations (like swap I/O.) The "VMIO" buffers are buffers with data backed by VM objects. This scheme was chosen to support relatively seamless compatibility with legacy BSD systems. The non-"VMIO" buffers are used when it isn't convienient to use the VMIO scheme, or when there is little to be gained from the coherency. The VMIO scheme works, but is complex for block sizes < PAGE_SIZE. Since directories are usually < PAGE_SIZE, and directory corruption is disasterous, I initially chose not to use a file VM object backing for dirs. Eventually VDIRs should probably be backed the same way as regular files, but it isn't really needed. The buffer cache policy is meant to bias towards keeping non-VM object based buffers longer than VM object based buffers. This is because that VM object based buffered data can persist longer than the buffer itself. (This is one reason for some of the problems with softupdates.) FreeBSD is generally not dependent on the buffer cache for buffering. In fact, the original goal was to use the buffer cache as a temporary I/O mapping and I/O request scheme, and the actual bulk data caching would be in the VM objects. The policies in the buffer cache code are NOT LRU, but are similar to LRU. This can significantly improve performance under load, with almost no light loaded cost. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 20:19:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29865 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 20:19:30 -0700 (PDT) (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 UAA29860 for ; Wed, 12 Aug 1998 20:19:25 -0700 (PDT) (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 MAA00721; Thu, 13 Aug 1998 12:48:40 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA01600; Thu, 13 Aug 1998 12:48:32 +0930 (CST) Message-ID: <19980813124831.D1147@freebie.lemis.com> Date: Thu, 13 Aug 1998 12:48:31 +0930 From: Greg Lehey To: eT , hackers@FreeBSD.ORG Subject: Re: developing device drivers References: <35D1C5E1.3C33DB61@iname.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35D1C5E1.3C33DB61@iname.com>; from eT on Wed, Aug 12, 1998 at 04:42:09PM +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, 12 August 1998 at 16:42:09 +0000, eT wrote: > Greets, > > Thanks to all the guys out there who are so willing to help. One day > when I'm big I want to be like you guys :) > > I have read 'Writing a Unix Device driver 2nd edition' and have read > 'FreeBSD device driver's guide' and I now need to take the plunge and > start developing/coding. > > I was wondering if there was a way to develop & test & debug a device > driver before linking it into the kernel .. i know it sorta doesn't make > sense, but as i said i was wondering... Sure. Make it an LKM. It's a lot easier to debug, though there are a couple of things you need to know to get the symbols for the kernel debugger. There's some stuff on this subject in the online handbook. I'm also planning to write some stuff up about the testing environment. Greg -- See complete headers for address 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 Aug 12 22:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11169 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 22:23:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11164 for ; Wed, 12 Aug 1998 22:23:39 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id XAA07849; Wed, 12 Aug 1998 23:23:08 -0600 (MDT) Message-Id: <199808130523.XAA07849@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Wed, 12 Aug 1998 23:23:07 -0600 To: hackers@FreeBSD.ORG From: Brett Glass Subject: 64-bit time_t Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How soon will FreeBSD move to a 64-bit time_t? The article at http://www.wired.com/news/news/technology/story/14390.html paints a dire picture; it'd be nice to say that FreeBSD solves the problem already. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 12 22:28:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11684 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 22:28:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA11677 for ; Wed, 12 Aug 1998 22:28:36 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id BAA27253; Thu, 13 Aug 1998 01:30:55 -0400 From: Bill Paul Message-Id: <199808130530.BAA27253@skynet.ctr.columbia.edu> Subject: Re: developing device drivers To: grog@lemis.com (Greg Lehey) Date: Thu, 13 Aug 1998 01:30:54 -0400 (EDT) Cc: edebruin@iname.com, hackers@FreeBSD.ORG In-Reply-To: <19980813124831.D1147@freebie.lemis.com> from "Greg Lehey" at Aug 13, 98 12:48:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Greg Lehey had to walk into mine and say: > On Wednesday, 12 August 1998 at 16:42:09 +0000, eT wrote: > > Greets, > > > > Thanks to all the guys out there who are so willing to help. One day > > when I'm big I want to be like you guys :) > > > > I have read 'Writing a Unix Device driver 2nd edition' and have read > > 'FreeBSD device driver's guide' and I now need to take the plunge and > > start developing/coding. > > > > I was wondering if there was a way to develop & test & debug a device > > driver before linking it into the kernel .. i know it sorta doesn't make > > sense, but as i said i was wondering... > > Sure. Make it an LKM. It's a lot easier to debug, though there are a > couple of things you need to know to get the symbols for the kernel > debugger. > > There's some stuff on this subject in the online handbook. I'm also > planning to write some stuff up about the testing environment. I second this. If you look in /usr/share/examples, you'll find a couple of sample LKMs written by Terry Lambert. I hijacked the syscall example from here and used it a lot to experiment with the XL driver. What I did, being in a rush one day, was to wrap the whole of the driver code inside the module by simply #including the whole C module into the misccall.c file. This allows me to add bits and pieces to the misccall() routine that can invoke the functions in the driver code and report the results. You actually end up with two instances of the driver in core; the one linked in the kernel and the one wrapped inside the LKM, but the functions are all declared static so the LKM can only call its own copies of the routines. This is most useful for testing things like EEPROM and register access routines. For PCI devices, you need to write at least a stub driver to do the required PCI device setup and determine the iobase address where the devices has been configured. It's also a good idea to register an interrupt routine. Once you set up an ifnet structure and do an ether_attach(), the LKM can grab a pointer to the interface's ifnet structure by calling the ifunit() function. The main idea here is to get the kernel to recognize the device and allow you to learn its configuration information, as well as making sure that the right bits are set in the PCI command register (iospace enabled, memory mapped space enabled, bus master enabled). In fact, you can probably develop most of the driver this way. There are a couple of functions that have to be specified in the ifnet structure (transmission start, adapter init, adapter stop, ioctl, etc...) which are called from higher protocol layers, but you can stub these out in such a way that they do nothing normally but can be re-mapped by your LKM initialization routine so that they call into the routines loaded with the LKM. You also have to unmap the routines when the LKM is removed; once the LKM is unloaded, trying to jump to the addresses where its routines used to reside will cause a panic. You can also panic the system by making a coding error in the LKM. You could probably extend this somewhat to create a generic mechanism for implementing all PCI ethernet drivers as LKMs, but then you'd have to come up with a way to implement diskless booting (you can't load the driver LKM until you mount the rootfs, but you can't mount the rootfs until you load the driver LKM, but you can't load the driver LKM until you mount the rootfs, but...). -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 01:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23963 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 01:05:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23958 for ; Thu, 13 Aug 1998 01:05:37 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id JAA02070 for ; Thu, 13 Aug 1998 09:05:06 +0100 (BST) Message-ID: <35D29E32.81A62F7D@tdx.co.uk> Date: Thu, 13 Aug 1998 09:05:06 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Device / Driver presentation advice needed... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I'm now getting on quite well with the device driver I'm writing, but I'm stuck as to how best it is to present the 'device' to the outside world... If I reserve 3 bits of the minor number to indicate the actual card in the system, I can then use the remaining 5 bits to give different 'presentations' of the device (Is this good practice?) The device in question has 8 x 16 bit input registers. I can either let the application software select these via ioctl(), or I can use the minor bits to map out say, /dev/daqb0a /dev/daqb0b ... (With 1 /dev/daqb device for each channel). Latency when switching between channels is fairly high (though exactly how high I haven't measured yet - when you switch channels you have to wait for the hardware to become ready again) Which is the preferred method? - by using the minor bits to map out multiple devices (one per channel) or by making the application issue ioctl()'s to control it? - Or is it just a design decision? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 01:06:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24048 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 01:06:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24032; Thu, 13 Aug 1998 01:06:33 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.7/8.7.3) with SMTP id BAA08861; Thu, 13 Aug 1998 01:06:02 -0700 (PDT) Date: Thu, 13 Aug 1998 01:06:02 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: vmopar state in 2.2.7? 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'm having a problem with my INN 2.1 newsreader machines NFS mounting the spool. The nnrpd's are occasionally getting stuck in what top shows as the vmopar state. ps shows the process in Ds state. No kill (obviously) will get it unstuck, and nothing else I do seems to make it come back to life. The NFS server is a Network Appliance, running latest released code, UDP mounts, v2 NFS. Any tip appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 01:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25673 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 01:21:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25664 for ; Thu, 13 Aug 1998 01:21:22 -0700 (PDT) (envelope-from nadav@csa.cs.technion.ac.il) Received: from csd.csa (csd [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with SMTP id LAA03275; Thu, 13 Aug 1998 11:21:02 +0300 (IDT) Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id LAA27558; Thu, 13 Aug 1998 11:20:54 +0300 Date: Thu, 13 Aug 1998 11:20:53 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: chris/reman cc: Nick Hibma , Josef Grosch , FreeBSD hackers mailing list Subject: Re: solaris is free. In-Reply-To: <35D1A991.26389012@student.unsw.edu.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 Thu, 13 Aug 1998, chris/reman wrote: > Nick Hibma wrote: > > > To be honest, x86 SOlaris has always been a bit a forgotten child in the > > Sun family. Sun likes to ship complete systems they can reliably > > support. Giving supports to PC weenies is not one of their favourite > > hobbies. > > Thats funny, because the uni. where I am at (UNSW, Sydney) the comp sci > labs were originally running (and still is) a mix of decstations and > labtams running SunOS, when they redid their workstations upstairs they > bought p200's and stuck x86 SunOS on them, weird eh. Personally I would > have saved the money bought cheaper workstations and stuck linux or > freebsd on them, but what can you do when your only an undergrad, and > your uni purchasing scheme is up $h*t creek. Here they use Solaris (on SPARC) for almost anything (including the machine I use to write this email). When they wanted an OS with sources they went and paid some $10000 or some such for an educational source license for Solaris/x86 (though normally they use Sun hardware too). The fact that on the day they were supposed to receive the CD Sun backed off the deal and wanted another ~$10000 didn't bother them at all :-( I tell you, many times, being a PhD student sucks just as bad... It was kind of funny though, because I was installing FreeBSD for a friend in the same room where they were installing Solaris/x86. Eventhough they were installing from a CD on a PII/300MHz and I was installing over FTP from the other end of the world on a P5/90MHz, I had fvwm95 and Netscape running before they managed to have Solaris even boot. Took them another month to make CDE work... > > Then again I spose they were going for tried and tested, (insert remark about > tired and bested here) > > regards, chris > > -- > Christopher Day > > E-Mail the_reman@hotmail.com > Homepage http://www.geocities.com/TimesSquare/Lair/1218 > > when the rain/when the children reign/keep your conscience in the dark > melt the statues in the park - Fall On Me, REM > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 01:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26851 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 01:36:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26816 for ; Thu, 13 Aug 1998 01:36:13 -0700 (PDT) (envelope-from kev@lab321.ru) Received: from localhost (kev@localhost) by lab321.ru (8.8.8/8.8.5) with SMTP id PAA19515 for ; Thu, 13 Aug 1998 15:35:40 +0700 (OSS) Date: Thu, 13 Aug 1998 15:35:40 +0700 (OSS) From: Eugeny Kuzakov To: hackers@FreeBSD.ORG Subject: 3.0-19980804 & ipfilter & ipnat & panics ! 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 ! I have installed subj. After 3-5 min reconfiguration if ipnat permanently kernel panic.... ipnat config: map ppp1 193.168.6.0/24 -> a.b.c.d/32 proxy port ftp ftp/tcp map ppp1 193.168.6.0/24 -> a.b.c.d/32 portmap udp 20000:60000 map ppp1 193.168.6.0/24 -> a.b.c.d/32 map ppp1 193.168.7.0/24 -> a.b.c.d/32 proxy port ftp ftp/tcp map ppp1 193.168.7.0/24 -> a.b.c.d/32 portmap udp 20000:60000 map ppp1 193.168.7.0/24 -> a.b.c.d/32 map ppp1 193.168.8.0/24 -> a.b.c.d/32 proxy port ftp ftp/tcp map ppp1 193.168.8.0/24 -> a.b.c.d/32 portmap udp 20000:60000 map ppp1 193.168.8.0/24 -> a.b.c.d/32 :) Now trying do downgrade to previous snap... Can anyone help me ? It is very important for me and need very quickly. Thanks. I am available at uni #5885106. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 03:32:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05428 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 03:32:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05411 for ; Thu, 13 Aug 1998 03:32:41 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id MAA02666 for ; Thu, 13 Aug 1998 12:32:02 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0z6ufp-002ZjZC; Thu, 13 Aug 98 12:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 13 Aug 1998 12:03:54 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@freebsd.org; Thu, 13 Aug 1998 11:57:23 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #1 built 1998-Jun-6) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: developing device drivers In-Reply-To: <199808130530.BAA27253@skynet.ctr.columbia.edu> from Bill Paul at "Aug 13, 98 01:30:54 am" To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) Date: Thu, 13 Aug 1998 11:57:23 +0200 (CEST) Organization: Kitchen Table Systems Reply-To: hm@kts.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 Bill Paul wrote: > I second this. If you look in /usr/share/examples, you'll find a > couple of sample LKMs written by Terry Lambert. I hijacked the syscall > example from here and used it a lot to experiment with the XL driver. I'd really like to write drivers (for ISA cards) as LKM modules, but so far i don't know how to assign 1) the IRQ, 2) the iobase and 3) the membase ( and perhaps flags and spl) to the LKM at module load time. Did i miss something ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 04:11:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12368 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 04:11:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsd.synx.com (rt.synx.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA12304 for ; Thu, 13 Aug 1998 04:10:54 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn [192.1.1.241]) by bsd.synx.com (8.6.12/8.6.12) with ESMTP id MAA03143; Thu, 13 Aug 1998 12:08:03 +0100 Message-Id: <199808131108.MAA03143@bsd.synx.com> Date: Thu, 13 Aug 1998 13:08:03 +0200 (CEST) From: Remy NONNENMACHER Reply-To: remy@synx.com Subject: Re: network problem with FreeBSD/Yard (yardnetd) To: didier@omnix.net cc: support@yard.de, hackers@FreeBSD.ORG 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 On 12 Aug, Didier Derny wrote: > On Wed, 12 Aug 1998, Remy NONNENMACHER wrote: > >> >> no, TCP_NODELAY allows your local stack to immediatly send packets to >> peer without waiting for a ack. It's also called the Nagle algo. >> It is intented for applications sending a lot of small packets. Delaying >> send in this case is good since it allows the local stack to accumulate >> data and build bigger pakets. >> > > I did some testing with the ...ack_delayed=1 (not modified) > and with the TCP_NODELAY forced in tcp_output.c (horrible hack) > > I obtained the same result and the database was really fast > so, TCP_NODELAY could at least be a work around if Yard compiled a version > of their program with this flag set. > (actually the database is unusable 1 raw/s [without any hack]) > but I'm not sure if it's the best solution > > By the way, I aslo did some testing with tcpblast on the loopback > > with ...ack_delayed=1 and without my awful hack on TCP_NODELAY > I get a repeateable 30Mbs/s > MBytes/s, i suppose. > with ..ack_delayed=0 or the hack I get a very irregular result going from > 2 to 30 Mb/s > That's due to the fact that tcpblast uses the discard service so data flows only on one direction. NODELAY=0 and delayed_ack=1 give you the best performance in that case because pushing a lot of data onto the socket forces sending of concatenated data and, on the other side, acks are generated quickly for big amounts of data. (also note that disabling delayed_ack forces the peer to send a ack for each PUSHed packet, that is the case for each write() with NODELAY. In that case you can consider that setting NODELAY on the sender side also (partially) controls the ack delaying on the other side) The situation would be the opposite if, for example, you send 5 paquets of 50 bytes (5 write(), creating two physical packets), then wait for a response..... (may be the case for your DB). Once again, getting the two parameters the right value needs: - a good knowledge of the flow behaviour (between client and server) and preferably: - a client/server software behaving always the same way. (ie, not something like 50% ping/pong and 50% one way) Also remind that getting 98Mb/s for 10% of the time and 10Mb/s for 90% is worst than having always 50Mb/s About the sanity of hacking NODELAY in the kernel, hum, well, imagine yourself with a proprietary Unix and no possibility to have the TCP_NODELAY engraved in the application.....you could die of that !! (i know: i saw bodies..;). RN. (BTW, this is interesting. I will spend one day writting a little client/server tools to test all best/worst behaviour i already encountered). Bonne journee. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 04:19:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13306 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 04:19:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.iol.ie (mail2.mail.iol.ie [194.125.2.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13300 for ; Thu, 13 Aug 1998 04:19:26 -0700 (PDT) (envelope-from Martind@iol.ie) Received: from default (Byte@dialup-039.cork.iol.ie [194.125.43.39]) by mail.iol.ie Sendmail (v8.8.8) with ESMTP id MAA13703 for ; Thu, 13 Aug 1998 12:18:46 +0100 Message-Id: <199808131118.MAA13703@mail.iol.ie> Reply-To: From: "Martind" To: Subject: gpm Date: Thu, 13 Aug 1998 12:16:08 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know you may not be the right people to tell this, but I dont know who else to ask. Why not port gpm from linux to FreeBSD. I am saying this because I have gotten lots of linux users to change to FreeBSD and they all miss that feature, I as a all time (well except the start) have been using FreeBSD and I think I would be a great addition to the o/s. Thanks for your time Byte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 04:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13536 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 04:22:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsd.synx.com (rt.synx.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA13474 for ; Thu, 13 Aug 1998 04:21:11 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn [192.1.1.241]) by bsd.synx.com (8.6.12/8.6.12) with ESMTP id MAA03256; Thu, 13 Aug 1998 12:17:47 +0100 Message-Id: <199808131117.MAA03256@bsd.synx.com> Date: Thu, 13 Aug 1998 13:17:47 +0200 (CEST) From: Remy NONNENMACHER Reply-To: remy@synx.com Subject: Re: Moving ahead with LDAP To: stephane@lituus.fr cc: pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808122101.XAA00420@sequoia.lituus.fr> 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 Aug, Stephane Legrand wrote: > Peter van Heusden writes: > > After a frustrating meeting with a local PHB, I've decided to try and put > > some more structured involvement into making FreeBSD easily manageable via > > a browser-like UI (as discussed on freebsd-hackers 2 months ago under the > > subject 'Adding a new user interface to FreeBSD'). As discussed then, LDAP > > might be a good tool to store configuration info in. > > > > The existing port of the UMich LDAP server, is, however sadly inadaquate. > > I have applied all patches I know of (Terry Lambert's collection from > > Critical Angle and elsewhere, as well as the patches forthcoming from > > freebsd-hackers), and created an updated port including the patches > > (and notified past (and possible future) port maintainers) but that still > > leaves UMich LDAP at LDAP v.2. > > > > Thus, I am interested in knowing who might want to work on moving ahead > > with better LDAP support on FreeBSD, with the intention of putting > > together and implementing a plan to get working LDAP v.3. > > > > So, who is interested? > > > > Just my 2 eurocents but does a software like "cfengine" > (/usr/ports/sysutils/cfengine) could be more adapted than something > like LDAP ? > > I quote the "cfengine" doc : > > "Cfengine is a tool for setting up and maintaining BSD and > System-5-like operating system optionnally attached to a TCP/IP > network". > Tried a look on it ? quiet tricky !! (and lacking a GUI, as i remember). Comparatively, LDAP is clear and simple !!. (and the web500gw (http://www.tu-chemnitz.de/~fri/web500gw) can be an HTTP converter entry point). RN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 05:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19164 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:08:47 -0700 (PDT) (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 FAA19156 for ; Thu, 13 Aug 1998 05:08:42 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id OAA02778; Thu, 13 Aug 1998 14:07:49 +0200 (MET DST) Date: Thu, 13 Aug 1998 14:07:49 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: hm@kts.org cc: FreeBSD hackers mailing list Subject: Re: developing device drivers 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 second this. If you look in /usr/share/examples, you'll find a > > couple of sample LKMs written by Terry Lambert. I hijacked the syscall > > example from here and used it a lot to experiment with the XL driver. > > I'd really like to write drivers (for ISA cards) as LKM modules, but so > far i don't know how to assign 1) the IRQ, 2) the iobase and 3) the membase > ( and perhaps flags and spl) to the LKM at module load time. > > Did i miss something ? Perhaps, Have a look at the verious examples, for example the wcd driver. Another possibility is to write a device driver that hooks into the kernel at boot time, picks up the relevant information and stores it in a struct. Besides attaching to the device getting that information and maybe initialising the device it doesn't do anything. About 200 lines of code should be easy enough to debug. Then you write an LKM that abuses this information struct to initialise the card as soon as the LKM is loaded. If you get the init and deinit right in your LKM there should be no problem. It worked for me while doing some work on a USB driver stack. If needed I can send that code to you as an example. Or pick it up at http://www.etla.net/~n_hibma/usb/usb.pl Cheers, Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 05:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19294 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:10:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19244; Thu, 13 Aug 1998 05:10:02 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199808131210.FAA19244@hub.freebsd.org> Subject: Re: lists dead? In-Reply-To: <199808130121.SAA15589@hub.freebsd.org> from "terry@lambert.org" at "Aug 12, 98 06:21:45 pm" To: terry@lambert.org Date: Thu, 13 Aug 1998 05:10:01 -0700 (PDT) Cc: 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 terry@lambert.org wrote: > Majordomo not responding? > > -- Terry Lambert > Terry, i you need to test the lists subscribe and send mail to test@freebsd.org. not the regular lists. this message now appears in the archives ;( repeated offensees are a reason to be removed from the lists ;((( jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 05:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19592 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:13:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ic.vrn.ru (ic.vrn.ru [195.98.64.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19563 for ; Thu, 13 Aug 1998 05:12:48 -0700 (PDT) (envelope-from bazilio@monitord.vrn.ru) Received: from dialup34.vrn.ru (dialup34.vrn.ru [195.98.64.192]) by ic.vrn.ru (8.8.8/Relcom-2A) with SMTP id QAA17396 for ;Thu, 13 Aug 1998 16:01:48 +0400 (MSD) Received: from baz_station [192.168.100.10] by monitor.voronezh.su [127.0.0.1] with SMTP (MDaemon.v2.7.SP0.R) for ; Thu, 13 Aug 98 14:25:56 +0400 Message-ID: <000801bdc6a4$6e6fd180$0a64a8c0@baz_station.monitord.vrn.ru> From: "Vasily V. Grechishnikov" To: "Bill Paul" Cc: Subject: Re: Some errors in XL driver ? Date: Thu, 13 Aug 1998 14:23:35 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.0 X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Bill Paul To: Vasily V. Grechishnikov Cc: hackers@freebsd.org Date: 12 Á×ÇÕÓÔÁ 1998 Ç. 1:01 Subject: Re: Some errors in XL driver ? >Of all the gin joints in all the towns in all the world, Vasily V. >Grechishnikov had to walk into mine and say: > >> Hi ! >> Today I had to test 3C905 NIC. After downloading XL driver >> from www.freebsd.org/~/wpaul I had strange results. NIC detection >> and autonegotiation works fine but some performance problem >> occured - 380-400Kb/s at 10Mbps. After looking at network >> statistic I saw very high Ierrs count. Here netstat -ni from my >> test box running 2.2.7-RELEASE after downloading 12MB >> file from local ftp. Whats happen ? >> >> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs >> Coll >> xl0 1500 00.a0.24.4d.c3.3b 9305 1757 4113 0 >> 0 >> xl0 1500 192.168.100 192.168.100.245 9305 1757 4113 0 >> 0 Now my 3c905B works nicely. netstat -ni after applying patch listed below: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 332 xl0 1500 192.168.100 192.168.100.245 9083 4 4018 1565 332 lp0* 1500 0 0 0 0 0 tun0* 1500 0 0 0 0 0 sl0* 552 0 0 0 0 0 ppp0* 1500 0 0 0 0 0 lo0 16384 26 0 26 0 0 lo0 16384 127 127.0.0.1 26 0 26 0 0 > >Aieeee! I think I found the cause of this problem. The autonegotiation >code is setting the modes incorrectly. Please try to fix this using >one of the following methods: > >- Force the card to 10mbps/half-duplex mode using the following command: > # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex > This is just to see if setting the mode correctly clears up the > problem. If so, do one of the next to things. > >- Apply the following patch to if_xl.c, recompile your kernel, and > reboot: > >--- if_xl.c 1998/08/11 02:13:59 1.33 >+++ if_xl.c 1998/08/11 15:26:28 >@@ -796,13 +796,13 @@ > ability & PHY_ANAR_10BTFULL) { > ifm->ifm_media = IFM_ETHER|IFM_10_T|IFM_FDX; > media &= ~PHY_BMCR_SPEEDSEL; >- media &= ~PHY_BMCR_DUPLEX; >+ media |= PHY_BMCR_DUPLEX; > printf("(full-duplex, 10Mbps)\n"); > } else if (advert & PHY_ANAR_10BTHALF && > ability & PHY_ANAR_10BTHALF) { > ifm->ifm_media = IFM_ETHER|IFM_10_T|IFM_HDX; > media &= ~PHY_BMCR_SPEEDSEL; >- media |= PHY_BMCR_DUPLEX; >+ media &= ~PHY_BMCR_DUPLEX; > printf("(half-duplex, 10Mbps)\n"); > } > > >- Download a new copy of if_xl.c from www.freebsd.org/~wpaul/3Com, > recompile your kernel and reboot. > >As you can see, I transposed a couple of lines: the chip is detecting >the right modes, but the code later sets the duplex mode incorrectly. >I'm not sure how this crept in, but it explains the poor performance >at 10Mbps: if you set the duplex bit incorrectly, the card behaves >very strangely. I didn't notice this initially because the machine I >use for 10Mbps testing has a 3c900 card, which does not have a PHY, >hance the autoneg code is never used. The other code in xl_setmode_mii() >which manually sets the chip modes gets this right, which is why >setting the mode manually works. > >I apologize for this stupid mistake; that's what I get for not doing >proper testing. Naturally, at 100Mbps, which is what my 3c905B test >machines were set for, it works right. > >[chop] > >> dmesg output (disabled XL_USEIOSPACE), else if this variable >> defined we has supplement warning xl0: command never completed!: > >[chop] > >This I want to know more about. It anybody else sees this, please >let me know. Try to show me where the warning appears and whether or >not it affects the operation of the NIC. > >-Bill > >-- >=========================================================================== == >-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu >Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >=========================================================================== == > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" >=========================================================================== == > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 05:37:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23270 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:37:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tig.com.au (mail.tig.com.au [209.76.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23265 for ; Thu, 13 Aug 1998 05:36:58 -0700 (PDT) (envelope-from z2172268@student.unsw.edu.au) Received: from student.unsw.edu.au (p30-max8.syd.ihug.com.au [209.79.138.94]) by tig.com.au (8.8.8/8.7.3) with ESMTP id WAA16500; Thu, 13 Aug 1998 22:35:14 +1000 (EST) Message-ID: <35D2DD0D.C6EE27E5@student.unsw.edu.au> Date: Thu, 13 Aug 1998 22:33:17 +1000 From: chris/reman X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: "Daniel O'Connor" CC: Nick Hibma , Josef Grosch , FreeBSD hackers mailing list Subject: Re: solaris is free. References: <199808130203.LAA21212@cain.gsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > Thats funny, because the uni. where I am at (UNSW, Sydney) the comp sci labs [snip my stuff] > > Then again I spose they were going for tried and tested, (insert remark about > > tired and bested here) > At least when your uni decided to upgrade to SOlaris they bought new hardware! > When I was at uni (a few months ago) they where running Solaris on Sparc 10's > :( > > They got 2 E450's just as I left tho.. bastards ;) > well then you'll love this they still have a lab full of sparc classics running, they so awfully slow, you could see X refresh the screen. I don't know how much worse it can get, cept maybe a text term that slow! regards, chris -- Christopher Day E-Mail the_reman@hotmail.com Homepage http://www.geocities.com/TimesSquare/Lair/1218 when the rain/when the children reign/keep your conscience in the dark melt the statues in the park - Fall On Me, REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 05:41:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23740 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:41:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23735 for ; Thu, 13 Aug 1998 05:41:06 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id FAA09318; Thu, 13 Aug 1998 05:40:09 -0700 (PDT) Message-Id: <199808131240.FAA09318@implode.root.com> To: "Vasily V. Grechishnikov" cc: "Bill Paul" , freebsd-hackers@FreeBSD.ORG Subject: Re: Some errors in XL driver ? In-reply-to: Your message of "Thu, 13 Aug 1998 14:23:35 +0400." <000801bdc6a4$6e6fd180$0a64a8c0@baz_station.monitord.vrn.ru> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 05:40:09 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Now my 3c905B works nicely. >netstat -ni after applying patch listed below: >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs >Coll >xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 >332 1565 output errors? That doesn't look so nice to me... -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 Thu Aug 13 05:52:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24776 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 05:52:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smok.apk.net (mail.apk.net [207.54.158.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24769 for ; Thu, 13 Aug 1998 05:52:08 -0700 (PDT) (envelope-from stuart@junior.apk.net) Received: from junior.apk.net (stuart@junior.apk.net [207.54.158.20]) by smok.apk.net (8.9.1/8.9.1/ts-apk-rel.980722) with ESMTP id IAA07426; Thu, 13 Aug 1998 08:38:53 -0400 (EDT) Received: from localhost by junior.apk.net (8.9.1/8.9.1) with SMTP id IAA24263; Thu, 13 Aug 1998 08:38:51 -0400 (EDT) Date: Thu, 13 Aug 1998 08:38:51 -0400 (EDT) From: Stuart Krivis To: Nadav Eiron cc: FreeBSD hackers mailing list Subject: Re: solaris is 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 Thu, 13 Aug 1998, Nadav Eiron wrote: > funny though, because I was installing FreeBSD for a friend in the same > room where they were installing Solaris/x86. Eventhough they were > installing from a CD on a PII/300MHz and I was installing over FTP from > the other end of the world on a P5/90MHz, I had fvwm95 and Netscape > running before they managed to have Solaris even boot. Took them another > month to make CDE work... They must have been having a bad day. :-) I didn't find x86 2.6 to be difficult to install. CDE works also. There _are_ some reasons for choosing x86. 1. You run Solaris SPARC and want a uniform environment. 2. You rely on SMP. x86 seems to be better at this than FreeBSD or Linux at this point. (No hard proof on this one, but it seems to be the case given our limited testing.) 3. You need a name-brand solution to sell to the bosses or customers. 4. You need someone to blame when things go wrong. :-) (Here boss, this is Jordan's phone #, talk to him about this problem... hehe) It is very nice to be able to say something like, "We isolated the problem to "x" and have called SunSoft. They said such and such and this is the estimated timetable for a solution. (There may be no solution, in which case you have trouble. But this could happen with anything.) -- Stuart Krivis stuart@krivis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 06:56:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00601 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 06:56:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00596 for ; Thu, 13 Aug 1998 06:56:25 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id JAA01261 for ; Thu, 13 Aug 1998 09:56:42 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 13 Aug 1998 09:56:42 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: freebsd-hackers@FreeBSD.ORG Subject: Re: Some errors in XL driver ? In-Reply-To: <199808131240.FAA09318@implode.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 xl0 1500 00.10.4b.98.fa.3b 127761 4 39952 0 0 wooo :) great performance too. using the xl driver snapshot as of late yersterday. (on hands and knees) could someone at least add the line to src/conf/files for the xl driver? it's a pain building a kernel after cvsup. (well i'm just lazy i guess, but it's kinda annoying that config doesn't complain about the unknown option and then i boot with no network.) thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Thu, 13 Aug 1998, David Greenman wrote: > >Now my 3c905B works nicely. > >netstat -ni after applying patch listed below: > >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > >Coll > >xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 > >332 > > 1565 output errors? That doesn't look so nice to me... > > -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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 07:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04855 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 07:29:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA04850 for ; Thu, 13 Aug 1998 07:29:15 -0700 (PDT) (envelope-from leisner@sdsp.mc.xerox.com) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <53190(2)>; Thu, 13 Aug 1998 07:28:42 PDT Received: from gnu.sdsp.mc.xerox.com (gnu [13.231.133.90]) by gemini.sdsp.mc.xerox.com (8.8.7/8.8.7) with SMTP id KAA02234; Thu, 13 Aug 1998 10:27:13 -0400 (EDT) Received: from gnu (localhost) by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA13406; Thu, 13 Aug 98 10:27:12 EDT Message-Id: <9808131427.AA13406@gnu.sdsp.mc.xerox.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stuart Krivis Cc: Nadav Eiron , FreeBSD hackers mailing list Subject: Re: solaris is free. In-Reply-To: Your message of "Thu, 13 Aug 1998 05:38:51 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 07:27:11 PDT From: "Marty Leisner" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I had solaris 2.5...with the patched disks... I have several machines (intel pc's)...they both run redhat linux and freebsd without a problem (and NT and win95). I couldn't install solaris on either machine...gawd, Sun got a lot to learn... -- marty leisner@sdsp.mc.xerox.com The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer Murray Gell-mann in the NY Times To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 07:40:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05776 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 07:40:28 -0700 (PDT) (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 HAA05770 for ; Thu, 13 Aug 1998 07:40:27 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id HAA24625 for freebsd-hackers@freebsd.org; Thu, 13 Aug 1998 07:38:15 -0700 (PDT) (envelope-from dhw) Date: Thu, 13 Aug 1998 07:38:15 -0700 (PDT) From: David Wolfskill Message-Id: <199808131438.HAA24625@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 13 Aug 1998 08:38:51 -0400 (EDT) >From: Stuart Krivis >There _are_ some reasons for choosing [Solaris] x86. >1. You run Solaris SPARC and want a uniform environment. (Well, speaking from a sysadmin perspective, it's not at all clear to me that mixing Solaris x86 & Solaris SPARC yields an environment I'd characterize as "uniform".... That's just my perspective, though....) >2. You rely on SMP.... >3. You need a name-brand solution to sell to the bosses or customers. >4. You need someone to blame when things go wrong. :-)... 5. You have a commercial software package for which a Solaris version is available, but the vendor/author has shown no sign of being interested in porting to an OS whose source is freely available. 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 Thu Aug 13 08:07:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09236 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 08:07:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA09227 for ; Thu, 13 Aug 1998 08:07:55 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA27984; Thu, 13 Aug 1998 11:10:13 -0400 From: Bill Paul Message-Id: <199808131510.LAA27984@skynet.ctr.columbia.edu> Subject: Re: Some errors in XL driver ? To: dg@root.com Date: Thu, 13 Aug 1998 11:10:11 -0400 (EDT) Cc: bazilio@monitord.vrn.ru, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808131240.FAA09318@implode.root.com> from "David Greenman" at Aug 13, 98 05:40:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, David Greenman had to walk into mine and say: > >Now my 3c905B works nicely. > >netstat -ni after applying patch listed below: > >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > >Coll > >xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 > >332 > > 1565 output errors? That doesn't look so nice to me... > > -DG The oerrors counter is incremented either if there's a watchdog timeout, or by the xl_stats_update() routine when reading the stats counters. The only statistic that's counted as an output error is 'FramesDeferred,' which the manual describes as the number of times a transmit packet must defer to network traffic. These occur only in half-duplex modes, for obvious reasons. Perhaps it's not correct to account for this as an output error? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 08:10:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09630 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 08:10:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from snitterly.nanoteq.co.za (snitterly.nanoteq.co.za [196.37.90.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09398 for ; Thu, 13 Aug 1998 08:09:27 -0700 (PDT) (envelope-from edebruin@iname.com) Received: from iname.com (mossie.nanoteq.co.za [196.37.91.6]) by snitterly.nanoteq.co.za (8.8.3/8.8.3) with ESMTP id RAA17234 for ; Thu, 13 Aug 1998 17:13:35 GMT Message-ID: <35D31D59.5DBDA848@iname.com> Date: Thu, 13 Aug 1998 17:07:37 +0000 From: eT X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: linking dev in kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greets According to FreeBSD DDWG (device driver writer's guide) section 4.1.2 one is supposed to add your device driver's hookup points to the file: /usr/src/sys/i386/i386/conf.c This file doesn't seem to exist on my RELEASE 2.2.6 Did section 4.1.2 fall away or how is it done? Does this apply to PCI cards as well? eT -- Etienne de Bruin E-mail: edebruin@iname.com OR edebruin@netscape.net WWW: http://listen.to/eT Forcefully advancing the Kingdom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 08:22:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11483 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 08:22:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11477 for ; Thu, 13 Aug 1998 08:22:51 -0700 (PDT) (envelope-from hans@news.IAEhv.nl) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.8.8/1.63) with IAEhv.nl; pid 27369 on Thu, 13 Aug 1998 15:22:19 GMT; id PAA27369 efrom: hans; eto: freebsd-hackers@freebsd.org Received: by truk.brandinnovators.com (8.8.7/BI96070101) for id RAA14501; Thu, 13 Aug 1998 17:05:48 +0200 (CEST) Message-Id: <199808131505.RAA14501@truk.brandinnovators.com> From: hans@brandinnovators.com (Hans Zuidam) Subject: bootpgw & windows NT To: freebsd-hackers@FreeBSD.ORG Date: Thu, 13 Aug 1998 17:05:48 +0200 (CEST) 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 Hi, In the bootpgw sources it is noted somewhere that using the address of the interface on which the bootp packet is relayed in the giaddr field of the packet is wrong, but done anyway. When using the windowsNT dhcp server to supply IP addresses through bootpgw, windowsNT refuses to send an answer if the giaddr field is not set to the same network as the requested IP address is for: +-------+ +---------+ +-------+ | NT | ----------- | FreeBSD | ----------- | Other | +-------+ 192.9.200 +---------+ 192.9.201 +-------+ giaddr = 192.9.200.xx -> no answer from NT giaddr = 192.9.201.yy -> correct answer from NT I understand that when you have aliases on an interface it is very difficult to find the correct interface address after receiving a broadcast (to say the least.) But apart from the (in the bootpgw sources) noted portability problem is there any compelling reason why bootpgw should not pick the first interface address it finds on the interface it received the bootp broadcast on? Regards, Hans -- H. Zuidam E-Mail: hans@brandinnovators.com Brand Innovators B.V. P-Mail: P.O. Box 1377 de Pinckart 54 5602 BJ Eindhoven, The Netherlands 5674 CC Nuenen Tel. +31 40 2631134, Fax. +31 40 2831138 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 08:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14133 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 08:39:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14119 for ; Thu, 13 Aug 1998 08:39:05 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA11637; Thu, 13 Aug 1998 08:38:23 -0700 (PDT) Message-Id: <199808131538.IAA11637@implode.root.com> To: Bill Paul cc: bazilio@monitord.vrn.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: Some errors in XL driver ? In-reply-to: Your message of "Thu, 13 Aug 1998 11:10:11 EDT." <199808131510.LAA27984@skynet.ctr.columbia.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 08:38:23 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The oerrors counter is incremented either if there's a watchdog timeout, >or by the xl_stats_update() routine when reading the stats counters. >The only statistic that's counted as an output error is 'FramesDeferred,' >which the manual describes as the number of times a transmit packet must >defer to network traffic. These occur only in half-duplex modes, for >obvious reasons. Perhaps it's not correct to account for this as an >output error? I don't know exactly what it means by 'FramesDeferred', but I don't think it should be included as an output error. oerrors should only be incremented when a packet is dropped due to a failure of some kind, e.g. a too many collisions, DMA underrun, or device timeout. -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 Thu Aug 13 09:01:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17205 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 09:01:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17184 for ; Thu, 13 Aug 1998 09:01:05 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id RAA02640; Thu, 13 Aug 1998 17:00:18 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id QAA02315; Thu, 13 Aug 1998 16:59:56 +0100 (BST) Message-ID: <19980813165956.A2303@iii.co.uk> Date: Thu, 13 Aug 1998 16:59:56 +0100 To: David Wolfskill , freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. References: <199808131438.HAA24625@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808131438.HAA24625@pau-amma.whistle.com>; from David Wolfskill on Thu, Aug 13, 1998 at 07:38:15AM -0700 Organization: interactive investor Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 13, 1998 at 07:38:15AM -0700, David Wolfskill wrote: > 5. You have a commercial software package for which a Solaris version is > available, but the vendor/author has shown no sign of being interested > in porting to an OS whose source is freely available. Just out of interest, does this offer open to the door to someone being able to put together a Solaris emulator for FreeBSD, along the same lines as the Linux emulator? FreeBSD: Faster Solaris than Solaris. has a nice ring to it. N -- --+==[ Nik Clayton becomes Just Another Perl Contractor in 30 days. ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 10:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28003 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:03:43 -0700 (PDT) (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 KAA27991 for ; Thu, 13 Aug 1998 10:03:37 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id TAA27373; Thu, 13 Aug 1998 19:03:09 +0200 (MET DST) Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Thu, 13 Aug 1998 19:03:09 +0200 (MET DST) Mime-Version: 1.0 To: Brett Glass Cc: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808130523.XAA07849@lariat.lariat.org> 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 Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 13 Aug 1998 19:03:08 +0200 In-Reply-To: Brett Glass's message of "Wed, 12 Aug 1998 23:23:07 -0600" Message-ID: Lines: 19 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 KAA27997 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass writes: > How soon will FreeBSD move to a 64-bit time_t? The article at > > http://www.wired.com/news/news/technology/story/14390.html > > paints a dire picture; it'd be nice to say that FreeBSD solves the problem > already. Well, they could at least have gone to the trouble of getting the facts right. ``Time is measured in seconds since midnight, 1 January 1970 -- this is known as the "epoch." It is stored in such systems in a variable called "time_t," which can store a value up to 2,147,483,647 -- but no larger.'' 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 Thu Aug 13 10:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00161 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:16:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00131 for ; Thu, 13 Aug 1998 10:16:49 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00793; Thu, 13 Aug 1998 10:14:55 -0700 (PDT) Message-Id: <199808131714.KAA00793@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Martind@iol.ie cc: hackers@FreeBSD.ORG Subject: Re: gpm In-reply-to: Your message of "Thu, 13 Aug 1998 12:16:08 BST." <199808131118.MAA13703@mail.iol.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 10:14:54 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I know you may not be the right people to tell this, but I dont know who > else to ask. Why not port > gpm from linux to FreeBSD. I am saying this because I have gotten lots of > linux users to change to FreeBSD and they all miss that feature, I as a all > time (well except the start) have been using FreeBSD and I think I would be > a great addition to the o/s. See moused(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 Aug 13 10:19:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00731 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:19:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00720 for ; Thu, 13 Aug 1998 10:19:27 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00818; Thu, 13 Aug 1998 10:17:47 -0700 (PDT) Message-Id: <199808131717.KAA00818@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Pielorz cc: hackers@FreeBSD.ORG Subject: Re: Device / Driver presentation advice needed... In-reply-to: Your message of "Thu, 13 Aug 1998 09:05:06 BST." <35D29E32.81A62F7D@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 10:17:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi All, > > I'm now getting on quite well with the device driver I'm writing, but I'm stuck > as to how best it is to present the 'device' to the outside world... > > If I reserve 3 bits of the minor number to indicate the actual card in the > system, I can then use the remaining 5 bits to give different 'presentations' of > the device (Is this good practice?) It's one way to do it. There is a lot more room in the minor though; 32 bits in fact. > The device in question has 8 x 16 bit input registers. I can either let the > application software select these via ioctl(), or I can use the minor bits to > map out say, > > /dev/daqb0a > /dev/daqb0b > .... > > (With 1 /dev/daqb device for each channel). > > Latency when switching between channels is fairly high (though exactly how high > I haven't measured yet - when you switch channels you have to wait for the > hardware to become ready again) > > Which is the preferred method? - by using the minor bits to map out multiple > devices (one per channel) or by making the application issue ioctl()'s to > control it? - Or is it just a design decision? If the device is slow, and the data rate low, an ioctl-based solution is probably as good as any, and simpler to implement. -- \\ 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 Aug 13 10:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01628 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:23:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01608 for ; Thu, 13 Aug 1998 10:23:33 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00864; Thu, 13 Aug 1998 10:21:52 -0700 (PDT) Message-Id: <199808131721.KAA00864@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Wed, 12 Aug 1998 23:23:07 MDT." <199808130523.XAA07849@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 10:21:52 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How soon will FreeBSD move to a 64-bit time_t? The article at > > http://www.wired.com/news/news/technology/story/14390.html > > paints a dire picture; it'd be nice to say that FreeBSD solves the problem > already. Read the article: Certainly by 2038, Unix 'time_t' will be 64 bits or more, assuming Unix survives in some form," said Dennis Ritchie, co-author of the Unix operating system. If you have nothing else to worry about for the next 40 years, I'm sure we can find you something more useful to do. 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 Aug 13 10:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03070 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:30:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03045 for ; Thu, 13 Aug 1998 10:30:48 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00903; Thu, 13 Aug 1998 10:28:06 -0700 (PDT) Message-Id: <199808131728.KAA00903@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Giao Nguyen cc: Mike Smith , Peter van Heusden , freebsd-hackers@FreeBSD.ORG Subject: Re: Moving ahead with LDAP In-reply-to: Your message of "Wed, 12 Aug 1998 18:46:33 EDT." <19980812184633.A18658@beelzebubba.sysabend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 10:28:06 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith said: > > > > This seems to parallel work that was being done by another party whose > > name has been eaten by my mailer (Giao, you know who you are). > > Damn he's persistent :) Ask yourself; why is he pushing me to do something? Did I promise to do it? Am I late in delivering? 8) > > Are there any portable LDAPv3 servers available? Is the UMich server > > at a developmental dead-end? > > In the exact order asked. I can't think of any except for UMich* and I > hope not. There will be some significant ripping aparts to get it to v3 > and it'll require some significant chunks of work. I've reached the same > state as Peter (well, except for the port part. I haven't put together > the files for that, but it's not v3 yet so what's the point?). The point is that 2.2 is better than nothing, even if it's not 3.0. We do need to start somewhere, even if it means starting with an older standard. Given that we have code for this, and it works, it would seem to make more sense to focus elsewhere than to waste resources playing version catch-up games. -- \\ 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 Aug 13 10:35:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04069 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:35:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04053 for ; Thu, 13 Aug 1998 10:34:56 -0700 (PDT) (envelope-from msanders@shell.aros.net) Received: from shell.aros.net (root@shell.aros.net [207.173.16.19]) by mars.aros.net (8.9.1/8.9.1) with ESMTP id LAA04189; Thu, 13 Aug 1998 11:31:04 -0600 (MDT) Received: from shell.aros.net (msanders@localhost.aros.net [127.0.0.1]) by shell.aros.net (8.8.7/8.8.7) with ESMTP id LAA03523; Thu, 13 Aug 1998 11:34:23 -0600 (MDT) Message-Id: <199808131734.LAA03523@shell.aros.net> X-Attribution: msanders To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-reply-to: Your message of "Thu, 13 Aug 1998 07:38:15 PDT." <199808131438.HAA24625@pau-amma.whistle.com> X-Mailer: MH 6.8.3 Date: Thu, 13 Aug 1998 11:34:23 -0600 From: "Michael K. Sanders" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808131438.HAA24625@pau-amma.whistle.com>, David Wolfskill writes : >>From: Stuart Krivis > >>There _are_ some reasons for choosing [Solaris] x86. > >5. You have a commercial software package for which a Solaris version is > available, but the vendor/author has shown no sign of being interested > in porting to an OS whose source is freely available. Only if your application doesn't work under NetBSD's emulation... COMPAT_SVR4(8) NetBSD System Manager's Manual COMPAT_SVR4(8) NAME compat_svr4 - setup procedure for running SVR4/iBCS2 binaries DESCRIPTION NetBSD supports running SVR4/iBCS2 binaries. This code has been tested on i386 and sparc systems. Most programs should work, but not ones that use or depend on: kernel internal data structures the /proc filesystem the pty subsystem the ticotsord loopback rpc mechanism (nis uses this) sound and video interfaces threads (ttsession uses threads) the streams administrative driver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 10:51:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07549 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:51:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07543 for ; Thu, 13 Aug 1998 10:51:26 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id NAA19891; Thu, 13 Aug 1998 13:47:51 -0400 (EDT) From: Peter Dufault Message-Id: <199808131747.NAA19891@hda.hda.com> Subject: Re: Allocating memory in a network device driver In-Reply-To: <199808122248.PAA09142@bubba.whistle.com> from Archie Cobbs at "Aug 12, 98 03:48:23 pm" To: archie@whistle.com (Archie Cobbs) Date: Thu, 13 Aug 1998 13:47:46 -0400 (EDT) Cc: Emmanuel.Duros@sophia.inria.fr, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have seen in many device drivers allocating memory in the following > > way: > > > > u_char *buf; > > buf = malloc( BUFSIZ, M_DEVBUF, M_NOWAIT); > > > > Do we get the same result with : ? > > > > u_char buf[BUFSIZ]; > > The kernel malloc works just like the libc malloc... The allocation is preferred for large objects since an auto object will be on the kernel stack. The kernel stack is a finite resource and (in general and not FBSD specifically) on some systems isn't shared across multiple processors. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 10:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07742 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:53:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07737 for ; Thu, 13 Aug 1998 10:53:12 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id LAA13111; Thu, 13 Aug 1998 11:52:39 -0600 (MDT) Message-Id: <199808131752.LAA13111@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Thu, 13 Aug 1998 11:13:25 -0600 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) From: Brett Glass Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199808130523.XAA07849@lariat.lariat.org> 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 KAA07738 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:03 PM 8/13/98 +0200, Dag-Erling Coidan Smørgrav wrote: >Well, they could at least have gone to the trouble of getting the >facts right. Yes, you're right.... They're short a couple billion. But the sentiment is there. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 10:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07876 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 10:53:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07868 for ; Thu, 13 Aug 1998 10:53:53 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id LAA13123; Thu, 13 Aug 1998 11:52:44 -0600 (MDT) Message-Id: <199808131752.LAA13123@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Thu, 13 Aug 1998 11:41:05 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG In-Reply-To: <199808131721.KAA00864@antipodes.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:21 AM 8/13/98 -0700, Mike Smith wrote: >Read the article: > > Certainly by 2038, Unix 'time_t' will be 64 bits or more, > assuming Unix survives in some form," said Dennis Ritchie, > co-author of the Unix operating system. > >If you have nothing else to worry about for the next 40 years, I'm sure >we can find you something more useful to do. 8) I'd kind of like to do financial projections for my retirement and not have the calculations blow up, as they do now. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 11:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13715 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 11:35:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from staff.sirius.com (staff.sirius.com [205.134.226.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13682; Thu, 13 Aug 1998 11:34:57 -0700 (PDT) (envelope-from peter@staff.sirius.com) Received: (from peter@localhost) by staff.sirius.com (8.8.7/Sirius-Inhouse) id LAA14961; Thu, 13 Aug 1998 11:34:01 -0700 (PDT) From: peter@sirius.com Message-Id: <199808131834.LAA14961@staff.sirius.com> Subject: Re: vmopar state in 2.2.7? In-Reply-To: from Jaye Mathisen at "Aug 13, 98 01:06:02 am" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Thu, 13 Aug 1998 11:34:00 -0700 (PDT) Cc: hackers@FreeBSD.ORG, stable@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 > > > I'm having a problem with my INN 2.1 newsreader machines NFS mounting > the spool. > > The nnrpd's are occasionally getting stuck in what top shows as > the vmopar state. ps shows the process in Ds state. > > > No kill (obviously) will get it unstuck, and nothing else I do seems to > make it come back to life. > > The NFS server is a Network Appliance, running latest released code, > UDP mounts, v2 NFS. > > Any tip appreciated. > We worked around a similar problem (processes left immortal, here in the context of several processes [httpd] writing to the same NFS mounted file [http log file]) by adjusting the timeout value from 0 (never) to 2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in FreeBSD.org's gnats problem report database. It looks like other parts of the kernel (here the vm subsystem) suffer similar problems. It appears to me that an overly optimistic use of tsleep() with both, interrupts disabled and time-out set to infinity, leaves immortal yet paralyzed processes around. >From /usr/src/sys/vm/vm_object.c (a second, similar occurence around line 1261): 1218 /* 1219 * The busy flags are only cleared at 1220 * interrupt -- minimize the spl transitions 1221 */ 1222 if ((p->flags & PG_BUSY) || p->busy) { 1223 s = splvm(); 1224 if ((p->flags & PG_BUSY) || p->busy) { 1225 p->flags |= PG_WANTED; 1226 tsleep(p, PVM, "vmopar", 0); 1227 splx(s); 1228 goto again; 1229 } 1230 splx(s); 1231 } The code in line 1224 checks a condition to see whether somebody else is already performing an operation on object p; in this case it wants to ensure that a wakeup() for the following tsleep() is delivered by setting a flag in line 1225. But what ensures that the world did not change between lines 1224 and 1225? Could the wakeup() happen after 1224 has determined to issue the tsleep() but before the flagging in 1225 was registered? Then it would be missed. Is this a race condition biting heavily hit machines? Try changing lines 1226 and 1261 to something like: tsleep(p, PVM, "vmopar", 5 * hz); >From the tsleep man page: Tsleep is the general sleep call. Suspends the current process until a wakeup is performed on the specified identifier. The process will then be made runnable with the specified priority. Sleeps at most timo / hz seconds (0 means no timeout). If pri includes the PCATCH flag, signals are checked before and after sleeping, else signals are not checked. Re- turns 0 if awakened, EWOULDBLOCK if the timeout expires. If PCATCH is set and a signal needs to be delivered, ERESTART is returned if the cur- rent system call should be restarted if possible, and EINTR is returned if the system call should be interrupted by the signal (return EINTR). This function would return "EWOULDBLOCK" after the time-out expires then, no clue what that will do to your system or apps ;) -- I would expect the blocked process to go away within 5 seconds... Peter Preuss Sirius Connections, San Francisco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 11:35:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13741 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 11:35:05 -0700 (PDT) (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 LAA13721 for ; Thu, 13 Aug 1998 11:35:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA09319; Thu, 13 Aug 1998 11:25:00 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdrN9306; Thu Aug 13 18:24:53 1998 Date: Thu, 13 Aug 1998 11:24:45 -0700 (PDT) From: Julian Elischer To: eT cc: hackers@FreeBSD.ORG Subject: Re: linking dev in kernel In-Reply-To: <35D31D59.5DBDA848@iname.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, 13 Aug 1998, eT wrote: > Greets > > According to FreeBSD DDWG (device driver writer's guide) section 4.1.2 > one is supposed to add your device driver's hookup points to the file: > > /usr/src/sys/i386/i386/conf.c The structure refereded to in the document is now dynamically created. it is up to each driver to add it's own entry to the array when it is initialised.. look in any driver and check the init function and the SYSINIT entry. julian > > This file doesn't seem to exist on my RELEASE 2.2.6 > > Did section 4.1.2 fall away or how is it done? > > Does this apply to PCI cards as well? > > eT > > -- > Etienne de Bruin > E-mail: edebruin@iname.com OR edebruin@netscape.net > WWW: http://listen.to/eT > Forcefully advancing the Kingdom > > > > > 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 Aug 13 12:26:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23707 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 12:26:57 -0700 (PDT) (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 MAA23702 for ; Thu, 13 Aug 1998 12:26:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00367; Thu, 13 Aug 1998 12:24:12 -0700 (PDT) Message-Id: <199808131924.MAA00367@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Thu, 13 Aug 1998 11:41:05 MDT." <199808131752.LAA13123@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 12:24:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:21 AM 8/13/98 -0700, Mike Smith wrote: > > >Read the article: > > > > Certainly by 2038, Unix 'time_t' will be 64 bits or more, > > assuming Unix survives in some form," said Dennis Ritchie, > > co-author of the Unix operating system. > > > >If you have nothing else to worry about for the next 40 years, I'm sure > >we can find you something more useful to do. 8) > > I'd kind of like to do financial projections for my retirement and not > have the calculations blow up, as they do now. time_t is a format for the system current time. As such, you're abusing it mightily if you expect it to be a general-purpose time value. Might I suggest that you should consider using something with perhaps a slightly reduced precision, like anyone else that does work involving longer timeframes? time_t is not a hammer. -- \\ 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 Aug 13 12:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25615 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 12:36:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (kenya-138.ppp.hooked.net [206.169.227.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25565 for ; Thu, 13 Aug 1998 12:35:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id MAA00555; Thu, 13 Aug 1998 12:36:06 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 13 Aug 1998 12:36:05 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Martind cc: hackers@FreeBSD.ORG Subject: Re: gpm In-Reply-To: <199808131118.MAA13703@mail.iol.ie> 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, 13 Aug 1998, Martind wrote: > I know you may not be the right people to tell this, but I dont know who > else to ask. Why not port > gpm from linux to FreeBSD. I am saying this because I have gotten lots of > linux users to change to FreeBSD and they all miss that feature, I as a all > time (well except the start) have been using FreeBSD and I think I would be > a great addition to the o/s. man moused. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD 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 Aug 13 12:40:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26463 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 12:40:13 -0700 (PDT) (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 MAA26447 for ; Thu, 13 Aug 1998 12:40:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00458; Thu, 13 Aug 1998 12:36:35 -0700 (PDT) Message-Id: <199808131936.MAA00458@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephane Legrand cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG Subject: Re: Moving ahead with LDAP In-reply-to: Your message of "Wed, 12 Aug 1998 23:01:35 +0200." <199808122101.XAA00420@sequoia.lituus.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 12:36:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just my 2 eurocents but does a software like "cfengine" > (/usr/ports/sysutils/cfengine) could be more adapted than something > like LDAP ? cfengine is a distribution tool. LDAP is a networked parameter store. The two are very different animals. cfengine is a complete and working "I want it now" solution. LDAP is a ways off yet, but is also the general direction that much of the rest of the industry is trying to go in. -- \\ 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 Aug 13 12:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26961 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 12:41:52 -0700 (PDT) (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 MAA26950 for ; Thu, 13 Aug 1998 12:41:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00486; Thu, 13 Aug 1998 12:38:53 -0700 (PDT) Message-Id: <199808131938.MAA00486@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bruce M. Walter" cc: MAG , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown In-reply-to: Your message of "Tue, 11 Aug 1998 11:02:51 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 12:38:53 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had submitted patches (kern/5863) which corrected the function of the > halt/reboot -p commands and also prioritized and added a third kernel > callout function list which gets called after all of the other drivers > spin-down stuff is called (namely the DPT driver which uses the second > shutdown callout list to sync the array... Very bad to poweroff during > that, take my word) I don't believe any interest was shown, so I just run > the patches here. I just wanted to say that there is interest, and you're still in my "to do" queue. I appreciate you mentioning this every time the issue comes up though, and I do still hope to get through my pile to your work before it goes stale. -- \\ 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 Aug 13 12:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28265 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 12:50:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28248 for ; Thu, 13 Aug 1998 12:50:05 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.8/8.8.5) with SMTP id PAA16401; Thu, 13 Aug 1998 15:48:04 -0400 (EDT) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Thu, 13 Aug 1998 15:48:03 -0400 (EDT) From: "Bruce M. Walter" Reply-To: "Bruce M. Walter" To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown In-Reply-To: <199808131938.MAA00486@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 had submitted patches (kern/5863) which corrected the function of the >> [...snip...] >> I don't believe any interest was shown, so I just run the patches here. Mike Smith writes: > I just wanted to say that there is interest, and you're still in my "to > do" queue. I appreciate you mentioning this every time the issue comes > up though, and I do still hope to get through my pile to your work > before it goes stale. Thanks Mike. This brings up an interesting (to me at least) question though... Terry made a suggestion about altering the at_shutdown queue operation with regards to certain flags (ie: processing the queues once with arg = arg & ~RB_POWEROFF and then again with RB_POWEROFF only presuming (arg & RB_POWEROFF) == RB_POWEROFF). Supposing I come up with a new set of patches doing this and instituting a new RB_ flag (like RB_KILLUPS), would I sendpr these as a new PR or would I post them to bugs as a reply to PR#5863? - B ======================================================================== || Bruce M. Walter || 107 Timber Hollow Court #335 || || Senior Network Consultant || Chapel Hill, NC 27514 || || Fortean Technologies, Inc. || Tel: 919-829-4908 || || Information Technology Consultants || Fax: 919-829-4993 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 13:02:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01288 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 13:02:07 -0700 (PDT) (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 NAA01258; Thu, 13 Aug 1998 13:02:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00604; Thu, 13 Aug 1998 12:59:45 -0700 (PDT) Message-Id: <199808131959.MAA00604@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: peter@sirius.com cc: mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 11:34:00 PDT." <199808131834.LAA14961@staff.sirius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 12:59:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We worked around a similar problem (processes left immortal, here in > the context of several processes [httpd] writing to the same NFS mounted > file [http log file]) by adjusting the timeout value from 0 (never) to > 2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in > FreeBSD.org's gnats problem report database. As this is an NFS-related issue, you should follow this up with Poul Henning (phk@freebsd.org). I understand he's working on NFS amongst other things at the moment (I know he's working on FreeBSD for us, as he keeps sending us invoices... 8). > It looks like other parts of the kernel (here the vm subsystem) suffer > similar problems. It appears to me that an overly optimistic use of > tsleep() with both, interrupts disabled and time-out set to infinity, > leaves immortal yet paralyzed processes around. I don't think you mean interrupts disabled. > >From /usr/src/sys/vm/vm_object.c (a second, similar occurence around > line 1261): > > 1218 /* > 1219 * The busy flags are only cleared at > 1220 * interrupt -- minimize the spl transitions > 1221 */ > 1222 if ((p->flags & PG_BUSY) || p->busy) { > 1223 s = splvm(); > 1224 if ((p->flags & PG_BUSY) || p->busy) { > 1225 p->flags |= PG_WANTED; > 1226 tsleep(p, PVM, "vmopar", 0); > 1227 splx(s); > 1228 goto again; > 1229 } > 1230 splx(s); > 1231 } > > The code in line 1224 checks a condition to see whether somebody else > is already performing an operation on object p; in this case it wants > to ensure that a wakeup() for the following tsleep() is delivered by > setting a flag in line 1225. > > But what ensures that the world did not change between lines 1224 and > 1225? Could the wakeup() happen after 1224 has determined to issue > the tsleep() but before the flagging in 1225 was registered? Then it > would be missed. Is this a race condition biting heavily hit machines? It shouldn't. the splvm() call should mask vm-related activities from its return through to the call to tsleep (where the mask is saved and the mask for the new context is restored). There is a risk that the assumption in the comment is invalid; you would want to look for any likely operations involving PG_BUSY. To track this one further, you would want to look at the code that's responsible for for dealing with pages with PG_WANTED set, and work out why it's never satisfying this request (or if it is, why it's not waking the above caller up). > Try changing lines 1226 and 1261 to something like: > tsleep(p, PVM, "vmopar", 5 * hz); ... > This function would return "EWOULDBLOCK" after the time-out expires then, > no clue what that will do to your system or apps ;) -- I would expect the > blocked process to go away within 5 seconds... I dont' have 2.2 sources to hand, and the above is now just a call to vm_page_sleep, but if the timeout expires, the entire operation is retried, so it should be harmless (although it is masking a legitimate bug). This might be a candidate for a bandaid patch for 2.2 systems, as 2.2 goes into life-support mode. BTW, thanks for looking at this at all, and thanks for making your findings generally known. If you can roll a patch and put it out for general testing, we'd be very interested in hearing about the feedback you get. -- \\ 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 Aug 13 13:05:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02119 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 13:05:02 -0700 (PDT) (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 NAA02098 for ; Thu, 13 Aug 1998 13:05:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00630; Thu, 13 Aug 1998 13:02:33 -0700 (PDT) Message-Id: <199808132002.NAA00630@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bruce M. Walter" cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about shutdown In-reply-to: Your message of "Thu, 13 Aug 1998 15:48:03 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 13:02:33 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I had submitted patches (kern/5863) which corrected the function of the > >> [...snip...] > >> I don't believe any interest was shown, so I just run the patches here. > > Mike Smith writes: > > I just wanted to say that there is interest, and you're still in my "to > > do" queue. I appreciate you mentioning this every time the issue comes > > up though, and I do still hope to get through my pile to your work > > before it goes stale. > > Thanks Mike. This brings up an interesting (to me at least) question > though... Terry made a suggestion about altering the at_shutdown queue > operation with regards to certain flags (ie: processing the queues > once with arg = arg & ~RB_POWEROFF and then again with RB_POWEROFF > only presuming (arg & RB_POWEROFF) == RB_POWEROFF). > > Supposing I come up with a new set of patches doing this and instituting a > new RB_ flag (like RB_KILLUPS), would I sendpr these as a new PR or would > I post them to bugs as a reply to PR#5863? You should be able to submit a followup to the PR itself, and since the changes would affect the PR directly (ie. supersede your previous patches) that would definitely be the best course of action. If you go to http://www.freebsd.org/cgi/query-pr.cgi?pr=5863 and whack the 'submit followup' link at the bottom, it should all happen automagically. -- \\ 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 Aug 13 13:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05033 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 13:17:46 -0700 (PDT) (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 NAA05028 for ; Thu, 13 Aug 1998 13:17:44 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id NAA14664; Thu, 13 Aug 1998 13:17:17 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd014641; Thu Aug 13 13:17:16 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id NAA14261; Thu, 13 Aug 1998 13:17:13 -0700 (MST) From: Terry Lambert Message-Id: <199808132017.NAA14261@usr09.primenet.com> Subject: Re: developing device drivers To: hm@kts.org Date: Thu, 13 Aug 1998 20:17:13 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Hellmuth Michaelis" at Aug 13, 98 11:57:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I second this. If you look in /usr/share/examples, you'll find a > > couple of sample LKMs written by Terry Lambert. I hijacked the syscall > > example from here and used it a lot to experiment with the XL driver. > > I'd really like to write drivers (for ISA cards) as LKM modules, but so > far i don't know how to assign 1) the IRQ, 2) the iobase and 3) the membase > ( and perhaps flags and spl) to the LKM at module load time. > > Did i miss something ? You probe and attach at load time, normally. This means you detect the IRQ/DRQ/IOBase/MemBase/Etc., not assign it. That means you should write the probe code first. The flags and spl have to be dealt with by unloading, modifying, and loading. Frankly, I think you'll not need to change the spl you use since it's pretty much fixed by the kind of device you are driving. You could also provide an ioctl to diddle the flags, and run a program in user space that diddles them one the driver is loaded. You are doing this under -current, right? If not, it's going to be hard to unload, since detaching ISA resources wasn't well supported before the PCMCIA code required it. One of the sample drivers used to be an LPT driver, which grabbed IRQ7; I haven't looked at the hardware part of the codebase for LKM in a while (well, mostly; I did help someone with loading a line discipline recently, but that didn't grab and release resources). Most -current drivers are capable of dual-mode compilation. For specific examples, look in /usr/src/lkm/ for joy, pcic, qcam, and wcd. 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 Thu Aug 13 13:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10175 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 13:35:48 -0700 (PDT) (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 NAA10142 for ; Thu, 13 Aug 1998 13:35:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00878; Thu, 13 Aug 1998 13:33:32 -0700 (PDT) Message-Id: <199808132033.NAA00878@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: wjw@IAEhv.nl cc: hackers@FreeBSD.ORG Subject: Re: Adding system calls In-reply-to: Your message of "Thu, 06 Aug 1998 00:41:37 +0200." <199808052241.AAA05242@surf.IAE.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 13:33:32 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What/were is the receipe to add new system calls. > I'd like to add my own sysctl_* calls. You don't feel that you can overload the current calls? > Are there any directives on what "design" to use while defining these calls. > Like: > - Use only one syscall as a multiplexer > (Which created a not so trivial mess is the current sysctl) This is good if all the subcalls share similar data. > - What parameters are a bad idea to transfer from > user to kernel space? Just the ones you need. > And answers to questions like: > - Where can I find the "user"-data Such as? > - Hoe to I return results for "call-by-ref" parameters Use copyin/copyout and the fu*/su* calls, all of which have manpages in -current. -- \\ 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 Aug 13 14:12:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17227 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:12:01 -0700 (PDT) (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 OAA17206 for ; Thu, 13 Aug 1998 14:11:57 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA04310; Thu, 13 Aug 1998 14:11:29 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd004273; Thu Aug 13 14:11:25 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA16200; Thu, 13 Aug 1998 14:11:22 -0700 (MST) From: Terry Lambert Message-Id: <199808132111.OAA16200@usr09.primenet.com> Subject: Re: gpm To: mike@smith.net.au (Mike Smith) Date: Thu, 13 Aug 1998 21:11:22 +0000 (GMT) Cc: Martind@iol.ie, hackers@FreeBSD.ORG In-Reply-To: <199808131714.KAA00793@antipodes.cdrom.com> from "Mike Smith" at Aug 13, 98 10:14:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > See moused(8) Thanks for the context pointer, Mike... The only expansion for "gpm" I could think of was "Ground Penguin Meat". 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 Thu Aug 13 14:13:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17553 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:13:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17547 for ; Thu, 13 Aug 1998 14:13:18 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id PAA15313; Thu, 13 Aug 1998 15:12:42 -0600 (MDT) Message-Id: <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Thu, 13 Aug 1998 15:03:05 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808131924.MAA00367@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 12:24 PM 8/13/98 -0700, Mike Smith wrote: >> I'd kind of like to do financial projections for my retirement and not >> have the calculations blow up, as they do now. > >time_t is a format for the system current time. As such, you're abusing >it mightily if you expect it to be a general-purpose time value. It's used throughout UNIX and UNIX programs as such. And rightfully so; it's silly to have multiple date formats. >Might I suggest that you should consider using something with perhaps a >slightly reduced precision, like anyone else that does work involving >longer timeframes? This would create an incompatible notation and would make life much more difficult than fixing the basic problem. >time_t is not a hammer. Nope, but I don't intend to carry an entire box of tools to screw in a light bulb.... ;-) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 14:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20068 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:24:14 -0700 (PDT) (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 OAA20054; Thu, 13 Aug 1998 14:24:08 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA08609; Thu, 13 Aug 1998 14:23:41 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd008571; Thu Aug 13 14:23:35 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA16645; Thu, 13 Aug 1998 14:23:32 -0700 (MST) From: Terry Lambert Message-Id: <199808132123.OAA16645@usr09.primenet.com> Subject: Re: lists dead? To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Thu, 13 Aug 1998 21:23:32 +0000 (GMT) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <199808131210.FAA19244@hub.freebsd.org> from "Jonathan M. Bresler" at Aug 13, 98 05:10:01 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 > Terry, > i you need to test the lists subscribe and send mail to > test@freebsd.org. not the regular lists. this message > now appears in the archives ;( > > repeated offensees are a reason to be removed from the lists > ;((( Unfortunately, there's no way to bail out of a "DATA" command. I expected to get a response other than "250 Message accepted for delivery". Sorry about that... there should be a better way of testing whether a message will be sent than actually sending one. Does the "test" address have an autoresponder? Is it backed by the Majordomo code that backs the lists? If so, I guess it's as good as any a method of doing the half-pipe test that I used to accidently send that message. What was the problem, BTW? 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 14:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23246 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:38:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23238 for ; Thu, 13 Aug 1998 14:38:34 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA29683 (5.67b/IDA-1.5); Thu, 13 Aug 1998 22:53:25 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA03913; Thu, 13 Aug 1998 22:03:24 +0200 (CEST) From: Wilko Bulte Message-Id: <199808132003.WAA03913@yedi.iaf.nl> Subject: Re: Anyone useing an ADIC FastStor tape changer successfully? In-Reply-To: <199808122144.OAA22098@pau-amma.whistle.com> from David Wolfskill at "Aug 12, 98 02:44:29 pm" To: dhw@whistle.com (David Wolfskill) Date: Thu, 13 Aug 1998 22:03:24 +0200 (CEST) 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 David Wolfskill wrote... > >In the last episode (Aug 12), David Wolfskill said: [stuff about ADIC > > FastStor tape changer] > > >Depending on how smart/dumb the changer is, you may have to eject the > >tape from the drive before the autoloader will see it. Like: Some loaders, like the DLT4500 and 4700 can be set to automatically load the next cartridge when a rewoffl occurs. You can flip a mode page bit to change this. I even think there are 2 bits, one that makes the drive forget about automatic loading a new tape whenever it encounters a robotic scsi command. Check out the DLTtools program on www.quantum.com for a tool to change DLT setup. [snip] > > Somehow, on realizing this is what makes it work, I'm reminded of first > learning that the star-tipped rod scares the bird.... (*) > > Thanks, Dan.... > > Now I need to get amanda set up to use this.... :-} > > * Ref. to "Adventure," in case that's not obvious. "You are at the end > of a road, near a small brick building...." It was obvious. I fought ferocious cave bears in my day ;-) 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 Aug 13 14:40:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23510 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:40:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23488 for ; Thu, 13 Aug 1998 14:40:03 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA29675 (5.67b/IDA-1.5); Thu, 13 Aug 1998 22:53:17 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA03807; Thu, 13 Aug 1998 21:58:27 +0200 (CEST) From: Wilko Bulte Message-Id: <199808131958.VAA03807@yedi.iaf.nl> Subject: Re: solaris is free. In-Reply-To: <199808122310.QAA25510@lestat.nas.nasa.gov> from Jason Thorpe at "Aug 12, 98 04:10:29 pm" To: thorpej@nas.nasa.gov Date: Thu, 13 Aug 1998 21:58:27 +0200 (CEST) Cc: tlambert@primenet.com, joerg@krdl.org.sg, jgrosch@mooseriver.com, marcs@znep.com, imp@village.org, jbryant@unix.tfs.net, 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 Jason Thorpe wrote... > On Wed, 12 Aug 1998 23:01:32 +0000 (GMT) > Terry Lambert wrote: > > > If they were selling SunOS for $10 instead of Solaris, then you > > might have a point. I think there is a lot of Sun hardware running > > NetBSD because people are nostalgic for the feel of the old SunOS. > > More like: They have these good old workhorse machines, and they want > to run an OS that doesn't suck, in constrast to SunOS and Solaris. > > If I wanted the nostalgia of running SunOS, I'd run SunOS. (Hey, I > still have a machine that runs 4.2BSD...) You must be a newbie..... 2.11BSD here (PDP11/73) Could not resist.. 8-) _ ______________________________________________________________________ | / 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 Aug 13 14:50:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25507 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 14:50:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from send103.yahoomail.com (send103.yahoomail.com [205.180.60.92]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA25501 for ; Thu, 13 Aug 1998 14:50:40 -0700 (PDT) (envelope-from lc001@yahoo.com) Message-ID: <19980813215010.20298.rocketmail@send103.yahoomail.com> Received: from [139.87.242.56] by send103.yahoomail.com; Thu, 13 Aug 1998 14:50:10 PDT Date: Thu, 13 Aug 1998 14:50:10 -0700 (PDT) From: "L.C." Subject: Which vendors' PC you would recommend for FreeBSD? better with DVD supported 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'm going to buy PCs and intend to have FreeBSD/Linux/NT/Win95 coexist. Which vendors' machines would you suggest? I don't worry about how to make them coexist but more concern with will the hardware be supported by FreeBSD and/or Linux. Please comment. Thanks, L.C. == **_____________ Have a nice day _______________** _________________________________________________________ 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 Aug 13 15:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00503 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 15:27:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA00470 for ; Thu, 13 Aug 1998 15:27:02 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA28536 for hackers@freebsd.org; Thu, 13 Aug 1998 18:29:44 -0400 From: Bill Paul Message-Id: <199808132229.SAA28536@skynet.ctr.columbia.edu> Subject: Yet another XL driver update To: hackers@FreeBSD.ORG Date: Thu, 13 Aug 1998 18:29:42 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grrr. Okay, I've uploaded another XL driver update to www.freebsd.org/~wpaul. This update deals with the following issues: - Counting 'FramesDeferred' from the stats registers as interface output errors isn't quite correct (I think if a frame gets deferred a certain number of times, it counts as a collision, but collisions are counted using separate stats registers anyway). Now, output errors are only counted if a 'TxComplete' interrupt is generated, and in the watchdog timeout handler (the way the driver initializes things, TxComplete interrupts are never delivered unless there's a transmission error). - While I tested 10Mbps performace on a 3c905B and a 3c900, I did not test it on a 3c905. At 10Mbps/half-duplex I observed watchdog timeout errors and spotty performance. I'm not sure why, but setting the RxEarly threshold seems to fix this (I observed that the RX FIFO was filling up in these cases, which was the only unusual condition I could find when the errors occurred). The new driver sets this in xl_init(). I've had one person report this problem with a 3c905 operating in 10Mbps mode. 100Mbps mode seems to work fine. The 3c905B seems to work well in either mode, and the 3c900 uses its internal 10baseT transceiver for 10Mbps mode whereas the 3c905 uses an external NS83840A PHY so it doesn't behave the same. - I tweaked the packet transmission routines a little in order to try reducing the amount of interrupts delivered. Previously, the code would set the 'download indicate' bit in the status word of every transmit descriptor, which means that a 'download complete' interrupt would be generated each time a packet was successfully transfered into the NIC's memory. Now, the 'download indicate' bit is only set in the last descriptor of a chain. If only one packet is queued, then the behavior is basically the same as before. But if several packets are queued all at once, there will only be an interrupt generated for the last packet in the queue. - An update on the problem with the Dell Latitude laptop. First of all, the NIC is actually in the laptop docking station, not the laptop itself. Second of all, it's not a 3c905B but is instead a 3c905-TX. (The owner of the laptop thought it was a 3c905B-TX and told me that by mistake.) The 3c905 NICs don't load the media options word from the EEPROM: instead, the media bits are latched from pins on the ASIC, which I suppose are tied either to ground or Vcc when the board is manufactured. The value e100 makes a little more sense in this case; the upper three bits represent a test mode indicator, with 0xe actually signifying 'normal mode.' The 0x100 could indicate that the internal VCO is being used. However, the fact that the lower byte is 0x00 is totally bogus: it should be set to 0x40 (external PHY attached to MII) instead. The owner of the laptop and docking station told me that he tried another docking station and got the same results, so it's not a defect in this one unit. This means that either Dell has some perverted reason for wiring the chip this way, or else this is a manufacturing defect in this run of devices. Why it doesn't trip up the Lose95/98/NT driver I have no idea. In any case, I have added code to the driver to detect the condition where none of the media type bits are set and try to guess what it should be depending on the PCI device ID (which can be read from the EEPROM as well as from the PCI device ID register. So. If you have a 3c905-TX, please test this version of the driver in low speed modes. Hopefully you should not see any timeouts or card lockups. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 15:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02755 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 15:44:31 -0700 (PDT) (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 PAA02724 for ; Thu, 13 Aug 1998 15:44:18 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id GAA17404; Fri, 14 Aug 1998 06:43:21 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199808132243.GAA17404@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: zhihuizhang , hackers Subject: Re: Questions about MFS_ROOT and MFS_AUTOLOAD In-reply-to: Your message of "Sat, 08 Aug 1998 15:11:31 MST." <199808082211.PAA02183@antipodes.cdrom.com> Date: Fri, 14 Aug 1998 06:43:21 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > Hi, I have two questions about MFS: > > > > (1) Does option MFS_ROOT mean that the memory file system will be the root > > of the entire file system hierarchy (all other disk-based file systems, if > > any, hang off the memory-based file system)? > > It means that the kernel-internal MFS will be mounted as /. If your > startup code in that filesystem mounts others, then they will be hung > off the MFS, yes. > > > (2) How can the MFS image be made separately from the other part of the > > kernel? This is required by MFS_AUTOLOAD. > > Use 'dd' to create a file of the appropriate size, then 'vnconfig' to > attach it to a 'vn' device, then newfs it and install stuff as desired. > Have a look at the way that the src/release makefile does it as it > builds the MFS for the install kernel. MFS_AUTOLOAD is a variation on the MFS_ROOT system. It was meant as an option for loading a floppy into the mfs ramdisk after the kernel had started. This is leftover from attempts to get it to install a 4MB system, at the expense of using two boot disks instead of one. > -- > \\ 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 > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 16:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06351 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 16:09:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06331 for ; Thu, 13 Aug 1998 16:09:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-76.camalott.com [208.229.74.76]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA19453; Thu, 13 Aug 1998 18:10:49 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA08253; Thu, 13 Aug 1998 18:08:41 -0500 (CDT) (envelope-from joelh) Date: Thu, 13 Aug 1998 18:08:41 -0500 (CDT) Message-Id: <199808132308.SAA08253@detlev.UUCP> To: lc001@yahoo.com CC: hackers@FreeBSD.ORG In-reply-to: <19980813215010.20298.rocketmail@send103.yahoomail.com> (lc001@yahoo.com) Subject: Re: Which vendors' PC you would recommend for FreeBSD? better with DVD supported From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <19980813215010.20298.rocketmail@send103.yahoomail.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm going to buy PCs and intend to have FreeBSD/Linux/NT/Win95 coexist. > Which vendors' machines would you suggest? I don't worry about how to > make them coexist but more concern with will the hardware be supported > by FreeBSD and/or Linux. Please comment. I normally suggest homebrew. If you want a large OEM, I like Gateway 2000. They tend to use fairly standard parts, or at least used to. The best suggestion: Ask the vendors you're considering about their hardware. Look at the OSs' docs. The remainder is left as an exercise to the reader. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 13 16:28:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09218 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 16:28:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09037 for ; Thu, 13 Aug 1998 16:28:05 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-76.camalott.com [208.229.74.76]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA20714; Thu, 13 Aug 1998 18:28:31 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA08388; Thu, 13 Aug 1998 18:26:24 -0500 (CDT) (envelope-from joelh) Date: Thu, 13 Aug 1998 18:26:24 -0500 (CDT) Message-Id: <199808132326.SAA08388@detlev.UUCP> To: brett@lariat.org CC: mike@smith.net.au, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> (message from Brett Glass on Thu, 13 Aug 1998 15:03:05 -0600) Subject: Re: 64-bit time_t From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808131752.LAA13123@lariat.lariat.org> <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I'd kind of like to do financial projections for my retirement and not >>> have the calculations blow up, as they do now. >> time_t is a format for the system current time. As such, you're abusing >> it mightily if you expect it to be a general-purpose time value. > It's used throughout UNIX and UNIX programs as such. And rightfully so; > it's silly to have multiple date formats. You use multiple format constantly. For instance, strtol is a common operation when reading configuration files. If you are manipulating dates, use a lower-precision format, such as number of days since the epoch, or alternately since 01 Jan 0000, or whatever. Then, in your calls to ctime or strftime or whatever, simply convert it. (Use #defines. Use weak symbols. Use alternate names, like my_ctime or whatever.) It's not different than having to translate between ASCII-encoded numbers and binary-encoded numbers every time you read an ASCII config file. Happy hacking, joelh PS: Check your MUA. It seems to be generating invalid "References:" lines, ie (line break added by yours truly): References: -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 13 17:16:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15413 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 17:16:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15359; Thu, 13 Aug 1998 17:16:13 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA17635; Thu, 13 Aug 1998 17:15:44 -0700 (PDT) Message-Id: <199808140015.RAA17635@implode.root.com> To: peter@sirius.com cc: mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 11:34:00 PDT." <199808131834.LAA14961@staff.sirius.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 17:15:44 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We worked around a similar problem (processes left immortal, here in >the context of several processes [httpd] writing to the same NFS mounted >file [http log file]) by adjusting the timeout value from 0 (never) to >2 * hz (2 seconds). Details are posted as follow-up to kern/4588 in >FreeBSD.org's gnats problem report database. > >It looks like other parts of the kernel (here the vm subsystem) suffer >similar problems. It appears to me that an overly optimistic use of >tsleep() with both, interrupts disabled and time-out set to infinity, >leaves immortal yet paralyzed processes around. No, there's just a missing or unprotected wakeup() somewhere. >>From /usr/src/sys/vm/vm_object.c (a second, similar occurence around >line 1261): > > 1218 /* > 1219 * The busy flags are only cleared at > 1220 * interrupt -- minimize the spl transitions > 1221 */ > 1222 if ((p->flags & PG_BUSY) || p->busy) { > 1223 s = splvm(); > 1224 if ((p->flags & PG_BUSY) || p->busy) { > 1225 p->flags |= PG_WANTED; > 1226 tsleep(p, PVM, "vmopar", 0); > 1227 splx(s); > 1228 goto again; > 1229 } > 1230 splx(s); > 1231 } > >The code in line 1224 checks a condition to see whether somebody else >is already performing an operation on object p; in this case it wants >to ensure that a wakeup() for the following tsleep() is delivered by >setting a flag in line 1225. > >But what ensures that the world did not change between lines 1224 and >1225? Could the wakeup() happen after 1224 has determined to issue >the tsleep() but before the flagging in 1225 was registered? Then it >would be missed. Is this a race condition biting heavily hit machines? No. The wakeup occurs as a function of IO rundown which occurs in an interrupt context. The purpose of splvm() is to block interrupts to prevent the race condition. >Try changing lines 1226 and 1261 to something like: > tsleep(p, PVM, "vmopar", 5 * hz); > >>From the tsleep man page: > > Tsleep is the general sleep call. Suspends the current process until a > wakeup is performed on the specified identifier. The process will then > be made runnable with the specified priority. Sleeps at most timo / hz > seconds (0 means no timeout). If pri includes the PCATCH flag, signals > are checked before and after sleeping, else signals are not checked. Re- > turns 0 if awakened, EWOULDBLOCK if the timeout expires. If PCATCH is > set and a signal needs to be delivered, ERESTART is returned if the cur- > rent system call should be restarted if possible, and EINTR is returned > if the system call should be interrupted by the signal (return EINTR). > >This function would return "EWOULDBLOCK" after the time-out expires then, >no clue what that will do to your system or apps ;) -- I would expect the >blocked process to go away within 5 seconds... It would do bad things. There's a bug, but not there and that isn't the fix. I think this is another manifestation of the lack of NFSnode locking in the kernel, but that's just a guess. -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 Thu Aug 13 17:24:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16924 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 17:24:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16897; Thu, 13 Aug 1998 17:24:20 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA17790; Thu, 13 Aug 1998 17:23:38 -0700 (PDT) Message-Id: <199808140023.RAA17790@implode.root.com> To: Mike Smith cc: peter@sirius.com, mrcpu@internetcds.com (Jaye Mathisen), hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Thu, 13 Aug 1998 12:59:45 PDT." <199808131959.MAA00604@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 13 Aug 1998 17:23:38 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Try changing lines 1226 and 1261 to something like: >> tsleep(p, PVM, "vmopar", 5 * hz); >... >> This function would return "EWOULDBLOCK" after the time-out expires then, >> no clue what that will do to your system or apps ;) -- I would expect the >> blocked process to go away within 5 seconds... > >I dont' have 2.2 sources to hand, and the above is now just a call to >vm_page_sleep, but if the timeout expires, the entire operation is >retried, so it should be harmless (although it is masking a legitimate >bug). I said in my last reply on this that it would do bad things, but you're probably right that it should be harmless. There are other parts of the code where premature wakeups would be bad, so one must be careful about making this assumption. If that "fixes" the problem, then this probably indicates a problem with a missing wakeup somewhere. -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 Thu Aug 13 17:41:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18819 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 17:41:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18806 for ; Thu, 13 Aug 1998 17:41:12 -0700 (PDT) (envelope-from brawley@camtech.com.au) Received: from sebastion.sa.camtech.com.au (sebastion.sa.camtech.com.au [203.28.3.2]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id KAA03698 for ; Fri, 14 Aug 1998 10:10:24 +0930 (CST) Received: (from smtp@localhost) by sebastion.sa.camtech.com.au (8.8.5/8.8.7) id KAA08087 for ; Fri, 14 Aug 1998 10:10:40 +0930 (CST) Received: from slingshot(192.168.1.2) by sebastion via smap (V2.0) id xma008085; Fri, 14 Aug 98 10:10:30 +0930 Received: from mad.ct (mad.ct [192.168.1.12]) by slingshot.camtech.com.au (8.6.12/8.6.12) with ESMTP id KAA18758 for ; Fri, 14 Aug 1998 10:10:29 +0930 From: Ivan Brawley Received: (from brawley@localhost) by mad.ct (8.8.8/8.8.8) id KAA14156 for hackers@FreeBSD.ORG; Fri, 14 Aug 1998 10:10:03 +0930 (CST) Message-Id: <199808140040.KAA14156@mad.ct> Subject: Re: 64-bit time_t In-Reply-To: <199808131721.KAA00864@antipodes.cdrom.com> from Mike Smith at "Aug 13, 98 10:21:52 am" To: hackers@FreeBSD.ORG Date: Fri, 14 Aug 1998 10:10:02 +0930 (CST) X-Phase-Of-Moon: Waning Gibbous (60% of Full) 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 The one named Mike Smith wrote: } > How soon will FreeBSD move to a 64-bit time_t? The article at } > } > http://www.wired.com/news/news/technology/story/14390.html } Read the article: } } Certainly by 2038, Unix 'time_t' will be 64 bits or more, } assuming Unix survives in some form," said Dennis Ritchie, } co-author of the Unix operating system. } } If you have nothing else to worry about for the next 40 years, I'm sure } we can find you something more useful to do. 8) Question: What is wrong with using an unsigned long for time_t, instead of long (which is then assumed signed). Fits in 32 bits, clocks keep going for another 69 years, one (or a maybe a few) words added to source code of os and libraries... As the above article hinted at, time_t can only count to 2^31-1 seconds. With unsigned long, it can count to 2^32-1 seconds. Yeah, 64bit time_t (signed or unsigned) will mean that we don't need to worry about for a while longer (other more urgent things may happen first, like the sun dieing, etc :-) Just my 2cents worth... ivan. -- #define private public // As spotted in a C++ program Phone: +61 8 8303 3300 Ivan Brawley Fax: +61 8 8303 4403 Systems Administrator Email: brawley@camtech.com.au CAMTECH http://www.camtech.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 Aug 13 19:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01323 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:10:04 -0700 (PDT) (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 TAA01252 for ; Thu, 13 Aug 1998 19:09:54 -0700 (PDT) (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 LAA03094; Fri, 14 Aug 1998 11:39:10 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA16787; Fri, 14 Aug 1998 11:38:53 +0930 (CST) Message-ID: <19980814113852.J1921@freebie.lemis.com> Date: Fri, 14 Aug 1998 11:38:52 +0930 From: Greg Lehey To: Terry Lambert , hm@kts.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: developing device drivers References: <199808132017.NAA14261@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808132017.NAA14261@usr09.primenet.com>; from Terry Lambert on Thu, Aug 13, 1998 at 08:17:13PM +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 Thursday, 13 August 1998 at 20:17:13 +0000, Terry Lambert wrote: >>> I second this. If you look in /usr/share/examples, you'll find a >>> couple of sample LKMs written by Terry Lambert. I hijacked the syscall >>> example from here and used it a lot to experiment with the XL driver. >> >> I'd really like to write drivers (for ISA cards) as LKM modules, but so >> far i don't know how to assign 1) the IRQ, 2) the iobase and 3) the membase >> ( and perhaps flags and spl) to the LKM at module load time. >> >> Did i miss something ? > > You probe and attach at load time, normally. This means you detect the > IRQ/DRQ/IOBase/MemBase/Etc., not assign it. That means you should write > the probe code first. > > The flags and spl have to be dealt with by unloading, modifying, and > loading. Frankly, I think you'll not need to change the spl you use > since it's pretty much fixed by the kind of device you are driving. > You could also provide an ioctl to diddle the flags, and run a program > in user space that diddles them one the driver is loaded. > > You are doing this under -current, right? If not, it's going to be > hard to unload, since detaching ISA resources wasn't well supported > before the PCMCIA code required it. > > One of the sample drivers used to be an LPT driver, which grabbed IRQ7; > I haven't looked at the hardware part of the codebase for LKM in a > while (well, mostly; I did help someone with loading a line discipline > recently, but that didn't grab and release resources). > > Most -current drivers are capable of dual-mode compilation. > > For specific examples, look in /usr/src/lkm/ for joy, pcic, qcam, > and wcd. I think Hellmuth brought up an important issue which you don't appear to have covered: sure, it's easy enough to probe. But some probes are destructive, and if you don't know what's already been taken, you're liable to kill some other device while messing around looking for your devices. Is there some list which contains information about what resources are already assigned to other drivers? 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 Aug 13 19:10:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01522 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:10:46 -0700 (PDT) (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 TAA01498 for ; Thu, 13 Aug 1998 19:10:43 -0700 (PDT) (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 LAA03111; Fri, 14 Aug 1998 11:40:14 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA19012; Fri, 14 Aug 1998 11:40:15 +0930 (CST) Message-ID: <19980814114015.K1921@freebie.lemis.com> Date: Fri, 14 Aug 1998 11:40:15 +0930 From: Greg Lehey To: Mike Smith , Karl Pielorz Cc: hackers@FreeBSD.ORG Subject: Re: Device / Driver presentation advice needed... References: <35D29E32.81A62F7D@tdx.co.uk> <199808131717.KAA00818@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808131717.KAA00818@antipodes.cdrom.com>; from Mike Smith on Thu, Aug 13, 1998 at 10:17:47AM -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 Thursday, 13 August 1998 at 10:17:47 -0700, Mike Smith wrote: >> Hi All, >> >> I'm now getting on quite well with the device driver I'm writing, but I'm stuck >> as to how best it is to present the 'device' to the outside world... >> >> If I reserve 3 bits of the minor number to indicate the actual card in the >> system, I can then use the remaining 5 bits to give different 'presentations' of >> the device (Is this good practice?) > > It's one way to do it. There is a lot more room in the minor though; > 32 bits in fact. 24 bits. The total 32 bit word includes 8 bits of major number. 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 Aug 13 19:27:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03487 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:27:57 -0700 (PDT) (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 TAA03481; Thu, 13 Aug 1998 19:27:52 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA25648; Thu, 13 Aug 1998 19:27:21 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd025613; Thu Aug 13 19:27:16 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA25476; Thu, 13 Aug 1998 19:27:05 -0700 (MST) From: Terry Lambert Message-Id: <199808140227.TAA25476@usr02.primenet.com> Subject: Re: vmopar state in 2.2.7? To: dg@root.com Date: Fri, 14 Aug 1998 02:27:05 +0000 (GMT) Cc: mike@smith.net.au, peter@sirius.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199808140023.RAA17790@implode.root.com> from "David Greenman" at Aug 13, 98 05:23:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Try changing lines 1226 and 1261 to something like: > >> tsleep(p, PVM, "vmopar", 5 * hz); > >... > >> This function would return "EWOULDBLOCK" after the time-out expires then, > >> no clue what that will do to your system or apps ;) -- I would expect the > >> blocked process to go away within 5 seconds... > > > >I dont' have 2.2 sources to hand, and the above is now just a call to > >vm_page_sleep, but if the timeout expires, the entire operation is > >retried, so it should be harmless (although it is masking a legitimate > >bug). > > I said in my last reply on this that it would do bad things, but you're > probably right that it should be harmless. There are other parts of the code > where premature wakeups would be bad, so one must be careful about making > this assumption. > If that "fixes" the problem, then this probably indicates a problem with > a missing wakeup somewhere. It will do bad things. Or rather, it will increase the frequency of bad things; the code itself is broken. I have sent them patches, which are wrong because I neglected the non-increment case. If it sleeps on the first iteration, the page will be bogusly freed twice. 8-(. This may very well be the nasty VM bug no one has fixed... Here is the analysis I sent them, which is correct: ----------------------------------------------------------------------------- > But what ensures that the world did not change between lines 1224 and > 1225? Could the wakeup() happen after 1224 has determined to issue > the tsleep() but before the flagging in 1225 was registered? Then it > would be missed. Is this a race condition biting heavily hit machines? There is a race condition here, but only for SMP systems. Since this is vm_object.c from the 2.2.x stream, it will never hit. If the process is in the kernel, the only way for the kernel to be reentered is via interrupt. Since this code is never called at interrupt level (it's in vm_object_page_remove()), it will never be reentered. FreeBSD, unfortunately, does not support kernel preemption (it's necessary for hard realtime, which is why it's unfortunate). Basically, the race that would exist in the SMP case, if the code was even vaguely similar under 3.x, is between 1222 and 1223; there is no race between 1224 and 1225, since the vm_page object p is present and buys, and the flags modification occurs at splvm. Timing out the tsleep would certianly be harmless; I would expect it to do nothing in the 1226 case. That is, if you ever hit a condition where this was an issue, you would merely increase the size of your infinite loop. In the second case, 1261, the consequences could be bad. In fact, the consequences of sleeping at all could be bad. The reason it seems to work around the problem for you is that the page causing the problem is not the first page on the list and start has been incremented. Because start is not decremented before the "goto again", the calculation on line 1207: again: size = end - start; if (size > 4 || size >= object->size / 4) { Bogusly omits the page which was just obtained. This means that vm_page_protect(p, VM_PROT_NONE); PAGE_WAKEUP(p); vm_page_free(p); is never called. The net result is that pages are left hanging out in space, but the system thinks they have been reclaimed. ----------------------------------------------------------------------------- Here is a patch for 3.1, which has the same bug; I didn't change the while to a for because I still need to know if start was incremented: ----------------------------------------------------------------------------- *** vm_object.c Thu May 21 07:47:58 1998 --- vm_object.c.good Fri Aug 14 02:08:15 1998 *************** *** 1348,1353 **** --- 1348,1354 ---- } } } else { + s = 0; while (size > 0) { if ((p = vm_page_lookup(object, start)) != 0) { *************** *** 1356,1361 **** --- 1357,1363 ---- vm_page_protect(p, VM_PROT_NONE); start += 1; size -= 1; + s = 1; continue; } *************** *** 1363,1376 **** * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) goto again; if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; continue; } } --- 1365,1381 ---- * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) { ! start -= s; goto again; + } if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; + s = 1; continue; } } *************** *** 1381,1386 **** --- 1386,1392 ---- } start += 1; size -= 1; + s = 1; } } vm_object_pip_wakeup(object); ----------------------------------------------------------------------------- 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 Thu Aug 13 19:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04866 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:35:50 -0700 (PDT) (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 TAA04857 for ; Thu, 13 Aug 1998 19:35:48 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA06836; Thu, 13 Aug 1998 19:35:19 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd006792; Thu Aug 13 19:35:12 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA25965; Thu, 13 Aug 1998 19:35:04 -0700 (MST) From: Terry Lambert Message-Id: <199808140235.TAA25965@usr02.primenet.com> Subject: Re: developing device drivers To: grog@lemis.com (Greg Lehey) Date: Fri, 14 Aug 1998 02:35:04 +0000 (GMT) Cc: tlambert@primenet.com, hm@kts.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980814113852.J1921@freebie.lemis.com> from "Greg Lehey" at Aug 14, 98 11:38:52 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 think Hellmuth brought up an important issue which you don't appear > to have covered: sure, it's easy enough to probe. But some probes are > destructive, and if you don't know what's already been taken, you're > liable to kill some other device while messing around looking for your > devices. Is there some list which contains information about what > resources are already assigned to other drivers? Yes. Otherwise PCMCIA cards couldn't work. That's why I specifically referenced them. 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 Thu Aug 13 19:46:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06038 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:46:07 -0700 (PDT) (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 TAA06023 for ; Thu, 13 Aug 1998 19:46:03 -0700 (PDT) (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 MAA03345; Fri, 14 Aug 1998 12:15:18 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA16462; Fri, 14 Aug 1998 12:15:17 +0930 (CST) Message-ID: <19980814121517.O1921@freebie.lemis.com> Date: Fri, 14 Aug 1998 12:15:17 +0930 From: Greg Lehey To: Terry Lambert Cc: hm@kts.org, freebsd-hackers@FreeBSD.ORG Subject: Re: developing device drivers References: <19980814113852.J1921@freebie.lemis.com> <199808140235.TAA25965@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808140235.TAA25965@usr02.primenet.com>; from Terry Lambert on Fri, Aug 14, 1998 at 02:35:04AM +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 Friday, 14 August 1998 at 2:35:04 +0000, Terry Lambert wrote: >> I think Hellmuth brought up an important issue which you don't appear >> to have covered: sure, it's easy enough to probe. But some probes are >> destructive, and if you don't know what's already been taken, you're >> liable to kill some other device while messing around looking for your >> devices. Is there some list which contains information about what >> resources are already assigned to other drivers? > > Yes. Otherwise PCMCIA cards couldn't work. That's why I specifically > referenced them. Thanks for the details. 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 Aug 13 19:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06242 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:48:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mcfeely.interaccess.com (mcfeely.interaccess.com [207.70.126.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06237 for ; Thu, 13 Aug 1998 19:48:33 -0700 (PDT) (envelope-from ras@interaccess.com) Received: from wildrock (d87.tp.interaccess.com [199.88.134.87]) by mcfeely.interaccess.com (8.9.0/8.9.0) with SMTP id VAA06299 for ; Thu, 13 Aug 1998 21:47:56 -0500 (CDT) From: "Chris Silva" To: Subject: gdbm Date: Thu, 13 Aug 1998 21:48:35 -0500 Message-ID: <000201bdc72e$084f9c20$0100000a@wildrock.interaccess.com> 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.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How well does gdbm work? I am using TCL 7.6 and get a no command found when doing a gdbm_open (I Think) _____________________________________________________________________ RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6 RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A PGP Mail encouraged / preferred - keys available on common keyservers _____________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 19:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07026 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 19:53:18 -0700 (PDT) (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 TAA07021 for ; Thu, 13 Aug 1998 19:53:17 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA03381; Thu, 13 Aug 1998 19:52:50 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd003321; Thu Aug 13 19:52:41 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA27058; Thu, 13 Aug 1998 19:52:35 -0700 (MST) From: Terry Lambert Message-Id: <199808140252.TAA27058@usr02.primenet.com> Subject: Re: developing device drivers To: grog@lemis.com (Greg Lehey) Date: Fri, 14 Aug 1998 02:52:35 +0000 (GMT) Cc: tlambert@primenet.com, hm@kts.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980814121517.O1921@freebie.lemis.com> from "Greg Lehey" at Aug 14, 98 12:15: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 > >> I think Hellmuth brought up an important issue which you don't appear > >> to have covered: sure, it's easy enough to probe. But some probes are > >> destructive, and if you don't know what's already been taken, you're > >> liable to kill some other device while messing around looking for your > >> devices. Is there some list which contains information about what > >> resources are already assigned to other drivers? > > > > Yes. Otherwise PCMCIA cards couldn't work. That's why I specifically > > referenced them. > > Thanks for the details. Sorry, but I don't have documentation for the relevent routines, other than the routines themselves. 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 Thu Aug 13 20:21:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10241 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 20:21:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10232 for ; Thu, 13 Aug 1998 20:21:05 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id WAA13960; Thu, 13 Aug 1998 22:20:24 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id WAA08495; Thu, 13 Aug 1998 22:20:24 -0500 (CDT) Message-ID: <19980813222024.27227@mcs.net> Date: Thu, 13 Aug 1998 22:20:24 -0500 From: Karl Denninger To: Alex Cc: jgrosch@mooseriver.com, Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. References: <19980812082400.24443@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Alex on Wed, Aug 12, 1998 at 07:14:03PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 12, 1998 at 07:14:03PM -0700, Alex wrote: > On Wed, 12 Aug 1998, Karl Denninger wrote: > > > On Wed, Aug 12, 1998 at 01:46:14AM -0700, Josef Grosch wrote: > > > My guess is that Sun is beginning to feel the heat from FreeBSD and > > > Linux. Last time I looked very few people we running Solaris on X86. Mayby > > > they are starting to worry about all those older Sparc's running NetBSD. > > > > Frankly, FreeBSD + Afterstep on a Pentium Pro 200 makes a damn nice > > workstation; I prefer it over Solaris. > > Ahh replace AS with KDE, and you've got a better workstation ;) I can't find KDE in the X11 ports tree....... > Anyhow, I think Solaris still has some advantages over FreeBSD, including > better SMP, and support for a better C++ compiler (nearly anything is > better than gcc 2.7.2). Still not worth 20 bucks tho ;) > > - alex > -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 20:45:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12547 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 20:45:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12540 for ; Thu, 13 Aug 1998 20:45:07 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id WAA01315; Thu, 13 Aug 1998 22:43:13 -0400 (EDT) Date: Thu, 13 Aug 1998 22:43:13 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Chris Silva cc: hackers@FreeBSD.ORG Subject: Re: gdbm In-Reply-To: <000201bdc72e$084f9c20$0100000a@wildrock.interaccess.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, 13 Aug 1998, Chris Silva wrote: > Hi, > How well does gdbm work? I am using TCL 7.6 and get a no command > found when doing a gdbm_open (I Think) gdbm is a library, but the error you mention, "no command found", is very often printed when executing a script. The first line of a script often has: #! if happens to be "sh" (for most shell scripts) then the line would be: #!/bin/sh For another example, perl scripts have: #!/usr/local/bin/perl You get the error if any part of the interpreter path is incorrect (if the startup code can't locate the interpreter to start it off). Tcl scripts are very prone to this, because there are so many different versions of tcl, and the name of the executeable, "wish", is renamed on some systems as "wish7.6", and tcl scripts that just have "wish" in them give the error you saw. ----------------------------+----------------------------------------------- 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 Aug 13 21:06:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14427 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:06:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nexus.astro.psu.edu (nexus.astro.psu.edu [128.118.147.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA14422 for ; Thu, 13 Aug 1998 21:06:37 -0700 (PDT) (envelope-from mph@astro.psu.edu) Received: from mstar.astro.psu.edu by nexus.astro.psu.edu (4.1/Nexus-1.3) id AA18135; Fri, 14 Aug 98 00:06:12 EDT Received: by mstar.astro.psu.edu (SMI-8.6/Client-1.3) id AAA25065; Fri, 14 Aug 1998 00:06:05 -0400 Message-Id: <19980814000605.A25012@astro.psu.edu> Date: Fri, 14 Aug 1998 00:06:05 -0400 From: Matthew Hunt To: Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808140040.KAA14156@mad.ct>; from Ivan Brawley on Fri, Aug 14, 1998 at 10:10:02AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 10:10:02AM +0930, Ivan Brawley wrote: > Question: What is wrong with using an unsigned long for time_t, instead of > long (which is then assumed signed). man 3 time: Upon successful completion, time() returns the value of time. Otherwise a value of ((time_t) -1) is returned and the global variable errno is set to indicate the error. -- Matthew Hunt * Inertia is a property of matter. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 21:15:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15686 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:15:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15680 for ; Thu, 13 Aug 1998 21:15:41 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id AAA68278; Fri, 14 Aug 1998 00:14:28 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> References: <199808131924.MAA00367@dingo.cdrom.com> Date: Fri, 14 Aug 1998 00:18:24 -0400 To: Brett Glass , Mike Smith From: Garance A Drosihn Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:03 PM -0600 8/13/98, Brett Glass wrote: >At 12:24 PM 8/13/98 -0700, Mike Smith wrote: >> time_t is not a hammer. > > Nope, but I don't intend to carry an entire box of tools to screw > in a light bulb.... ;-) Does this imply that you often use hammers to screw in light-bulbs?!? :-) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 21:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16427 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:23:03 -0700 (PDT) (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 VAA16418 for ; Thu, 13 Aug 1998 21:23:00 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id XAA24294; Thu, 13 Aug 1998 23:22:31 -0500 (CDT) (envelope-from dan) Message-ID: <19980813232231.A24202@emsphone.com> Date: Thu, 13 Aug 1998 23:22:31 -0500 From: Dan Nelson To: Chris Silva , hackers@FreeBSD.ORG Subject: Re: gdbm References: <000201bdc72e$084f9c20$0100000a@wildrock.interaccess.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: <000201bdc72e$084f9c20$0100000a@wildrock.interaccess.com>; from "Chris Silva" on Thu Aug 13 21:48:35 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 (Aug 13), Chris Silva said: > Hi, > How well does gdbm work? I am using TCL 7.6 and get a no > command found when doing a gdbm_open (I Think) Assuming you installed the databases/gdbm port before compiling TCL, it should work just fine. -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 Thu Aug 13 21:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16639 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:26:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (dantooine-1-115.mdm.mke.execpc.com [169.207.137.115]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16633 for ; Thu, 13 Aug 1998 21:26:08 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199808140426.VAA16633@hub.freebsd.org> Received: (qmail 3776 invoked from network); 13 Aug 1998 23:19:51 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 13 Aug 1998 23:19:51 -0500 To: Ivan Brawley cc: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 10:10:02 +0930." <199808140040.KAA14156@mad.ct> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 23:19:51 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808140040.KAA14156@mad.ct>, Ivan Brawley wrote: } The one named Mike Smith wrote: } } > How soon will FreeBSD move to a 64-bit time_t? The article at } } > } } > http://www.wired.com/news/news/technology/story/14390.html } } Read the article: } } } } Certainly by 2038, Unix 'time_t' will be 64 bits or more, } } assuming Unix survives in some form," said Dennis Ritchie, } } co-author of the Unix operating system. } } } } If you have nothing else to worry about for the next 40 years, I'm sure } } we can find you something more useful to do. 8) } } Question: What is wrong with using an unsigned long for time_t, instead of } long (which is then assumed signed). You can't represent dates prior to the epoch, for starters. Some people don't care about this, some do. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 21:30:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17232 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:30:09 -0700 (PDT) (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 VAA17189 for ; Thu, 13 Aug 1998 21:30:01 -0700 (PDT) (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 NAA07687; Fri, 14 Aug 1998 13:59:19 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA14277; Fri, 14 Aug 1998 13:59:19 +0930 (CST) Message-ID: <19980814135919.U1921@freebie.lemis.com> Date: Fri, 14 Aug 1998 13:59:19 +0930 From: Greg Lehey To: Matthew Hunt , Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980814000605.A25012@astro.psu.edu>; from Matthew Hunt on Fri, Aug 14, 1998 at 12:06:05AM -0400 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, 14 August 1998 at 0:06:05 -0400, Matthew Hunt wrote: > On Fri, Aug 14, 1998 at 10:10:02AM +0930, Ivan Brawley wrote: > >> Question: What is wrong with using an unsigned long for time_t, instead of >> long (which is then assumed signed). > > man 3 time: > > Upon successful completion, time() returns the value of time. Otherwise > a value of ((time_t) -1) is returned and the global variable errno is set > to indicate the error. More to the point, time_t *can* be used to represent BE (Before Epoch) dates. Make it unsigned and you break that. 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 Aug 13 21:32:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17446 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:32:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17411 for ; Thu, 13 Aug 1998 21:32:10 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-47.camalott.com [208.229.74.47]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id XAA11006; Thu, 13 Aug 1998 23:33:00 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA00473; Thu, 13 Aug 1998 23:30:37 -0500 (CDT) (envelope-from joelh) Date: Thu, 13 Aug 1998 23:30:37 -0500 (CDT) Message-Id: <199808140430.XAA00473@detlev.UUCP> To: freebsd-hackers@FreeBSD.ORG Subject: Patch: Booting with -v From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I've finally found my round tuit (it was in the square hole, natch). This means that I finally wrote the patch to allow -v (and other flags) to be in the /boot.config (yay!). In the process of saving a few bytes, I did change the boot message bit that says "internal", "internal/dual", "serial", or "serial/dual" to read just "internal", "serial", or "dual". Is the distinction between serial/dual and internal/dual in that message a useful one? Enclosed is the patch to /sys/i386/boot/biosboot/boot.c (against -current sources); I've tested it a total of once. Caveat emptor, and vivat hacker, and all that. If nobody has any objections, I'll submit a pr on this (after a little stylistic cleanup and a manpage change). But I would appreciate people looking over it and trying it out before I submit a patch that will leave every third system unbootable. Send results-- good, bad or indifferent-- to me personally. Again: This has been tested only once. Although I don't see any reason it should fail, be sure that you have a boot and fixit floppy and your old boot2 handy. Happy hacking, joelh -----cut here----- *** boot.c-orig Thu Aug 13 23:18:19 1998 --- boot.c Thu Aug 13 22:23:49 1998 *************** *** 86,91 **** --- 86,92 ---- boot(int drive) { int ret; + int cfg_loadflags = 0; /* Pick up the story from the Bios on geometry of disks */ *************** *** 142,177 **** name = "kernel"; if (boot_config[0] != '\0') { printf("boot.config: %s", boot_config); ! getbootdev(boot_config, &loadflags); if (openrd() != 0) name = "kernel"; } loadstart: /* print this all each time.. (saves space to do so) */ /* If we have looped, use the previous entries as defaults */ ! printf("\r \n>> FreeBSD BOOT @ 0x%x: %d/%d k of memory, %s%s console\n" ! "Boot default: %d:%s(%d,%c)%s\n" "%s\n" "boot: ", ouraddr, bootinfo.bi_basemem, bootinfo.bi_extmem, (loadflags & RB_SERIAL) ? "serial" : "internal", - (loadflags & RB_DUAL) ? "/dual" : "", dosdev & 0x7f, devs[maj], unit, 'a' + part, name ? name : "*specify_a_kernel_name*", boot_help); ! /* ! * Ignore flags from previous attempted boot, if any. ! * XXX this is now too strict. Settings given in boot.config should ! * not be changed. ! */ ! loadflags &= (RB_DUAL | RB_SERIAL); ! /* * Be paranoid and make doubly sure that the input buffer is empty. */ if (loadflags & (RB_DUAL | RB_SERIAL)) init_serial(); if (!gets(linebuf)) putchar('\n'); --- 143,177 ---- name = "kernel"; if (boot_config[0] != '\0') { printf("boot.config: %s", boot_config); ! getbootdev(boot_config, &cfg_loadflags); if (openrd() != 0) name = "kernel"; } loadstart: + /* Ignore flags from previous attempted boot, if any. */ + loadflags = cfg_loadflags; + /* print this all each time.. (saves space to do so) */ /* If we have looped, use the previous entries as defaults */ ! printf("\r \n>> FreeBSD BOOT @ 0x%x: %d/%d k of memory, %s console\n" ! "Boot default: %d:%s(%d,%c)%s (flags 0x%x)\n" "%s\n" "boot: ", ouraddr, bootinfo.bi_basemem, bootinfo.bi_extmem, + (loadflags & RB_DUAL) ? "dual" : (loadflags & RB_SERIAL) ? "serial" : "internal", dosdev & 0x7f, devs[maj], unit, 'a' + part, name ? name : "*specify_a_kernel_name*", + loadflags, boot_help); ! #if 0 /* * Be paranoid and make doubly sure that the input buffer is empty. */ if (loadflags & (RB_DUAL | RB_SERIAL)) init_serial(); + #endif if (!gets(linebuf)) putchar('\n'); *************** *** 376,382 **** char *p; /* Copy the flags to save some bytes. */ ! f = *howto; c = *ptr; for (;;) { --- 376,382 ---- char *p; /* Copy the flags to save some bytes. */ ! f = *howto & (RB_DUAL | RB_SERIAL | RB_PROBEKBD); c = *ptr; for (;;) { -----cut here----- -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 13 21:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19068 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:46:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from a486n1.znh.org (dialup4.gaffaneys.com [208.155.161.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19063 for ; Thu, 13 Aug 1998 21:46:56 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.9.1/8.9.1) id EAA01205; Fri, 14 Aug 1998 04:47:31 GMT (envelope-from zach) Message-ID: <19980813234730.A1133@znh.org.> Date: Thu, 13 Aug 1998 23:47:30 -0500 From: Zach Heilig To: Karl Denninger , Alex Cc: jgrosch@mooseriver.com, Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. References: <19980812082400.24443@mcs.net> <19980813222024.27227@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980813222024.27227@mcs.net>; from Karl Denninger on Thu, Aug 13, 1998 at 10:20:24PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 13, 1998 at 10:20:24PM -0500, Karl Denninger wrote: > I can't find KDE in the X11 ports tree....... $ grep ^kde /usr/ports/INDEX kdemultimedia-1.0|/usr/ports/audio/kdemultimedia|... kdesupport-1.0|/usr/ports/converters/kdesupport|... kdegames-1.0|/usr/ports/games/kdegames|... kdegraphics-1.0|/usr/ports/graphics/kdegraphics|... kdeutils-1.0|/usr/ports/misc/kdeutils|... kdenetwork-1.0|/usr/ports/net/kdenetwork|... kde-1.0|/usr/ports/x11/kde|... kdebase-1.0|/usr/ports/x11/kdebase|... kdelibs-1.0|/usr/ports/x11/kdelibs|... -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 21:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19118 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:47:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19113 for ; Thu, 13 Aug 1998 21:47:31 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id WAA19633; Thu, 13 Aug 1998 22:46:36 -0600 (MDT) Message-Id: <199808140446.WAA19633@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Thu, 13 Aug 1998 22:46:28 -0600 To: Garance A Drosihn , Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG In-Reply-To: References: <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> <199808131924.MAA00367@dingo.cdrom.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 12:18 AM 8/14/98 -0400, Garance A Drosihn wrote: >Does this imply that you often use hammers to screw in light-bulbs?!? > :-) No, but I do get ham-handed at times. Which accounts for the excessive breakage rate. ;-) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 21:58:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20186 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 21:58:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20179 for ; Thu, 13 Aug 1998 21:58:36 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id WAA08017; Thu, 13 Aug 1998 22:00:03 -0700 (PDT) Date: Thu, 13 Aug 1998 22:00:03 -0700 (PDT) From: Jim Shankland Message-Id: <199808140500.WAA08017@biggusdiskus.flyingfox.com> To: brawley@camtech.com.au, hackers@FreeBSD.ORG, mph@pobox.com Subject: Re: 64-bit time_t In-Reply-To: <19980814000605.A25012@astro.psu.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Hunt writes: > On Fri, Aug 14, 1998 at 10:10:02AM +0930, Ivan Brawley wrote: > > > Question: What is wrong with using an unsigned long for time_t, > > instead of long (which is then assumed signed). > > man 3 time: > > Upon successful completion, time() returns the value of time. > Otherwise a value of ((time_t) -1) is returned and the > global variable errno is set to indicate the error. ... which will cause an unsigned-long (32-bit) time counter to fail precisely 1 second earlier than it would have otherwise, some time in the early twenty second century. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 22:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23381 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 22:29:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from monitord.vrn.ru (dialup44.vrn.ru [195.98.64.202]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA23350 for ; Thu, 13 Aug 1998 22:29:22 -0700 (PDT) (envelope-from bazilio@monitord.vrn.ru) Received: from baz_station [192.168.100.10] by monitor.voronezh.su [127.0.0.1] with SMTP (MDaemon.v2.7.SP0.R) for ; Fri, 14 Aug 98 09:13:44 +0400 Message-ID: <000e01bdc741$f992efc0$0a64a8c0@baz_station.monitord.vrn.ru> From: "Vasily V. Grechishnikov" To: Cc: "Bill Paul" , Subject: Re: Some errors in XL driver ? Date: Fri, 14 Aug 1998 09:11:20 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.0 X-MDaemon-Deliver-To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: David Greenman To: Vasily V. Grechishnikov Cc: freebsd-hackers@FreeBSD.ORG Date: 13 Á×ÇÕÓÔÁ 1998 Ç. 17:01 Subject: Re: Some errors in XL driver ? >>Now my 3c905B works nicely. >>netstat -ni after applying patch listed below: >>Name Mtu Network Address Ipkts Ierrs Opkts Oerrs >>Coll >>xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 >>332 > > 1565 output errors? That doesn't look so nice to me... Ueaah ! I confused ! We haven't any serious transmit errors, because I didn't seen any error message like xl0: watchdog timeout. After analyzing if_xl.c I understood source of this big Oerrs count: as output errors driver treated xl_stats.tx_deffered, I guess number of deffered transmitted frames. After manually ifconfig'uring xl0 interface with media/mediaopt or after pacthing I seen performance impact on this NIC 650Kb/s with NE2000 as peer. Also I'm not feel delays due to recieve errors, but before telnet from 3c905 box looks like busy ppp connection :-( . One suspicuous thing: I tried to test this NIC in times of our network inactivity but we has big number of collisions: 250, 332, 400 ! It's not good ! > >-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 Thu Aug 13 22:32:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23717 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 22:32:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ic.vrn.ru (ic.vrn.ru [195.98.64.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23705 for ; Thu, 13 Aug 1998 22:32:38 -0700 (PDT) (envelope-from bazilio@monitord.vrn.ru) Received: from dialup44.vrn.ru (dialup44.vrn.ru [195.98.64.202]) by ic.vrn.ru (8.8.8/Relcom-2A) with SMTP id JAA04190 for ;Fri, 14 Aug 1998 09:28:42 +0400 (MSD) Received: from baz_station [192.168.100.10] by monitor.voronezh.su [127.0.0.1] with SMTP (MDaemon.v2.7.SP0.R) for ; Fri, 14 Aug 98 09:18:13 +0400 Message-ID: <001701bdc742$99ca8fc0$0a64a8c0@baz_station.monitord.vrn.ru> From: "Vasily V. Grechishnikov" To: "Bill Paul" Cc: Subject: Re: Some errors in XL driver ? Date: Fri, 14 Aug 1998 09:15:49 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.0 X-MDaemon-Deliver-To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Bill Paul To: dg@root.com Cc: bazilio@monitord.vrn.ru ; freebsd-hackers@FreeBSD.ORG Date: 14 Á×ÇÕÓÔÁ 1998 Ç. 1:01 Subject: Re: Some errors in XL driver ? >Of all the gin joints in all the towns in all the world, David Greenman >had to walk into mine and say: > >> >Now my 3c905B works nicely. >> >netstat -ni after applying patch listed below: >> >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs >> >Coll >> >xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 >> >332 >> >> 1565 output errors? That doesn't look so nice to me... >> >> -DG > >The oerrors counter is incremented either if there's a watchdog timeout, >or by the xl_stats_update() routine when reading the stats counters. >The only statistic that's counted as an output error is 'FramesDeferred,' >which the manual describes as the number of times a transmit packet must >defer to network traffic. These occur only in half-duplex modes, for >obvious reasons. Perhaps it's not correct to account for this as an >output error? I think you thrown deffered frames to output errors by mistake. And I'm didn't seen any transmit errors due to watchdog timeout. > >-Bill > >-- >=========================================================================== == >-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu >Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >=========================================================================== == > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" >=========================================================================== == > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 23:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26563 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:01:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26545; Thu, 13 Aug 1998 23:01:02 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id CAA09249; Fri, 14 Aug 1998 02:02:02 -0400 (EDT) Date: Fri, 14 Aug 1998 02:02:02 -0400 (EDT) From: Mark turpin To: FreeBSD hackers , FreeBSD Current Subject: UDF Filesystem 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 any body working on implementing UDF on FreeBSD? I looked in the archives and didn't see anything about it? Thanks Mark Turpin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 23:16:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28689 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:16:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28684 for ; Thu, 13 Aug 1998 23:16:35 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id XAA00355; Thu, 13 Aug 1998 23:12:53 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808132312.XAA00355@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger cc: Alex , jgrosch@mooseriver.com, Marc Slemko , Warner Losh , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-reply-to: Your message of "Thu, 13 Aug 1998 22:20:24 EST." <19980813222024.27227@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 23:12:52 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Frankly, FreeBSD + Afterstep on a Pentium Pro 200 makes a damn nice > > > workstation; I prefer it over Solaris. > > > > Ahh replace AS with KDE, and you've got a better workstation ;) > > I can't find KDE in the X11 ports tree....... Install sysutils/pib, and never have any trouble finding anything again. -- \\ 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 Aug 13 23:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28920 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:18:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28912 for ; Thu, 13 Aug 1998 23:18:21 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id IAA04738 for hackers@FreeBSD.ORG; Fri, 14 Aug 1998 08:17:50 +0200 (SAT) From: John Hay Message-Id: <199808140617.IAA04738@zibbi.mikom.csir.co.za> Subject: pci register map problem To: hackers@FreeBSD.ORG Date: Fri, 14 Aug 1998 08:17:50 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to update the ar(4) device driver to also understand the Digi SYNC/570i-PCI cards, but found a little problem. According to the docs for the card it has 4 pci maps, but FreeBSD only see 3 of them. I have tried it in another machine with a different motherboard and BIOS, but the result is the same, although the addresses differ. Here is what the pci probe code with verbose on says: -------------------- found-> vendor=0x114f, dev=0x5012, revid=0x00 class=07-80-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 map[0]: type 1, range 32, base fed7fc00, size 7 map[1]: type 4, range 32, base 0000fc00, size 7 map[2]: type 1, range 32, base fed80000, size 19 -------------------- I have tried the DOS diagnostic utility that came with the card and that works fine. What is interresting is that according to the diagnostic utility the base for map[0] is a little different: 0xfedc1000. The base for map[3] according to it is: 0xfedc0000. Do anybody have an idea what is happening or how I can resolve it? If I understand correctly the BIOS do the mapping and FreeBSD only read and use it? Is that correct? In the mean time I'll start to read the pci code and see if I can figure out where the problem is. This is on 3.0-CURRENT. I don't have a 2.2.x machine at the moment to see if it behaves the same. Attached below is the output of a verbose boot. John -- John Hay -- John.Hay@mikom.csir.co.za Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Wed Aug 12 19:02:27 SAT 1998 root@orca.cids.org.za:/usr/src/sys/compile/ORCAUP Calibrating clock(s) ... TSC clock: 99702886 Hz, i8254 clock: 1193079 Hz Timecounter "i8254" frequency 1193079 Hz cost 3604 ns Timecounter "TSC" frequency 99702886 Hz cost 229 ns CPU: Pentium/P54C (99.70-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x3bf real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x001db000 - 0x01ffdfff, 31600640 bytes (7715 pages) avail memory = 31051776 (30324K bytes) Found BIOS32 Service Directory header at 0xf00f7690 Entry = 0xfcee1 (0xf00fcee1) Rev = 0 Len = 1 PCI BIOS entry at 0x9ac Other BIOS signatures found: ACPI: 00000000 $PnP: 000eb530 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x80000000 (0xff000001) pci_cfgcheck: device 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 -- nothing found pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x04a3, revid=0x11 class=06-00-00, hdrtype=0x00, mfdev=0 chip0: rev 0x11 on pci0.0.0 CPU: Pentium, 60MHz, CPU->Memory posting ON, read around write Warning: Cache parity disabled! Cache: 256KB writeback, cache clocks=3-2-2-2/4-2-2-2 Cache flags: cache-all byte-control DRAM: page mode memory clocks=X-4-4-4 (70ns), RAS-wait, CAS-wait CPU->PCI: posting ON, burst mode ON, PCI clocks=2-1-1-1 PCI->Memory: posting ON Refresh: RAS#Only found-> vendor=0x8086, dev=0x0482, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 chip1: rev 0x03 on pci0.2.0 found-> vendor=0x1095, dev=0x0640, revid=0x02 class=01-01-0a, hdrtype=0x00, mfdev=0 intpin=a, irq=14 ide_pci0: rev 0x02 int a irq 14 on pci0.4.0 found-> vendor=0x114f, dev=0x5012, revid=0x00 class=07-80-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 map[0]: type 1, range 32, base fed7fc00, size 7 map[1]: type 4, range 32, base 0000fc00, size 7 map[2]: type 1, range 32, base fed80000, size 19 arc1: rev 0x00 int a irq 10 on pci0.14.0 arp: ID 5012114f arp: PCIcmd 2800107 arp: PBADR fed7fc00 arp: SIOBADR fc01 arp: MBADR fed80000 arp: HBADR 0 arp: vaddr f2b22000, paddr fed80000 arp: map failed. Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0045 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 flags 0x8 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c ae 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: video mode:24 sc0: VGA registers 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 ae 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: VGA registers 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 ae 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: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x8> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:1d:43:db, type SMC8216/SMC8216C (16 bit) bpf: ed0 attached sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A 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: 610MB (1249920 sectors), 1240 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0203, apio = 0001, udma = 0000 arc0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 64960374 bytes/sec bzero() bandwidth = 32507639 bytes/sec imasks: bio c0084040, tty c003001a, net c0060020 stray irq 7 BIOS Geometries: 0:026a1f3f 0..618=619 cylinders, 0..31=32 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround bpf: lo0 attached Considering FFS root f/s. changing root device to wd0s4a wd0s4: type 0xa5, start 63, end = 1249919, size 1249857 : OK ffs_mountfs: superblock updated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 23:24:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29943 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:24:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29938 for ; Thu, 13 Aug 1998 23:24:48 -0700 (PDT) (envelope-from poipoi@famipow.com) From: poipoi@famipow.com Received: from root@tamaya.wanadoo.fr [193.252.19.31] by wanadoo.fr for Paris Fri, 14 Aug 1998 08:23:56 +0200 (MET DST) Received: from qmailr@cergy13-7.abo.wanadoo.fr [164.138.1.7] by smtp.wanadoo.fr for Paris Fri, 14 Aug 1998 08:23:56 +0200 (MET DST) Received: (qmail 176 invoked by uid 501); 14 Aug 1998 06:34:40 -0000 Message-ID: <19980814063439.175.qmail@hwi.poi.org> Subject: solaris smp management To: freebsd-hackers@FreeBSD.ORG Date: Fri, 14 Aug 1998 08:34:39 +0200 (MET DST) 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 a lot of people on this list seems agree to say "solaris smp is faster freebsd or linux one". Can you explain why it is faster ? and why freebsd and linux dont use the same algorithm ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 13 23:27:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00584 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:27:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00560 for ; Thu, 13 Aug 1998 23:27:15 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id XAA00422; Thu, 13 Aug 1998 23:25:10 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808132325.XAA00422@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Thu, 13 Aug 1998 15:03:05 CST." <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 23:25:09 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 12:24 PM 8/13/98 -0700, Mike Smith wrote: > > >> I'd kind of like to do financial projections for my retirement and not > >> have the calculations blow up, as they do now. > > > >time_t is a format for the system current time. As such, you're abusing > >it mightily if you expect it to be a general-purpose time value. > > It's used throughout UNIX and UNIX programs as such. And rightfully so; > it's silly to have multiple date formats. It's used throughout Unix and Unix programs to represent values of 'now' which may relate to the system time. It is abused to represent time values which overlap this to some degree. It is not "silly" to have multiple date formats. It is *sensible* to have multiple date formats, where each format is chosen for suitability for its purpose. time_t is too imprecise for many things (hence struct timeval) and too limited in range for others (eg. your application). Neither of these mean that it's not suited to its correct usage. > >Might I suggest that you should consider using something with perhaps a > >slightly reduced precision, like anyone else that does work involving > >longer timeframes? > > This would create an incompatible notation and would make life much more > difficult than fixing the basic problem. Surely you jest. Fixing *just* your application is "much more difficult" than fixing every other application that uses time_t correctly? I think not. > >time_t is not a hammer. > > Nope, but I don't intend to carry an entire box of tools to screw in a light > bulb.... ;-) Funny, that's what Unix is. A big box full of tools. Pick the right one for the job, and you'll bruise much less often. -- \\ 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 Aug 13 23:36:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02598 for freebsd-hackers-outgoing; Thu, 13 Aug 1998 23:36:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02573 for ; Thu, 13 Aug 1998 23:36:18 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from localhost (localhost.cdrom.com [127.0.0.1]) by myname.my.domain (8.8.8/8.8.8) with ESMTP id UAA00204; Thu, 13 Aug 1998 20:31:13 GMT (envelope-from mike@myname.my.domain) Message-Id: <199808132031.UAA00204@myname.my.domain> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: grog@lemis.com (Greg Lehey), hm@kts.org, freebsd-hackers@FreeBSD.ORG Subject: Re: developing device drivers In-reply-to: Your message of "Fri, 14 Aug 1998 02:35:04 GMT." <199808140235.TAA25965@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 20:31:13 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Apologies off the top if my address in this message is unrepliable to, I'm just reconstructing my laptop after a major upgrade, performed with no help from Toshiba's BIOS, the cost of SelectBay shells, or the z* drivers. *mumble*) > > I think Hellmuth brought up an important issue which you don't appear > > to have covered: sure, it's easy enough to probe. But some probes are > > destructive, and if you don't know what's already been taken, you're > > liable to kill some other device while messing around looking for your > > devices. Is there some list which contains information about what > > resources are already assigned to other drivers? > > Yes. Otherwise PCMCIA cards couldn't work. That's why I specifically > referenced them. Unfortunately, there are two lists covered by your reply. The first is manintained manually in /etc/pccard.conf, and is usually wrong. The second is maintained internal to the kernel, and is also often wrong. Only the first can be corrected at the moment. Work is underway to improve the second, but this requires vetting of Jonathan Lemon's 16-bit protected mode call code, which David has been silent on (to me at least) since it was submitted to him some weeks back. -- \\ 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 Aug 14 00:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08448 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 00:17:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from control.colossus.dyn.ml.org (206-18-115-33.la.inreach.net [206.18.115.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08092; Fri, 14 Aug 1998 00:16:00 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by control.colossus.dyn.ml.org (8.8.8/8.8.8) id AAA03639; Fri, 14 Aug 1998 00:14:30 -0700 (PDT) (envelope-from dburr) 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: Fri, 14 Aug 1998 00:14:30 -0700 (PDT) Organization: Computer Help From: Donald Burr To: FreeBSD Multimedia , FreeBSD Hackers mailing list Subject: 3dfx thingie (GLIDE) for FreeBSD? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while ago, a guy (forget his name -- was it Kevin ?) was asking for help and testers for porting some 3dfx (VOodoo) thingie -- GLIDE? -= to FreeBSD. At the time, I didn't pay much attention to it, since I had no interested in purchasing such a card. But I have one now, and would like to use it under FreeBSD. I'd be happy to be a tester and help out where I can. If someone would be so kind as to point me in the direction of this project (a web site? or the maintainer's e-mail address, even) I would be very grateful. Many thanks! --- Donald Burr *NEW EMAIL ADDRESS!* | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ#16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. >>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 Aug 14 00:19:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09297 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 00:19:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09257; Fri, 14 Aug 1998 00:19:48 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id DAA00487; Fri, 14 Aug 1998 03:19:17 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Mark turpin cc: FreeBSD hackers , FreeBSD Current Reply-To: freebsd-fs@FreeBSD.ORG From: "Gary Palmer" Subject: Re: UDF Filesystem In-reply-to: Your message of "Fri, 14 Aug 1998 02:02:02 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 03:19:17 -0400 Message-ID: <483.903079157@gjp.erols.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark turpin wrote in message ID : > > Is any body working on implementing UDF on FreeBSD? I looked in the > archives and didn't see anything about it? URL with details? (reply-to set to the correct list) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 00:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13521 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 00:37:19 -0700 (PDT) (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 AAA13516 for ; Fri, 14 Aug 1998 00:37:17 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA15536; Fri, 14 Aug 1998 09:36:36 +0200 (MET DST) Date: Fri, 14 Aug 1998 09:36:33 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Steve Hearn cc: FreeBSD hackers mailing list Subject: Re: Freebsd on Portables 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 > 1. General 'brand recommendations' for Portable to run freebsd. Myself, I have a Fujitsu. Fast and reliable. Works well with the APM code. CD ROM acts a bit funny, as a number of cdplayer utils do not work. Have to look into that one. X is a bit difficult to get to work. But I finally found a configuration that works. For me it is a good price/performance. Needs dual boot though to get all the features to work. > 2. Also, specifically, whats the best option for getting network connection > on a freebsd notebook. DHCP. isc-dhcp works quite nicely. Wide DHCP trips on strange netmasks (255.255.255.0 on 139.191.71.0 does not work. I've not the foggiest why. but it gives me a 'no more addresses error' You plug in your PCMCIA card and it starts to detect it. You need to install 2.2.6 and the PAO additions to make it work off the shelf though. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 00:47:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15203 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 00:47:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15188 for ; Fri, 14 Aug 1998 00:47:04 -0700 (PDT) (envelope-from nadav@csa.cs.technion.ac.il) Received: from csd.csa (csd [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with SMTP id KAA20438; Fri, 14 Aug 1998 10:46:49 +0300 (IDT) Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id KAA08634; Fri, 14 Aug 1998 10:46:45 +0300 Date: Fri, 14 Aug 1998 10:46:45 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Stuart Krivis cc: FreeBSD hackers mailing list Subject: Re: solaris is 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 Thu, 13 Aug 1998, Stuart Krivis wrote: > On Thu, 13 Aug 1998, Nadav Eiron wrote: > > They must have been having a bad day. :-) I didn't find x86 2.6 to be > difficult to install. CDE works also. > > > There _are_ some reasons for choosing x86. > > 1. You run Solaris SPARC and want a uniform environment. > > 2. You rely on SMP. x86 seems to be better at this than FreeBSD or Linux > at this point. (No hard proof on this one, but it seems to be the case > given our limited testing.) > > 3. You need a name-brand solution to sell to the bosses or customers. > > 4. You need someone to blame when things go wrong. :-) (Here boss, this is > Jordan's phone #, talk to him about this problem... hehe) No. Their reason was: 5. You need an OS with sources! (they dumped NT in favour of Solaris/x86 since they didn't get a source license from M$). > > It is very nice to be able to say something like, "We isolated the problem > to "x" and have called SunSoft. They said such and such and this is the > estimated timetable for a solution. (There may be no solution, in which > case you have trouble. But this could happen with anything.) > > > > -- > > Stuart Krivis stuart@krivis.com > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 01:02:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16224 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 01:02:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16205; Fri, 14 Aug 1998 01:02:23 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.7/8.7.3) with SMTP id BAA18050; Fri, 14 Aug 1998 01:01:43 -0700 (PDT) Date: Fri, 14 Aug 1998 01:01:43 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: David Greenman cc: peter@sirius.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: More info: Re: vmopar state in 2.2.7? In-Reply-To: <199808140015.RAA17635@implode.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 I have a tad more info that may shed some light. After much wailing and gnashing of teeth, I realized I had copied my INN 2.1 config files built on a 3.0 box to a 2.2 box, and one of the settings was to mmap() the overview files. mmap() for the active file has always had problems with file truncation under the 2.2.x series, as has been well documented. I'm suspicious that mmap() on an NFS mounted file is the culprit here more than anythingelse. Changing it to not mmap() the overfile seems to have corrected the problem, at least so far. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 01:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16287 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 01:02:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16275 for ; Fri, 14 Aug 1998 01:02:30 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id KAA23629; Fri, 14 Aug 1998 10:02:02 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0z7EoD-002ZjZC; Fri, 14 Aug 98 10:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Fri, 14 Aug 1998 08:48:33 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@FreeBSD.ORG; Fri, 14 Aug 1998 08:41:55 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #1 built 1998-Jun-6) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: developing device drivers In-Reply-To: <199808132017.NAA14261@usr09.primenet.com> from Terry Lambert at "Aug 13, 98 08:17:13 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 14 Aug 1998 08:41:55 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.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 Terry Lambert wrote: > > I'd really like to write drivers (for ISA cards) as LKM modules, but so > > far i don't know how to assign 1) the IRQ, 2) the iobase and 3) the membase > > ( and perhaps flags and spl) to the LKM at module load time. > > > > Did i miss something ? > > You probe and attach at load time, normally. This means you detect the > IRQ/DRQ/IOBase/MemBase/Etc., not assign it. I don't quite understand, sorry. Given an ISA card, supporting IRQ's 3..15, i/o 0x100...0x300 and mem 0xa0000 ...0dffff. What i was looking for in the first place was something like modload -I -O -M .... to specify the same parameters i'd have to specify in the kernel config file. When i probe at load time, i try to detect the card in question, but where shall i start to search without knowing _where_ to search (iobase/membase) (other than searching through the whole supported iobase/membase) ? Given i found the card to be the one i looked for, which of the IRQ/iobase/mem supports shall i use in the attach ? How is the user to be able to specify the parameters he prefers ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 02:21:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24652 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 02:21:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24596; Fri, 14 Aug 1998 02:20:44 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id LAA08042; Fri, 14 Aug 1998 11:19:44 +0200 (CEST) Message-ID: <19980814111944.50903@foobar.franken.de> Date: Fri, 14 Aug 1998 11:19:44 +0200 From: Harold Gutch To: Donald Burr , FreeBSD Multimedia , FreeBSD Hackers mailing list Subject: Re: 3dfx thingie (GLIDE) for FreeBSD? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Donald Burr on Fri, Aug 14, 1998 at 12:14:30AM -0700 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 12:14:30AM -0700, Donald Burr wrote: > A while ago, a guy (forget his name -- was it Kevin ?) was > asking for help and testers for porting some 3dfx (VOodoo) thingie -- > GLIDE? -= to FreeBSD. > > If someone would be so kind as to point me in the direction of this > project (a web site? or the maintainer's e-mail address, even) I would be > very grateful. > I guess you're thinking of Kurt Olsen and Kevin Day . Kurt was the one who originally posted to -multimedia, Kevin replied stating that he had already gotten a "yes" and the sources from 3dfx and would be starting with the port later that week. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 04:16:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07284 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 04:16:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07279 for ; Fri, 14 Aug 1998 04:16:09 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id FAA21672; Fri, 14 Aug 1998 05:15:22 -0600 (MDT) Message-Id: <199808141115.FAA21672@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 05:15:20 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808132325.XAA00422@word.smith.net.au> 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 11:25 PM 8/13/98 +0000, Mike Smith wrote: >Funny, that's what Unix is. A big box full of tools. Many of which, due to legacy code, are redundant and cause unnecessary bloat and confusion. >Pick the right one for the job, and you'll bruise much less often. Make one more generally useful, and you won't have to root around hunting for the one (of dozens) that's exactly right. It's amazing the excuses people will make not to update their tools! I suppose this is why so much is still written in C, which is generally acknowledged to be a rusty tool without safety guards. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 04:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10254 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 04:48:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10240; Fri, 14 Aug 1998 04:48:13 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA23436; Fri, 14 Aug 1998 04:47:10 -0700 (PDT) Message-Id: <199808141147.EAA23436@implode.root.com> To: Terry Lambert cc: mike@smith.net.au, peter@sirius.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: vmopar state in 2.2.7? In-reply-to: Your message of "Fri, 14 Aug 1998 02:27:05 -0000." <199808140227.TAA25476@usr02.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Aug 1998 04:47:10 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In the second case, 1261, the consequences could be bad. In fact, >the consequences of sleeping at all could be bad. The reason it >seems to work around the problem for you is that the page causing >the problem is not the first page on the list and start has been >incremented. Because start is not decremented before the "goto again", >the calculation on line 1207: > > again: > size = end - start; > if (size > 4 || size >= object->size / 4) { > >Bogusly omits the page which was just obtained. This means that > > vm_page_protect(p, VM_PROT_NONE); > PAGE_WAKEUP(p); > vm_page_free(p); > >is never called. > >The net result is that pages are left hanging out in space, but the system >thinks they have been reclaimed. Err, it doesn't "omit the page which was just obtained". First off, pages aren't obtained; all that happens is a pointer to them is gotten - they are still on the object page list. For optimal performance, there are two ways that the code will traverse the resident pages in the object. The first is the case where the object either contains a small number of pages or if all the pages should be removed. In this case, it just accesses the unsorted object resident page list. Since this list contains all of the pages in a resident object, the code must check the offset of the pages to ensure that they are within the proper range that is being removed. Pages that are wired or dirty are skipped. If while doing this a busy page is encountered, then the system must wait for the page to become not busy. While sleeping, the order of pages might have changed in the list, however, so it is necessary to start over again from the beginning of the object page list. "start" isn't and can't be updated since the order of pages that are removed is random. The second method is to look up the page on the object page hash list. This has somewhat higher overhead, but is more efficient when dealing with a small number of pages in an object that has a large number of resident pages. Since in this case we process the pages sequentially in the start to end range, we can increment start as each page is removed (or skipped as the case may be). If the page is busy, then start isn't incremented and thus the 'goto again' will begin with the page which was just slept on. Once again, the bug isn't in the code there. The effects that have been described suggest a missing wakeup. I believe the attached patches should fix the problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project Index: nfs/nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.28.2.7 diff -c -r1.28.2.7 nfs_bio.c *** nfs_bio.c 1998/01/28 00:26:54 1.28.2.7 --- nfs_bio.c 1998/08/14 11:42:02 *************** *** 131,136 **** --- 131,140 ---- m->flags |= PG_BUSY; m->busy--; + if (m->busy == 0 && (m->flags & PG_WANTED)) { + m->flags &= ~PG_WANTED; + wakeup(m); + } if (error && (auio.uio_resid == MAXBSIZE)) return VM_PAGER_ERROR; Index: vm/vnode_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.65.2.2 diff -c -r1.65.2.2 vnode_pager.c *** vnode_pager.c 1997/05/28 18:26:46 1.65.2.2 --- vnode_pager.c 1998/08/14 11:43:06 *************** *** 963,970 **** if (i < ncount) { rtvals[i] = VM_PAGER_OK; } ! if ((m[i]->busy == 0) && (m[i]->flags & PG_WANTED)) wakeup(m[i]); } return rtvals[0]; } --- 963,972 ---- if (i < ncount) { rtvals[i] = VM_PAGER_OK; } ! if ((m[i]->busy == 0) && (m[i]->flags & PG_WANTED)) { ! m[i]->flags &= ~PG_WANTED; wakeup(m[i]); + } } return rtvals[0]; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 05:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18080 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 05:49:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18075 for ; Fri, 14 Aug 1998 05:49:58 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id HAA18118; Fri, 14 Aug 1998 07:49:07 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199808132325.XAA00422@word.smith.net.au> References: Your message of "Thu, 13 Aug 1998 15:03:05 CST." <4.1.0.44.19980813150058.03f4dd80@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 14 Aug 1998 07:48:45 -0500 To: Brett Glass From: Richard Wackerbarth Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:25 PM -0500 8/13/98, Mike Smith wrote: >> >> I'd kind of like to do financial projections for my retirement and not >> >> have the calculations blow up, as they do now. >> > >> >time_t is a format for the system current time. As such, you're abusing >> >it mightily if you expect it to be a general-purpose time value. >> >> It's used throughout UNIX and UNIX programs as such. And rightfully so; >> it's silly to have multiple date formats. > >It's used throughout Unix and Unix programs to represent values of >'now' which may relate to the system time. It is abused to represent >time values which overlap this to some degree. > >It is not "silly" to have multiple date formats. It is *sensible* to >have multiple date formats, where each format is chosen for suitability >for its purpose. Brett, I have to agree with Mike on this point. Since I need time measured in picoseconds for the data in some scientific experiments and others need to measure geologic time, I guess that 64 bits is not enough. :-) If we follow your suggestion, EVERYONE would ALWAYS have to pay an extreme burden to process and store multi-precision time values. It is much more efficient to use the right tool, (or in this case, format) for the job at hand. "One size fits all" is really the wrong attitude. At best, it produces a sloppy fit. "One size fits none" is much closer to the truth. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 05:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19941 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 05:54:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA19917 for ; Fri, 14 Aug 1998 05:54:31 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id IAA29923; Fri, 14 Aug 1998 08:56:54 -0400 From: Bill Paul Message-Id: <199808141256.IAA29923@skynet.ctr.columbia.edu> Subject: Re: Some errors in XL driver ? To: bazilio@monitord.vrn.ru (Vasily V. Grechishnikov) Date: Fri, 14 Aug 1998 08:56:53 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <000e01bdc741$f992efc0$0a64a8c0@baz_station.monitord.vrn.ru> from "Vasily V. Grechishnikov" at Aug 14, 98 09:11:20 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Vasily V. Grechishnikov had to walk into mine and say: > -----Original Message----- > From: David Greenman > To: Vasily V. Grechishnikov > Cc: freebsd-hackers@FreeBSD.ORG > Date: 13 Á×ÇÕÓÔÁ 1998 Ç. 17:01 > Subject: Re: Some errors in XL driver ? > > > >>Now my 3c905B works nicely. > >>netstat -ni after applying patch listed below: > >>Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > >>Coll > >>xl0 1500 00.10.4b.06.a7.55 9083 4 4018 1565 > >>332 > > > > 1565 output errors? That doesn't look so nice to me... > Ueaah ! I confused ! > We haven't any serious transmit errors, because I > didn't seen any error message like xl0: watchdog timeout. > After analyzing if_xl.c I understood source of this big Oerrs > count: as output errors driver treated xl_stats.tx_deffered, I > guess number of deffered transmitted frames. After manually > ifconfig'uring xl0 interface with media/mediaopt or after > pacthing I seen performance impact on this NIC 650Kb/s with > NE2000 as peer. Also I'm not feel delays due to recieve errors, > but before telnet from 3c905 box looks like busy > ppp connection :-( . So you're saying it works, but it doesn't work? Wait. Is this really a 3c905 and not a 3c905B? If so, then please try the newest driver at www.freebsd.org/~wpaul. I did find a problem with performance on 10Mbps links. Even if you're not seeing watchdog timeouts, it may be worth a try. > One suspicuous thing: I tried to test this NIC in times of > our network inactivity but we has big number of collisions: > 250, 332, 400 ! It's not good ! The driver adds up single collisions, late collisions and multiple collisions into the one counter. I also see a lot of collisions on my 3c900 on a 10base2 network. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 06:14:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22534 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 06:14:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA22529 for ; Fri, 14 Aug 1998 06:14:15 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 19964 invoked by uid 3759); 14 Aug 1998 13:15:00 -0000 Date: Fri, 14 Aug 1998 09:14:59 -0400 (EDT) From: "B. Richardson" To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-Reply-To: <199808141115.FAA21672@lariat.lariat.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 Slightly out of thread, but .... do any 32 bit Unices have a 64 bit time_t? I was under the impression (maybe wrongfully so) that they do not. - Barrett Richardson rabtter@orion.aye.net On Fri, 14 Aug 1998, Brett Glass wrote: > At 11:25 PM 8/13/98 +0000, Mike Smith wrote: > > >Funny, that's what Unix is. A big box full of tools. > > Many of which, due to legacy code, are redundant and cause > unnecessary bloat and confusion. > > >Pick the right one for the job, and you'll bruise much less often. > > Make one more generally useful, and you won't have to root around > hunting for the one (of dozens) that's exactly right. > > It's amazing the excuses people will make not to update their tools! > I suppose this is why so much is still written in C, which is > generally acknowledged to be a rusty tool without safety guards. > > --Brett > > > 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 Aug 14 08:27:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11266 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 08:27:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11261 for ; Fri, 14 Aug 1998 08:26:56 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id JAA23467; Fri, 14 Aug 1998 09:26:19 -0600 (MDT) Message-Id: <199808141526.JAA23467@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 09:22:45 -0600 To: "B. Richardson" From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: References: <199808141115.FAA21672@lariat.lariat.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 believe that Linux is already moving to a 64-bit time_t. The BSDs are behind. Maybe that's why there's resistance here (I can't figure out any LOGICAL reason for resisting this necessary change.) --Brett At 09:14 AM 8/14/98 -0400, B. Richardson wrote: > >Slightly out of thread, but .... do any 32 bit Unices have a 64 bit >time_t? I was under the impression (maybe wrongfully so) that they do not. > >- > >Barrett Richardson rabtter@orion.aye.net > >On Fri, 14 Aug 1998, Brett Glass wrote: > >> At 11:25 PM 8/13/98 +0000, Mike Smith wrote: >> >> >Funny, that's what Unix is. A big box full of tools. >> >> Many of which, due to legacy code, are redundant and cause >> unnecessary bloat and confusion. >> >> >Pick the right one for the job, and you'll bruise much less often. >> >> Make one more generally useful, and you won't have to root around >> hunting for the one (of dozens) that's exactly right. >> >> It's amazing the excuses people will make not to update their tools! >> I suppose this is why so much is still written in C, which is >> generally acknowledged to be a rusty tool without safety guards. >> >> --Brett >> >> >> 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 Aug 14 09:23:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18729 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:23:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18722 for ; Fri, 14 Aug 1998 09:23:22 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id MAA02113; Fri, 14 Aug 1998 12:23:35 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 12:23:35 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: poipoi@famipow.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris smp management In-Reply-To: <19980814063439.175.qmail@hwi.poi.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 it isn't an "algorithm" rather a total restructuring of the kernel. freebsd wouldn't be "BSD" anymore if it adopted the same path as sun. that's why there is no more "sunos" just solaris, sunos was a BSD kernel, while solaris was a resturctured blend of BSD and SRV4. -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 14 Aug 1998 poipoi@famipow.com wrote: > hi > > a lot of people on this list seems agree to say "solaris smp > is faster freebsd or linux one". Can you explain why it is faster ? and > why freebsd and linux dont use the same algorithm ? > > 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 Aug 14 09:26:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19575 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:26:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19566 for ; Fri, 14 Aug 1998 09:26:51 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA12980; Fri, 14 Aug 1998 09:24:55 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808140924.JAA12980@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 05:15:20 CST." <199808141115.FAA21672@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 09:24:54 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 11:25 PM 8/13/98 +0000, Mike Smith wrote: > > >Funny, that's what Unix is. A big box full of tools. > > Many of which, due to legacy code, are redundant and cause > unnecessary bloat and confusion. Nice sweeping statement there. Not really accurate either. > >Pick the right one for the job, and you'll bruise much less often. > > Make one more generally useful, and you won't have to root around > hunting for the one (of dozens) that's exactly right. This is the attitude that leads to the condition that you lambasted in your previous statement. You can't have it both ways. > It's amazing the excuses people will make not to update their tools! > I suppose this is why so much is still written in C, which is > generally acknowledged to be a rusty tool without safety guards. No, so much stuff is written in C because it's a good tool for the job. -- \\ 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 Aug 14 09:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20179 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:29:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp6560.on.bellglobal.com [206.172.208.152]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20171 for ; Fri, 14 Aug 1998 09:29:20 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id LAA04072; Fri, 14 Aug 1998 11:45:25 -0400 (EDT) (envelope-from tim) Message-ID: <19980814114525.B4001@zappo> Date: Fri, 14 Aug 1998 11:45:25 -0400 From: Tim Vanderhoek To: Greg Lehey , Matthew Hunt , Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> <19980814135919.U1921@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980814135919.U1921@freebie.lemis.com>; from Greg Lehey on Fri, Aug 14, 1998 at 01:59:19PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 01:59:19PM +0930, Greg Lehey wrote: > > More to the point, time_t *can* be used to represent BE (Before Epoch) > dates. Make it unsigned and you break that. "time_t is a format for the system current time. As such, you're abusing it mightily if you expect it to be a general-purpose time value." - Mike Smith -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 09:35:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21294 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:35:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21289 for ; Fri, 14 Aug 1998 09:35:49 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id QAA10218; Fri, 14 Aug 1998 16:35:19 GMT (envelope-from didier@omnix.net) Date: Fri, 14 Aug 1998 18:35:19 +0200 (CEST) From: Didier Derny To: hackers@FreeBSD.ORG cc: support@yard.de Subject: Yard/FreeBSD Problem (Re: database for tests (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 With my patch on the tcp_output, The program is executed (for the 8000 records of the normal file in less than 2minutes) It seems do be considerably faster with FreeBSD+patch than Linux I send a copy of your message to the hackers mailing list, hoping that someone has a clue. this week end I'll do some test myself with linux. I'll also try to rewrite the small program in ESQL to compare the results. the main problem for me is that that people who will be using perl/dbi have never programmed in C. (and will never) That's why I have to find a reliable solution. I'm ready to do any testing you want to help you. by the way, setting the "net.inet.tcp.delayed_ack=0" on FreeBSD 3.0 as the same result as my hack in the 2.2.5 Kernel. For the entire program, the long one (with the entire database) without the hack or ..delayed_ack --> running time 2 hours with ..delayed_ack=0 --> running time 2 minutes. on a pentium II with 96Mb of Memory. -- Didier Derny didier@omnix.net ---------- Forwarded message ---------- Hi, I ran your (small version) program on our Linux site. It's compared to FreeBSD 15 times faster, which indicates a FreeBSD problem. When the program is running on FreeBSD, vmstat reports at least 95% idle time, which also points to a problem in the kernel. In addition, you have to consider an overhead of the Perl interface in opposite to eg. ESQLC. Perl will declare/open/fetch/close/free for each SELECT, which will result in many small packages transmitted through TCP. I assume the TCP_NODELAY flag doesn't work because it doesn't make sense for the client not to wait for the TCP acknowledge, because it has to wait for the servers response anyway. If possible, consider to implement your program in ESQLC, which will be probably much faster. Best Regards Thomas Schonhoven -- ///!! ///!! //!! ////////////!! ///////////!! ///!! ///!! ////!! ///!! ///!! ///!! ///!! ///!! ///!! //////!! ///!! ///!! ///!! ///!! ///!! ///!! ///!////!! ///////////!! ///!! ///!! ///!! ///!! ///!! ////!! //////////!! ///!! ///!! //////!! ///!! ////!! ///!! ///!! ///!! ///!! ////!! //////////////!! ///!! ///!! ///!! ///!! ////!! ////!! ////!! ///!! ///!! ///////////!! YARD Software GmbH YARD Software Ltd. Wikingerstr. 18 - 20 Wikingerstr. 18 - 20 51107 Koeln 51107 Cologne Tel.: +4922198664-0 FAX.: +4922198664-99 E-Mail: support@yard.de FTP : ftp.yard.de WWW : http://www.yard.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 09:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23487 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:44:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23437 for ; Fri, 14 Aug 1998 09:44:27 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA13112; Fri, 14 Aug 1998 09:42:22 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808140942.JAA13112@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Glass cc: "B. Richardson" , Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 09:22:45 CST." <199808141526.JAA23467@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 09:42:21 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aside from breaking legacy interfaces in K&R mode, the only real change this will effect is to slow down the handling of system time issues on 32-bit platforms. This change (if they implement it correctly) will break at least one major commercial application. Note that we already have 64-bit time support as I previously mentioned (struct timeval), again geared more for usefulness than pointless generality. > I believe that Linux is already moving to a 64-bit time_t. The BSDs > are behind. Maybe that's why there's resistance here (I can't figure > out any LOGICAL reason for resisting this necessary change.) > > --Brett > > At 09:14 AM 8/14/98 -0400, B. Richardson wrote: > > > > >Slightly out of thread, but .... do any 32 bit Unices have a 64 bit > >time_t? I was under the impression (maybe wrongfully so) that they do not. > > > >- > > > >Barrett Richardson rabtter@orion.aye.net > > > >On Fri, 14 Aug 1998, Brett Glass wrote: > > > >> At 11:25 PM 8/13/98 +0000, Mike Smith wrote: > >> > >> >Funny, that's what Unix is. A big box full of tools. > >> > >> Many of which, due to legacy code, are redundant and cause > >> unnecessary bloat and confusion. > >> > >> >Pick the right one for the job, and you'll bruise much less often. > >> > >> Make one more generally useful, and you won't have to root around > >> hunting for the one (of dozens) that's exactly right. > >> > >> It's amazing the excuses people will make not to update their tools! > >> I suppose this is why so much is still written in C, which is > >> generally acknowledged to be a rusty tool without safety guards. > >> > >> --Brett > >> > >> > >> 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 > -- \\ 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 Aug 14 09:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24185 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:46:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24160 for ; Fri, 14 Aug 1998 09:46:37 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id KAA24210; Fri, 14 Aug 1998 10:45:59 -0600 (MDT) Message-Id: <199808141645.KAA24210@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 10:40:00 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG In-Reply-To: <199808140924.JAA12980@word.smith.net.au> 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 09:24 AM 8/14/98 +0000, Mike Smith wrote: >No, so much stuff is written in C because it's a good tool for the job. Don't want to get into language wars here, but in case the current rash of security problems doesn't make it painfully obvious, C isn't a good tool for ANYTHING. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 09:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24737 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 09:49:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24703 for ; Fri, 14 Aug 1998 09:48:50 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA06288; Fri, 14 Aug 1998 09:48:06 -0700 (PDT) (envelope-from jdp) Message-Id: <199808141648.JAA06288@austin.polstra.com> To: volf@oasis.IAEhv.nl Subject: Re: File permissions in CVS tree obtained using CTM In-Reply-To: <199808112051.UAA00914@avalon.oasis.IAEhv.nl> References: <199808112051.UAA00914@avalon.oasis.IAEhv.nl> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Fri, 14 Aug 1998 09:48:06 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808112051.UAA00914@avalon.oasis.IAEhv.nl>, Frank Volf wrote: > A more theoretical question would be: can we safely rely on the file > permissions on the CVS tree, or should we take precautions (in this case > use the Makefile to set execute permissions on the checkout files, > before running them). Historically, the execute bits have had a tendency to dissolve from the repository over time. :-) You should not count on them being set properly. The only things in the repository that might need to be "executed" are scripts. There aren't any program binaries there. The best way to execute shell scripts is with "sh foo". (For ports only, there is a make macro ${SH} defined.) For perl, awk, and tcl scripts, do the analogous thing -- invoke the interpreter explicitly. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 10:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28543 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:08:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28538; Fri, 14 Aug 1998 10:08:26 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id TAA00337; Fri, 14 Aug 1998 19:07:06 +0200 (CEST) (envelope-from sos) Message-Id: <199808141707.TAA00337@sos.freebsd.dk> Subject: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: current@FreeBSD.ORG (FreeBSD current), hackers@FreeBSD.ORG (FreeBSD hackers) Date: Fri, 14 Aug 1998 19:07:06 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 A workable snapshot is available on: ftp;//sos.freebsd.dk/pub/ATAPI/* >From the README: This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. Please dont distribute this, only use it for testing, as it is alpha level code which is undergoing rapid changes. The main use of this snap is to test the support for ATAPI CD burners, and the driver has been adapted to the old ATAPI system to serve only this purpose. Both ATAPI CD-R & CD-RW drives are supported, and it has been tested with a HP7200i and a BTC BCE621E (also sold under the KISS name). The driver might scribble various messages on the console, but most should be harmless diagnostics. As always YMMV. Install the new driver files new-files.tgz and apply the patches in sys-diff, make a new entry in your configfile for the new "acd" atapi device, config & make a new kernel. The acd driver uses the same devicemajor as the old wcd driver, so you can reuse the /dev/*wcd* devices. However if you use DEVFS it will register itself under the name /dev/*acd*. I have includes a modified version of "wormcontrol" that can talk to the acd driver. It has two new commands "nextwriteable" that tells the driver the next writeable block on a CDR/CDRW, used when burning more that 1 track (for audio mostly). Example scripts for burning data & audio CD's are also included. The cd ripper program "cdd" is also here in a modified version that can talk to the acd driver. Enjoy and let me know the results... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 10:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00253 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:16:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00235 for ; Fri, 14 Aug 1998 10:16:56 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id NAA105584; Fri, 14 Aug 1998 13:15:57 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808141526.JAA23467@lariat.lariat.org> References: <199808141115.FAA21672@lariat.lariat.org> Date: Fri, 14 Aug 1998 13:19:53 -0400 To: Brett Glass , "B. Richardson" From: Garance A Drosihn Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:22 AM -0600 8/14/98, Brett Glass wrote: > I believe that Linux is already moving to a 64-bit time_t. The BSDs > are behind. Maybe that's why there's resistance here (I can't figure > out any LOGICAL reason for resisting this necessary change.) Just that it's work, and it's work which does not need to be done right this second (so to speak). It will most likely be somewhat disruptive work. Perhaps we should consider it for FreeBSD 4.0, because (IMO) it does seem like a good thing to do "sometime". But right now we have other projects we should concentrate on and finish off (IMO) before opening this one up. (elf, SMP, perl5, softupdates, etc) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 10:26:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01868 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:26:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01863 for ; Fri, 14 Aug 1998 10:26:56 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id KAA13339; Fri, 14 Aug 1998 10:24:58 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808141024.KAA13339@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 10:40:00 CST." <199808141645.KAA24210@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 10:24:57 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 09:24 AM 8/14/98 +0000, Mike Smith wrote: > > >No, so much stuff is written in C because it's a good tool for the job. > > Don't want to get into language wars here, but in case the current rash > of security problems doesn't make it painfully obvious, C isn't a good > tool for ANYTHING. ... which is why it's been a perfectly good tool for the last couple of decades. Language has nothing to do with security, in case it wasn't already plainly obvious. Security is a design issue. -- \\ 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 Aug 14 10:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03320 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:34:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03315 for ; Fri, 14 Aug 1998 10:34:14 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id LAA24664; Fri, 14 Aug 1998 11:33:31 -0600 (MDT) Message-Id: <199808141733.LAA24664@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 11:33:25 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808141024.KAA13339@word.smith.net.au> 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:24 AM 8/14/98 +0000, Mike Smith wrote: >> Don't want to get into language wars here, but in case the current rash >> of security problems doesn't make it painfully obvious, C isn't a good >> tool for ANYTHING. > >... which is why it's been a perfectly good tool for the last couple of >decades. Language has nothing to do with security, in case it wasn't >already plainly obvious. Security is a design issue. Security is also a safety issue. Use safe tools, and you're less likely to create security holes. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 10:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05309 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:44:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05301 for ; Fri, 14 Aug 1998 10:44:06 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id KAA13457; Fri, 14 Aug 1998 10:41:56 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808141041.KAA13457@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 11:33:25 CST." <199808141733.LAA24664@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 10:41:50 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:24 AM 8/14/98 +0000, Mike Smith wrote: > > >> Don't want to get into language wars here, but in case the current rash > >> of security problems doesn't make it painfully obvious, C isn't a good > >> tool for ANYTHING. > > > >... which is why it's been a perfectly good tool for the last couple of > >decades. Language has nothing to do with security, in case it wasn't > >already plainly obvious. Security is a design issue. > > Security is also a safety issue. Use safe tools, and you're less likely > to create security holes. "Safe" is context-sensitive. Safety is not something that can generally be implemented in a language, as it can't know in what context it will be used. C is not "unsafe", it is "not-safe", meaning that you're responsible for your own security. In this it is no less "safe" than any other language as you are a fool if you take the "safety" of any other language on trust. -- \\ 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 Aug 14 10:47:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05728 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:47:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shasta.wstein.com (shasta.wstein.com [206.163.206.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05721 for ; Fri, 14 Aug 1998 10:47:36 -0700 (PDT) (envelope-from joes@shasta.wstein.com) Received: (from joes@localhost) by shasta.wstein.com (8.9.0/8.9.0) id KAA20357; Fri, 14 Aug 1998 10:46:55 -0700 (PDT) From: Joseph Stein Message-Id: <199808141746.KAA20357@shasta.wstein.com> Subject: Re: 64-bit time_t In-Reply-To: <199808141733.LAA24664@lariat.lariat.org> from Brett Glass at "Aug 14, 98 11:33:25 am" To: brett@lariat.org (Brett Glass) Date: Fri, 14 Aug 1998 10:46:55 -0700 (PDT) Cc: mike@smith.net.au, 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 Brett Glass allegedly wrote: > Security is also a safety issue. Use safe tools, and you're less likely > to create security holes. There is no such thing as a "safe" tool. You can write code in assembly language and still end up with security holes. Until someone writes a compiler (for *any* compiled language) that will test for every possible conceivable security holes (volunteers needed...) there will be security holes in *every* application -- that can be fixed when found, using, the "unsafe" tool that was used to create it. My 2c on this issue. -- Joseph Stein; Beaverton, Oregon USA email: joes@wstein.com Finger joes@shasta.wstein.com for contact information and PGP Public Key! Oregon FirePage http://www.ofp.org [OFP-504] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 10:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07679 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:56:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07661 for ; Fri, 14 Aug 1998 10:56:51 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id LAA24900; Fri, 14 Aug 1998 11:56:00 -0600 (MDT) Message-Id: <199808141756.LAA24900@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 11:53:33 -0600 To: Mike Smith From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808141041.KAA13457@word.smith.net.au> 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:41 AM 8/14/98 +0000, Mike Smith wrote: >C is not "unsafe", it is "not-safe", meaning that you're responsible for >your own security. In this it is no less "safe" than any other >language as you are a fool if you take the "safety" of any other >language on trust. Gee, by this reasoning a car without seat belts, a horn, or bumpers is is really no less "safe" than any other car. After all, you're a fool if you trust your car to be safe. I guess I'll remove that pesky blade guard from my circular saw, too. After all, doing that doesn't make the saw any less safe. NOT. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 11:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09265 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:04:30 -0700 (PDT) (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 LAA09245; Fri, 14 Aug 1998 11:04:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17762; Fri, 14 Aug 1998 11:00:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdp17758; Fri Aug 14 18:00:30 1998 Date: Fri, 14 Aug 1998 11:00:27 -0700 (PDT) From: Julian Elischer To: Mark turpin cc: FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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 what's UDF? On Fri, 14 Aug 1998, Mark turpin wrote: > > Is any body working on implementing UDF on FreeBSD? I looked in the > archives and didn't see anything about it? > > > Thanks > > Mark Turpin > > > > 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 Aug 14 11:14:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11477 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:14:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11464 for ; Fri, 14 Aug 1998 11:14:27 -0700 (PDT) (envelope-from Olivier.Galibert@loria.fr) Received: from renaissance.loria.fr (renaissance.loria.fr [152.81.4.102]) by lorraine.loria.fr (8.8.7/8.8.7/8.8.7/JCG) with ESMTP id UAA29887 for ; Fri, 14 Aug 1998 20:12:36 +0200 (MET DST) Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id UAA08971; Fri, 14 Aug 1998 20:12:34 +0200 (MET DST) Message-ID: <19980814201233.A8962@loria.fr> Date: Fri, 14 Aug 1998 20:12:33 +0200 From: Olivier Galibert To: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808141115.FAA21672@lariat.lariat.org> <199808141526.JAA23467@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808141526.JAA23467@lariat.lariat.org>; from Brett Glass on Fri, Aug 14, 1998 at 09:22:45AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 09:22:45AM -0600, Brett Glass wrote: > I believe that Linux is already moving to a 64-bit time_t. The BSDs > are behind. Maybe that's why there's resistance here (I can't figure > out any LOGICAL reason for resisting this necessary change.) I has a far-from-zero cost on 32bits architectures, i.e. everything short of R8000, R10000, alphas and very recent sparcs. Guess why linux still isn't supporting >2Gb files on 32bits achitectures? OG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 11:21:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12341 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:21:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12335 for ; Fri, 14 Aug 1998 11:21:05 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id MAA25200; Fri, 14 Aug 1998 12:20:32 -0600 (MDT) Message-Id: <199808141820.MAA25200@lariat.lariat.org> X-Sender: brett@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 12:20:25 -0600 To: Joseph Stein From: Brett Glass Subject: Re: 64-bit time_t Cc: mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199808141746.KAA20357@shasta.wstein.com> References: <199808141733.LAA24664@lariat.lariat.org> 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:46 AM 8/14/98 -0700, Joseph Stein wrote: >There is no such thing as a "safe" tool. You can write code in assembly >language and still end up with security holes. Of course. Assembly language has even fewer safeguards against shooting oneself in the foot, though in many cases it's easy to spot and prevent problems than it is in C. >Until someone writes a >compiler (for *any* compiled language) that will test for every possible >conceivable security holes (volunteers needed...) there will be security >holes in *every* application -- that can be fixed when found, using, the >"unsafe" tool that was used to create it. This argument (which, again, is often used to justify doing nothing) is analogous to saying, "If it's not absolutely impossible to kill myself in a car under any conditions, there's no point in requiring it to have any basic safety features such as seat belts." My personal opinion is that we, as software professionals, should take a more professional attitude about this. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 11:32:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14833 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:32:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14811; Fri, 14 Aug 1998 11:32:37 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id OAA02613; Fri, 14 Aug 1998 14:32:54 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 14:32:54 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Søren Schmidt cc: FreeBSD current , FreeBSD hackers Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808141707.TAA00337@sos.freebsd.dk> 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 LAA14817 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does this code have a watchdog to prevent ATAPI proccesses from tsleeping forever? (i don't have a burner, but i will test it if does) -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 14 Aug 1998, Søren Schmidt wrote: > > A workable snapshot is available on: > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > >From the README: > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > Please dont distribute this, only use it for testing, as it is > alpha level code which is undergoing rapid changes. > > The main use of this snap is to test the support for ATAPI CD burners, > and the driver has been adapted to the old ATAPI system to serve only > this purpose. > > Both ATAPI CD-R & CD-RW drives are supported, and it has been tested > with a HP7200i and a BTC BCE621E (also sold under the KISS name). > The driver might scribble various messages on the console, but > most should be harmless diagnostics. As always YMMV. > > Install the new driver files new-files.tgz and apply the patches > in sys-diff, make a new entry in your configfile for the new > "acd" atapi device, config & make a new kernel. > > The acd driver uses the same devicemajor as the old wcd driver, so > you can reuse the /dev/*wcd* devices. However if you use DEVFS it > will register itself under the name /dev/*acd*. > > I have includes a modified version of "wormcontrol" that can talk > to the acd driver. It has two new commands "nextwriteable" that > tells the driver the next writeable block on a CDR/CDRW, used when > burning more that 1 track (for audio mostly). > > Example scripts for burning data & audio CD's are also included. > > The cd ripper program "cdd" is also here in a modified version > that can talk to the acd driver. > > Enjoy and let me know the results... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 11:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16088 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:36:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16055; Fri, 14 Aug 1998 11:36:36 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id OAA10077; Fri, 14 Aug 1998 14:37:38 -0400 (EDT) Date: Fri, 14 Aug 1998 14:37:38 -0400 (EDT) From: Mark turpin To: Julian Elischer cc: FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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 Universal Disk Format... It's how DVDs and some CD-Rs store data.. On Fri, 14 Aug 1998, Julian Elischer wrote: > what's UDF? > > > On Fri, 14 Aug 1998, Mark turpin wrote: > > > > > Is any body working on implementing UDF on FreeBSD? I looked in the > > archives and didn't see anything about it? > > > > > > Thanks > > > > Mark Turpin > > > > > > > > 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 Aug 14 11:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20105 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 11:53:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19979; Fri, 14 Aug 1998 11:52:41 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id UAA00605; Fri, 14 Aug 1998 20:50:59 +0200 (CEST) (envelope-from sos) Message-Id: <199808141850.UAA00605@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: from Alfred Perlstein at "Aug 14, 98 02:32:54 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Fri, 14 Aug 1998 20:50:59 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 In reply to Alfred Perlstein who wrote: > does this code have a watchdog to prevent ATAPI proccesses from tsleeping > forever? No, this is only to test ATAPI burners, prober timeout & error handeling is part of the new atapi subsystem, but that is not ready for primetime yet. Why are you especially interested in that ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:02:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22072 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:02:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22039; Fri, 14 Aug 1998 12:02:29 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id PAA02661; Fri, 14 Aug 1998 15:02:44 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 15:02:44 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Søren Schmidt cc: hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808141850.UAA00605@sos.freebsd.dk> 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 MAA22063 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Søren Schmidt wrote: > In reply to Alfred Perlstein who wrote: > > does this code have a watchdog to prevent ATAPI proccesses from tsleeping > > forever? > > No, this is only to test ATAPI burners, prober timeout & error handeling > is part of the new atapi subsystem, but that is not ready for primetime > yet. Why are you especially interested in that ?? uh, why not? it's kinda bad when i run some cdplayer and hit the manual eject or somehow confuse the lame atapi cd-drive and then i have to reboot to use it again. (all processes trying to do anything with it lock in disk activity if i remeber correctly) the problem is in the atapi driver, a call to "reset" mearly sleeps on the atapi device "becoming ready" there is no code to actually reset the device. since i barely understand atapi and i couldn't find any place where the driver actually does a HARD reset i don't know how to actually reset it. perhaps a hard reset on the IDE bus... but that sounds icky. -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Aug 14 12:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23083 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:12:47 -0700 (PDT) (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 MAA23068 for ; Fri, 14 Aug 1998 12:12:43 -0700 (PDT) (envelope-from kaleb@ics.com) Received: from ics.com (kaleb@teapot.ics.com [140.186.40.160]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA29537 Fri, 14 Aug 1998 15:12:14 -0400 (EDT) Message-ID: <35D48ABF.E82E5037@ics.com> Date: Fri, 14 Aug 1998 19:06:39 +0000 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.31 i586) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808141115.FAA21672@lariat.lariat.org> <199808141526.JAA23467@lariat.lariat.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass wrote: > > I believe that Linux is already moving to a 64-bit time_t. Linux isn't exactly known for being stable or easy to develop on, and nobody in the Linux camp has ever shown to my satisfaction that they really appreciate things like source and binary compatibility from one release to the next. > The BSDs > are behind. Maybe that's why there's resistance here (I can't figure > out any LOGICAL reason for resisting this necessary change.) > Because you don't know what things changing it might break? I'm just guessing but I wonder if there wouldn't be less resistance if someone (you?) took it upon your self to setup a system, change time_t to a 64-bit type, build-and-install the whole world, and let everyone know how it went. -- 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 Fri Aug 14 12:34:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26873 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:34:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thought.calbbs.com (thought.calbbs.com [207.71.213.16] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26859 for ; Fri, 14 Aug 1998 12:34:36 -0700 (PDT) (envelope-from brian@wasteland.calbbs.com) Received: from localhost (localhost [127.0.0.1]) by thought.calbbs.com (8.8.8/8.6.12) with SMTP id MAA00324 for ; Fri, 14 Aug 1998 12:34:03 -0700 (PDT) Date: Fri, 14 Aug 1998 12:34:03 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@thought.calbbs.com To: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-Reply-To: <199808141756.LAA24900@lariat.lariat.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 Fri, 14 Aug 1998, Brett Glass wrote: > At 10:41 AM 8/14/98 +0000, Mike Smith wrote: > > >C is not "unsafe", it is "not-safe", meaning that you're responsible for > >your own security. In this it is no less "safe" than any other > >language as you are a fool if you take the "safety" of any other > >language on trust. > > Gee, by this reasoning a car without seat belts, a horn, or bumpers is > is really no less "safe" than any other car. After all, you're a fool if > you trust your car to be safe. A better analogy of a "safe" language would be a car that doesn't go above 35MPH. Sure, you're a little bit safer, but you're wasting a lot of time. Down with inefficient code. -- Brian Buchanan brian@smarter.than.nu Never believe that you know the whole story. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28437 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:40:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28431 for ; Fri, 14 Aug 1998 12:40:44 -0700 (PDT) (envelope-from Olivier.Galibert@loria.fr) Received: from renaissance.loria.fr (renaissance.loria.fr [152.81.4.102]) by lorraine.loria.fr (8.8.7/8.8.7/8.8.7/JCG) with ESMTP id VAA01385 for ; Fri, 14 Aug 1998 21:39:03 +0200 (MET DST) Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id VAA09267; Fri, 14 Aug 1998 21:39:02 +0200 (MET DST) Message-ID: <19980814213902.D9044@loria.fr> Date: Fri, 14 Aug 1998 21:39:02 +0200 From: Olivier Galibert To: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808141733.LAA24664@lariat.lariat.org> <199808141746.KAA20357@shasta.wstein.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808141746.KAA20357@shasta.wstein.com>; from Joseph Stein on Fri, Aug 14, 1998 at 10:46:55AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 10:46:55AM -0700, Joseph Stein wrote: > There is no such thing as a "safe" tool. You can write code in assembly > language and still end up with security holes. Until someone writes a > compiler (for *any* compiled language) that will test for every possible > conceivable security holes (volunteers needed...) there will be security > holes in *every* application -- that can be fixed when found, using, the > "unsafe" tool that was used to create it. There are safe tools. They are called "formal languages" or "formal methods" and combine the power of strictly specified programming languages and mathematical provers. Writing something like sendmail of telnetd with what currently exists is out of the picture, but they already are used to prove sections of life-critical code. Just a matter of time. OG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28541 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:41:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA28536 for ; Fri, 14 Aug 1998 12:41:48 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z7Pil-0006TU-00; Fri, 14 Aug 1998 13:41:07 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA16592; Fri, 14 Aug 1998 13:43:05 -0600 (MDT) Message-Id: <199808141943.NAA16592@harmony.village.org> To: Olivier Galibert Subject: Re: 64-bit time_t Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 14 Aug 1998 20:12:33 +0200." <19980814201233.A8962@loria.fr> References: <19980814201233.A8962@loria.fr> <199808141115.FAA21672@lariat.lariat.org> <199808141526.JAA23467@lariat.lariat.org> Date: Fri, 14 Aug 1998 13:43:04 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980814201233.A8962@loria.fr> Olivier Galibert writes: : I has a far-from-zero cost on 32bits architectures, i.e. everything : short of R8000, R10000, alphas and very recent sparcs. The R4000 and R5000 (both of which implement MIPS III) are 64 bit as well. They have 64 bit instructions[*] and registers. While it is true that there is a cost associated with snagging bits from memory or squirting it back to memory, the cache tends to mitigate these effects somewhat. Warner [*] Meaning instructions that operate on 64 bit quantities. These are available even in 32-bit address-mode. The n32 api makes use of this to give you everything you could want from n64, without the bloat of pointers 2x in size. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:42:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28695 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:42:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28690 for ; Fri, 14 Aug 1998 12:42:18 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id NAA26781; Fri, 14 Aug 1998 13:41:07 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Fri, 14 Aug 1998 13:41:07 -0600 (MDT) From: Brett Taylor To: Karl Denninger cc: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris is free. In-Reply-To: <19980813222024.27227@mcs.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 On Thu, 13 Aug 1998, Karl Denninger wrote: > I can't find KDE in the X11 ports tree....... /usr/ports/x11/kdebase Note the huge number of dependencies so it's not likely to be a quick install. Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ "There is something uncanny in the noiseless rush of the cyclist, as he comes into view, passes by, and disappears." - Popular Science, 1891 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29646 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:46:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29637 for ; Fri, 14 Aug 1998 12:46:34 -0700 (PDT) (envelope-from Olivier.Galibert@loria.fr) Received: from renaissance.loria.fr (renaissance.loria.fr [152.81.4.102]) by lorraine.loria.fr (8.8.7/8.8.7/8.8.7/JCG) with ESMTP id VAA01524; Fri, 14 Aug 1998 21:44:45 +0200 (MET DST) Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id VAA09282; Fri, 14 Aug 1998 21:44:41 +0200 (MET DST) Message-ID: <19980814214441.A9271@loria.fr> Date: Fri, 14 Aug 1998 21:44:41 +0200 From: Olivier Galibert To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <19980814201233.A8962@loria.fr> <199808141115.FAA21672@lariat.lariat.org> <199808141526.JAA23467@lariat.lariat.org> <19980814201233.A8962@loria.fr> <199808141943.NAA16592@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808141943.NAA16592@harmony.village.org>; from Warner Losh on Fri, Aug 14, 1998 at 01:43:04PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 01:43:04PM -0600, Warner Losh wrote: > The R4000 and R5000 (both of which implement MIPS III) are 64 bit as > well. They have 64 bit instructions[*] and registers. Actually, not all R4K. But anyway, "definitively not x86" was the point ;-) > While it is > true that there is a cost associated with snagging bits from memory or > squirting it back to memory, the cache tends to mitigate these effects > somewhat. What's really costly in terms of instructions and register pressure is 64-bits arithmetic on 32-bits architectures. OG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 12:48:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29902 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 12:48:42 -0700 (PDT) (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 MAA29879 for ; Fri, 14 Aug 1998 12:48:32 -0700 (PDT) (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 MAA21378; Fri, 14 Aug 1998 12:45:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Brett Glass , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 10:41:50 -0000." <199808141041.KAA13457@word.smith.net.au> Date: Fri, 14 Aug 1998 12:45:15 -0700 Message-ID: <21374.903123915@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike: *whack*, do not *whack*, argue with the Brett *whack*. You know what happens when you or anyone else argues with the Brett! Brett: *whack*, see *whack* my private *whack* missive to you about *whack* knowing when to shut up! Thank you! Enough of this evil, tired thread in -hackers; we've been here already and it accomplished just as little last time. Let's move on to religion, politics and civil liberties already! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 13:30:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08066 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 13:30:31 -0700 (PDT) (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 NAA08061 for ; Fri, 14 Aug 1998 13:30:28 -0700 (PDT) (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 OAA29139; Fri, 14 Aug 1998 14:29:52 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA23942; Fri, 14 Aug 1998 14:29:50 -0600 Date: Fri, 14 Aug 1998 14:29:50 -0600 Message-Id: <199808142029.OAA23942@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brett Glass Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-Reply-To: <199808141756.LAA24900@lariat.lariat.org> References: <199808141041.KAA13457@word.smith.net.au> <199808141756.LAA24900@lariat.lariat.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >C is not "unsafe", it is "not-safe", meaning that you're responsible for > >your own security. In this it is no less "safe" than any other > >language as you are a fool if you take the "safety" of any other > >language on trust. > > Gee, by this reasoning a car without seat belts, a horn, or bumpers is > is really no less "safe" than any other car. After all, you're a fool if > you trust your car to be safe. You are. I can kill people if I'm not careful driving a car. The tool is the not the problem, the person who improperly wields the tool is. (ie; guns don't kill people, people kill people...) The reason for most of the safety precautions on tools today is because of how sue-crazy Americans are. You have to put disclaimers on things because people use lawn-mowers to mow their hedges and other such stupidity, and then when the mower falls and cuts of their fingers they succuessfully sue the manufacturer for not making it safe. It's really no more safe than it was, but it prevents the manufacturer from losing their shorts in a lawsuit. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 14:03:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13353 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 14:03:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sequoia.lituus.fr ([193.252.217.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13348 for ; Fri, 14 Aug 1998 14:03:21 -0700 (PDT) (envelope-from root@smtp.wanadoo.fr) Received: (from root@localhost) by sequoia.lituus.fr (8.9.1/8.8.8) id WAA00702; Fri, 14 Aug 1998 22:59:05 +0200 (CEST) (envelope-from root) Date: Fri, 14 Aug 1998 22:59:05 +0200 (CEST) Message-Id: <199808142059.WAA00702@sequoia.lituus.fr> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Subject: Re: UDF Filesystem In-Reply-To: References: X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > what's UDF? > > > On Fri, 14 Aug 1998, Mark turpin wrote: > > > > > Is any body working on implementing UDF on FreeBSD? I looked in the > > archives and didn't see anything about it? > > > > > > Thanks > > > > Mark Turpin > > > > > > It seems that UDF is that : UDF, Universal Disk Format, is the file system used by DVD disks and players. (found on http://www.softarch.com/us/products.services/newthings.html). Stephane Legrand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 14:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17061 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 14:33:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17054 for ; Fri, 14 Aug 1998 14:33:50 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id PAA27018; Fri, 14 Aug 1998 15:33:14 -0600 (MDT) Message-Id: <199808142133.PAA27018@lariat.lariat.org> X-Sender: brett@127.0.0.1 (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Fri, 14 Aug 1998 15:32:59 -0600 To: Nate Williams From: Brett Glass Subject: Re: 64-bit time_t Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199808142029.OAA23942@mt.sri.com> References: <199808141756.LAA24900@lariat.lariat.org> <199808141041.KAA13457@word.smith.net.au> <199808141756.LAA24900@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please send future responses off-list, please, in consideration of Jordan's request. At 02:29 PM 8/14/98 -0600, Nate Williams wrote: >The reason for most of the safety precautions on tools today is because >of how sue-crazy Americans are. You have to put disclaimers on things >because people use lawn-mowers to mow their hedges and other such >stupidity, and then when the mower falls and cuts of their fingers they >succuessfully sue the manufacturer for not making it safe. > >It's really no more safe than it was, but it prevents the manufacturer >from losing their shorts in a lawsuit. The blade guard on a circular saw does not fall into that category, as any experienced carpenter can tell you. Nor do seat belts, air bags, bumpers, or child seats. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 14:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19164 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 14:46:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19132 for ; Fri, 14 Aug 1998 14:46:53 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id RAA08962; Fri, 14 Aug 1998 17:46:52 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 17:46:52 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Nick Johnson cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: perl 5 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 (some people's effort to get perl5 into 3.0) one thing i have no clue on how to find out is if FreeBSD can do secure setuid scripts. can it? -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 14 Aug 1998, Nick Johnson wrote: > It seems like bsd.man.mk shouldn't have to do anything with those > module::foo pages; I thought perldoc handled reading those. Maybe I'm > confusing things though. > > So /usr/src/contrib/perl needs to look essentially identical to what you > get when you untar a virgin perl tarball, and this makefile needs to > handle making whatever patches are necessary as it goes without changing > anything in /usr/src/contrib/perl, eh? > > Nick > > On Fri, 14 Aug 1998, Jordan K. Hubbard wrote: > > > It needs to be berkeley make'd, which someone did partially but never > > finished (do a PR search for perl5) - they polluted the contrib > > portion by not running configure over it as a 2nd stage (you want the > > _pure_ sources going into /usr/src/contrib, not modified stuff) and > > they punted on installing all the module::foo man pages because > > bsd.man.mk has problems with ::'s. That needs to be fixed too, as > > part of bringing perl5 in by default. > > > > - Jordan > > > > > Al (brightmn) and I have been discussing perl5 being the default perl in a > > > future FreeBSD release; what could keep this from happening? The last > > > perl 5 build I did went flawlessly and passed all of the self tests. I've > > > also been looking into the standard distribution perl scripts (which, > > > whereis, adduser, etc) and it is taking very minimal effort to make them > > > run in perl 5 without errors or warnings in strict mode. > > > > > > What do you suggest? > > > > > > Nick > > > > > > -- > > > The hardest thing in the world to understand is the income tax. > > > -- Albert Einstein > > > My PGP public key: http://www.spatula.net/pubkey.txt > > > Nick Johnson, version 1.3 http://www.spatula.net/ > > > > > > > -- > "A woman's place is in the cellar." > My PGP public key: http://www.spatula.net/pubkey.txt > Nick Johnson, version 1.3 http://www.spatula.net/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 15:15:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25828 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 15:15:06 -0700 (PDT) (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 PAA25720; Fri, 14 Aug 1998 15:14:38 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA06086; Fri, 14 Aug 1998 15:14:06 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd006051; Fri Aug 14 15:14:04 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA21199; Fri, 14 Aug 1998 15:14:02 -0700 (MST) From: Terry Lambert Message-Id: <199808142214.PAA21199@usr04.primenet.com> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: sos@FreeBSD.ORG Date: Fri, 14 Aug 1998 22:14:02 +0000 (GMT) Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199808141707.TAA00337@sos.freebsd.dk> from "S?ren Schmidt" at Aug 14, 98 07:07:06 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A workable snapshot is available on: > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > From the README: > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > Please dont distribute this, only use it for testing, as it is > alpha level code which is undergoing rapid changes. I didn't see CAM in there; are you making it fit under CAM? NetBSD has unified their device model this wat, with apparently good results... 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 Fri Aug 14 15:22:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28174 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 15:22:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (gyndine-74.mdm.mke.execpc.com [169.207.83.74]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28013 for ; Fri, 14 Aug 1998 15:22:02 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199808142222.PAA28013@hub.freebsd.org> Received: (qmail 11071 invoked from network); 14 Aug 1998 17:24:33 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 14 Aug 1998 17:24:33 -0500 To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG, chat@FreeBSD.ORG Reply-To: chat@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "Fri, 14 Aug 1998 10:40:00 MDT." <199808141645.KAA24210@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 17:24:33 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ redirected to -chat ] In message <199808141645.KAA24210@lariat.lariat.org>, Brett Glass wrote: } At 09:24 AM 8/14/98 +0000, Mike Smith wrote: } } >No, so much stuff is written in C because it's a good tool for the job. } } Don't want to get into language wars here, but in case the current rash } of security problems doesn't make it painfully obvious, C isn't a good } tool for ANYTHING. Oh, look, it's Brett spewing hyperbole. You can make the argument that C isn't a good tool for security critical code (though even that position is somewhat weak), but even if we accept that proposition, that doesn't make it a poor tool for non security critical code. Do you wear a chin pad to protect yourself from that knee jerking wildly all the time? -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 15:34:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01714 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 15:34:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts02-002.dublin.indigo.ie [194.125.134.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01487; Fri, 14 Aug 1998 15:33:49 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id XAA01501; Fri, 14 Aug 1998 23:27:40 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808142227.XAA01501@indigo.ie> Date: Fri, 14 Aug 1998 23:27:39 +0000 In-Reply-To: <199808132123.OAA16645@usr09.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Terry Lambert , jmb@FreeBSD.ORG (Jonathan M. Bresler) Subject: Re: lists dead? Cc: terry@lambert.org, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 13, 9:23pm, Terry Lambert wrote: } Subject: Re: lists dead? > > Terry, > > i you need to test the lists subscribe and send mail to > > test@freebsd.org. not the regular lists. this message > > now appears in the archives ;( > > > > repeated offensees are a reason to be removed from the lists > > ;((( > > Unfortunately, there's no way to bail out of a "DATA" command. ^]q? Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 15:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04053 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 15:42:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03865; Fri, 14 Aug 1998 15:41:51 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199808142241.PAA03865@hub.freebsd.org> Subject: Re: lists dead? In-Reply-To: <199808132123.OAA16645@usr09.primenet.com> from Terry Lambert at "Aug 13, 98 09:23:32 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 14 Aug 1998 15:41:41 -0700 (PDT) Cc: jmb@FreeBSD.ORG, terry@lambert.org, 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 Terry Lambert wrote: > > Terry, > > i you need to test the lists subscribe and send mail to > > test@freebsd.org. not the regular lists. this message > > now appears in the archives ;( > > > > repeated offensees are a reason to be removed from the lists > > ;((( > > Unfortunately, there's no way to bail out of a "DATA" command. > > I expected to get a response other than "250 Message accepted for delivery". but your honor, once i plugged the trigger there was no way to recall the bullet even asked the manufacturer. > > Sorry about that... there should be a better way of testing whether > a message will be sent than actually sending one. > > Does the "test" address have an autoresponder? Is it backed by the > Majordomo code that backs the lists? If so, I guess it's as good as > any a method of doing the half-pipe test that I used to accidently > send that message. the very same software. its just another majordomo list. thats why its so useful for testing.....the configuration is soooooo similar. ;) > > What was the problem, BTW? 8-(. > dont know you are the only one to have mentioned a problem. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 15:54:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07370 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 15:54:59 -0700 (PDT) (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 PAA07351 for ; Fri, 14 Aug 1998 15:54:48 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA22464; Fri, 14 Aug 1998 15:54:10 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd022435; Fri Aug 14 15:54:09 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA23086; Fri, 14 Aug 1998 15:54:03 -0700 (MST) From: Terry Lambert Message-Id: <199808142254.PAA23086@usr04.primenet.com> Subject: Re: 64-bit time_t To: mike@smith.net.au (Mike Smith) Date: Fri, 14 Aug 1998 22:54:03 +0000 (GMT) Cc: brett@lariat.org, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199808132325.XAA00422@word.smith.net.au> from "Mike Smith" at Aug 13, 98 11:25:09 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > time_t is too imprecise for many things (hence struct > timeval) and too limited in range for others (eg. your application). Until 2039. Then it becomes far less limited in range, and thus suitable for his application... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 16:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09097 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 16:03:57 -0700 (PDT) (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 QAA09087 for ; Fri, 14 Aug 1998 16:03:54 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA25645; Fri, 14 Aug 1998 16:03:23 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd025607; Fri Aug 14 16:03:16 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA23463; Fri, 14 Aug 1998 16:03:15 -0700 (MST) From: Terry Lambert Message-Id: <199808142303.QAA23463@usr04.primenet.com> Subject: Re: 64-bit time_t To: mph@pobox.com (Matthew Hunt) Date: Fri, 14 Aug 1998 23:03:14 +0000 (GMT) Cc: brawley@camtech.com.au, hackers@FreeBSD.ORG In-Reply-To: <19980814000605.A25012@astro.psu.edu> from "Matthew Hunt" at Aug 14, 98 00:06: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 > > Question: What is wrong with using an unsigned long for time_t, instead of > > long (which is then assumed signed). > > man 3 time: > > Upon successful completion, time() returns the value of time. Otherwise > a value of ((time_t) -1) is returned and the global variable errno is set > to indicate the error. See also: http://www.eunet.pt/ano2000/sun/sup_sun5.htm Negative values are (potentially) abused for dates back to December 13th, 1901. 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 Fri Aug 14 16:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14566 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 16:33:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14545 for ; Fri, 14 Aug 1998 16:33:32 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-20.HiWAAY.net [208.147.148.20]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id SAA15845 for ; Fri, 14 Aug 1998 18:33:00 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id SAA17855 for ; Fri, 14 Aug 1998 18:17:10 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199808142317.SAA17855@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: solaris is free. In-reply-to: Message from Zach Heilig of "Thu, 13 Aug 1998 23:47:30 CDT." <19980813234730.A1133@znh.org.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 18:17:10 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zach Heilig writes: > On Thu, Aug 13, 1998 at 10:20:24PM -0500, Karl Denninger wrote: > > I can't find KDE in the X11 ports tree....... > > $ grep ^kde /usr/ports/INDEX > kdemultimedia-1.0|/usr/ports/audio/kdemultimedia|... > kdesupport-1.0|/usr/ports/converters/kdesupport|... Better yet: % cd /usr/ports % make search key=KDE | more -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 16:39:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15588 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 16:39:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15489; Fri, 14 Aug 1998 16:38:41 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA03368; Fri, 14 Aug 1998 19:38:08 -0400 (EDT) Date: Fri, 14 Aug 1998 19:38:08 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Mark turpin cc: Julian Elischer , FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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, 14 Aug 1998, Mark turpin wrote: > Universal Disk Format... It's how DVDs and some CD-Rs store data.. Whatever happened to ISO9660? Or is this a superset thereof? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 17:08:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20560 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 17:08:38 -0700 (PDT) (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 RAA20531 for ; Fri, 14 Aug 1998 17:08:25 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA19649; Fri, 14 Aug 1998 17:07:52 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd019603; Fri Aug 14 17:07:45 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA28867; Fri, 14 Aug 1998 17:07:41 -0700 (MST) From: Terry Lambert Message-Id: <199808150007.RAA28867@usr04.primenet.com> Subject: Re: 64-bit time_t To: drosih@rpi.edu (Garance A Drosihn) Date: Sat, 15 Aug 1998 00:07:41 +0000 (GMT) Cc: brett@lariat.org, rabtter@aye.net, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: from "Garance A Drosihn" at Aug 14, 98 01:19:53 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 believe that Linux is already moving to a 64-bit time_t. The BSDs > > are behind. Maybe that's why there's resistance here (I can't figure > > out any LOGICAL reason for resisting this necessary change.) > > Just that it's work, and it's work which does not need to be done > right this second (so to speak). It will most likely be somewhat > disruptive work. Perhaps we should consider it for FreeBSD 4.0, > because (IMO) it does seem like a good thing to do "sometime". > But right now we have other projects we should concentrate on and > finish off (IMO) before opening this one up. > > (elf, SMP, perl5, softupdates, etc) The FS is going to be worst, mostly because of the quota code and some ill-considered changes which used up the spare fields. The quota code is broken (struct dqblk has no spaces in it). But the quota code needs to become a stacking layer anyway. The ufsmount struct is broken (in the quota code), but it's not an on-disk structure, so it doesn't need to change. The fs_time field in struct fs is broken, but the purpose of the last written time is to avoid the AppleTalk polling refresh, so it can be deprecated out as an int32_t "spare" field, and the real thing can be kept in the in core data fields that are never written out. If you need to keep it on disk (why?), then you can steal two of the adjacent 32 bit long fields that can be calculated from the other fields at mount time, and themselves kept incore instead. The struct cg and ocg cg_time field is a bit sticky. Probably it would be best to spare it out and take two adjacent 32 bit fields from cg_sparecon (which is 13 32 bit fields long and reserved for future use). This will only work for cg, not ocg. cg_cgx could be overridden, and abused as half of the time_t, since you could calculate this value as well. It's even in the right place for the byte order. Unless there is a pressing use for the struct fs/struct cg/struct ocg values except for them to monotonically increment (note: *not* "increase"), then it might even be worthwhile to just mask the low 32 bits from the time_t. Which leaves us with the non-POSIX struct timespec, which ate our beloved spare longs which were put there for expanding time_t in the year 2038, and stolen by some nasty person to store useless nanoseconds (breaking stat's Y2039 compliance at the same time). Back out the timespec crap, and the FS should be easily convertable, leaving only the issues that Sun was kind enough to document for us: http://www.sun.com/y2000/strategy.html 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 Fri Aug 14 17:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21648 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 17:14:28 -0700 (PDT) (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 RAA21636 for ; Fri, 14 Aug 1998 17:14:22 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA02398; Fri, 14 Aug 1998 17:13:50 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd002368; Fri Aug 14 17:13:42 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA29219; Fri, 14 Aug 1998 17:13:39 -0700 (MST) From: Terry Lambert Message-Id: <199808150013.RAA29219@usr04.primenet.com> Subject: Re: 64-bit time_t To: joes@shasta.wstein.com (Joseph Stein) Date: Sat, 15 Aug 1998 00:13:39 +0000 (GMT) Cc: brett@lariat.org, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199808141746.KAA20357@shasta.wstein.com> from "Joseph Stein" at Aug 14, 98 10:46:55 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 > > Security is also a safety issue. Use safe tools, and you're less likely > > to create security holes. > > There is no such thing as a "safe" tool. You can write code in assembly > language and still end up with security holes. Until someone writes a > compiler (for *any* compiled language) that will test for every possible > conceivable security holes (volunteers needed...) there will be security > holes in *every* application -- that can be fixed when found, using, the > "unsafe" tool that was used to create it. > > My 2c on this issue. There is a branch path analysis tool in the comp.sources archives which will generate full code coverage tests. It was written as an example of the utility of the object oriented programming model used by C++. Unfortunately, it doesn't work on ANSI C, so you would have to remove the ANSI-isms that have crept into the FreeBSD kernel, or you would have to fix the tool. The tool is not Grammar based, so fixing it would be a bitch. Rewriting it would require a strong mathematical programmer (but I'm busy right now, and all my code that is in C is K&R compilable, unless it's the result of me maintaining already ANSI code). 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 Fri Aug 14 17:24:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22960 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 17:24:23 -0700 (PDT) (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 RAA22947; Fri, 14 Aug 1998 17:24:11 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA24149; Fri, 14 Aug 1998 17:23:39 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd024105; Fri Aug 14 17:23:29 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA29712; Fri, 14 Aug 1998 17:23:26 -0700 (MST) From: Terry Lambert Message-Id: <199808150023.RAA29712@usr04.primenet.com> Subject: Re: lists dead? To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Sat, 15 Aug 1998 00:23:26 +0000 (GMT) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <199808142241.PAA03865@hub.freebsd.org> from "Jonathan M. Bresler" at Aug 14, 98 03:41:41 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 > > Does the "test" address have an autoresponder? Is it backed by the > > Majordomo code that backs the lists? If so, I guess it's as good as > > any a method of doing the half-pipe test that I used to accidently > > send that message. > > the very same software. its just another majordomo list. > thats why its so useful for testing.....the configuration > is soooooo similar. ;) 8-). > > What was the problem, BTW? 8-(. > > dont know you are the only one to have mentioned a problem. Julian and I both noticed a 6 hour or so famine of traffic. Julian logged into hub, and there were sendmails running, but nothing was coming out. Alternet was losing about 30% of all packets sent through it that day as well, but neither of our mailboxes are that poorly connected that we didn't see packets going through in both directions. Anyway, it's cleared up now. Just in time_t. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 17:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23600 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 17:27:49 -0700 (PDT) (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 RAA23584 for ; Fri, 14 Aug 1998 17:27:46 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA05409; Fri, 14 Aug 1998 17:27:15 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd005393; Fri Aug 14 17:27:12 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA29950; Fri, 14 Aug 1998 17:27:10 -0700 (MST) From: Terry Lambert Message-Id: <199808150027.RAA29950@usr04.primenet.com> Subject: Re: lists dead? To: rotel@indigo.ie Date: Sat, 15 Aug 1998 00:27:09 +0000 (GMT) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <199808142227.XAA01501@indigo.ie> from "Niall Smart" at Aug 14, 98 11:27:39 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 > > Unfortunately, there's no way to bail out of a "DATA" command. > > ^]q? But then it wouldn't have given me the "421 out of disk space" error I was expecting to get... 8-). Using the test list is the way to go; I just wasn't sure it was the same configuration, and not just an alias (or even a vacation mailbox) with no utility other than a "hub ping". Now I know and I won't do stupid things like that in the future. 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 Fri Aug 14 18:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28858 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 18:11:47 -0700 (PDT) (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 SAA28849 for ; Fri, 14 Aug 1998 18:11:44 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA15877; Fri, 14 Aug 1998 18:11:10 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd015853; Fri Aug 14 18:11:04 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA02595; Fri, 14 Aug 1998 18:11:01 -0700 (MST) From: Terry Lambert Message-Id: <199808150111.SAA02595@usr04.primenet.com> Subject: Re: developing device drivers To: hm@kts.org Date: Sat, 15 Aug 1998 01:11:00 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Hellmuth Michaelis" at Aug 14, 98 08:41:55 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 > > You probe and attach at load time, normally. This means you detect the > > IRQ/DRQ/IOBase/MemBase/Etc., not assign it. > > I don't quite understand, sorry. > > Given an ISA card, supporting IRQ's 3..15, i/o 0x100...0x300 and mem 0xa0000 > ...0dffff. > > What i was looking for in the first place was something like > > modload -I -O -M .... > > to specify the same parameters i'd have to specify in the kernel config file. > > When i probe at load time, i try to detect the card in question, but where > shall i start to search without knowing _where_ to search (iobase/membase) > (other than searching through the whole supported iobase/membase) ? > > Given i found the card to be the one i looked for, which of the > IRQ/iobase/mem supports shall i use in the attach ? How is the user to > be able to specify the parameters he prefers ? In general, the answer is that the modload can't communicate this information to the driver. The problem here is that there may, in fact, be a large amount data to communicate, and there's no agreement between the driver and the lkm device about how to marshall this data, or even what data to marshall, across /dev/lkm; or in fact, what code you would have to put in the driver to "catch" the data. So modload would not know where to begin to get this data into the device in a useful way. On top of this, it is generally undesirable to have to communicate this information from the hardware, through a human, to the driver; doing this has really bad consequences when you attempt to dike the human out of the picture and have the driver demand-loaded into the kernel. Especially if the driver is needed for booting, and the kernel pulls it out of an mfs, for example. The best answer is that the driver needs to be able to find its hardware. If this is impossible, and the only way it is physically possible to detect the hardware is either through a destructive probe that may render the machine unstable, or through a human telling the driver where the hardware is, *AND* the human can't edit a config.h header and recompile the driver (lacking one of source, tools, or brains), then you have several options: 1) Supply the information in a seperate "config.c", which the user compiles, and then uses "ld -r" to make a single object file, which is then used for the modload. The only requirement for a module is that it reside in a single object file; a module need not reside in a single compilation unit (in fact, modload depends on this being true). I call this the easy approach. 2) Make the probe do nothing and make the attach create a pseudo-device instead. Supply a user space program that the user runs to configure the driver in a device-specific way, communicating the configuration via ioctl()'s over the pseudo device (this is how the LKM system started life: as a linkable device driver on an SVR3.2 system that let me twiddle kernel structures, mostly because gcc of the day didn't support PIC code until Jeffrey Hsu added it). The last act of this user space program would be to say "become the real device when I close you". I call this the Pinnochio approach. 3) Use a configuration file, and use kernel level file I/O to retrieve the information from the file at driver load time. The easiest, safest, least error-prone way to do this is to use the PCMCIA configuration interface, which has already done all of the device classification and file I/O for you, and wrapped it in a nice (well, an OK) API. I call this the leech approach. Obviously, it would be better if your device had a ROM associated with it, and you usesd the kernel md5 to see if it was the ROM for your device, and then probe it safely from there. If the reason you can't probe the device is lack of information, your best bet is to take the DOS/Windows drivers that devices without programming information inevitably come with, and have a friend in a country with mostly sane ideas of intellectual property law not equalling a God-given right to not sell products on equal terms regardless of who is buying them, like Germany, run a copy of "Sourcer" from V Communications, Inc. (this is Frank van Gilluwe's, author of _The Undocumented PC_, company) on the driver for the purpose of documenting the hardware interface. Which puts you back in the ballpark for the best approach: the driver needs to be able to find its hardware. 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 Fri Aug 14 19:23:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04803 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 19:23:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04796; Fri, 14 Aug 1998 19:23:32 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-121.camalott.com [208.229.74.121]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id VAA15048; Fri, 14 Aug 1998 21:24:25 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id VAA03399; Fri, 14 Aug 1998 21:22:03 -0500 (CDT) (envelope-from joelh) Date: Fri, 14 Aug 1998 21:22:03 -0500 (CDT) Message-Id: <199808150222.VAA03399@detlev.UUCP> To: rotel@indigo.ie CC: tlambert@primenet.com, jmb@FreeBSD.ORG, terry@lambert.org, hackers@FreeBSD.ORG In-reply-to: <199808142227.XAA01501@indigo.ie> (message from Niall Smart on Fri, 14 Aug 1998 23:27:39 +0000) Subject: Re: lists dead? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808142227.XAA01501@indigo.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> i you need to test the lists subscribe and send mail to >>> test@freebsd.org. not the regular lists. this message >>> now appears in the archives ;( >> Unfortunately, there's no way to bail out of a "DATA" command. > ^]q? Add X-Loop: to the headers? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 14 19:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05695 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 19:35:40 -0700 (PDT) (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 TAA05685 for ; Fri, 14 Aug 1998 19:35:37 -0700 (PDT) (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 MAA06416; Sat, 15 Aug 1998 12:05:00 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA21751; Sat, 15 Aug 1998 12:04:46 +0930 (CST) Message-ID: <19980815120445.C21662@lemis.com> Date: Sat, 15 Aug 1998 12:04:45 +0930 From: Greg Lehey To: Tim Vanderhoek , Matthew Hunt , Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> <19980814135919.U1921@freebie.lemis.com> <19980814114525.B4001@zappo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19980814114525.B4001@zappo>; from Tim Vanderhoek on Fri, Aug 14, 1998 at 11:45:25AM -0400 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, 14 August 1998 at 11:45:25 -0400, Tim Vanderhoek wrote: > On Fri, Aug 14, 1998 at 01:59:19PM +0930, Greg Lehey wrote: >> >> More to the point, time_t *can* be used to represent BE (Before Epoch) >> dates. Make it unsigned and you break that. > > "time_t is a format for the system current time. As such, you're > abusing it mightily if you expect it to be a general-purpose time > value." - Mike Smith Yes, I read that. That doesn't mean that I agree with it. I don't. But even if it were true, it wouldn't be a valid argument. One problem UNIX has is that there is no standardized format for representing times. There is no sensible reason to use one format for representing system times, one (inconvenient) format for representing times more accurately (down to only 1 microsecond, when it could have been down to a nanosecond), and one format broken down into representations of the individual units of time. None are of any use when I want to know "How many seconds has it been since my grandfather was born?". time_t *will* answer the question "How many seconds has it been since my father was born?". Moving to 64 bits creates a number of opportunities to improve this situation: 1. Make it an extended time_t and you can measure time from before the big bang until after the predicted collapse of the universe. 2. Make it a merged struct timeval (i.e. tv_usec + 1000000 * tv_sec) and you have a *useful* replacement for both time_t and struct timeval which will still measure time from before the beginning of recorded history to at least the release of FreeBSD 3.0. 3. Make it (2) * 1000 and base it on the year 2000 (just to rub it in) and you can measure time to the nearest nanosecond from 1708 to 2292. Of course, for this to make *any* sense at all, it should be a format that everybody accepts. Otherwise we've just made the matter worse. 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 Aug 14 20:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08021 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 20:08:24 -0700 (PDT) (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 UAA08009 for ; Fri, 14 Aug 1998 20:08:19 -0700 (PDT) (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 MAA11033; Sat, 15 Aug 1998 12:37:48 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA21794; Sat, 15 Aug 1998 12:37:49 +0930 (CST) Message-ID: <19980815123748.E21662@lemis.com> Date: Sat, 15 Aug 1998 12:37:48 +0930 From: Greg Lehey To: Alfred Perlstein , poipoi@famipow.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: solaris smp management References: <19980814063439.175.qmail@hwi.poi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Fri, Aug 14, 1998 at 12:23: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 On Friday, 14 August 1998 at 12:23:35 -0500, Alfred Perlstein wrote: > it isn't an "algorithm" rather a total restructuring of the kernel. > freebsd wouldn't be "BSD" anymore if it adopted the same path as sun. > > that's why there is no more "sunos" just solaris, sunos was a BSD > kernel, while solaris was a resturctured blend of BSD and SRV4. Well, not quite. SunOS 1 to 4 were a BSD kernel, SunOS 5 is an SVR4 kernel. Solaris 1 includes SunOS4, and Solaris 2 includes SunOS 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 Fri Aug 14 20:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10534 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 20:48:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10513 for ; Fri, 14 Aug 1998 20:48:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-114.camalott.com [208.229.74.114]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA20472; Fri, 14 Aug 1998 22:48:17 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA03794; Fri, 14 Aug 1998 22:45:39 -0500 (CDT) (envelope-from joelh) Date: Fri, 14 Aug 1998 22:45:39 -0500 (CDT) Message-Id: <199808150345.WAA03794@detlev.UUCP> To: grog@lemis.com CC: bright@www.hotjobs.com, poipoi@famipow.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <19980815123748.E21662@lemis.com> (message from Greg Lehey on Sat, 15 Aug 1998 12:37:48 +0930) Subject: Re: solaris smp management From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <19980814063439.175.qmail@hwi.poi.org> <19980815123748.E21662@lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> it isn't an "algorithm" rather a total restructuring of the kernel. >> freebsd wouldn't be "BSD" anymore if it adopted the same path as sun. >> that's why there is no more "sunos" just solaris, sunos was a BSD >> kernel, while solaris was a resturctured blend of BSD and SRV4. > Well, not quite. SunOS 1 to 4 were a BSD kernel, SunOS 5 is an SVR4 > kernel. Solaris 1 includes SunOS4, and Solaris 2 includes SunOS 5. I thought that the name "Solaris 1" was a retcon. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan 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 Aug 14 20:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11026 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 20:52:15 -0700 (PDT) (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 UAA11021 for ; Fri, 14 Aug 1998 20:52:12 -0700 (PDT) (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 NAA19220; Sat, 15 Aug 1998 13:21:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA21885; Sat, 15 Aug 1998 13:21:02 +0930 (CST) Message-ID: <19980815132102.A21880@freebie.lemis.com> Date: Sat, 15 Aug 1998 13:21:02 +0930 From: Greg Lehey To: joelh@gnu.org Cc: bright@www.hotjobs.com, poipoi@famipow.com, freebsd-hackers@FreeBSD.ORG Subject: Re: solaris smp management References: <19980814063439.175.qmail@hwi.poi.org> <19980815123748.E21662@lemis.com> <199808150345.WAA03794@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808150345.WAA03794@detlev.UUCP>; from Joel Ray Holveck on Fri, Aug 14, 1998 at 10:45:39PM -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 On Friday, 14 August 1998 at 22:45:39 -0500, Joel Ray Holveck wrote: >>> it isn't an "algorithm" rather a total restructuring of the kernel. >>> freebsd wouldn't be "BSD" anymore if it adopted the same path as sun. >>> that's why there is no more "sunos" just solaris, sunos was a BSD >>> kernel, while solaris was a resturctured blend of BSD and SRV4. >> Well, not quite. SunOS 1 to 4 were a BSD kernel, SunOS 5 is an SVR4 >> kernel. Solaris 1 includes SunOS4, and Solaris 2 includes SunOS 5. > > I thought that the name "Solaris 1" was a retcon. May be. But they introduced Solaris as a term which was much broader than SunOS, and they still use SunOS. 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 Aug 14 23:30:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26063 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 23:30:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26027; Fri, 14 Aug 1998 23:29:48 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id IAA03408; Sat, 15 Aug 1998 08:25:14 +0200 (CEST) (envelope-from sos) Message-Id: <199808150625.IAA03408@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808142214.PAA21199@usr04.primenet.com> from Terry Lambert at "Aug 14, 98 10:14:02 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 15 Aug 1998 08:25:13 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 In reply to Terry Lambert who wrote: > > A workable snapshot is available on: > > > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > > > From the README: > > > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > > Please dont distribute this, only use it for testing, as it is > > alpha level code which is undergoing rapid changes. > > I didn't see CAM in there; are you making it fit under CAM? NetBSD > has unified their device model this wat, with apparently good results... There is no CAM in there. There might be a hook in the ata driver to register the ATAPI devices through CAM later. Acessing ATA disk devices through CAM is not planned. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 14 23:47:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27557 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 23:47:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27545 for ; Fri, 14 Aug 1998 23:47:09 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id CAA25292; Sat, 15 Aug 1998 02:46:12 -0400 (EDT) Date: Sat, 15 Aug 1998 02:46:12 -0400 (EDT) From: "Matthew N. Dodd" To: Brett Glass cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-Reply-To: <199808141756.LAA24900@lariat.lariat.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 Fri, 14 Aug 1998, Brett Glass wrote: > At 10:41 AM 8/14/98 +0000, Mike Smith wrote: > >C is not "unsafe", it is "not-safe", meaning that you're responsible for > >your own security. In this it is no less "safe" than any other > >language as you are a fool if you take the "safety" of any other > >language on trust. > > Gee, by this reasoning a car without seat belts, a horn, or bumpers is > is really no less "safe" than any other car. After all, you're a fool if > you trust your car to be safe. You seem to be arguing for cars that are fixed to their lanes by iron rails down the center of the lane. (Probably one of the most annoying rides at DisneyLand) > I guess I'll remove that pesky blade guard from my circular saw, too. > After all, doing that doesn't make the saw any less safe. You're not adding anything to your arguement. The summary of this entire thread (and the previous ones you've been on in -security) is: Poor programmers write poor code, which may contain bugs that expose the system to security risks. If you choose to write or use poor code you have read the disclaimer and are agreeing to use 'unsafe' tools. If you are going to contribute to a meaningful discussion, don't resort to 'C sucks, its not safe' every other sentence. (I should probably just procmail Brett so he doesn't acidently annoy me at 3 am and incur the list a flame from me.) Brett, if you want to rewrite FreeBSD in Modula-3, Jave, Smalltalk, Intercal or whatever 'safe' language gives you the most wood, go for it. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 01:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05815 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 01:51:23 -0700 (PDT) (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 BAA05809 for ; Sat, 15 Aug 1998 01:51:19 -0700 (PDT) (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 SAA17385; Sat, 15 Aug 1998 18:20:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA22506; Sat, 15 Aug 1998 18:20:33 +0930 (CST) Message-ID: <19980815182033.E22238@freebie.lemis.com> Date: Sat, 15 Aug 1998 18:20:33 +0930 From: Greg Lehey To: Terry Lambert , Matthew Hunt Cc: brawley@camtech.com.au, hackers@FreeBSD.ORG Subject: Do we have a Y2K problem after all? (was 64-bit time_t) References: <19980814000605.A25012@astro.psu.edu> <199808142303.QAA23463@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808142303.QAA23463@usr04.primenet.com>; from Terry Lambert on Fri, Aug 14, 1998 at 11:03:14PM +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 Friday, 14 August 1998 at 23:03:14 +0000, Terry Lambert wrote: >>> Question: What is wrong with using an unsigned long for time_t, instead of >>> long (which is then assumed signed). >> >> man 3 time: >> >> Upon successful completion, time() returns the value of time. Otherwise >> a value of ((time_t) -1) is returned and the global variable errno is set >> to indicate the error. > > See also: > > http://www.eunet.pt/ano2000/sun/sup_sun5.htm A very interesting page. It doesn't have much to do with the subject of the purpose of time_t, but it does indicate that we haven't done all our homework relating to Y2K. How much of the changes suggested in this page should *we* emulate? > Negative values are (potentially) abused for dates back to December > 13th, 1901. I didn't see the word "abuse" anywhere in the page. What's wrong with using negative time_t if they're defined in the spec? 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 Aug 15 02:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08139 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 02:20:53 -0700 (PDT) (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 CAA08134 for ; Sat, 15 Aug 1998 02:20:51 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from naglfar.ifi.uio.no (3034@naglfar.ifi.uio.no [129.240.64.54]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA26561 for ; Sat, 15 Aug 1998 11:20:20 +0200 (MET DST) Received: (from andreasd@localhost) by naglfar.ifi.uio.no ; Sat, 15 Aug 1998 11:20:19 +0200 (MET DST) To: hackers@FreeBSD.ORG Subject: video mode switching is only partially supported From: Andreas Dobloug Date: 15 Aug 1998 11:20:18 +0200 Message-ID: Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently using FreeBSD 2.2CAM-19980716-SNAP I get these lines when booting: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: WARNING: video mode switching is only partially supported sc0: VGA color <16 virtual consoles, flags=0x0> my display card is a "Hercules Dynamite 3D/GL 8MB AGP". How does the syscons determine whether or not a display-card supports switching? -- Andreas Dobloug : email: andreasd@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 Sat Aug 15 02:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08711 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 02:31:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from linkdead.paranoia.com (linkdead.paranoia.com [204.145.225.245]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08704 for ; Sat, 15 Aug 1998 02:31:13 -0700 (PDT) (envelope-from vax@linkdead.paranoia.com) Received: from localhost (localhost [127.0.0.1]) by linkdead.paranoia.com (8.8.8/8.7.3) with SMTP id EAA00661; Sat, 15 Aug 1998 04:26:38 -0500 (CDT) Message-Id: <199808150926.EAA00661@linkdead.paranoia.com> X-Authentication-Warning: linkdead.paranoia.com: localhost [127.0.0.1] didn't use HELO protocol To: netbsd-users@netbsd.org, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org, linux-kernel@vger.rutgers.edu Subject: ups/power management techniques X-URI: http://www.paranoia.com/~vax Date: Sat, 15 Aug 1998 04:26:36 -0500 From: VaX#n8 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies for sending to such a broad audience. I have been working quite hard on a cable, adapting electronics, and UPS monitoring software for NetBSD. I sent an email to the vendor about building a cable, and was told it wasn't possible. Naturally, I could not resist this challenge. I examined the Linux UPS HOWTO, various web pages, and built my own (learning quite a bit about RS-232 in the process). I was a little surprised to find that most of the serial communication information on the Internet began and ended with pin assignments. I couldn't even find a suitable newsgroup to ask questions in. After investigating several of the Linux packages, I decided it would still be worthwhile (instructive) to write my own. I've done so. However, my UPS only supports immediate shutdown (by raising a serial line for 50 milliseconds). This led to some rather interesting race conditions when trying to implement it in a stand-alone daemon. So, I figured I'd query the collective open-source knowledge base. Searching various mailing list archives has tended to generate more heat than light - there's a number of terms and synonyms people could use in describing the issue, and there are far more people asking where to find a particular software package than in discussing the real issues. So the questions I want to ask are: 1) What kind of kernel support would handle this in the cleanest way? 2) Where should the shutdown signal be asserted; in the userland monitoring program, the reboot command, the kernel reboot(2), or the instruction before HALT? ;) 3) Should there be any special handling after a powerfail shutdown? Specifically, should the OS idle in single-user mode until some condition is met, to avoid yo-yo-ing? 4) Anything else? I will summarize in a web page, so you need only email me and check my home page later (see the mail headers). Cc any mailing list at your own peril. While I wouldn't mind a cross-list technical discussion about the various approaches, they haven't worked in the past. Apologies for my semi-literacy; it has been a long night. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 03:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11297 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 03:24:08 -0700 (PDT) (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 DAA11289 for ; Sat, 15 Aug 1998 03:24:06 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id DAA11292; Sat, 15 Aug 1998 03:23:36 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd011255; Sat Aug 15 03:23:28 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id DAA12272; Sat, 15 Aug 1998 03:23:22 -0700 (MST) From: Terry Lambert Message-Id: <199808151023.DAA12272@usr06.primenet.com> Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) To: grog@lemis.com (Greg Lehey) Date: Sat, 15 Aug 1998 10:23:20 +0000 (GMT) Cc: tlambert@primenet.com, mph@pobox.com, brawley@camtech.com.au, hackers@FreeBSD.ORG In-Reply-To: <19980815182033.E22238@freebie.lemis.com> from "Greg Lehey" at Aug 15, 98 06:20:33 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://www.eunet.pt/ano2000/sun/sup_sun5.htm > > A very interesting page. It doesn't have much to do with the subject > of the purpose of time_t, but it does indicate that we haven't done > all our homework relating to Y2K. Actually, you have to dig for it, but it appears that Sun does not plan to update to a 64 bit time_t yet. > How much of the changes suggested in this page should *we* emulate? The strptime() changes account for about 2/3rds of the Y2K patch releases (on the page referenced by the original article that incited this thread). FreeBSD includes this in libcompat (I think), so it's technically not as severe (except for all those Linux-heads who keep wanting it as part of libc). The other bugs may or may not exist; certianly the two digit positive roll on the year changes aren't in there, and they only put the problem off to 2069, so they aren't very satisfying -- but it does mean FreeBSD has Y2K problems. > > Negative values are (potentially) abused for dates back to December > > 13th, 1901. > > I didn't see the word "abuse" anywhere in the page. What's wrong with > using negative time_t if they're defined in the spec? They aren't in the POSIX or SOLO specification. In general, I say abuse because you either can't represent one second before Jan 1 1970 GMT, or you can, but you do it using a discontinuity (ie: it's -2, since -1 is an error indicator). Without a mandate about the discontinuity, it would probably be an error waiting to happen if, by advancing your clock monotonically from a per 1970 date through a range to a post 1970 date (ie: you would return -1, the error indicator). I think the correct thing is to mandate the discontinuity, but this may result in a one second differential based on system implementation for dates prior to 1970. I fully expect to live to see the day when 0x80000000 is one second after 0x7fffffff (in the year 2039) as the "fix" for some systems 2039 bug. Holding the next bug off another 69 years. It's interesting that we are 3/7 of the way to the 2039 bug, which was made on a similar assumption about our software not outliving our dogs... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 04:25:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18865 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 04:25:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.linkdesign.com (relay.linkdesign.com [194.42.128.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18856 for ; Sat, 15 Aug 1998 04:25:01 -0700 (PDT) (envelope-from Michael.Bielicki@linkdesign.com) Received: from nt-home (CyBaer.Nicosia.CY.GalaxyNet.ORG.harr.harr.harr.bofh.com.cy [194.42.135.84]) by relay.linkdesign.com (8.8.8/8.8.6) with SMTP id OAA19162 for ; Sat, 15 Aug 1998 14:23:49 +0300 (EEST) Reply-To: From: "Michael Bielicki" To: Subject: RE: solaris smp management Date: Sat, 15 Aug 1998 14:28:32 +0300 Message-ID: <000201bdc83f$d51fd550$54872ac2@nt-home> 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 In-Reply-To: <19980815123748.E21662@lemis.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Greg Lehey > Sent: Saturday, August 15, 1998 6:08 AM > To: Alfred Perlstein; poipoi@famipow.com > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: solaris smp management > > > > Well, not quite. SunOS 1 to 4 were a BSD kernel, SunOS 5 is an SVR4 > kernel. Solaris 1 includes SunOS4, and Solaris 2 includes SunOS 5. > Solaris = SunOS + OpenWindows thats what SUN stated as the first Solaris came out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 04:53:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20489 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 04:53:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20484 for ; Sat, 15 Aug 1998 04:53:17 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.3]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA154; Sat, 15 Aug 1998 13:51:34 +0200 Message-ID: <35D5767D.1A2F93A2@pipeline.ch> Date: Sat, 15 Aug 1998 13:52:29 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Greg Lehey CC: hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> <19980814135919.U1921@freebie.lemis.com> <19980814114525.B4001@zappo> <19980815120445.C21662@lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: -snip- [and cc trimmed] > Of course, for this to make *any* sense at all, it should be a format > that everybody accepts. Otherwise we've just made the matter worse. TAI64 looks good (quotes from DJB's definition): "TAI stands for Temps Atomique International, the current international real time standard." "TAI64 represents a few hundred billion years of real time with 1-second precision." "One-second precision is inadequate for many applications. This section defines 96-bit and 128-bit formats, TAI64N and TAI64NA, with nanosecond and attosecond precision respectively. ..." More on: ftp://koobera.math.uic.edu/www/proto/tai64.txt ftp://koobera.math.uic.edu/www/y2k.html ftp://koobera.math.uic.edu/www/libtai.html -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 05:21:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21962 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 05:21:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21937 for ; Sat, 15 Aug 1998 05:21:07 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id MAA22843; Sat, 15 Aug 1998 12:20:34 GMT (envelope-from didier@omnix.net) Date: Sat, 15 Aug 1998 14:20:34 +0200 (CEST) From: Didier Derny To: support@yard.de cc: hackers@FreeBSD.ORG Subject: Yard/FreeBSD Problem 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 ---------- Forwarded message ---------- >Hi, >I ran your (small version) program on our Linux site. It's compared to >FreeBSD 15 times faster, which indicates a FreeBSD problem. When the program >is running on FreeBSD, vmstat reports at least 95% idle time, which also >points to a problem in the kernel. Results of my personal test this morning (on the same machine) FreeBSD: FreeBSD 3.0-SNAPSHOT (Mai 98) Linux: Suse 5.2 Test on 7461 rows FreeBSD with ...ack_delayed=1 several hours FreeBSD with ...ack_delayed=0 1m48 Linux 5m19 My personal idea on this problem: I suppose that there is a slight problem with the yard handling of the network and that this problemcan be amplified by FreeBSD. After having ran FreeBSD for years on large servers I can hardly beleive that the problem only come from FreeBSD. One of the tests that could be done would be to convert the yard database to msql and see the results. -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 08:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05273 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 08:06:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp6520.on.bellglobal.com [206.172.208.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05268 for ; Sat, 15 Aug 1998 08:06:18 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id LAA02437; Sat, 15 Aug 1998 11:04:46 -0400 (EDT) (envelope-from tim) Message-ID: <19980815110445.A2355@zappo> Date: Sat, 15 Aug 1998 11:04:45 -0400 From: Tim Vanderhoek To: Greg Lehey , Matthew Hunt , Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> <19980814135919.U1921@freebie.lemis.com> <19980814114525.B4001@zappo> <19980815120445.C21662@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980815120445.C21662@lemis.com>; from Greg Lehey on Sat, Aug 15, 1998 at 12:04:45PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 15, 1998 at 12:04:45PM +0930, Greg Lehey wrote: > > One problem UNIX has is that there is no standardized format for > representing times. There is no sensible reason to use one format for > representing system times, one (inconvenient) format for representing > times more accurately (down to only 1 microsecond, when it could have > been down to a nanosecond), and one format broken down into > representations of the individual units of time. None are of any use > when I want to know "How many seconds has it been since my grandfather > was born?". time_t *will* answer the question "How many seconds has Why the hell would you want to know how many seconds it has been since your grandfather was born? The whole idea of measuring the current time in seconds (or useconds, or nanoseconds) since some epoch is bogus. The current time is constantly being corrected and changed. Simply because the current time "is" 57382023 seconds since the epoch does not mean that 57382023 seconds have passed since the epoch. If some physicist performing an experiment needs to record time passed, he needs his own clock to track seconds passed, but comparing seconds (or any time) passed to the current time as recorded by some central clock isn't necessarily meaningful. If there are two physicists, perhaps they will synchronize their counting at some given current time, but after that, they're on their own. Goes double for anyone here who is trying to figure-out how many seconds they have been alive. A 64bit time_t will only _perpetuate_ the error of time_t in the first place. Propose a solution (preferably before A.D. 2039) and let those who need to count time passed do so in with whatever units and counters are appropriate for their needs. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 08:42:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07738 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 08:42:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA07692 for ; Sat, 15 Aug 1998 08:41:55 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 1013 invoked by uid 1000); 15 Aug 1998 16:43:54 -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: <199808151023.DAA12272@usr06.primenet.com> Date: Sat, 15 Aug 1998 12:43:54 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Terry Lambert Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) Cc: hackers@FreeBSD.ORG, brawley@camtech.com.au, mph@pobox.com, (Greg Lehey) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, we have... Create a file with date of 2017, theen ls -al it. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 09:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12748 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 09:53:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12743 for ; Sat, 15 Aug 1998 09:53:52 -0700 (PDT) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:beattie@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id JAA19606; Sat, 15 Aug 1998 09:19:58 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id JAA15996; Sat, 15 Aug 1998 09:21:30 -0700 Date: Sat, 15 Aug 1998 09:21:30 -0700 (PDT) From: Brian Beattie To: Simon Shapiro cc: Terry Lambert , hackers@FreeBSD.ORG, brawley@camtech.com.au, mph@pobox.com, grog@lemis.com Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) 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 Sat, 15 Aug 1998, Simon Shapiro wrote: > Yup, we have... > > Create a file with date of 2017, theen ls -al it. > > Simon > > OK... 506% touch -t 201701010000 x 507% ls -la x -rw-rw-r-- 1 beattie beattie 0 Jan 1 2017 x Maybe I'm missing something, but it looks ok to me... Brian Beattie | If my corporate life has taught me anything, beattie@aracnet.com | it was that running multi-million dollar www.aracnet.com/~beattie | projects in no way implied managerial competence. | Tony Porczyk ( in comp.unix.bsd.freebsd.misc ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 10:58:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18641 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 10:58:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18635 for ; Sat, 15 Aug 1998 10:58:40 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id KAA00653; Sat, 15 Aug 1998 10:11:27 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808151011.KAA00653@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: wjw@IAEhv.nl cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: Adding system calls In-reply-to: Your message of "Sat, 15 Aug 1998 12:28:58 +0200." <199808151028.MAA20095@surf.IAE.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 10:11:26 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You ( Mike Smith ) write: > => > > => > What/were is the receipe to add new system calls. > => > I'd like to add my own sysctl_* calls. > => > => You don't feel that you can overload the current calls? > > Well I'd like to make a nsysctl call for starters, just to able to leave > everything in place, and add my own version in parallel. This would make the > migration a lot simpler: I don't have to take care of all kinds of pitfalls > which pop up due to unforseen loop-holes. Fair enough, especially for testing. > And there are structures for the new functionality which I cannot get into > the original call without making it a real mess. I consider the current > implementation already warped. (appologies to phk) Poul didn't invent it, just made it more useful. > => > Are there any directives on what "design" to use while defining these calls. > => > Like: > => > - Use only one syscall as a multiplexer > => > (Which created a not so trivial mess is the current sysctl) > => > => This is good if all the subcalls share similar data. > > Well think about this one: > sysctl_node *sysctl_getnext( sysctl_node *node); > > It allows you to give a kernel pointer, and gets you a pointer to a next > structure. > > Would this be a sensible move? It's easy but will allow invallid accesses to > memory, if somebody uses garbage as pointer. No, it's an extremely bad move unless it can validate its argument. > It is a little faster, since it doesn't have to find the starting point, but > that doesn't outweigh the disavantage. Correct. The 'correct' way to implement the above would be: char *sysctl_next(const char *name); where the return value would be a malloc()ed buffer containing the name of the next node, or NULL on error. Errno would be set to EINVAL if (name) did not exist, or ENOENT if there was no next node. You would use your hashtable to locate (name), and then pick the next node. If (name) had been deleted, you would have to perform a best-guess search. Keeping nodes sorted by name would trivialise this. > => > - What parameters are a bad idea to transfer from > => > user to kernel space? > => > => Just the ones you need. > > Well, kernel-pointers are perhaps an issue. > And or structures with kernel-pointers. None of these should ever be exposed. > => > And answers to questions like: > => > - Where can I find the "user"-data > => > => Such as? > > I'm still trying to parse the code which does something called > "userland_sysctl", which I thing does a lookup in userland data?? No, it just handles sysctl calls where the data portion may be in user space. > > => > - Hoe to I return results for "call-by-ref" parameters > => > => Use copyin/copyout and the fu*/su* calls, all of which have manpages in > => -current. > > Oke, I have some current-version on my disk. I'll put it at the end of my > MANPATH. But then I'd still need some happy guesses as to their names. copyin, copyout, fubyte, subyte. -- \\ 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 Aug 15 10:59:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18696 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 10:59:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18691 for ; Sat, 15 Aug 1998 10:59:05 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id KAA00964; Sat, 15 Aug 1998 10:57:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808151057.KAA00964@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Dobloug cc: hackers@FreeBSD.ORG Subject: Re: video mode switching is only partially supported In-reply-to: Your message of "15 Aug 1998 11:20:18 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 10:57:08 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm currently using FreeBSD 2.2CAM-19980716-SNAP > > I get these lines when booting: > > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: WARNING: video mode switching is only partially supported > sc0: VGA color <16 virtual consoles, flags=0x0> > > my display card is a "Hercules Dynamite 3D/GL 8MB AGP". > How does the syscons determine whether or not a display-card supports > switching? You've booted in a nonstandard video mode. There may be a BIOS option to select whether the spiffy graphics mode that the BIOS uses for it's logo is retained for bootroms, or whether it should switch to a standard mode. Pick the latter. -- \\ 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 Aug 15 10:59:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18800 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 10:59:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18770; Sat, 15 Aug 1998 10:59:42 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA00459; Sat, 15 Aug 1998 09:36:59 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808150936.JAA00459@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: tlambert@primenet.com (Terry Lambert), current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-reply-to: Your message of "Sat, 15 Aug 1998 08:25:13 +0200." <199808150625.IAA03408@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 15 Aug 1998 09:33:09 +0000 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA18792 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > > > Please dont distribute this, only use it for testing, as it is > > > alpha level code which is undergoing rapid changes. > > > > I didn't see CAM in there; are you making it fit under CAM? NetBSD > > has unified their device model this wat, with apparently good results... > > There is no CAM in there. There might be a hook in the ata driver > to register the ATAPI devices through CAM later. Acessing ATA disk > devices through CAM is not planned. You've changed your mind *again*? For what it's worth, I don't see much value in treating ATA disks as though they were SCSI disks; the overhead in translation is probably too high. On the other hand, I'm less sure about things that use the ATAPI packet protocol. Still, and more importantly, you're the one doing the work. -- \\ 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 Aug 15 11:48:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24140 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 11:48:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24132; Sat, 15 Aug 1998 11:48:47 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA05540; Sat, 15 Aug 1998 11:30:51 -0700 (PDT) Message-Id: <199808151830.LAA05540@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Mike Smith Cc: sos@FreeBSD.ORG, tlambert@primenet.com (Terry Lambert), current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 15 Aug 1998 11:30:50 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998 09:33:09 +0000 Mike Smith wrote: > You've changed your mind *again*? > > For what it's worth, I don't see much value in treating ATA disks as > though they were SCSI disks; the overhead in translation is probably > too high. On the other hand, I'm less sure about things that use the > ATAPI packet protocol. Considering that even SCSI command passthrough works on many ATAPI disks and CD-ROMS, it really is the right thing to do, and we have had a LOT of success doing it this way in NetBSD. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 11:55:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25084 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 11:55:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25076 for ; Sat, 15 Aug 1998 11:55:16 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id LAA01317; Sat, 15 Aug 1998 11:53:24 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808151153.LAA01317@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Thorpe cc: hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-reply-to: Your message of "Sat, 15 Aug 1998 11:30:50 MST." <199808151830.LAA05540@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 11:53:23 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 15 Aug 1998 09:33:09 +0000 > Mike Smith wrote: > > For what it's worth, I don't see much value in treating ATA disks as > > though they were SCSI disks; the overhead in translation is probably > > too high. On the other hand, I'm less sure about things that use the > > ATAPI packet protocol. > > Considering that even SCSI command passthrough works on many ATAPI > disks and CD-ROMS, it really is the right thing to do, and we have > had a LOT of success doing it this way in NetBSD. I'd be curious to know if anyone's measured the cost of the SCSI<->ATA translation for ATA disks, since that's where performance is really an issue. Nobody cares how efficient access to a Zip disk is, but an extra 10% overhead on ATA disk transactions would really hurt. Command passthrough doesn't (can't) work directly, as many fields are different sizes. I think what you mean is that there's no need for any intelligence in the translation, which is fair enough. -- \\ 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 Aug 15 11:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25455 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 11:58:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25450 for ; Sat, 15 Aug 1998 11:58:48 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA05693; Sat, 15 Aug 1998 11:40:50 -0700 (PDT) Message-Id: <199808151840.LAA05693@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 15 Aug 1998 11:40:49 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998 11:53:23 +0000 Mike Smith wrote: > I'd be curious to know if anyone's measured the cost of the SCSI<->ATA > translation for ATA disks, since that's where performance is really an > issue. Nobody cares how efficient access to a Zip disk is, but an > extra 10% overhead on ATA disk transactions would really hurt. We're not doing it for ATA, but then again ATAPI disk aren't ATA. We are, however, doing a SCSI-like layer for ATA. > Command passthrough doesn't (can't) work directly, as many fields are > different sizes. I think what you mean is that there's no need for any > intelligence in the translation, which is fair enough. ...this doens't really matter if you're, e.g., passing mmc commands to an ATAPI CD-ROM or CD-R. They're the same for SCSI and ATAPI. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 12:04:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26112 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 12:04:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26102; Sat, 15 Aug 1998 12:04:43 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id VAA08482; Sat, 15 Aug 1998 21:02:53 +0200 (CEST) (envelope-from sos) Message-Id: <199808151902.VAA08482@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808150936.JAA00459@word.smith.net.au> from Mike Smith at "Aug 15, 98 09:33:09 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 15 Aug 1998 21:02:53 +0200 (CEST) Cc: sos@FreeBSD.ORG, tlambert@primenet.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 In reply to Mike Smith who wrote: > > > > There is no CAM in there. There might be a hook in the ata driver > > to register the ATAPI devices through CAM later. Acessing ATA disk > > devices through CAM is not planned. > > You've changed your mind *again*? No :) > For what it's worth, I don't see much value in treating ATA disks as > though they were SCSI disks; the overhead in translation is probably > too high. On the other hand, I'm less sure about things that use the > ATAPI packet protocol. The ATA driver with lowlevel ATAPI support _must_ be implemented in all cases, the difference is if the ATAPI device are registered under CAM (scsi) or if there are nataive ATAPI drivers instead. Since I've allready written an ATAPI tape driver, and now an ATAPI CD-R/RW driver (which doesn't exist for CAM), I see no reason why not to have them. There is nothing hindering a CAM hook too, for those wanting that, but that will be up in the future until CAM gets "serious" enough. I se NO reason to bloat an ATA/ATAPI only system with all the CAM stuff though, but in a mixed ATA/ATAPI/SCSI system it might have some merit. > Still, and more importantly, you're the one doing the work. Exactly, and as long as its my spare time, I'll do the deciding :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 12:42:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00966 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 12:42:25 -0700 (PDT) (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 MAA00953 for ; Sat, 15 Aug 1998 12:42:19 -0700 (PDT) (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 VAA25225; Sat, 15 Aug 1998 21:41:21 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sat, 15 Aug 1998 21:41:21 +0200 (MET DST) Mime-Version: 1.0 To: Brett Glass Cc: Joseph Stein , mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808141733.LAA24664@lariat.lariat.org> <199808141820.MAA25200@lariat.lariat.org> 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 Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 15 Aug 1998 21:41:20 +0200 In-Reply-To: Brett Glass's message of "Fri, 14 Aug 1998 12:20:25 -0600" Message-ID: Lines: 16 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 MAA00956 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass writes: > At 10:46 AM 8/14/98 -0700, Joseph Stein wrote: > > There is no such thing as a "safe" tool. You can write code in assembly > > language and still end up with security holes. > Of course. Assembly language has even fewer safeguards against shooting > oneself in the foot, though in many cases it's easy to spot and prevent > problems than it is in C. Brett, I know someone who would *love* to talk to you. His name is Scott Nudds and he hangs out it comp.lang.c a lot. Now can we put an end to this ridiculous flamefest? 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 Sat Aug 15 12:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01313 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 12:47:07 -0700 (PDT) (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 MAA01308 for ; Sat, 15 Aug 1998 12:47:05 -0700 (PDT) (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 VAA25518; Sat, 15 Aug 1998 21:45:25 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sat, 15 Aug 1998 21:45:25 +0200 (MET DST) Mime-Version: 1.0 To: Greg Lehey Cc: Tim Vanderhoek , Matthew Hunt , Ivan Brawley , hackers@FreeBSD.ORG Subject: Re: 64-bit time_t References: <199808131721.KAA00864@antipodes.cdrom.com> <199808140040.KAA14156@mad.ct> <19980814000605.A25012@astro.psu.edu> <19980814135919.U1921@freebie.lemis.com> <19980814114525.B4001@zappo> <19980815120445.C21662@lemis.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 Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 15 Aug 1998 21:45:24 +0200 In-Reply-To: Greg Lehey's message of "Sat, 15 Aug 1998 12:04:45 +0930" 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 MAA01309 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > 2. Make it a merged struct timeval (i.e. tv_usec + 1000000 * tv_sec) > and you have a *useful* replacement for both time_t and struct > timeval which will still measure time from before the beginning of > recorded history to at least the release of FreeBSD 3.0. Wow, wow, hold it, Greg, you're spooking me. Jordan, we're still planning to ship on October 15th, right? We're not gonna postpone it until, say, your greatgrandson's fiftieth birthday or something? 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 Sat Aug 15 13:03:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03333 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:03:40 -0700 (PDT) (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 NAA03325 for ; Sat, 15 Aug 1998 13:03:36 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA24017 for ; Sat, 15 Aug 1998 16:03:04 -0400 (EDT) Date: Sat, 15 Aug 1998 16:03:03 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: Question on delayed write. 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 comment in vfs_clean_pages() in vfs_bio.c says we can set the pages in a buffer clean to avoid VM intervention and I am quite confused with this. (1) Even if the field valid/dirty in vm_page structure are set to be zero, the pageout process can get the current dirty/clean status directly from the PTE and then write the whole page to disk. The code is: If (m->dirty == 0) vm_page_test_dirty(); (2) When there is a page shortage, the pages of the buffer can be reclaimed without being written to disk (because we have declared them as clean). If this happens before the delayed write happens, it will lose data. (active pages can become inactive pages) Any help is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 13:04:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03455 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:04:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net ([139.146.210.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03450 for ; Sat, 15 Aug 1998 13:04:05 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id PAA19945; Sat, 15 Aug 1998 15:01:20 -0500 (CDT) From: Jim Bryant Message-Id: <199808152001.PAA19945@unix.tfs.net> Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) In-Reply-To: from Simon Shapiro at "Aug 15, 98 12:43:54 pm" To: shimon@simon-shapiro.org Date: Sat, 15 Aug 1998 15:01:19 -0500 (CDT) 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: > Yup, we have... > > Create a file with date of 2017, theen ls -al it. > > Simon Ahem... What's wrong with it? 2:54:04pm argus(33): touch -t 201701010000.00 t 2:54:08pm argus(34): ls -laT total 5 drwxr-xr-x 2 jbryant wheel 512 Aug 15 14:53:57 1998 . drwx------ 37 jbryant wheel 4096 Aug 15 14:49:35 1998 .. -rw-r--r-- 1 jbryant wheel 0 Jan 1 00:00:00 2017 t 2:54:11pm argus(35): uname -a FreeBSD argus 3.0-CURRENT FreeBSD 3.0-CURRENT #27: Sat Jul 25 17:51:25 CDT 1998 jbryant@argus:/usr/src/sys/compile/ARGUS i386 2:55:29pm argus(36): touch -t 192910290000.00 t 2:58:28pm argus(37): ls -laT total 5 drwxr-xr-x 2 jbryant wheel 512 Aug 15 14:53:57 1998 . drwx------ 37 jbryant wheel 4096 Aug 15 14:55:20 1998 .. -rw-r--r-- 1 jbryant wheel 0 Oct 29 00:00:00 1929 t 2:58:30pm argus(38): [yes, i know... i'll prob do another make world this weekend...] 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 Sat Aug 15 13:12:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04757 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:12:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04752 for ; Sat, 15 Aug 1998 13:12:47 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id NAA00965; Sat, 15 Aug 1998 13:11:44 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808152011.NAA00965@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 to: Brett Glass cc: Joseph Stein , mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-reply-to: Your message of "15 Aug 1998 21:41:20 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 13:11:43 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Brett , Just leave the issue alone. We do have language experts and architects in the house and they can lead if they want to . C was originally a bullet target however someone shot the target and unleashed the language on the world 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 13:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04931 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:14:22 -0700 (PDT) (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 NAA04923 for ; Sat, 15 Aug 1998 13:14:20 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from heidi (mobile19.jrc.it [139.191.250.19]) by mrelay.jrc.it (LMC5688) with SMTP id WAA03156; Sat, 15 Aug 1998 22:13:37 +0200 (MET DST) Date: Sat, 15 Aug 1998 22:16:44 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi Reply-To: Nick Hibma To: Dan Langille cc: FreeBSD hackers mailing list Subject: Re: large drives, old BIOS, IDE Controllers In-Reply-To: <199808150108.NAA27823@cyclops.xtra.co.nz> 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 Try to find an IDE adapter you can jumper for 'second controller'. They exist, given the fact that I once had an IDE, ESDI and SCSI controller in one box and booted of the ESDI (because it made such a lovely sound when being used :-). I've seen adapters that could be jumpered to use 0x17x instead if 0x1fx (or the other way around), but were not able to be switched to IRQ 15 (or 14, again, have a look at the current settings for the active controller). But that is nothing a good soldering iron can't solve. Nick On Sat, 15 Aug 1998, Dan Langille wrote: > I've been talking to my computer store (which doesn't know much about > Unix) and searching the mail archives. I think I've found my solution. > > The "problem" is my machine is a 486/dx2 something. I'm installed a 5G > drive. The shop figured I might not be able to use this drive as the BIOS > won't handle more than the first 512M of the drive. Yet, what I've just > read in the mail archives is that FreeBSD doesn't use the BIOS. If so, my > job is easy. > > At present, the machine has a CD-ROM and a 330M drive. Both are IDE and > are running off the I/O board. I'm about to add a 5G drive. Problem: > there's only 1 IDE connecter on my i/o board and none on the mother board. > And I can't buy an i/board with two IDE connecters. None are available > to be had. > > Any suggestions? I was planning to do this install this weekend. > > -- > Dan Langille > DVL Software Limited > http://www.dvl-software.com/freebsd : my [mis]adventures > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" 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 Sat Aug 15 13:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06238 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:23:15 -0700 (PDT) (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 NAA06232 for ; Sat, 15 Aug 1998 13:23:13 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from hrotti.ifi.uio.no (3034@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA27006; Sat, 15 Aug 1998 22:22:42 +0200 (MET DST) Received: (from andreasd@localhost) by hrotti.ifi.uio.no ; Sat, 15 Aug 1998 22:22:42 +0200 (MET DST) To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: video mode switching is only partially supported References: <199808151057.KAA00964@word.smith.net.au> From: Andreas Dobloug Date: 15 Aug 1998 22:22:41 +0200 In-Reply-To: <199808151057.KAA00964@word.smith.net.au> Message-ID: Lines: 12 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | > sc0: WARNING: video mode switching is only partially supported | > my display card is a "Hercules Dynamite 3D/GL 8MB AGP". | You've booted in a nonstandard video mode. There may be a BIOS option | to select whether the spiffy graphics mode that the BIOS uses for it's | logo is retained for bootroms, or whether it should switch to a | standard mode. Pick the latter. I've got an Asus P2B-DS. Has anybody else on this list got this card and know which option (if any) which fixes this? -- Andreas Dobloug : email: andreasd@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 Sat Aug 15 13:24:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06334 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:24:02 -0700 (PDT) (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 NAA06329 for ; Sat, 15 Aug 1998 13:24:01 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id NAA28913; Sat, 15 Aug 1998 13:23:31 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd028877; Sat Aug 15 13:23:22 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA20511; Sat, 15 Aug 1998 13:23:15 -0700 (MST) From: Terry Lambert Message-Id: <199808152023.NAA20511@usr01.primenet.com> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: mike@smith.net.au (Mike Smith) Date: Sat, 15 Aug 1998 20:23:15 +0000 (GMT) Cc: thorpej@nas.nasa.gov, hackers@FreeBSD.ORG In-Reply-To: <199808151153.LAA01317@word.smith.net.au> from "Mike Smith" at Aug 15, 98 11:53:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd be curious to know if anyone's measured the cost of the SCSI<->ATA > translation for ATA disks, since that's where performance is really an > issue. Nobody cares how efficient access to a Zip disk is, but an > extra 10% overhead on ATA disk transactions would really hurt. > > Command passthrough doesn't (can't) work directly, as many fields are > different sizes. I think what you mean is that there's no need for any > intelligence in the translation, which is fair enough. A question I have is this: If I'm passing SCSI commands down, is it possible to actually support multiple outstanding tagged commands? I know that the EIDE specification allows for this, but I am unaware of any IDE disk drives that support it. If I could get multiple outstanding transactions at a cost of 10% overhead, all I need is two of them and my system is running 80% faster than it was... For a single user workstation running a curses program on the console, this is not a problem. For any other load, this should generally be a win, especially if swapping is occurring. The inability of most IDE hardware to support multiple outstanding tagged commands is the primary reason I still recommend SCSI to people who are running light loads and are never going to need more than one disk and one CDROM (though "never" is a very long time indeed... for systems with most Intel chipsets, there is a limit to 2 simultaneous PCI bus masters before the negotiation fails, meaning I'm limited to 4 IDE devices no matter what). 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 Aug 15 13:28:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07160 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:28:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07088 for ; Sat, 15 Aug 1998 13:28:02 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id NAA01735; Sat, 15 Aug 1998 13:26:06 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808151326.NAA01735@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Dobloug cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: video mode switching is only partially supported In-reply-to: Your message of "15 Aug 1998 22:22:41 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 13:26:04 +0000 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | > sc0: WARNING: video mode switching is only partially supported > | > my display card is a "Hercules Dynamite 3D/GL 8MB AGP". > | You've booted in a nonstandard video mode. There may be a BIOS option > | to select whether the spiffy graphics mode that the BIOS uses for it's > | logo is retained for bootroms, or whether it should switch to a > | standard mode. Pick the latter. > > I've got an Asus P2B-DS. Has anybody else on this list got this card > and know which option (if any) which fixes this? Which BIOS? Probably AWARD, in which case it'll be in the "BIOS Feature Setup" screen. If you can't find it, it's either not there or you shouldn't be using a PC. 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 Sat Aug 15 13:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08978 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 13:42:34 -0700 (PDT) (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 NAA08971 for ; Sat, 15 Aug 1998 13:42:33 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id NAA02029; Sat, 15 Aug 1998 13:42:03 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd002014; Sat Aug 15 13:42:01 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA21190; Sat, 15 Aug 1998 13:41:52 -0700 (MST) From: Terry Lambert Message-Id: <199808152041.NAA21190@usr01.primenet.com> Subject: Re: Adding system calls To: mike@smith.net.au (Mike Smith) Date: Sat, 15 Aug 1998 20:41:51 +0000 (GMT) Cc: wjw@IAEhv.nl, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199808151011.KAA00653@word.smith.net.au> from "Mike Smith" at Aug 15, 98 10:11:26 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 > > Well I'd like to make a nsysctl call for starters, just to able to leave > > everything in place, and add my own version in parallel. This would make the > > migration a lot simpler: I don't have to take care of all kinds of pitfalls > > which pop up due to unforseen loop-holes. > > Fair enough, especially for testing. But not for cutover. The sysctl(3) code uses a multiplexed system call; the new code can be multiplexed off the old system call entry without introducing and backward incompatabilities to current sysctl using code. It may (but probably won't) help you to multiplex at the call level rather than the parameter level. It would be very easy to pass in a NULL pointer for ctl_name, ans use that to set up a seperate mux in the system call itself. Meanwhile, looking into this, I was alarmed to find that kld was not using a multiplex entry point. 8-(. People, these things are not performance sensitive; this is not "read" we are talking about here, and these things are not interacting to provide a bottleneck over a large number of iterations while doing something else. You are unlikely to see sysctl speed as one of the things tested in lmbench. If it becomes an issue, you can argue for why a switch statement is a significant fraction of trap or call gate overhead. 8-). > > => Use copyin/copyout and the fu*/su* calls, all of which have manpages in > > => -current. > > > > Oke, I have some current-version on my disk. I'll put it at the end of my > > MANPATH. But then I'd still need some happy guesses as to their names. > > copyin, copyout, fubyte, subyte. Note that copying in or out strings is an inherenetly bad idea, unless those strings represent a filesystem path name. I've long commiserated over the fact that the NFS subsystem uses copyinstr. Linux actually has the right idea (although it resulted in a memory leak in a lookup failure case, until I corrected it for them ;-)) where they have a single string routine, usable solely to obtain a user space path buffer in kernel space. Of course, their use of address space preverification for copyin/out makes some of their code faster, but with kernel threads, they now have the problem of a race wherein one thread preverifies and blocks, and a second thread modified the address space out from under the first, and they copyin/out from/to "the noplace". So do what they do, but not how they do it. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 14:04:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11791 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 14:04:42 -0700 (PDT) (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 OAA11786 for ; Sat, 15 Aug 1998 14:04:41 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA17596; Sat, 15 Aug 1998 14:04:11 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd017556; Sat Aug 15 14:04:00 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA22129; Sat, 15 Aug 1998 14:03:56 -0700 (MST) From: Terry Lambert Message-Id: <199808152103.OAA22129@usr01.primenet.com> Subject: Re: 64-bit time_t To: ac199@hwcn.org (Tim Vanderhoek) Date: Sat, 15 Aug 1998 21:03:55 +0000 (GMT) Cc: grog@lemis.com, mph@pobox.com, brawley@camtech.com.au, hackers@FreeBSD.ORG In-Reply-To: <19980815110445.A2355@zappo> from "Tim Vanderhoek" at Aug 15, 98 11:04:45 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 > Why the hell would you want to know how many seconds it has been since > your grandfather was born? > > The whole idea of measuring the current time in seconds (or useconds, > or nanoseconds) since some epoch is bogus. Or years since some epoch... 8-) 8-). The value of a single epoch (positive *or* negative relative, so all it is is a baseline, not a limit before which there was no time) is the ability to do calendar mathematics quickly and easily. > If some physicist performing an experiment needs to record time > passed, he needs his own clock to track seconds passed, but comparing > seconds (or any time) passed to the current time as recorded by some > central clock isn't necessarily meaningful. That would be Cesium cycles, most likely, for most interesting recent physics. 8-). However, to deal with audio Doppler shift for a train in your standard Newtonian universe, the only real guarantee necessary is that the clock doesn't go backwards, and monotonically increases. For an event with a duration of N ticks, so long as N is sufficiently large that the tick duration does not impact the significant digits obtained (ie: there are more significant digits than the required precision), then there's no problem. The difference between accuracy and precision is often hard to grasp. Most measurements need only repeatable precision, and can be scaled to obtain accuracy by measuring the precision's interval against an accurate base. If my clock always ticks at the same rate, it is precise. If my clock always ticks at the same rate and always tells the correct time, it's accurate. The problem here is that tickadj and friends are abstracted in such a way that it looks like we are trying to make time_t accurate, when those things which use time_t need only be precise. The internal clock should go at whatever rather the internal clock goes, to avoid "stretch seconds" in stored values, and deltas should be measured against whatever timebase. The value of time_t is as a monoclock value; ie: what it calls "seconds" are actually "ticks", and it is useful to know "how many ticks between X and Y" for things like making makefiles work. The scaling of "ticks" to "timebase delta" needs to be performed based on (1) a known tick count at the time a timebase reference sample occurred, and (2) a known tick count vs. the expected tick count at the time a timebase delta sample occurred. Let's deal first with the time_t overflow (which only approximately coincides with 2039, since a tick interval only approximately coincides with a second) given the physical constraints we have on inode size and layout for existing systems, and then use some of our spare fields to deal with subsecond timing when it becomes important to the operation of the system. 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 Aug 15 14:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12552 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 14:09:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12547 for ; Sat, 15 Aug 1998 14:09:35 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id XAA08791; Sat, 15 Aug 1998 23:09:03 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id XAA05502; Sat, 15 Aug 1998 23:09:03 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199808152109.XAA05502@surf.IAE.nl> Subject: Re: Adding system calls In-Reply-To: <199808152041.NAA21190@usr01.primenet.com> from Terry Lambert at "Aug 15, 98 08:41:51 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 15 Aug 1998 23:09:02 +0200 (MET DST) Cc: mike@smith.net.au, wjw@IAEhv.nl, hackers@FreeBSD.ORG Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae 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 You ( Terry Lambert ) write: => > > Well I'd like to make a nsysctl call for starters, just to able to leave => > > everything in place, and add my own version in parallel. This would make the => > > migration a lot simpler: I don't have to take care of all kinds of pitfalls => > > which pop up due to unforseen loop-holes. => > => > Fair enough, especially for testing. => => But not for cutover. I'd like to migrate my system in such a way that it keeps functioning as much as possible. That means that if there are possibilities to work around existing/working subsystems, that's my way of preference. In the end I'll provide code which should provide a migration with a little pain as possible. This case has the MUX-call to libc, which is easy to mimmic. But then getting all the MACRO-created stuff merged, that is more of a pain. => The sysctl(3) code uses a multiplexed system call; the new code can be => multiplexed off the old system call entry without introducing and => backward incompatabilities to current sysctl using code. Yes, that is the part I understand. But what about the other issues. You'd like me to "cramp" everything into this omni-potent parameterlist. Or is this the answer below? I do not understand the technical text, whilest I'm able to read the english. :-( => It may (but probably won't) help you to multiplex at the call level => rather than the parameter level. It would be very easy to pass in => a NULL pointer for ctl_name, ans use that to set up a seperate mux => in the system call itself. => People, these things are not performance sensitive; this is not "read" => we are talking about here, and these things are not interacting to => provide a bottleneck over a large number of iterations while doing => something else. You are unlikely to see sysctl speed as one of the => things tested in lmbench. If it becomes an issue, you can argue for => why a switch statement is a significant fraction of trap or call => gate overhead. 8-). Numbers?? This is why I asked about a "list" of things to concern myself with! If the callgate overhead is humongous, then I'll skip some of the "optimisations" I had in mind. => > > => Use copyin/copyout and the fu*/su* calls, all of which have manpages in => > > => -current. => > > => > > Oke, I have some current-version on my disk. I'll put it at the end of my => > > MANPATH. But then I'd still need some happy guesses as to their names. => > => > copyin, copyout, fubyte, subyte. => => Note that copying in or out strings is an inherenetly bad idea, unless => those strings represent a filesystem path name. I've long commiserated => over the fact that the NFS subsystem uses copyinstr. So what about getting/returning my sysctl-mibs? Mike Smith has argued to completely go the text way. (but they are no FS-paths). Currently SNMP is strings/arrays with numbers. Currently I take arrays of integers (could call that a sort of string), or an arrays of strings. Which could be turned into an array of point-concatenated strings, if it makes life easier to get the data. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 14:21:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13733 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 14:21:01 -0700 (PDT) (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 OAA13720 for ; Sat, 15 Aug 1998 14:20:59 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from hrotti.ifi.uio.no (3034@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA29711; Sat, 15 Aug 1998 23:20:26 +0200 (MET DST) Received: (from andreasd@localhost) by hrotti.ifi.uio.no ; Sat, 15 Aug 1998 23:20:25 +0200 (MET DST) To: Mike Smith Cc: Andreas Dobloug , hackers@FreeBSD.ORG Subject: Re: video mode switching is only partially supported References: <199808151326.NAA01735@word.smith.net.au> From: Andreas Dobloug Date: 15 Aug 1998 23:20:24 +0200 In-Reply-To: <199808151326.NAA01735@word.smith.net.au> Message-ID: Lines: 20 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Smith | > | You've booted in a nonstandard video mode. There may be a BIOS option | > I've got an Asus P2B-DS. Has anybody else on this list got this card | > and know which option (if any) which fixes this? | Which BIOS? Probably AWARD, in which case it'll be in the "BIOS | Feature Setup" screen. If you can't find it, it's either not there or | you shouldn't be using a PC. 8) Yes, it's an AWARD-bios. Believe me: I've tried all tried all the options regarding the display-card before I posted here :-). The only thing I cand find in the "BIOS Feature Setup" which has anything to do with the video-card is 'Video ROM BIOS Shadow' (yep, I've tried switching it off) and 'PCI/VGA Palette Snoop' which doesn't agree with my monitor. The 'Standard CMOS Setup' screen has got a field called 'Video', but the field always comes up with 'EGA/VGA' after saving the settings to the bios. Guess I have to choose between running X or a console :-). -- Andreas Dobloug : email: andreasd@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 Sat Aug 15 14:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15713 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 14:32:42 -0700 (PDT) (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 OAA15705; Sat, 15 Aug 1998 14:32:38 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA22323; Sat, 15 Aug 1998 21:45:40 +0200 From: Luigi Rizzo Message-Id: <199808151945.VAA22323@labinfo.iet.unipi.it> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: bright@www.hotjobs.com (Alfred Perlstein) Date: Sat, 15 Aug 1998 21:45:40 +0200 (MET DST) Cc: sos@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Aug 14, 98 03:02:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 14 Aug 1998, Søren Schmidt wrote: > > > In reply to Alfred Perlstein who wrote: > > > does this code have a watchdog to prevent ATAPI proccesses from tsleeping > > > forever? > > > > No, this is only to test ATAPI burners, prober timeout & error handeling > > is part of the new atapi subsystem, but that is not ready for primetime but.. is that such a big change in the system ? I thought one just needed to add a reference from the atapi device descriptor to the relevant wd controller and mostly reuse the existing timeout code which already works for wd disks... am i wrong ? 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 Sat Aug 15 15:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19678 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 15:03:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19667; Sat, 15 Aug 1998 15:03:13 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id AAA00503; Sun, 16 Aug 1998 00:01:40 +0200 (CEST) (envelope-from sos) Message-Id: <199808152201.AAA00503@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808151945.VAA22323@labinfo.iet.unipi.it> from Luigi Rizzo at "Aug 15, 98 09:45:40 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Sun, 16 Aug 1998 00:01:40 +0200 (CEST) Cc: bright@www.hotjobs.com, sos@FreeBSD.ORG, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 In reply to Luigi Rizzo who wrote: > > On Fri, 14 Aug 1998, Søren Schmidt wrote: > > > > > In reply to Alfred Perlstein who wrote: > > > > does this code have a watchdog to prevent ATAPI proccesses from tsleeping > > > > forever? > > > > > > No, this is only to test ATAPI burners, prober timeout & error handeling > > > is part of the new atapi subsystem, but that is not ready for primetime > > but.. is that such a big change in the system ? I thought one just > needed to add a reference from the atapi device descriptor > to the relevant wd controller and mostly reuse the existing timeout > code which already works for wd disks... am i wrong ? No not exactly, you are close, there is new timeout code that knows how long different commands should take, so that we dont need to (busy) wait for results, and can about when an ATAPI command hangs. Also there is prober handeling of the error codes much like the SCSI system... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 15:32:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23487 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 15:32:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA23457 for ; Sat, 15 Aug 1998 15:32:13 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 5659 invoked by uid 1000); 15 Aug 1998 23:34:26 -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: Sat, 15 Aug 1998 19:34:26 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Brian Beattie Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) Cc: Terry Lambert , hackers@FreeBSD.ORG, brawley@camtech.com.au, mph@pobox.com, grog@lemis.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Aug-98 Brian Beattie wrote: > On Sat, 15 Aug 1998, Simon Shapiro wrote: > >> Yup, we have... >> >> Create a file with date of 2017, theen ls -al it. >> >> Simon >> >> > > OK... > > 506% touch -t 201701010000 x > 507% ls -la x > -rw-rw-r-- 1 beattie beattie 0 Jan 1 2017 x > > Maybe I'm missing something, but it looks ok to me... Good news! You are right and I am wrong. I have a witness that, on current, I was right a week or two ago. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 16:00:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27812 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 16:00:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27787 for ; Sat, 15 Aug 1998 16:00:34 -0700 (PDT) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:beattie@shell2.aracnet.com [205.159.88.20]) by mail4.aracnet.com (8.9.1/8.9.0) with ESMTP id DAA07384; Sun, 16 Aug 1998 03:58:46 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id QAA12080; Sat, 15 Aug 1998 16:00:00 -0700 Date: Sat, 15 Aug 1998 16:00:00 -0700 (PDT) From: Brian Beattie To: Simon Shapiro cc: hackers@FreeBSD.ORG Subject: Re: Do we have a Y2K problem after all? (was 64-bit time_t) 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 Sat, 15 Aug 1998, Simon Shapiro wrote: > > On 15-Aug-98 Brian Beattie wrote: > > On Sat, 15 Aug 1998, Simon Shapiro wrote: > > > >> Yup, we have... > >> > >> Create a file with date of 2017, theen ls -al it. ... > > Maybe I'm missing something, but it looks ok to me... > > Good news! You are right and I am wrong. I have a witness that, on > current, I was right a week or two ago. So what was it you were seeing? Brian Beattie | If my corporate life has taught me anything, beattie@aracnet.com | it was that running multi-million dollar www.aracnet.com/~beattie | projects in no way implied managerial competence. | Tony Porczyk ( in comp.unix.bsd.freebsd.misc ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 16:21:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01180 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 16:21:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp1718.on.bellglobal.com [206.172.249.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01171 for ; Sat, 15 Aug 1998 16:21:31 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id TAA01760; Sat, 15 Aug 1998 19:19:50 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 15 Aug 1998 19:19:50 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Terry Lambert cc: Tim Vanderhoek , grog@lemis.com, mph@pobox.com, brawley@camtech.com.au, hackers@FreeBSD.ORG Subject: Re: 64-bit time_t In-Reply-To: <199808152103.OAA22129@usr01.primenet.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, 15 Aug 1998, Terry Lambert wrote: > The difference between accuracy and precision is often hard to grasp. Actually, it's high-school science, now. At least around here. :) > The problem here is that tickadj and friends are abstracted in such > a way that it looks like we are trying to make time_t accurate, > when those things which use time_t need only be precise. ^ should Exactly how many things should use it is, I suppose, up for debate. The settimeofday(2) shouldn't use it (it does). The localtime(3) shouldn't use it. Calculating your grandfather's age or your retirement savings shouldn't. > The value of time_t is as a monoclock value; ie: what it calls > "seconds" are actually "ticks", and it is useful to know "how many > ticks between X and Y" for things like making makefiles work. Do you mean for dependencies? They would work just as well if the filesystem stored accurate time information (although fs size might increase). :) Of course, any system trusting time data to store ordering information is subject to the timer's resolution. Ideally, the filesystem needs to provide an alternate way of storing this information. Practically, GNU and MS will ensure that software is always bloated enough that no computer will be fast enough to make us do anything. ;-) -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 16:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02310 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 16:33:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02305 for ; Sat, 15 Aug 1998 16:33:30 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA20267; Sat, 15 Aug 1998 16:32:49 -0700 (PDT) Message-Id: <199808152332.QAA20267@implode.root.com> To: zhihuizhang cc: hackers Subject: Re: Question on delayed write. In-reply-to: Your message of "Sat, 15 Aug 1998 16:03:03 EDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 15 Aug 1998 16:32:49 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The comment in vfs_clean_pages() in vfs_bio.c says we can set the pages in >a buffer clean to avoid VM intervention and I am quite confused with this. > >(1) Even if the field valid/dirty in vm_page structure are set to be zero, >the pageout process can get the current dirty/clean status directly from >the PTE and then write the whole page to disk. The code is: > > If (m->dirty == 0) vm_page_test_dirty(); > >(2) When there is a page shortage, the pages of the buffer can be >reclaimed without being written to disk (because we have declared them as >clean). If this happens before the delayed write happens, it will lose >data. (active pages can become inactive pages) > >Any help is appreciated. The pageout daemon won't touch pages that are attached to buffers. -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 Sat Aug 15 17:19:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07941 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 17:19:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07924; Sat, 15 Aug 1998 17:19:00 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA21108; Sat, 15 Aug 1998 17:18:21 -0700 (PDT) Message-Id: <199808160018.RAA21108@implode.root.com> To: Jaye Mathisen cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: vmopar state in 2.2.7? From: David Greenman Reply-To: dg@root.com Date: Sat, 15 Aug 1998 17:18:21 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The nnrpd's are occasionally getting stuck in what top shows as >the vmopar state. ps shows the process in Ds state. Should be fixed in rev 1.28.2.8 of nfs_bio.c. Let me know if you have any further trouble. -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 Sat Aug 15 17:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10708 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 17:46:09 -0700 (PDT) (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 RAA10700 for ; Sat, 15 Aug 1998 17:46:07 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA00731; Sat, 15 Aug 1998 17:45:36 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd000676; Sat Aug 15 17:45:29 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA15910; Sat, 15 Aug 1998 17:45:17 -0700 (MST) From: Terry Lambert Message-Id: <199808160045.RAA15910@usr07.primenet.com> Subject: Re: 64-bit time_t To: ac199@hwcn.org Date: Sun, 16 Aug 1998 00:45:17 +0000 (GMT) Cc: tlambert@primenet.com, grog@lemis.com, mph@pobox.com, brawley@camtech.com.au, hackers@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Aug 15, 98 07:19:50 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 difference between accuracy and precision is often hard to grasp. > > Actually, it's high-school science, now. At least around here. :) It's the secret they tell you after you get your PhD, here in the US... > > The value of time_t is as a monoclock value; ie: what it calls > > "seconds" are actually "ticks", and it is useful to know "how many > > ticks between X and Y" for things like making makefiles work. > > Do you mean for dependencies? They would work just as well if > the filesystem stored accurate time information (although fs size > might increase). :) Make dependencies. In effect, if you create an object at the same second as the source was modified, you may be hurt. This is a practical impossibility, for all but machine generated source files. For those, the penalty is that when you type "make" again, an unnecessary compilation of an object may occur to make it "at least one second older". The FS layout is not permitted to change; that's one of our major constraints. Can you imagine "well, we converted 98% of your hard drive, but you don't have room for these new indows here...."? > Of course, any system trusting time data to store ordering > information is subject to the timer's resolution. Ideally, the > filesystem needs to provide an alternate way of storing this > information. On-or-after laways works, and would result only in extra builds. If your builds are subsecond, what do you care? 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 22:53:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04026 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 22:53:17 -0700 (PDT) (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 SMTP id WAA04020 for ; Sat, 15 Aug 1998 22:53:12 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA32709; Sun, 16 Aug 1998 14:51:26 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA22229; Sun, 16 Aug 1998 15:00:45 +0900 (JST) Message-Id: <199808160600.PAA22229@zodiac.mech.utsunomiya-u.ac.jp> To: Andreas Dobloug Cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: video mode switching is only partially supported In-Reply-To: Your message of "15 Aug 1998 23:20:24 +0200." References: <199808151326.NAA01735@word.smith.net.au> Date: Sun, 16 Aug 1998 15:00:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >* Mike Smith >| > | You've booted in a nonstandard video mode. There may be a BIOS option >| > I've got an Asus P2B-DS. Has anybody else on this list got this card >| > and know which option (if any) which fixes this? >| Which BIOS? Probably AWARD, in which case it'll be in the "BIOS >| Feature Setup" screen. If you can't find it, it's either not there or >| you shouldn't be using a PC. 8) > >Yes, it's an AWARD-bios. Believe me: I've tried all tried all the >options regarding the display-card before I posted here :-). The only >thing I cand find in the "BIOS Feature Setup" which has anything to do >with the video-card is 'Video ROM BIOS Shadow' (yep, I've tried >switching it off) and 'PCI/VGA Palette Snoop' which doesn't agree with >my monitor. The 'Standard CMOS Setup' screen has got a field called >'Video', but the field always comes up with 'EGA/VGA' after saving the >settings to the bios. Guess I have to choose between running X or a >console :-). > >-- >Andreas Dobloug : email: andreasd@ifi.uio.no You don't need to worry too much about this "video mode switching is only partially supported" message, so long as you are using the standard 80x25 text mode in the console. The thing is that the syscons driver finds the video mode table in your card's BIOS is not organized the way it can understand. Therefore, syscons cannot switch to some video modes, such as EGA 80x43 and graphics modes for which syscons needs parameters from BIOS. The message does NOT mean that your card does not support mode switching. It is syscons which finds it difficult. There currently is no way to force syscons to switch video modes when it prints the above message. But, even if you see the above message, you should still be able to use VGA 80x25, VGA 80x30, VGA 80x50, VGA 80x60 (you need to load 8x8 font for the latter two modes, though). AND, you should have no trouble running the X server (if it supports your card), because the X server directly manipulates video hardware and needs little assistance from syscons when switching to a graphics mode. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 23:15:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05273 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 23:15:49 -0700 (PDT) (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 XAA05267; Sat, 15 Aug 1998 23:15:47 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id AAA02488; Sun, 16 Aug 1998 00:09:29 -0600 (MDT) Date: Sun, 16 Aug 1998 00:09:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808160609.AAA02488@narnia.plutotech.com> To: sos@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. Newsgroups: pluto.freebsd.hackers In-Reply-To: <199808151902.VAA08482@sos.freebsd.dk> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808151902.VAA08482@sos.freebsd.dk> you wrote: > >> For what it's worth, I don't see much value in treating ATA disks as >> though they were SCSI disks; the overhead in translation is probably >> too high. On the other hand, I'm less sure about things that use the >> ATAPI packet protocol. > > The ATA driver with lowlevel ATAPI support _must_ be implemented in > all cases, the difference is if the ATAPI device are registered under > CAM (scsi) or if there are nataive ATAPI drivers instead. I don't understand why everyone has this misconception. CAM != SCSI. CAM is primarily a transaction routing service. As such, most of CAM is oblivious to the format of the transactions it routes. You could route raw ATAPI or ATA commands or whatever you desire, by adding new function codes and CCB definitions. Whether ATAPI or ATA devices under CAM would talk in terms of SCSI is up to the implementor, it is not mandated by CAM. Essentially what moving ATAPI and/or ATA to CAM would buy you is a common registration/timeout/error handling framework that corrects many of the defects that are inherent in the current SCSI code (and perhaps replicated elsewhere??). If it makes sense for the ATAPI peripheral and controller drivers to talk in terms of SCSI commands, feel free to implement it that way. If not, don't, but whatever you do, don't argue that the reason the code isn't under the CAM framework is because it forces your hand towards a particular communication scheme. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 15 23:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05864 for freebsd-hackers-outgoing; Sat, 15 Aug 1998 23:28:43 -0700 (PDT) (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 XAA05859 for ; Sat, 15 Aug 1998 23:28:39 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA02059; Sat, 15 Aug 1998 23:28:08 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd002041; Sat Aug 15 23:28:02 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id XAA06454; Sat, 15 Aug 1998 23:27:56 -0700 (MST) From: Terry Lambert Message-Id: <199808160627.XAA06454@usr08.primenet.com> Subject: Re: 64-bit time_t To: ac199@hwcn.org Date: Sun, 16 Aug 1998 06:27:56 +0000 (GMT) Cc: tlambert@primenet.com, grog@lemis.com, mph@pobox.com, brawley@camtech.com.au, hackers@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Aug 15, 98 07:19:50 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 difference between accuracy and precision is often hard to grasp. > > Actually, it's high-school science, now. At least around here. :) In the US, people graduate high school not knowing how to read. It's hard for me to believe people could grasp something they couldn't read. 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