From owner-freebsd-hackers Sun Jun 25 0: 3:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id F0D3937B5D2; Sun, 25 Jun 2000 00:03:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA19355; Sun, 25 Jun 2000 01:02:54 -0600 (MDT) (envelope-from ken) Date: Sun, 25 Jun 2000 01:02:54 -0600 From: "Kenneth D. Merry" To: Nat Lanza Cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SCSI HBA device detection? Message-ID: <20000625010254.A19247@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from magus@cs.cmu.edu on Fri, Jun 23, 2000 at 01:10:26PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 23, 2000 at 13:10:26 -0400, Nat Lanza wrote: > I'm writing a SCSI HBA driver that simulates a bus with some > ramdisk-backed disks attached to it. I've read through the HBA > tutorial in Daemon News, but I'm still unsure how to tell the system > about my pretend disk devices. I suspect part of the problem is that > I don't actually have real devices or a real IO bus. > > Anyone feel like explaining this? Well, when the system boots, it sends out a SCSI INQUIRY command to each target on each bus. Each target that responds and sends back inquiry data will get further along in the probe process. The same thing happens when you do 'camcontrol rescan 4' to rescan SCSI bus 4. You need to have your "disks" respond to the inquiry command with inquiry data, as well as have them respond suitably to the various other commands that CAM will send. The commands you'll need to support include (but are not limited to), inquiry, test unit ready, read capacity, read (6, 10 and maybe 12 byte), write (6, 10 and maybe 12 byte) and perhaps mode sense. Those commands will probably get you most of the way towards probing and attaching with the da(4) driver. Another alternative to a ramdisk-like driver is a target mode driver. There is a target mode processor target device in sys/cam/scsi/scsi_target.c that you can look at as an example. You'd be limited to the SCSI bus speed (40, 80, 160MB/sec) for throughput though. You'll need specific hardware (Adaptec or QLogic) to do it as well. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 0:47:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 0351137B794 for ; Sun, 25 Jun 2000 00:47:20 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 136789-0008Nu-00; Sun, 25 Jun 2000 14:47:01 +0700 Date: Sun, 25 Jun 2000 14:47:00 +0700 (ALMST) From: Boris Popov To: Chuck Robey Cc: FreeBSD Hackers List Subject: Re: disassembling 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 Sun, 25 Jun 2000, Chuck Robey wrote: > Is there any tools whatever (free or commercial) that does disassembly on > FreeBSD obj's AND will show you the C line and the code that the C line > caused to be assembled? Yes, you can do it with the objdump utility which is in the base system. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 0:54:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 097F937B7C9 for ; Sun, 25 Jun 2000 00:54:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA63002; Sun, 25 Jun 2000 01:54:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA09841; Sun, 25 Jun 2000 01:52:34 -0600 (MDT) Message-Id: <200006250752.BAA09841@harmony.village.org> To: Chuck Robey Subject: Re: disassembling Cc: FreeBSD Hackers List In-reply-to: Your message of "Sun, 25 Jun 2000 00:19:35 EDT." References: Date: Sun, 25 Jun 2000 01:52:34 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Is there any tools whatever (free or commercial) that does disassembly on : FreeBSD obj's AND will show you the C line and the code that the C line : caused to be assembled? Yes. man objdump. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 3: 8: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 988B937B806 for ; Sun, 25 Jun 2000 03:07:57 -0700 (PDT) (envelope-from bains@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id PAA21979 for ; Sun, 25 Jun 2000 15:36:37 +0530 (IST) Received: from sassun8.sasi.com ([10.0.0.8]) by sasi.com; Sun, 25 Jun 2000 15:36:36 +0000 (IST) Received: from sassun8.sasi.com (sassun8.sasi.com [10.0.0.8]) by sassun8.sasi.com (8.9.1/8.9.1) with ESMTP id PAA26099 for ; Sun, 25 Jun 2000 15:36:29 +0530 (IST) Date: Sun, 25 Jun 2000 15:36:29 +0530 (IST) From: Shail Bains To: hackers@FreeBSD.ORG In-Reply-To: <20000625010254.A19247@panzer.kdm.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 unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 3:40:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 360DD37B636 for ; Sun, 25 Jun 2000 03:40:43 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (189.pool4.ipctokyo.att.ne.jp [165.76.42.189]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id TAA11011; Sun, 25 Jun 2000 19:40:41 +0900 (JST) Date: Sun, 25 Jun 2000 19:40:44 +0900 Message-ID: <86pup6qc0j.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: freebsd-hackers@FreeBSD.ORG Subject: VM coloring description in NOTES X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. ** this discussion is for i386 architectures ** I think there is some unclearness on the description about VM subsystem coloring in NOTES (formerly called LINT). Currently, # Options for the VM subsystem #options PQ_NOOPT # No coloring options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache #options PQ_MEDIUMCACHE # color for 64k/16k cache #options PQ_NORMALCACHE # color for 256k/16k cache But, in /sys/vm/vm_page.h, PQ_PRIME1, PQ_PRIME2, PQ_L2_SIZE are defined as below. PQ_NOOPT defines 1/1/1 to disable coloring PQ_LARGECACHE defines 31/23/128 for 512k cache PQ_HUGECACHE defines 31/23/256 for 1M cache PQ_MEDIUMCACHE defines 13/7/64 for 256k cache PQ_NORMALCACHE defines 5/3/16 for 64k cache and, on the default, these parameters are defined as 9/5/32. NOTES has obviously incorrect description about MEDIUM and NORMAL case, and there are no discription about the default coloring. Yes, this situation arise from its incomprehensive name. I suggest that these options should be renamed as follows: currently -> candidate PQ_HUGECACHE PQ_CACHE1024 PQ_LARGECACHE PQ_CACHE512 PQ_MEDIUMCACHE PQ_CACHE256 PQ_NORMALCACHE PQ_CACHE64 and newly PQ_CACHE128 should be defined as default. Any ideas? -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 4:43:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 21B8A37B8E5 for ; Sun, 25 Jun 2000 04:43:14 -0700 (PDT) (envelope-from Meerwaldt@t-online.de) Received: from fwd00.sul.t-online.com by mailout06.sul.t-online.com with smtp id 136Aoi-0007X8-04; Sun, 25 Jun 2000 13:43:12 +0200 Received: from server.wes.mee.com (320044045192-0001@[193.158.179.146]) by fwd00.sul.t-online.com with esmtp id 136Aob-02IAHhC; Sun, 25 Jun 2000 13:43:05 +0200 Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id NAA00891; Sun, 25 Jun 2000 13:01:06 +0200 (CEST) Date: Sun, 25 Jun 2000 13:01:06 +0200 (CEST) From: Meerwaldt@t-online.de (Frederik Meerwaldt) Reply-To: fm_sendthere@gmx.de To: Shail Bains Cc: hackers@freebsd.org Subject: Re: your mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320044045192-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Ever read the bottom of the mails?? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Regardsm Freddy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 7:47:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A0BDC37B5DC; Sun, 25 Jun 2000 07:47:50 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA12211; Sun, 25 Jun 2000 16:47:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "clemensF" Cc: Marius Bendiksen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: sys/ufs/ufs/ufs_quota.c In-reply-to: Your message of "Sun, 25 Jun 2000 00:18:40 +0200." <20000625001840.A1017@spotteswoode.de> Date: Sun, 25 Jun 2000 16:47:39 +0200 Message-ID: <12209.961944459@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000625001840.A1017@spotteswoode.de>, "clemensF" writes: >> Marius Bendiksen: > >> the various quota routines, rather than a (struct proc *). As I can see >> >from the code, chkdq(), for example, should rather be using an suser() >> check upon a process structure, than testing cred->cr_uid==0. Are there >> any objections to changing this? > >this should be more portable and future-save, right? Isn't there an issue with NFS server side ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 8:54:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from daemon.sofiaonline.com (daemon.sofiaonline.com [212.5.144.1]) by hub.freebsd.org (Postfix) with SMTP id 06CB537BB5C for ; Sun, 25 Jun 2000 08:53:34 -0700 (PDT) (envelope-from sofia@sofiaonline.com) Received: (qmail 11606 invoked from network); 25 Jun 2000 15:48:06 -0000 Received: from carnivoro.sofiaonline.com (212.5.144.5) by daemon.sofiaonline.com with SMTP; 25 Jun 2000 15:48:06 -0000 Date: Sun, 25 Jun 2000 16:59:04 +0300 (EEST) From: dungeonkeeper To: freebsd-net@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Measuring network-protocol implementation's performance 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 there, Recently we started implementing specific network protocols support code here. As a part of this process I would like to have the ability to measure the performance of the code and probably find a way to improve its speed once we have a working version. I would like to ask if somebody could point me to some article/documentation/etc about such methods? Best Regards: Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 9: 2:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id CFE9437B81C for ; Sun, 25 Jun 2000 09:02:17 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA26623; Sun, 25 Jun 2000 12:00:41 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 25 Jun 2000 12:00:40 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: FreeBSD Hackers List Subject: Re: disassembling In-Reply-To: <200006250752.BAA09841@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 Sun, 25 Jun 2000, Warner Losh wrote: > In message Chuck Robey writes: > : Is there any tools whatever (free or commercial) that does disassembly on > : FreeBSD obj's AND will show you the C line and the code that the C line > : caused to be assembled? > > Yes. man objdump. Thanks (also to Boris Popov), I didn't realize objdump would do that. I'd used disassembly before, with line number, but I hadn't seen that -S option. Just what I needed. > > Warner > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 10:12:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f53.law9.hotmail.com [64.4.9.53]) by hub.freebsd.org (Postfix) with SMTP id 2FDED37B6DD for ; Sun, 25 Jun 2000 10:12:26 -0700 (PDT) (envelope-from gerald_stoller@hotmail.com) Received: (qmail 15344 invoked by uid 0); 25 Jun 2000 17:12:23 -0000 Message-ID: <20000625171223.15343.qmail@hotmail.com> Received: from 209.246.86.55 by www.hotmail.com with HTTP; Sun, 25 Jun 2000 10:12:22 PDT X-Originating-IP: [209.246.86.55] From: "gerald stoller" To: dnelson@emsphone.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Passing values between shell-variables Date: Sun, 25 Jun 2000 13:12:22 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson resonded on Thu, 22 Jun 2000 17:42:37 -0500 with >In the last episode (Jun 22), gerald stoller said: > > I want to take an integer value from one shell-variable and pass > > a modified value to another shell-variable. First I tried setint_v > > (after using local to get tbl structures for the two shell-variables) > > and second I tried various forms of the var.c functions intval & > > setint . To see if things worked, I print the shell-variable (to > > which I assigned a value) afterwards, but neither path seems to have > > succeeded. I may try getint next, and also make my tests more basic, > > but if anyone could give me a good hint, I'd appreciate it. > > One thing that puzzles me is can be illustrated by the following >code: > > struct tbl *var1 ; > > int val1 ; > > > > var1 = local( "LINENO" , FALSE ) ; > > getint( var1 , &val1 ) ; > > printf( "%d %d\n" , var1->val.i , val1 ) ; > > which gives differing values in the two fields (the val1 value appears >to > > be correct). Isn't val.i (from struct tbl ) where the integer (or is >it > > floating point?, but it is declared long ) is stored? > > Please send a response directly to me, my bulk-mail folder is > > over-stuffed. > >I'm not sure what local() and getint() are, since you didn't include >the source to them, but you should probably be using the getenv() and >putenv() functions to read environment variables. > >-- > Dan Nelson > dnelson@emsphone.com Sorry for leaving out info; local() and getint() are functions in the file var.c of pdksh as is setint_v() , which I also tried. I am using version 3.3 . struct tbl is a structure defined in the file table.h of pdksh . Probably soon I will upgrade to version 4.1 or so. I want to be able to work with general variables, not only environment variables, so I don't feel that getenv() & putenv() are the way to go. ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 11:14:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 6357C37BC6F; Sun, 25 Jun 2000 11:14:18 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id UAA86902; Sun, 25 Jun 2000 20:14:13 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id UAA99073; Sun, 25 Jun 2000 20:14:12 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Sun, 25 Jun 2000 20:14:12 +0200 (CEST) From: Marius Bendiksen To: Poul-Henning Kamp Cc: clemensF , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: sys/ufs/ufs/ufs_quota.c In-Reply-To: <12209.961944459@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cred->cr_uid==0] > >this should be more portable and future-save, right? > Isn't there an issue with NFS server side ? There might be. I have not looked at the NFS code. However, offhand, I do not see any reason why this should be the case, except for bugs in the code, given that any requrest with uid 0 should, at the moment, have Super powers anyway. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 12: 7:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 42A9537B641 for ; Sun, 25 Jun 2000 12:07:17 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.geekhouse.net [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id MAA41818; Sun, 25 Jun 2000 12:07:22 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id MAA03026; Sun, 25 Jun 2000 12:07:38 -0700 (PDT) (envelope-from john) Message-Id: <200006251907.MAA03026@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86pup6qc0j.wl@tkc.att.ne.jp> Date: Sun, 25 Jun 2000 12:07:38 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Motomichi Matsuzaki Subject: RE: VM coloring description in NOTES Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jun-00 Motomichi Matsuzaki wrote: > > Hi. > > ** this discussion is for i386 architectures ** > > I think there is some unclearness on the description > about VM subsystem coloring in NOTES (formerly called LINT). > > Currently, > ># Options for the VM subsystem >#options PQ_NOOPT # No coloring > options PQ_LARGECACHE # color for 512k/16k cache >#options PQ_HUGECACHE # color for 1024k/16k cache >#options PQ_MEDIUMCACHE # color for 64k/16k cache >#options PQ_NORMALCACHE # color for 256k/16k cache > > > But, in /sys/vm/vm_page.h, PQ_PRIME1, PQ_PRIME2, PQ_L2_SIZE are > defined as below. > > PQ_NOOPT defines 1/1/1 to disable coloring > PQ_LARGECACHE defines 31/23/128 for 512k cache > PQ_HUGECACHE defines 31/23/256 for 1M cache > PQ_MEDIUMCACHE defines 13/7/64 for 256k cache > PQ_NORMALCACHE defines 5/3/16 for 64k cache > > and, on the default, these parameters are defined as 9/5/32. > > NOTES has obviously incorrect description about MEDIUM and NORMAL > case, and there are no discription about the default coloring. > > Yes, this situation arise from its incomprehensive name. > I suggest that these options should be renamed as follows: > > currently -> candidate > PQ_HUGECACHE PQ_CACHE1024 > PQ_LARGECACHE PQ_CACHE512 > PQ_MEDIUMCACHE PQ_CACHE256 > PQ_NORMALCACHE PQ_CACHE64 > > and newly PQ_CACHE128 should be defined as default. > > Any ideas? Sounds ok to me. Do you have any patches for this? If not, I'll make some and see if they pass muster. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 12:52:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 4631E37B843 for ; Sun, 25 Jun 2000 12:52:06 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA17586; Sun, 25 Jun 2000 15:51:30 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sun, 25 Jun 2000 15:52:03 -0400 To: Chuck Robey , From: Garance A Drosihn Subject: RE: libc_r/_read(), should the errno be reset to 0? Cc: , , hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:28 AM -0400 6/25/00, Chuck Robey wrote: >On Fri, 23 Jun 2000, Bohne, Peter wrote: > > > True enough. That's the best advice. However, your original > > post indicated an expectation on your part that errno would > > be somehow automatically reset to 0 before a system call, which > > is definitely *not* the case. You have to clear it - the kernel > > does not do it for you. > >Why would you bother to clear it? You don't check errno to determine >fail/success, you check the function return. If it returns fail, then >errno is going to be correct whether or not you bothered to reset it or >not. Setting it to zero might give you a warm fuzzy feeling, but if >you're correctly detected errors, it's not going to change anything. There are times when clearing errno is significant. What you said is correct for the routine which actually calls the system routine (is it some *_read() routine here?), but some library routines will call several system routines, and only return an error to caller (of that library routine) in some cases. For instance, it might stat() some file, which sets errno if that file does not exist. To the library routine, it isn't really an error if that file does not exist, it just creates the file or perhaps skips over some optional processing. Later on, it may return an error due to some OTHER condition, a condition which did not set errno. Someone checking errno will think that "file does not exist" is the problem, when the problem is elsewhere. As usual with this topic, I can never remember a good example of this, except that I know I've run into it on some occasions... For those occasions, it IS important to zero out errno "at the right place" (wherever that might be...). One of these days I'll have the presence of mind to save a good example of this... Please note that I'm not saying the system routine should necessarily set errno to zero, I'm just saying that there ARE occasions where it IS important for the programmer to reset it to zero before calling some other routines. In those situations, it does much more than just giving someone a "warm and fuzzy" feeling. --- Garance Alistair Drosehn = gad@eclipse.acs.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 Sun Jun 25 13: 4: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 1543237BCE3; Sun, 25 Jun 2000 13:03:48 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (173.pool5.tokyo.att.ne.jp [165.76.22.188]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id FAA26483; Mon, 26 Jun 2000 05:03:46 +0900 (JST) Date: Mon, 26 Jun 2000 05:03:45 +0900 Message-ID: <86og4pr0im.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: jhb@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: VM coloring description in NOTES In-Reply-To: In your message of "Sun, 25 Jun 2000 12:07:38 -0700 (PDT)" <200006251907.MAA03026@john.baldwin.cx> References: <86pup6qc0j.wl@tkc.att.ne.jp> <200006251907.MAA03026@john.baldwin.cx> X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 25 Jun 2000 12:07:38 -0700 (PDT), John Baldwin wrote: > Sounds ok to me. Do you have any patches for this? If not, > I'll make some and see if they pass muster. I have no patches. I would put it in your hands. Thank you. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 13:23:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C93BA37B5BE; Sun, 25 Jun 2000 13:23:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA23359; Sun, 25 Jun 2000 13:23:27 -0700 (PDT) (envelope-from dillon) Date: Sun, 25 Jun 2000 13:23:27 -0700 (PDT) From: Matthew Dillon Message-Id: <200006252023.NAA23359@apollo.backplane.com> To: John Baldwin Cc: Motomichi Matsuzaki , freebsd-hackers@FreeBSD.ORG Subject: Re: RE: VM coloring description in NOTES References: <200006251907.MAA03026@john.baldwin.cx> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> PQ_HUGECACHE PQ_CACHE1024 :> PQ_LARGECACHE PQ_CACHE512 :> PQ_MEDIUMCACHE PQ_CACHE256 :> PQ_NORMALCACHE PQ_CACHE64 :> :> and newly PQ_CACHE128 should be defined as default. :> :> Any ideas? : :Sounds ok to me. Do you have any patches for this? If not, :I'll make some and see if they pass muster. : :-- : :John Baldwin -- http://www.FreeBSD.org/~jhb/ I haven't worked any up. If you work up a set of patches I'll do a once-over and a quick test of them if you want, or you can and commit them straight. There being no operational changes I wouldn't expect any problems. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 13:40:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id E7CEA37B7C4 for ; Sun, 25 Jun 2000 13:40:39 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id PAA04864; Sun, 25 Jun 2000 15:40:35 -0500 (CDT) (envelope-from dan) Date: Sun, 25 Jun 2000 15:40:35 -0500 From: Dan Nelson To: gerald stoller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Passing values between shell-variables Message-ID: <20000625154035.A2263@dan.emsphone.com> References: <20000625171223.15343.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.4i In-Reply-To: <20000625171223.15343.qmail@hotmail.com>; from "gerald stoller" on Sun Jun 25 13:12:22 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 25), gerald stoller said: > Sorry for leaving out info; local() and getint() are functions > in the file var.c of pdksh as is setint_v() , which I also tried. I > am using version 3.3 . struct tbl is a structure defined in the file > table.h of pdksh . Probably soon I will upgrade to version 4.1 or > so. I want to be able to work with general variables, not only > environment variables, so I don't feel that getenv() & putenv() are > the way to go. So what you're really doing is modifying the pdksh source, maybe adding a command or something? You should be asking a ksh developers list then. -- 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 Sun Jun 25 17:38:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8905637B5A7 for ; Sun, 25 Jun 2000 17:38:38 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA29636; Sun, 25 Jun 2000 20:35:56 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 25 Jun 2000 20:35:55 -0400 (EDT) From: Chuck Robey To: Garance A Drosihn Cc: Peter.Bohne@hboc.com, fengyue@bluerose.windmoon.nu, andrew@ugh.net.au, hackers@FreeBSD.ORG Subject: RE: libc_r/_read(), should the errno be reset to 0? 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 Sun, 25 Jun 2000, Garance A Drosihn wrote: > At 12:28 AM -0400 6/25/00, Chuck Robey wrote: > >On Fri, 23 Jun 2000, Bohne, Peter wrote: > > > > > True enough. That's the best advice. However, your original > > > post indicated an expectation on your part that errno would > > > be somehow automatically reset to 0 before a system call, which > > > is definitely *not* the case. You have to clear it - the kernel > > > does not do it for you. > > > >Why would you bother to clear it? You don't check errno to determine > >fail/success, you check the function return. If it returns fail, then > >errno is going to be correct whether or not you bothered to reset it or > >not. Setting it to zero might give you a warm fuzzy feeling, but if > >you're correctly detected errors, it's not going to change anything. > > There are times when clearing errno is significant. What you said is > correct for the routine which actually calls the system routine (is it > some *_read() routine here?), but some library routines will call > several system routines, and only return an error to caller (of that > library routine) in some cases. > > For instance, it might stat() some file, which sets errno if that > file does not exist. To the library routine, it isn't really an > error if that file does not exist, it just creates the file or > perhaps skips over some optional processing. Later on, it may > return an error due to some OTHER condition, a condition which > did not set errno. Someone checking errno will think that "file > does not exist" is the problem, when the problem is elsewhere. > > As usual with this topic, I can never remember a good example of > this, except that I know I've run into it on some occasions... If there is an example, tell me and I'll fix it. I can't comment, Garance, on a nebulous "I know it's out there somewhere" type of reply. I know how it's supposed to work, and how it does in all cases I've seen. Anyone who knows of an exception, bail Garance out here. Context is, a system call that requires setting errno to zero before making the call in order to get a correct error return. Fair enough, Garance? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 18:18:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 275D837B60D; Sun, 25 Jun 2000 18:17:55 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from gateway.posi.net (user-33qtkm5.dialup.mindspring.com [199.174.210.197]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA27785; Sun, 25 Jun 2000 21:17:50 -0400 (EDT) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id SAA01680; Sun, 25 Jun 2000 18:17:44 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Sun, 25 Jun 2000 18:17:43 -0700 (PDT) From: Kelly Yancey To: John Baldwin Cc: Motomichi Matsuzaki , freebsd-hackers@FreeBSD.ORG Subject: RE: VM coloring description in NOTES In-Reply-To: <200006251907.MAA03026@john.baldwin.cx> 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, 25 Jun 2000, John Baldwin wrote: > > currently -> candidate > > PQ_HUGECACHE PQ_CACHE1024 > > PQ_LARGECACHE PQ_CACHE512 > > PQ_MEDIUMCACHE PQ_CACHE256 > > PQ_NORMALCACHE PQ_CACHE64 > > > > and newly PQ_CACHE128 should be defined as default. > > > > Any ideas? > > Sounds ok to me. Do you have any patches for this? If not, > I'll make some and see if they pass muster. > John, I've actually got something similar I worked up a while back on my local machine. It's not exactly the same (you set PQ_CACHESIZE to the value of your L2 cache as opposed to having multiple #defines/config options). I just cleaned it up and added backward-compatibility with the pre-existing PQ_ options so as to not break anyone's config files. :) Patches are attached below. I can only say that they've been working on my 4.0-STABLE machines for a few weeks. Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ --- sys/vm/vm_page.h.orig Sun Jun 25 17:52:37 2000 +++ sys/vm/vm_page.h Sun Jun 25 18:13:45 2000 @@ -150,46 +150,51 @@ */ /* Each of PQ_FREE, and PQ_CACHE have PQ_HASH_SIZE entries */ -/* Define one of the following */ +/* Backward compatibility for existing PQ_*CACHE config options. */ +#if !defined(PQ_CACHESIZE) #if defined(PQ_HUGECACHE) +#define PQ_CACHESIZE 1024 +#elsif defined(PQ_LARGECACHE) +#define PQ_CACHESIZE 512 +#elsif defined(PQ_MEDIUMCACHE) +#define PQ_CACHESIZE 256 +#elsif defined(PQ_NORMALCACHE) +#define PQ_CACHESIZE 64 +#else +#define PQ_CACHESIZE 0 +#endif +#endif + +#if PQ_CACHESIZE >= 1024 #define PQ_PRIME1 31 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_PRIME2 23 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_L2_SIZE 256 /* A number of colors opt for 1M cache */ -#endif -/* Define one of the following */ -#if defined(PQ_LARGECACHE) +#elsif PQ_CACHESIZE >= 512 #define PQ_PRIME1 31 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_PRIME2 23 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_L2_SIZE 128 /* A number of colors opt for 512K cache */ -#endif +#elsif PQ_CACHESIZE >= 256 +#define PQ_PRIME1 13 /* Prime number somewhat less than PQ_HASH_SIZE */ +#define PQ_PRIME2 7 /* Prime number somewhat less than PQ_HASH_SIZE */ +#define PQ_L2_SIZE 64 /* A number of colors opt for 256K cache */ -/* - * Use 'options PQ_NOOPT' to disable page coloring - */ -#if defined(PQ_NOOPT) -#define PQ_PRIME1 1 -#define PQ_PRIME2 1 -#define PQ_L2_SIZE 1 -#endif +#elsif PQ_CACHESIZE >= 128 +#define PQ_PRIME1 9 /* Produces a good PQ_L2_SIZE/3 + PQ_PRIME1 */ +#define PQ_PRIME2 5 /* Prime number somewhat less than PQ_HASH_SIZE */ +#define PQ_L2_SIZE 32 /* A number of colors opt for 128k cache */ -#if defined(PQ_NORMALCACHE) +#elsif PQ_CACHESIZE >= 64 #define PQ_PRIME1 5 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_PRIME2 3 /* Prime number somewhat less than PQ_HASH_SIZE */ #define PQ_L2_SIZE 16 /* A reasonable number of colors (opt for 64K cache) */ -#endif -#if defined(PQ_MEDIUMCACHE) -#define PQ_PRIME1 13 /* Prime number somewhat less than PQ_HASH_SIZE */ -#define PQ_PRIME2 7 /* Prime number somewhat less than PQ_HASH_SIZE */ -#define PQ_L2_SIZE 64 /* A number of colors opt for 256K cache */ -#endif +#else +#define PQ_PRIME1 1 /* Disable page coloring. */ +#define PQ_PRIME2 1 +#define PQ_L2_SIZE 1 -#if !defined(PQ_L2_SIZE) -#define PQ_PRIME1 9 /* Produces a good PQ_L2_SIZE/3 + PQ_PRIME1 */ -#define PQ_PRIME2 5 /* Prime number somewhat less than PQ_HASH_SIZE */ -#define PQ_L2_SIZE 32 /* 512KB or smaller, 4-way set-associative cache */ #endif #define PQ_L2_MASK (PQ_L2_SIZE - 1) --- sys/conf/options.orig Sun Jun 25 18:08:22 2000 +++ sys/conf/options Sun Jun 25 18:14:11 2000 @@ -364,6 +364,7 @@ PQ_MEDIUMCACHE opt_vmpage.h PQ_LARGECACHE opt_vmpage.h PQ_HUGECACHE opt_vmpage.h +PQ_CACHESIZE opt_vmpage.h # Standard SMP options SMP opt_global.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 19:40:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 1185837B567 for ; Sun, 25 Jun 2000 19:40:22 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA02016; Sun, 25 Jun 2000 19:40:03 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3956C282.AD89DD0C@gorean.org> Date: Sun, 25 Jun 2000 19:40:02 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0603 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Nicole Harrington." Cc: Luigi Rizzo , hackers@FreeBSD.ORG Subject: Re: How many files can I put in one diretory? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Nicole Harrington." wrote: > > On 22-Jun-00 Luigi Rizzo wrote: > >> > >> Hello > >> I have a user who needs to store a large amount of small html files. Like > >> around 2 million... > > > > that sounds insane! Because a name is a name, why dont they call > > those files xx/yy/zz/tt.html and the like, to get down to a more > > reasonable # of files per directory. > > > > Well.. Yea that's the idea.. But what is a reasonable number? 10K 100K etc. I heard 10k a while back from several sources I considered reliable. I've always stuck to that limit and never had a problem on freebsd or sun. I've also had very good luck with a hashed directory structure, such as: /a/b/c/abcfile The level of hashing, and the number of characters per level can be determined by your expected number of files, naming schemes, etc. Good luck, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 25 21: 3:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3AA2F37B6E5 for ; Sun, 25 Jun 2000 21:02:59 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA427042; Mon, 26 Jun 2000 00:02:34 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Mon, 26 Jun 2000 00:03:04 -0400 To: Chuck Robey From: Garance A Drosihn Subject: RE: libc_r/_read(), should the errno be reset to 0? Cc: Peter.Bohne@hboc.com, fengyue@bluerose.windmoon.nu, andrew@ugh.net.au, hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:35 PM -0400 6/25/00, Chuck Robey wrote: >On Sun, 25 Jun 2000, Garance A Drosihn wrote: > > > At 12:28 AM -0400 6/25/00, Chuck Robey wrote: > > > Why would you bother to clear it? You don't check errno to > > > determine fail/success, you check the function return. If it > > > returns fail, then errno is going to be correct whether or not > > > you bothered to reset it or not. > > > > There are times when clearing errno is significant. What you said is > > correct for the routine which actually calls the system routine (is it > > some *_read() routine here?), but some library routines will call > > several system routines, and only return an error to caller (of that > > library routine) in some cases. > > > > As usual with this topic, I can never remember a good example of > > this, except that I know I've run into it on some occasions... > >If there is an example, tell me and I'll fix it. I can't comment, >Garance, on a nebulous "I know it's out there somewhere" type of >reply. I know how it's supposed to work, and how it does in all >cases I've seen. > >Anyone who knows of an exception, bail Garance out here. Context >is, a system call that requires setting errno to zero before making >the call in order to get a correct error return. > >Fair enough, Garance? Almost. The thing is, I am almost certain I *have* had this same conversation before in a freebsd mailing list. While looking for whatever that conversation was, I came across the thread you get if you search freebsd-current for: Bogus errno twiddling by lstat I said "almost", because it's not just system calls which fiddle around with errno. I may have missed the original context of the current thread, but my vague hand-waving memory was not limiting itself to system calls. From the earlier thread in freebsd-current, for instance, there was a message from Bill Fenner which said: Someone else wrote: > So the question becomes: "At what point can I expect a > library routine to behave like a system call"? When it's documented to do so. > I *thought* that there were some ISO/POSIX requirements > that errno not be touched in non-error cases ISO/ANSI C says that library functions may modify errno unless the standard says otherwise. The standard says otherwise for at least the math functions, which set errno to things like EDOM and ERANGE or leave it alone if no error occurred, and the calling sequence errno = 0; y = asin(x); if (errno == EDOM) { ... } is meant to work in that situation. However, normal library functions are explicitly allowed to modify errno even if no error occurs. Note that in this case you would have to explicitly set errno before calling the library routine, if you wanted to check errno after calling the library routine. That's all I was saying (although this thread isn't the one I remember having earlier). The above message seems to be in reply to Terry Lambert, who gave some other examples. In reviewing the whole thread, my basic impression is that errno is a mechanism that no one particularly likes, but no one has come up with a replacement for, either. I don't know how much things have changed since that thread (June 1998). This isn't quite the situation I was trying to remember, but it will do good enough that I can go home now without feeling like I am merely ducking the question... :-) --- Garance Alistair Drosehn = gad@eclipse.acs.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 Mon Jun 26 1:17:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (ppp-179.dialup.clari.net.au [203.57.253.179]) by hub.freebsd.org (Postfix) with ESMTP id 97CE437B9EE for ; Mon, 26 Jun 2000 01:17:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id BAA00567; Mon, 26 Jun 2000 01:22:41 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200006260822.BAA00567@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lyndon Nerenberg Cc: freebsd-hackers@freebsd.org Subject: Re: Concurrent access to SMbus In-reply-to: Your message of "Mon, 05 Jun 2000 14:47:04 MDT." <200006052047.e55Kl5X51895@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jun 2000 01:22:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I notice that the /dev/smbX devices are exclusive access. This makes > it impossible to run two (or more) programs concurrently that want > to talk to SMbus devices (in my case, healthd and lmmon, both of which > want to open /dev/smb0 to access the LM78). > > Is this an SMbus restriction, or an artifact of the smb driver? I did a > very quick scan through /sys/dev/smbus/* and nothing jumped out to > indicate why it needs to be exclusive access. Transactions on the bus should be locked, ie. only one client talking at a time, but it should probably be feasible to allow more than one opener. The SMBus code is dearly in need of a maintainer. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 1:20: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (ppp-179.dialup.clari.net.au [203.57.253.179]) by hub.freebsd.org (Postfix) with ESMTP id 7772337BA61 for ; Mon, 26 Jun 2000 01:19:59 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id BAA00734; Mon, 26 Jun 2000 01:25:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200006260825.BAA00734@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: jmt@tbe.net Cc: freebsd-hackers@freebsd.org Subject: Re: APM problems on NEC Versa 2000C In-reply-to: Your message of "24 Jun 2000 14:12:53 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jun 2000 01:25:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an older 486 laptop which is newly running FreeBSD > 4.0-RELEASE. When I attempted to enable APM and reboot, I got the > following on my screen: > > --begin screen-- > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x58:0x337 > stack pointer = 0x10:0xc334dcdc > frame pointer = 0x10:0xc334dce0 > code segment = base 0xc00ea00, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 0, gran 0 > processor eflags = resume, IOPL = 0 > current process = 184 (apm) > interrupt mask = none > kernel: type 9 trap, code=0 > Stopped at 0x337: This is inside the APM BIOS - it's probably a BIOS bug that doesn't affect Windows/DOS. With such an old system, you are probably SOL unless you can track down more details (eg. special hacks for this system and Linux). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 1:42:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id A9FEB37BA2C for ; Mon, 26 Jun 2000 01:42:39 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JR20WWX4VG0005CX@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Mon, 26 Jun 2000 10:42:37 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Mon, 26 Jun 2000 10:42:36 +0100 Content-return: allowed Date: Mon, 26 Jun 2000 10:42:35 +0100 From: "Koster, K.J." Subject: RE: VM coloring description in NOTES To: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D76AF@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > currently -> candidate > > > PQ_HUGECACHE PQ_CACHE1024 > > > PQ_LARGECACHE PQ_CACHE512 > > > PQ_MEDIUMCACHE PQ_CACHE256 > > > PQ_NORMALCACHE PQ_CACHE64 > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in it that FreeBSD then proceeds to rediscover. Is there no way to whack the BIOS into submission and have it cough up the cache size? It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps it would be nice to have an interface to some of the more widely used bioses. I image you could pry all sorts of tuning information about the machine from its clammy little hands. Cache size, cache scheme, memory type. There were earlier comments on FreeBSD taking over the task of the BIOS. Food for thought. :-) Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 2:16:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 4284C37BD6E; Mon, 26 Jun 2000 02:16:23 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id IAA88204; Mon, 26 Jun 2000 08:25:30 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id TAA00516; Sun, 25 Jun 2000 19:52:03 GMT (envelope-from nik) Date: Sun, 25 Jun 2000 19:52:03 +0000 From: Nik Clayton To: doc@freebsd.org Cc: hackers@freebsd.org, jkh@freebsd.org, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@freebsd.org, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Documentation selection in sysinstall Message-ID: <20000625195203.C470@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Going to -doc where it's pertinent, -hackers where it might find someone who's prepared to do the work, and jkh for any expert commentary he feels like tossing in. And while I've got Jordan's attention -- did the last attempt at re-writing sysinstall generate any specification documents? If nothing else, they'd be useful content for the doc project. ] [ I didn't go through this at Usenix -- not enough time ] The documentation is now being built and made available as FreeBSD packages (one package per combination of document, language, and output format). This means we could do away with the "doc" distribution when installing FreeBSD, and instead allow the user to choose which documentation packages they want to install. In theory, this is a doddle. sysinstall already lets the user choose from packages to install. In practice, I think it's a little more difficult, because: 1. [ I haven't run the code to confirm this, not having a network connection at the moment. ] When you do the "post-install" configure via sysinstall, it wants to grab the INDEX file from somewhere (CDROM, the 'net, or whatever) in order to present you with an up-to-date list of packages to install. The doc package building doesn't work like that. There is no INDEX file for sysinstall to grok. We need to find some other way for sysinstall to get the list of docs, languages, and formats that are supported it. This shouldn't be too hard -- looking in /pub/FreeBSD/doc/packages on the FTP site gives a complete list of what's currently built in terms of languages and output formats, and the filenames are easily parseable. 2. We need to find a UI model that allows the user to efficiently select the language and formats they want to install. I'm thinking of initially presenting a dialog box that looks like this: ------------------------------------------------------------ Documentation is available in the following languages: English Spanish French Japanese Chinese ------------------------------------------------------------ with the list extending as necessary, based on what sysinstall found on the FTP site. After the user has chosen a language, then present them with a list like this: ------------------------------------------------------------ Now choose the documentation you would like to install, and the formats you would like to use. HTML HTML Text PS PDF PDB RTF Split Books Handbook [ ] [X] [ ] [ ] [ ] [ ] [ ] FAQ [X] [X] [ ] [ ] [ ] [ ] [ ] Porter's Handbook [ ] [ ] [ ] [X] [ ] [ ] [ ] [... and so on ...] ------------------------------------------------------------ From my reading of dialog(3) I believe this to be, uh, optimistic at best. I've also glossed over the issue of how sysinstall turns "porters-handbook" in a filename to "Porter's Handbook" on screen. Thinking about it, we will probably need an INDEX. file that maps filenames to titles -- we should be able to generate this when we build the packages by grabbing the first element from a document. The alternative to a display like this would seem to be a fairly horrendous nest of menus and sub-menus that the user would have to navigate through. That's about where I am in my thinking about this so far. Alternative viewpoints, suggestions, offers to do the work, and prototypes are gratefully received. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 2:34:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id C401737BCC7 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 02:34:35 -0700 (PDT) (envelope-from pmk@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id PAA12418 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 15:03:19 +0530 (IST) Received: from pcd134.sasi.com ([10.0.16.134]) by sasi.com; Mon, 26 Jun 2000 15:03:18 +0000 (IST) Received: from localhost (pmk@localhost) by pcd134.sasi.com (8.9.3/8.9.3) with ESMTP id PAA25559 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 15:03:11 +0530 X-Authentication-Warning: pcd134.sasi.com: pmk owned process doing -bs Date: Mon, 26 Jun 2000 15:03:10 +0530 (IST) From: Mohana Krishna Penumetcha <pmk@sasi.com> To: freebsd-hackers@FreeBSD.ORG Subject: PCI transaction ordering!!! In-Reply-To: <393EB0DD.B77711B4@ameslab.gov> Message-ID: <Pine.LNX.4.10.10006261442590.25550-100000@pcd134.sasi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, HP-UX device driver reference manual says, "The side-effects of any write are not guaranteed to happen immediately. Writes are posted; they will complete eventually" to make sure all writes are flushed from the queue, it suggests to perform a read operation. i would like to know if the above behaviour is same across all operating systems, esp if it is the same in FreeBSD case also?? Thanks, mohan Telecom R&D , FAC-D, SAS ph:- 5281461 x3078 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 6:42: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uosis.mif.vu.lt (uosis.mif.vu.lt [193.219.42.14]) by hub.freebsd.org (Postfix) with SMTP id EC71437B52A for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2000 06:41:55 -0700 (PDT) (envelope-from rn@uosis.mif.vu.lt) Received: (qmail 64553 invoked by uid 1001); 26 Jun 2000 13:41:52 -0000 Date: Mon, 26 Jun 2000 15:41:52 +0200 From: Rolandas Naujikas <rolnauj@pub.osf.lt> To: freebsd-hackers@freebsd.org Subject: I would like to know more about VFS and VM Message-ID: <20000626154151.A64462@uosis.mif.vu.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: VU MIF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to know more about current VFS and VM in FreeBSD kernel. Where I can get more details about that (from begginings). I'm requiring unionfs/nullfs to be working to use in jails. I'm ready to give some time to make changes in implementation to be working. roln (rolnauj@pub.osf.lt) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 8: 5:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id 1495A37B889 for <hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 08:05:11 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id LAA19865; Mon, 26 Jun 2000 11:04:51 -0400 (EDT) To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: "Nicole Harrington." <nicole@unixgirl.com>, Luigi Rizzo <luigi@info.iet.unipi.it>, hackers@FreeBSD.ORG Subject: Re: How many files can I put in one diretory? References: <XFMail.000623131248.doconnor@gsoft.com.au> From: Chris Shenton <cshenton@uucom.com> Date: 26 Jun 2000 11:04:51 -0400 In-Reply-To: "Daniel O'Connor"'s message of "Fri, 23 Jun 2000 13:12:48 +0930 (CST)" Message-ID: <lf8zvs5vqk.fsf@Samizdat.uucom.com> Lines: 37 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Jun-00 Nicole Harrington. wrote: >> > Yeah.. This is why databases where invented :) Hey I >> agree... However even if the html was databased.. (working on that >> now) the custom graphics cannot be. (yet) On Fri, 23 Jun 2000 13:12:48 +0930 (CST), "Daniel O'Connor" <doconnor@gsoft.com.au> said: Daniel> Hmm.. can't you do binary blobs in a DB and change the image Daniel> URL's to be cgi requests? I was considering this for a project I developed: web up/download of lots of large files. I was using MySQL and some of the folks on that list recommended not storing large files in the DB: even though the disk consumption is the same, if it's in a DB you can't spread it across partitions as space requirements grow. So I store the file path in the DB and the actual file on the UNIX filesystem. To reduce search time I use a two-level directory hierarchy, each of which has 256 subdirectories. To distribute files evenly, I store the file under a name which is the MD5 hash of the filename, time, etc, etc. This gives me a 32-char name of [0-9a-f]. So if file foo.tar.gz hashes to name cafebabedeadbeef0123456789abcdef it is stored under /filestore/ca/fe/cafebabedeadbeef0123456789abcdef This gives me 256 * 256 = 65536 directories. My requirement was to store at least 10 Million files, and this works out to about 150 files per directory -- easy for UNIX to get to quickly. It's been working very well for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 8:50:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 9537537B972 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 08:50:31 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e5QFoJg15381; Mon, 26 Jun 2000 08:50:19 -0700 (PDT) Date: Mon, 26 Jun 2000 08:50:19 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Rolandas Naujikas <rolnauj@pub.osf.lt> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: I would like to know more about VFS and VM In-Reply-To: <20000626154151.A64462@uosis.mif.vu.lt> Message-ID: <Pine.BSF.4.21.0006260849100.43159-100000@resnet.uoregon.edu> 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, 26 Jun 2000, Rolandas Naujikas wrote: > > I would like to know more about current VFS and VM in FreeBSD kernel. > Where I can get more details about that (from begginings). A back issue of DaemonNews's 'Blueprints' column has an excellent article explaining the VM system. http://www.daemonnews.org/ > I'm requiring unionfs/nullfs to be working to use in jails. > I'm ready to give some time to make changes in implementation to be working. If you're starting from nothing you have a lot to learn. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 8:51: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bedrock.hboc.com (hboc.com [139.177.224.128]) by hub.freebsd.org (Postfix) with SMTP id 2983837B972 for <hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 08:50:46 -0700 (PDT) (envelope-from Peter.Bohne@hboc.com) Received: from moosehead.hboc.com by bedrock.hboc.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 26 Jun 2000 15:50:45 UT Received: from SMTP (msteal.hboc.com [192.168.0.19]) by mrcheatem.hboc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id KJGFHZNQ; Mon, 26 Jun 2000 11:49:20 +0100 Received: from dmz.hboc.com ([139.177.6.114]) by 192.168.0.19 (Norton AntiVirus for Internet Email Gateways 1.0) ; Mon, 26 Jun 2000 15:51:51 0000 (GMT) Received: from atlexc90nthub.hboc.com by dmz.hboc.com via smtpd (for wildgoose.hboc.com [192.168.0.19]) with SMTP; 26 Jun 2000 15:50:32 UT Received: by atlexc90nthub.hboc.com with Internet Mail Service (5.5.2448.0) id <NQGSRLG3>; Mon, 26 Jun 2000 11:49:56 -0400 Message-ID: <35BEC7ED0A15D21199F000805F6F6D6A01CB00F4@bldexc01ntms.clinicom.com> From: "Bohne, Peter" <Peter.Bohne@hboc.com> To: 'Chuck Robey' <chuckr@picnic.mat.net> Cc: hackers@FreeBSD.ORG Subject: RE: libc_r/_read(), should the errno be reset to 0? Date: Mon, 26 Jun 2000 11:50:04 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My interest here was mainly to convey the fact that errno is not automatically reset to 0. I agree that there should be no need to check it if your system call succeeds. No arguments there. The original poster's question, however, was inquiring about an automatic reset of errno. In general, I've always held it to be good policy to reset errno before I make a call that can modify it if I plan to check it after the call. Regardless of OS - FreeBSD, HP-UX, AIX, what have you. pete > -----Original Message----- > From: Chuck Robey [mailto:chuckr@picnic.mat.net] > Sent: Saturday, June 24, 2000 10:28 PM > To: Bohne, Peter > Cc: 'FengYue'; 'andrew@ugh.net.au'; hackers@FreeBSD.ORG > Subject: RE: libc_r/_read(), should the errno be reset to 0? > > > On Fri, 23 Jun 2000, Bohne, Peter wrote: > > > True enough. That's the best advice. However, your > original post indicated > > an expectation on your part that errno would be somehow > automatically reset > > to 0 before a system call, which is definitely *not* the > case. You have to > > clear it - the kernel does not do it for you. > > Why would you bother to clear it? You don't check errno to determine > fail/success, you check the function return. If it returns fail, then > errno is going to be correct whether or not you bothered to > reset it or > not. Setting it to zero might give you a warm fuzzy feeling, but if > you're correctly detected errors, it's not going to change anything. > > If anyone is detecting the value of errno as an indication of > pass/fail, > they're going to be disappointed. > > > > > pete > > > > > -----Original Message----- > > > From: FengYue [mailto:fengyue@bluerose.windmoon.nu] > > > Sent: Friday, June 23, 2000 11:08 AM > > > To: Bohne, Peter > > > Cc: 'andrew@ugh.net.au'; hackers@FreeBSD.ORG > > > Subject: RE: libc_r/_read(), should the errno be reset to 0? > > > > > > > > > > > > Wait, that's not going to do anything, the errno is set inside the > > > _thread_sys_read(). But I agree with Andrew, why bother to check > > > errno if read() returns no error. > > > > > > On Fri, 23 Jun 2000, Bohne, Peter wrote: > > > > > > > This means that *you* should set errno to 0 just before you > > > do the read > > > > call. At this point, you no longer care what it had > been before. > > > > -- > > > > pete > > > > > > > > ====== pbohne at hboc dot com > > > > Peter Bohne -- McKessonHBOC -- Louisville, CO > > > > Work: 303-926-2218 -- Cell: 303-817-8312 -- Home Ofc: > 970-586-9031 > > > > ====== "Very funny, Scottie. Now beam down my clothes!" > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: andrew@ugh.net.au [mailto:andrew@ugh.net.au] > > > > > Sent: Friday, June 23, 2000 3:02 AM > > > > > To: FengYue > > > > > Cc: hackers@FreeBSD.ORG > > > > > Subject: Re: libc_r/_read(), should the errno be reset to 0? > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 23 Jun 2000, FengYue wrote: > > > > > > > > > > > My question is, shouldn't it be reset to zero? > > > > > > > > > > From intro(2): > > > > > > > > > > Successful calls never set errno; once set, it remains until > > > > > another error > > > > > occurs. It should only be examined after an error. > > > > > > > > > > Andrew > > > > > > > > > > > > > > > > > > > > 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 > > > > -------------------------------------------------------------- > -------------- > Chuck Robey | Interests include C & Java > programming, FreeBSD, > chuckr@picnic.mat.net | electronics, communications, and > signal processing. > > New Year's Resolution: I will not sphroxify gullible people > into looking up > fictitious words in the dictionary. > -------------------------------------------------------------- > -------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:10:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.mail.ru (mx3.mail.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id 35AEF37B8ED for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2000 09:10:40 -0700 (PDT) (envelope-from andersonfox@mail.ru) Received: from dialup-z15.comint.net ([213.154.192.143] helo=mail.ru) by smtp3.mail.ru with esmtp (Exim 3.14 #4) id 136bT3-000BwC-00 for freebsd-hackers@freebsd.org; Mon, 26 Jun 2000 20:10:37 +0400 Message-ID: <3957ABBD.6010407@mail.ru> Date: Mon, 26 Jun 2000 19:15:09 +0000 From: Fox Anderson <andersonfox@mail.ru> User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.12 i386; en-US; m14) Netscape6/6.0b1 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: struct proc Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! What is the difference between p and curproc in my syscall? static int my_syscall(struct proc *p, my_syscallargs *uap) { curproc->...... } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:21:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 407C237BD71 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 09:21:24 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FWR0041ZRW40L@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 26 Jun 2000 11:16:53 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id LAA51255; Mon, 26 Jun 2000 11:14:54 -0500 (CDT envelope-from chris) Date: Mon, 26 Jun 2000 11:14:53 -0500 From: Chris Costello <chris@calldei.com> Subject: Re: struct proc In-reply-to: <3957ABBD.6010407@mail.ru> To: Fox Anderson <andersonfox@mail.ru> Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000626111453.E20702@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <3957ABBD.6010407@mail.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, June 26, 2000, Fox Anderson wrote: > Hi all! > > What is the difference between p and curproc in my syscall? > > static int > my_syscall(struct proc *p, my_syscallargs *uap) { > curproc->...... > } p is the process that made the syscall, curproc is the current running process. You should be using p for the process that called my_syscall. -- |Chris Costello <chris@calldei.com> |It wasn't as easy to get programs right as we had thought. - Wilkes, 1949 `-------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:37: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9821837B852; Mon, 26 Jun 2000 09:37:02 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id JAA02887; Mon, 26 Jun 2000 09:37:40 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Nik Clayton <nik@freebsd.org> Cc: doc@freebsd.org, hackers@freebsd.org, jkh@freebsd.org, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@freebsd.org, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Re: Documentation selection in sysinstall In-reply-to: Your message of "Sun, 25 Jun 2000 19:52:03 -0000." <20000625195203.C470@kilt.nothing-going-on.org> Date: Mon, 26 Jun 2000 09:37:40 -0700 Message-ID: <2884.962037460@localhost> From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And while I've got Jordan's attention -- did the last attempt at > re-writing sysinstall generate any specification documents? If nothing > else, they'd be useful content for the doc project. ] No, this is one of the items on my TODO list which I really really really have to get to soon or we'll never get Son Of Sysinstall finished. > In theory, this is a doddle. sysinstall already lets the user choose from > packages to install. In practice, I think it's a little more difficult, > because: I'm still wondering why the docs bits can't be, at a minimum, "front-ended" by the ports collection in a new doc category? I can understand why you'd want to keep them in their own CVS repository section (doc/), but it would be cool if you could use ports to build and install (or make packages out of) the various documentation sets, especially now that there's talk of breaking up the handbook. Once that happened, you'd automagically appear in the INDEX and under your own category. No work would need to be done to sysinstall. My life would be easier. :) > 2. We need to find a UI model that allows the user to efficiently > select the language and formats they want to install. This wouldn't be quite so elegant, but perhaps Satoshi also wouldn't object to giving you more than one category under ports, just as the German, Japanese, Korean, etc. ports have done. It's either that or accelerate his efforts to go to a multi-layered ports collection so you could have sub-categories. That would lead to menu items like doc-english, doc-vietnamese, doc-french, etc. > I'm thinking of initially presenting a dialog box that looks > like this: I'm certain that once you start writing code for libdialog, my suggestions above will start sounding a lot less icky than they probably do to you right now. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:43:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 5CA7C37BA40 for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2000 09:43:33 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id JAA07293; Mon, 26 Jun 2000 09:42:46 -0700 Date: Mon, 26 Jun 2000 09:42:46 -0700 From: Arun Sharma <adsharma@sharmas.dhs.org> To: freebsd-hackers@freebsd.org Message-Id: <slrn8lf206.73g.adsharma@c62443-a.frmt1.sfba.home.com> Posted-To: mpc.lists.freebsd.hackers,muc.lists.freebsd.hackers Subject: Re: VM coloring description in NOTES References: <59063B5B4D98D311BC0D0001FA7E4522026D76AF@l04.research.kpn.com> Reply-To: adsharma@sharmas.dhs.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This message has also been posted.] On Mon, 26 Jun 2000 10:42:35 +0100, Koster, K.J. <K.J.Koster@kpn.com> wrote: > > > > > > currently -> candidate > > > > PQ_HUGECACHE PQ_CACHE1024 > > > > PQ_LARGECACHE PQ_CACHE512 > > > > PQ_MEDIUMCACHE PQ_CACHE256 > > > > PQ_NORMALCACHE PQ_CACHE64 > > > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in > it that FreeBSD then proceeds to rediscover. Is there no way to whack the > BIOS into submission and have it cough up the cache size? > > It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps > it would be nice to have an interface to some of the more widely used > bioses. I image you could pry all sorts of tuning information about the > machine from its clammy little hands. Cache size, cache scheme, memory type. For Intel processors, CPUID instruction spits out both L1 and L2 cache sizes. Perhaps, these things should be made a runtime option than a compile time option ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:51: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id A90AD37BA4C for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 09:50:52 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id MAA27441; Mon, 26 Jun 2000 12:50:41 -0400 (EDT) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA10478; Mon, 26 Jun 2000 12:50:41 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA10474; Mon, 26 Jun 2000 12:50:41 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 26 Jun 2000 12:50:41 -0400 (EDT) From: Kenneth Wayne Culver <culverk@wam.umd.edu> To: Arun Sharma <adsharma@sharmas.dhs.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VM coloring description in NOTES In-Reply-To: <slrn8lf206.73g.adsharma@c62443-a.frmt1.sfba.home.com> Message-ID: <Pine.GSO.4.21.0006261249510.19934-100000@rac5.wam.umd.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just curious because I have no experience in this area... but what exactly does cache coloring get us... I've never actually gotten a really straight answer on this... Thanks ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Mon, 26 Jun 2000, Arun Sharma wrote: > [This message has also been posted.] > On Mon, 26 Jun 2000 10:42:35 +0100, Koster, K.J. <K.J.Koster@kpn.com> wrote: > > > > > > > > currently -> candidate > > > > > PQ_HUGECACHE PQ_CACHE1024 > > > > > PQ_LARGECACHE PQ_CACHE512 > > > > > PQ_MEDIUMCACHE PQ_CACHE256 > > > > > PQ_NORMALCACHE PQ_CACHE64 > > > > > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in > > it that FreeBSD then proceeds to rediscover. Is there no way to whack the > > BIOS into submission and have it cough up the cache size? > > > > It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps > > it would be nice to have an interface to some of the more widely used > > bioses. I image you could pry all sorts of tuning information about the > > machine from its clammy little hands. Cache size, cache scheme, memory type. > > For Intel processors, CPUID instruction spits out both L1 and L2 cache > sizes. Perhaps, these things should be made a runtime option than a > compile time option ? > > -Arun > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:54:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 8764237B9CE for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 09:54:32 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id JAA07361; Mon, 26 Jun 2000 09:53:45 -0700 Date: Mon, 26 Jun 2000 09:53:45 -0700 From: Arun Sharma <adsharma@sharmas.dhs.org> To: Kenneth Wayne Culver <culverk@wam.umd.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VM coloring description in NOTES Message-ID: <20000626095345.A7344@sharmas.dhs.org> References: <slrn8lf206.73g.adsharma@c62443-a.frmt1.sfba.home.com> <Pine.GSO.4.21.0006261249510.19934-100000@rac5.wam.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <Pine.GSO.4.21.0006261249510.19934-100000@rac5.wam.umd.edu>; from culverk@wam.umd.edu on Mon, Jun 26, 2000 at 12:50:41PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 26, 2000 at 12:50:41PM -0400, Kenneth Wayne Culver wrote: > Just curious because I have no experience in this area... but what exactly > does cache coloring get us... I've never actually gotten a really straight > answer on this... Thanks Read Curt Schimmel's book UNIX systems for modern architectures for an answer. Basically, it ensures that if P1 and P2 are two pages that are allocated successively (temporal locality), then the first cache line in P1 and the first cache line in P2 do not compete with each other for the L2 cache. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:58: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7589037BA1B for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 09:57:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA68992; Mon, 26 Jun 2000 10:57:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA19938; Mon, 26 Jun 2000 10:56:01 -0600 (MDT) Message-Id: <200006261656.KAA19938@harmony.village.org> To: Mohana Krishna Penumetcha <pmk@sasi.com> Subject: Re: PCI transaction ordering!!! Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Jun 2000 15:03:10 +0530." <Pine.LNX.4.10.10006261442590.25550-100000@pcd134.sasi.com> References: <Pine.LNX.4.10.10006261442590.25550-100000@pcd134.sasi.com> Date: Mon, 26 Jun 2000 10:56:01 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <Pine.LNX.4.10.10006261442590.25550-100000@pcd134.sasi.com> Mohana Krishna Penumetcha writes: : HP-UX device driver reference manual says, : "The side-effects of any write are not guaranteed to happen : immediately. Writes are posted; they will complete eventually" : to make sure all writes are flushed from the queue, it suggests to perform : a read operation. : : i would like to know if the above behaviour is same across all operating : systems, esp if it is the same in FreeBSD case also?? I think so. This is a hardware bridge issue. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 9:58:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id AB0BE37BBA9 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 09:58:09 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id MAA27907; Mon, 26 Jun 2000 12:58:06 -0400 (EDT) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA11606; Mon, 26 Jun 2000 12:58:07 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA11602; Mon, 26 Jun 2000 12:58:07 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 26 Jun 2000 12:58:07 -0400 (EDT) From: Kenneth Wayne Culver <culverk@wam.umd.edu> To: Arun Sharma <adsharma@sharmas.dhs.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VM coloring description in NOTES In-Reply-To: <20000626095345.A7344@sharmas.dhs.org> Message-ID: <Pine.GSO.4.21.0006261257370.19934-100000@rac5.wam.umd.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, well that makes sense.. I guess it speeds things up some too? (I had it enabled for a while, but didn't notice a difference). ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Mon, 26 Jun 2000, Arun Sharma wrote: > On Mon, Jun 26, 2000 at 12:50:41PM -0400, Kenneth Wayne Culver wrote: > > Just curious because I have no experience in this area... but what exactly > > does cache coloring get us... I've never actually gotten a really straight > > answer on this... Thanks > > Read Curt Schimmel's book UNIX systems for modern architectures for an > answer. > > Basically, it ensures that if P1 and P2 are two pages that are allocated > successively (temporal locality), then the first cache line in P1 and > the first cache line in P2 do not compete with each other for the L2 cache. > > -Arun > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 11:46:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 8F99F37BC76 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 11:46:30 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 3584974 invoked from network); 26 Jun 2000 18:31:55 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender <root@gits.dyndns.org>) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for <freebsd-hackers@FreeBSD.ORG>; 26 Jun 2000 18:31:55 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id UAA96533; Mon, 26 Jun 2000 20:31:55 +0200 (CEST) (envelope-from root) From: Cyrille Lefevre <root@gits.dyndns.org> Posted-Date: Mon, 26 Jun 2000 20:31:55 +0200 (CEST) Message-Id: <200006261831.UAA96533@gits.dyndns.org> Subject: strange symlink behaviour if / terminated To: freebsd-hackers@FreeBSD.ORG Date: Mon, 26 Jun 2000 20:31:55 +0200 (CEST) Reply-To: clefevre@citeweb.net, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<<r#uCVjK"~Ke!@0vxS/.,wki/c|uVnNV!BA-_gY2sfoGc3 f{#/$PT>97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG preliminaries : # mkdir -p /path/name /path/to # touch /path/name/file # ln -s /path/name /path/to/symlink # mv /path/to/symlink/ /other/location ^ note the terminating slash. move the target of the symlink instead of the symlink itself. same results w/ rm -r and cp -r. slightly different results w/ rm and cp. # rm /path/to/symlink/ rm: /path/to/symlink/: is a directory # cp /path/to/symlink/ /other/location cp: /path/to/symlink/ is a directory (not copied). # rmdir -p /path/to/symlink/ remove the symlink itself instead of do nothing, such as in : # rmdir -p /path/to/symlink rmdir: /path/to/symlink: Not a directory also, strange output from rmdir -p : # mkdir -p /path/name # rmdir -p /path/name rmdir: : No such file or directory # mkdir -p /path/name/ # rmdir -p /path/name/ rmdir: /path/name: No such file or directory I don't have done these tests under some other OSes (HP-UX, Solaris, IRIX) yet, but I'm sure that they do nothing or they work on symlink itself instead of the target. Cyrille. -- home:mailto:clefevre@no-spam.citeweb.net Supprimer "no-spam." pour me repondre. work:mailto:Cyrille.Lefevre@no-spam.edf.fr Remove "no-spam." to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 12: 6:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2D06D37B51B; Mon, 26 Jun 2000 12:06:19 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA69546; Mon, 26 Jun 2000 13:06:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA25572; Mon, 26 Jun 2000 13:04:23 -0600 (MDT) Message-Id: <200006261904.NAA25572@harmony.village.org> To: clefevre@citeweb.net, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: strange symlink behaviour if / terminated In-reply-to: Your message of "Mon, 26 Jun 2000 20:31:55 +0200." <200006261831.UAA96533@gits.dyndns.org> References: <200006261831.UAA96533@gits.dyndns.org> Date: Mon, 26 Jun 2000 13:04:23 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006261831.UAA96533@gits.dyndns.org> Cyrille Lefevre writes: : # mv /path/to/symlink/ /other/location : ^ note the terminating slash. Read the terminating slash as "/." and it all should make sense. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 12: 9:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A46E637BCB4 for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2000 12:09:19 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA21653; Mon, 26 Jun 2000 15:09:10 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA49039; Mon, 26 Jun 2000 15:09:10 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin <gallatin@cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 26 Jun 2000 15:09:10 -0400 (EDT) To: adsharma@sharmas.dhs.org Cc: freebsd-hackers@freebsd.org Subject: Re: VM coloring description in NOTES In-Reply-To: <slrn8lf206.73g.adsharma@c62443-a.frmt1.sfba.home.com> References: <59063B5B4D98D311BC0D0001FA7E4522026D76AF@l04.research.kpn.com> <slrn8lf206.73g.adsharma@c62443-a.frmt1.sfba.home.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14679.40851.766762.577274@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma writes: > > For Intel processors, CPUID instruction spits out both L1 and L2 cache > sizes. Perhaps, these things should be made a runtime option than a > compile time option ? That sounds like a good idea. Also, I imagine that it would be possible to write a function to emperically determine the system cache size on non Intel CPUs where such an instruction is not available. Eg, Alpha processors don't specify the amount of Bcache (secondary or tertiary) cache they have & Tru64 sizes them on the fly. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 13:17:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id B963337BD19 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 13:17:31 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-1-175.club-internet.fr (Guyancourt-1-175.club-internet.fr [195.36.205.175]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA16696; Mon, 26 Jun 2000 22:17:11 +0200 (MET DST) Date: Mon, 26 Jun 2000 21:55:19 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> X-Sender: groudier@linux.local To: Mohana Krishna Penumetcha <pmk@sasi.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI transaction ordering!!! In-Reply-To: <Pine.LNX.4.10.10006261442590.25550-100000@pcd134.sasi.com> Message-ID: <Pine.LNX.4.10.10006262035350.1842-100000@linux.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jun 2000, Mohana Krishna Penumetcha wrote: > hi, >=20 > HP-UX device driver reference manual says,=20 >=20 > =09"The side-effects of any write are not guaranteed to happen > immediately. Writes are posted; they will complete eventually" >=20 > to make sure all writes are flushed from the queue, it suggests to perfor= m > a read operation. >=20 > i would like to know if the above behaviour is same across all operating > systems, esp if it is the same in FreeBSD case also?? It does not depend on the O/S. It is a PCI optimization that addresses bridges (PCI-host bridges and PCI-PCI bridges) and performing a read transaction (useful or dummy) is the way required by PCI specifications to flush posted transactions. Some bridges may also elect to flush posted transactions on some event like when IRQ is raised, but this is broken approach due to the fact that IRQ lines can be shared by several PCI devices and have no dependency with lines used for transactions (INTR lines look like side-band signals on PCI). On PCI, only PCI transactions (except interrupt acknowledge) can act as synchronisation events and read transactions (useful or dummy) have to be used when the software or the PCI device requires posted writes to be flushed. If you are interested in PCI, I suggest you to read the PCI specifications. May-be, you will have to read them several times prior to having a reasonnable understanding of them. :-) If this happens, you should not have to worry, since it seems to me that they have been often not well understood even by hardware designers and architects. ;-) (I may be disagreed here) As a result of this misunderstanding probably, some real hardwares are not full PCI compliant (or not enough PCI-friendly :-)). For example regarding flushing of posted transactions: PCI specifications require the following when a read is attempted through a bridge (I intentionnaly donnot speak about delayed transactions for simplicity): 1) Flush posted writes to the destination BUS 2) Perform the read to the device (on the destination BUS). 3) Flush posted writes to the originating BUS. (at least those attempted prior to the read having been accepted by the device targetted by the read) 4) Complete the read at the originating device (on the originating BUS). On some systems, as Alpha for example, (3) is not required to be performed. As a result, if the device does not flush posted transactions prior to telling the software driver about events (as completions), stale data can be read from memory by the software driver. When (3) is performed, the device is only required to move data to memory and set some flag in some proper order and the flushing of posted transactions that ensures no stale data will be read can be achieved from the software driver (no flushing is needed from the device). By the way, the documentations I have read about bridges and architectures let me under the impression that numerous PCI device drivers (not only on BSD systems) are broken (in race) regarding transaction posting issues. In my opinion, a PCI device driver that just don't care about posted transactions has every chance to be broken, at least on some architecture or using some bridge. Using legacy IO method rather than MMIO does not make it more safe, since host bridges are also allowed to post IO writes. Speaking about Intel hardware and architecture: - IA32 does not reorder STOREs when they are carried out to the system=20 BUS, neither it allows LOADs to pass STOREs. - Intel host bridges are, at least on paper, PCI compliant regarding=20 ordering rules and donnot post IO write transactions. Such strong ordering situation allows PCI devices and drivers designed with ISA in mind to work reasonnably, but if you move such a device and/or driver to MMIO world with posted writes or to systems that follow ordering rules weaker than PCI requirements, races will likely appear. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 13:21: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B6AF637BE37 for <hackers@freebsd.org>; Mon, 26 Jun 2000 13:20:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA07426; Mon, 26 Jun 2000 13:20:56 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra <jdp@polstra.com> Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA16125; Mon, 26 Jun 2000 13:20:55 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 26 Jun 2000 13:20:55 -0700 (PDT) Message-Id: <200006262020.NAA16125@vashon.polstra.com> To: chris@calldei.com Subject: Re: struct proc In-Reply-To: <20000626111453.E20702@holly.calldei.com> References: <3957ABBD.6010407@mail.ru> <20000626111453.E20702@holly.calldei.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000626111453.E20702@holly.calldei.com>, Chris Costello <chris@calldei.com> wrote: > On Monday, June 26, 2000, Fox Anderson wrote: > > What is the difference between p and curproc in my syscall? > > > > static int > > my_syscall(struct proc *p, my_syscallargs *uap) { > > curproc->...... > > } > > p is the process that made the syscall, curproc is the current > running process. You should be using p for the process that > called my_syscall. Since only one process can enter the kernel at a time (currently), and p is the process that made the system call, it is also the current process. I claim that (p == curproc) in this example, and that it would be better to code with p than with curproc. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 15: 4:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E51B37B7EE for <hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 15:04:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA30219; Mon, 26 Jun 2000 15:04:49 -0700 (PDT) (envelope-from dillon) Date: Mon, 26 Jun 2000 15:04:49 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> Message-Id: <200006262204.PAA30219@apollo.backplane.com> To: John Polstra <jdp@polstra.com> Cc: chris@calldei.com, hackers@FreeBSD.ORG Subject: Re: struct proc References: <3957ABBD.6010407@mail.ru> <20000626111453.E20702@holly.calldei.com> <200006262020.NAA16125@vashon.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> p is the process that made the syscall, curproc is the current :> running process. You should be using p for the process that :> called my_syscall. : :Since only one process can enter the kernel at a time (currently), :and p is the process that made the system call, it is also the :current process. I claim that (p == curproc) in this example, and :that it would be better to code with p than with curproc. : :John : John Polstra jdp@polstra.com :... Even in an MP system, curproc is not going to be ripped out from under a syscall. p will always be curproc. (curproc in an MP system is a per-cpu variable). This whole p vs curproc thing is a huge mess. 95% of the time p == curproc. The only places where it might not is in I/O ops that are completed by an interrupt or (in the case of NFS) some other process. -Matt Matthew Dillon <dillon@backplane.com> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 15:38:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id E1D7537B814 for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 2000 15:38:32 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 3649212 invoked from network); 26 Jun 2000 22:38:31 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender <root@gits.dyndns.org>) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for <clefevre@citeweb.net>; 26 Jun 2000 22:38:31 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id AAA01040; Tue, 27 Jun 2000 00:38:30 +0200 (CEST) (envelope-from root) From: Cyrille Lefevre <root@gits.dyndns.org> Posted-Date: Tue, 27 Jun 2000 00:38:30 +0200 (CEST) Message-Id: <200006262238.AAA01040@gits.dyndns.org> Subject: Re: cvs update failed In-Reply-To: <200006262010.NAA16075@vashon.polstra.com> "from John Polstra at Jun 26, 2000 01:10:12 pm" To: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Tue, 27 Jun 2000 00:38:29 +0200 (CEST) Cc: adrian@FreeBSD.ORG, imp@village.org, clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<<r#uCVjK"~Ke!@0vxS/.,wki/c|uVnNV!BA-_gY2sfoGc3 f{#/$PT>97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <200006260319.FAA29083@gits.dyndns.org>, > Cyrille Lefevre <clefevre@citeweb.net> wrote: > > > > the problem I have, is that, when I run "cvs -t update -r RELENG_4", > > I got the following message (last 4 lines) : > [...] > > cvs update: notice: main loop with CVSROOT=anoncvs@anoncvs.netbsd.org:/cvsroot > > -> Starting server: rsh anoncvs.netbsd.org -l anoncvs cvs server > > anoncvs.netbsd.org: Connection refused > > cvs [update aborted]: end of file from server (consult above messages if any) > > > > what's happen ? > > Either your CVSROOT environment variable is set incorrectly, or you > have a "CVS/Root" file somewhere in your tree that contains the wrong > value. The value listed is for NetBSD, and the NetBSD server doesn't > even like it. Thanks, that's a CVS/Root from adrian's fsck/fsck_ffs which was imported from the NetBSD source tree. I get rid of thoses CVS trees until there are incorporated w/in the FreeBSD source tree. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 16:46:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id A69A337B9C6 for <hackers@freebsd.org>; Mon, 26 Jun 2000 16:46:14 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 136iZV-000DSi-00; Tue, 27 Jun 2000 06:45:45 +0700 Date: Tue, 27 Jun 2000 06:45:45 +0700 (ALMST) From: Boris Popov <bp@butya.kz> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: John Polstra <jdp@polstra.com>, chris@calldei.com, hackers@FreeBSD.ORG Subject: Re: struct proc In-Reply-To: <200006262204.PAA30219@apollo.backplane.com> Message-ID: <Pine.BSF.4.10.10006270634460.51466-100000@lion.butya.kz> 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, 26 Jun 2000, Matthew Dillon wrote: > This whole p vs curproc thing is a huge mess. 95% of the time > p == curproc. The only places where it might not is in I/O ops > that are completed by an interrupt or (in the case of NFS) some > other process. Any chances to clean this up ? Eg., change the policy to either pass p as parameter or use curproc, but not both. As example of curproc/p mess I can point to VFS_ROOT() call which misses p parameter, but obviously needs it. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 26 22:47:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bastard.co.uk (node16292.a2000.nl [24.132.98.146]) by hub.freebsd.org (Postfix) with ESMTP id 9D2D937BDEE; Mon, 26 Jun 2000 22:47:48 -0700 (PDT) (envelope-from adrian@bastard.co.uk) Received: from adrian by mail.bastard.co.uk with local (Exim 3.14 #1) id 136oCd-000EVM-00; Tue, 27 Jun 2000 07:46:31 +0200 Date: Tue, 27 Jun 2000 07:46:31 +0200 From: Adrian Chadd <adrian@freebsd.org> To: Cyrille Lefevre <root@gits.dyndns.org> Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@freebsd.org, imp@village.org, clefevre@citeweb.net Subject: Re: cvs update failed Message-ID: <20000627074631.B36017@zoe.bastard.co.uk> References: <200006262010.NAA16075@vashon.polstra.com> <200006262238.AAA01040@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006262238.AAA01040@gits.dyndns.org>; from root@gits.dyndns.org on Tue, Jun 27, 2000 at 12:38:29AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 27, 2000, Cyrille Lefevre wrote: > John Polstra wrote: > > In article <200006260319.FAA29083@gits.dyndns.org>, > > Cyrille Lefevre <clefevre@citeweb.net> wrote: > > > > > > the problem I have, is that, when I run "cvs -t update -r RELENG_4", > > > I got the following message (last 4 lines) : > > [...] > > > cvs update: notice: main loop with CVSROOT=anoncvs@anoncvs.netbsd.org:/cvsroot > > > -> Starting server: rsh anoncvs.netbsd.org -l anoncvs cvs server > > > anoncvs.netbsd.org: Connection refused > > > cvs [update aborted]: end of file from server (consult above messages if any) > > > > > > what's happen ? > > > > Either your CVSROOT environment variable is set incorrectly, or you > > have a "CVS/Root" file somewhere in your tree that contains the wrong > > value. The value listed is for NetBSD, and the NetBSD server doesn't > > even like it. > > Thanks, that's a CVS/Root from adrian's fsck/fsck_ffs which was imported > from the NetBSD source tree. I get rid of thoses CVS trees until there > are incorporated w/in the FreeBSD source tree. No, the fsck wrappers came straight from NetBSD. FreeBSD's fsck was turned into fsck_ffs, and fsck comes from NetBSD. I've kept the CVS/Root entries intact for both, so people can generate a diff from the origin source trees. Adrian -- Adrian Chadd Build a man a fire, and he's warm for the <adrian@FreeBSD.org> rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 1:27:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from inetfw.sonycsl.co.jp (inetfw.SonyCSL.Co.Jp [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id 66A9937BE91 for <freebsd-hackers@freebsd.org>; Tue, 27 Jun 2000 01:27:44 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.9.3+3.2W/3.7Ws3/inetfw/2000050701/smtpfeed 1.07) with ESMTP id RAA78522; Tue, 27 Jun 2000 17:27:36 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.9.3+3.2W/3.7Ws3/hotaka/2000061722) with ESMTP id RAA17953; Tue, 27 Jun 2000 17:27:36 +0900 (JST) To: freebsd-hackers@freebsd.org Cc: akimichi@sfc.wide.ad.jp Subject: ieee1394 driver X-Mailer: Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000627172736Z.kjc@csl.sony.co.jp> Date: Tue, 27 Jun 2000 17:27:36 +0900 From: Kenjiro Cho <kjc@csl.sony.co.jp> X-Dispatcher: imput version 20000228(IM140) Lines: 9 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone asked at the USENIX BOF about the status of ieee1394 driver for FreeBSD. For those who want to play with DV cameras, a set of tools to transmit DV streasms over IP is available from http://www.sfc.wide.ad.jp/DVTS/ It includes the ieee1394 driver presented at the last year's freenix. -Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 2:38:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 74C8537BF49 for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 02:38:40 -0700 (PDT) (envelope-from pmk@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id PAA17179 for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 15:07:26 +0530 (IST) Received: from pcd134.sasi.com ([10.0.16.134]) by sasi.com; Tue, 27 Jun 2000 15:07:24 +0000 (IST) Received: from localhost (pmk@localhost) by pcd134.sasi.com (8.9.3/8.9.3) with ESMTP id PAA29502 for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 15:07:02 +0530 X-Authentication-Warning: pcd134.sasi.com: pmk owned process doing -bs Date: Tue, 27 Jun 2000 15:07:01 +0530 (IST) From: Mohana Krishna Penumetcha <pmk@sasi.com> To: hackers@FreeBSD.ORG Subject: PCI Specification !!! In-Reply-To: <200006190520.WAA06363@mass.osd.bsdi.com> Message-ID: <Pine.LNX.4.10.10006271502490.29500-100000@pcd134.sasi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, is the PCI Specification avaialable on the web? i tried a couple of search engines, couldn't find it. --mohan Telecom R&D , FAC-D, SAS ph:- 5281461 x3078 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 3: 9:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 436FF37BDE0 for <freebsd-hackers@FreeBSD.org>; Tue, 27 Jun 2000 03:09:27 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA27016; Tue, 27 Jun 2000 06:09:02 -0400 (EDT) Date: Tue, 27 Jun 2000 06:09:02 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: freebsd-hackers@FreeBSD.org Subject: Default (x86) floating point precision Message-ID: <Pine.SUN.3.91.1000627055606.25178B-100000@pcnet1.pcnet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed that we change the default setting for floating point precision from extended precision (64-bit) to double precision (53-bit). The comment in npx.h says: /* * The hardware default control word for i387's and later coprocessors is * 0x37F, giving: * * round to nearest * 64-bit precision * all exceptions masked. * * We modify the affine mode bit and precision bits in this to give: * * affine mode for 287's (if they work at all) (1 in bitfield 1<<12) * 53-bit precision (2 in bitfield 3<<8) * * 64-bit precision often gives bad results with high level languages * because it makes the results of calculations depend on whether * intermediate values are stored in memory or in FPU registers. */ #define __INITIAL_NPXCW__ 0x127F Oddly, this causes problems with GNAT (Ada is a high level language) because it wants/expects 64-bit extended precision. It seems as if GNAT for linux-i386 also uses 64-bit extended precision. The only other GNAT i386 platform that doesn't use 64-bit precision is NT. So is the above comment still valid? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 3:28:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bastard.co.uk (node16292.a2000.nl [24.132.98.146]) by hub.freebsd.org (Postfix) with ESMTP id 700F237B8FE; Tue, 27 Jun 2000 03:28:05 -0700 (PDT) (envelope-from adrian@bastard.co.uk) Received: from adrian by mail.bastard.co.uk with local (Exim 3.14 #1) id 136sb4-000ExA-00; Tue, 27 Jun 2000 12:28:02 +0200 Date: Tue, 27 Jun 2000 12:28:02 +0200 From: Adrian Chadd <adrian@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Cyrille Lefevre <root@gits.dyndns.org>, freebsd-fs@FreeBSD.ORG, freebsd-hackers@freebsd.org, imp@village.org, clefevre@citeweb.net Subject: Re: cvs update failed Message-ID: <20000627122802.E36017@zoe.bastard.co.uk> References: <200006262010.NAA16075@vashon.polstra.com> <200006262238.AAA01040@gits.dyndns.org> <20000627074631.B36017@zoe.bastard.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000627074631.B36017@zoe.bastard.co.uk>; from adrian@freebsd.org on Tue, Jun 27, 2000 at 07:46:31AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 27, 2000, Adrian Chadd wrote: > On Tue, Jun 27, 2000, Cyrille Lefevre wrote: > > John Polstra wrote: > > > In article <200006260319.FAA29083@gits.dyndns.org>, > > > Cyrille Lefevre <clefevre@citeweb.net> wrote: > > > > > > > > the problem I have, is that, when I run "cvs -t update -r RELENG_4", > > > > I got the following message (last 4 lines) : > > > [...] > > > > cvs update: notice: main loop with CVSROOT=anoncvs@anoncvs.netbsd.org:/cvsroot > > > > -> Starting server: rsh anoncvs.netbsd.org -l anoncvs cvs server > > > > anoncvs.netbsd.org: Connection refused > > > > cvs [update aborted]: end of file from server (consult above messages if any) > > > > > > > > what's happen ? > > > > > > Either your CVSROOT environment variable is set incorrectly, or you > > > have a "CVS/Root" file somewhere in your tree that contains the wrong > > > value. The value listed is for NetBSD, and the NetBSD server doesn't > > > even like it. > > > > Thanks, that's a CVS/Root from adrian's fsck/fsck_ffs which was imported > > from the NetBSD source tree. I get rid of thoses CVS trees until there > > are incorporated w/in the FreeBSD source tree. > > No, the fsck wrappers came straight from NetBSD. FreeBSD's fsck was turned > into fsck_ffs, and fsck comes from NetBSD. I've kept the CVS/Root entries > intact for both, so people can generate a diff from the origin source > trees. .. realising that this stuff isn't committed at all, so i'm curious how you managed to come across this.. :) Adrian -- Adrian Chadd Build a man a fire, and he's warm for the <adrian@FreeBSD.org> rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 7:12:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id 6C6B037B93F for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 07:12:06 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id JAA29484; Tue, 27 Jun 2000 09:11:59 -0500 (CDT) Date: Tue, 27 Jun 2000 09:11:59 -0500 (CDT) From: Mark Tinguely <tinguely@plains.NoDak.edu> Message-Id: <200006271411.JAA29484@plains.NoDak.edu> To: hackers@FreeBSD.ORG, pmk@sasi.com Subject: Re: PCI Specification !!! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > is the PCI Specification avaialable on the web? i tried a couple of search > engines, couldn't find it. The PCI Specification is published by the PCI Special Interest Group. The PCI Local Bus Specification Revision 2.0 cost about $20-25 a few years ago, and I see from the web order page: http://www.pcisig.com/tech/index.html that the price for the PCI Local Bus Specification Revision 2.2 is still in that ballpark. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 8:24: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 6E5F837C1BA for <freebsd-hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 08:23:59 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id IAA59630; Tue, 27 Jun 2000 08:25:31 -0700 (PDT) (envelope-from sgk) From: Steve Kargl <sgk@troutmask.apl.washington.edu> Message-Id: <200006271525.IAA59630@troutmask.apl.washington.edu> Subject: Re: Default (x86) floating point precision In-Reply-To: <Pine.SUN.3.91.1000627055606.25178B-100000@pcnet1.pcnet.com> from Daniel Eischen at "Jun 27, 2000 06:09:02 am" To: Daniel Eischen <eischen@vigrid.com> Date: Tue, 27 Jun 2000 08:25:31 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > > Oddly, this causes problems with GNAT (Ada is a high level language) > because it wants/expects 64-bit extended precision. It seems as if > GNAT for linux-i386 also uses 64-bit extended precision. The only > other GNAT i386 platform that doesn't use 64-bit precision is NT. > > So is the above comment still valid? > Does GNAT use the math library in /usr/lib? I've been testing our math library against UCBTEST, and there appear to be some pecularities. I need to dig deeper to understand all the info produced by UCBTEST. The point of this note is that turning on 64-bit extended precision in GNAT might be compromised by libm.a. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 9:35:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 3D47737C00E for <freebsd-hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 09:35:29 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id MAA20019; Tue, 27 Jun 2000 12:35:09 -0400 (EDT) Date: Tue, 27 Jun 2000 12:35:08 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Default (x86) floating point precision In-Reply-To: <200006271525.IAA59630@troutmask.apl.washington.edu> Message-ID: <Pine.SUN.3.91.1000627120043.14641A-100000@pcnet1.pcnet.com> 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, 27 Jun 2000, Steve Kargl wrote: > Daniel Eischen wrote: > > > > Oddly, this causes problems with GNAT (Ada is a high level language) > > because it wants/expects 64-bit extended precision. It seems as if > > GNAT for linux-i386 also uses 64-bit extended precision. The only > > other GNAT i386 platform that doesn't use 64-bit precision is NT. > > > > So is the above comment still valid? > > > > Does GNAT use the math library in /usr/lib? I've been testing > our math library against UCBTEST, and there appear to be some > pecularities. I need to dig deeper to understand all the info > produced by UCBTEST. The point of this note is that turning on > 64-bit extended precision in GNAT might be compromised by libm.a. Yeah, I kinda wondered how this would affect libm.a (after I changed GNAT to use extended precision :( ). GNAT does provide an Ada interface to some of the math functions in libm. You can configure GNAT to use either a 64-bit or 53-bit precision interface to the math functions. Actually, you can configure it to use 53-bit precision floating point numbers for everything else, but I based this part of the run-time on the Linux run-time which uses 64-bit precision. The more I think about it, I think I should just teach GNAT to expect 53-bit precision floating points and not change the precision of the FP processor. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 11:19: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2F99B37C296 for <freebsd-hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 11:18:51 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA08489; Tue, 27 Jun 2000 11:19:14 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Kenjiro Cho <kjc@csl.sony.co.jp> Cc: freebsd-hackers@FreeBSD.ORG, akimichi@sfc.wide.ad.jp Subject: Re: ieee1394 driver In-reply-to: Your message of "Tue, 27 Jun 2000 17:27:36 +0900." <20000627172736Z.kjc@csl.sony.co.jp> Date: Tue, 27 Jun 2000 11:19:13 -0700 Message-ID: <8486.962129953@localhost> From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Someone asked at the USENIX BOF about the status of ieee1394 driver > for FreeBSD. For those who want to play with DV cameras, a set of > tools to transmit DV streasms over IP is available from > http://www.sfc.wide.ad.jp/DVTS/ > > It includes the ieee1394 driver presented at the last year's freenix. Thanks for the pointer, I see the latest set of patches are at: ftp://new-tremaine.cc.uec.ac.jp/pub/firewire/firewire-freebsd-4.0-20000515 My question is simply: Why don't we bring this into the system? Is it for lack of manpower in committers or a desire from the development team that it stay a separate set of patches? Some observations on the code: Most of the cards they want to support are still on the TODO list, only one type of card being marked as fully working. Still, there's nothing like having users of your code to help that process along, so I wouldn't consider this reason enough to keep the code out. I'm not sure how I feel about /sys/net1394 as a new subdirectory for a lot of the lynx stuff. Is that really necessary? Most of the code patches straight into -current, though it's clear that a bit more work will need to be done to make it fully conform. Still, we need firewire support! Any suggestions on how to proceed? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 14:37:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id D06CE37C32C for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 14:37:21 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA18274; Tue, 27 Jun 2000 16:36:56 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Tue, 27 Jun 2000 16:36:55 -0500 (CDT) From: David Scheidt <dscheidt@enteract.com> To: Chris Shenton <cshenton@uucom.com> Cc: "Daniel O'Connor" <doconnor@gsoft.com.au>, "Nicole Harrington." <nicole@unixgirl.com>, Luigi Rizzo <luigi@info.iet.unipi.it>, hackers@FreeBSD.ORG Subject: Re: How many files can I put in one diretory? In-Reply-To: <lf8zvs5vqk.fsf@Samizdat.uucom.com> Message-ID: <Pine.NEB.3.96.1000627163504.83870A-100000@shell-1.enteract.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Jun 2000, Chris Shenton wrote: :I was considering this for a project I developed: web up/download of :lots of large files. I was using MySQL and some of the folks on that :list recommended not storing large files in the DB: even though the :disk consumption is the same, if it's in a DB you can't spread it :across partitions as space requirements grow. That's a failing of your DBMS, and not of a database in general. I add space to existing databases under Sybase fairly often. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 15:26:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id ABF5337BB50 for <freebsd-hackers@freeBSD.org>; Tue, 27 Jun 2000 15:26:41 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id SAA34251; Tue, 27 Jun 2000 18:26:18 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <39592A14.23E1EDF0@falcon.niksun.com> Date: Tue, 27 Jun 2000 22:26:29 +0000 From: Joy Ganguly <joy@niksun.com> X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: openfw <openfw@alteon.com>, freebsd-hackers <freebsd-hackers@freeBSD.org> Subject: Tigon firmware... 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 have been looking into the Tigon firmware code and i am totalyy puzzled about this: there is no place in the code where trp->local_mem_conf.rx_buf_consumer is incremented. (except in h_mac_rx_comp_nohost() which is not called) The tigon documentation says that it should be incremented by the firmware after the frames have been dma'd into the host. But h_dma_wr_assist() never does that. Setting a watchpoint on this register i saw that the register changes when the "dma write assist producer" register is updated in q_dma_to_host(). Isnt this strange??.....or am i missing something?? can anybody explain?? thanx in advance joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 16:12: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id F26A937BEE8; Tue, 27 Jun 2000 16:11:55 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWU005RC3XHA3@falla.videotron.net>; Tue, 27 Jun 2000 18:32:05 -0400 (EDT) Date: Tue, 27 Jun 2000 18:34:02 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: mbuf re-write(s): v 0.2: request-for-comments X-Sender: bmilekic@jehovah.technokratis.com To: freebsd-hackers@freebsd.org Cc: freebsd-net@freebsd.org Message-id: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just added a MEXTADD() routine to the [now getting bigger] mbuf re-write patch, as well as fixed and changed a few little things here and there (once again). Thus, so-called "version 2" of the diff is again available: http://www.technokratis.com/code/mbuf/ This code includes all that was discussed in the previous Email, as well as a better/actually working external storage facility for clusters. Previously, it was very difficult to allocate external storage, attach it to the mbuf, _and_ as well maintain a reference counter for it, primarily due to the arguments that were taken by ext_free() and ext_buf(). These have been changed to have a new void * pointer passed in as the second argument (following the base address of the storage buffer). Also has been included a void * multi-purpose ext_args pointer in the m_ext struct, so the caller has much more flexibility now. In fact, the caller can now attach a "management" or "reference" structure to the m_ext struct via the ext_args pointer, and have it passed to his ext_free and ext_buf routines. Naturally, for dynamically sized malloc() external buffers, the caller can also allocate along with it space for its reference counter and attach to the mbuf via the ext_args pointer. It will be incremented/decremented properly as ext_args can be passed as the second argument to the two functions. When ext_free, ext_buf, and ext_args are all NULL, but M_EXT is set, then the external storage corresponds to an mcluster. These changes will surely help out/make cleaner some code, like some of Bill Paul's device drivers (if_sk, if_ti, if_wb). For other purposes, such as sf_bufs, for example, it's not _as_ significant, mainly since sf_bufs are allocated from their own map such that the system can easily produce a unique index for a reference counter array just by looking at the offset base_addr_of_sf_buf - base_addr_of_map, like we do for mclusters. However, obviously, we don't want a new map for every new type of external storage we want to attach to an mbuf. :-) (Yes, this means easy attaching of dynamically sized buffers) What I still have left to do before I look into finding/bugging/annoying a committer (sigh) to reviewing/committing all of this: * Re-write the mcluster allocations/deallocations in the same style as the new mbuf allocator/deallocator. ... If someone has a more suitable proposition, please let me know. I love to hear suggestions. * I'm thinking of adopting NetBSD's "cute" and "clean" reference count system; they maintain their mbufs linked through the m_ext when they reference the same storage object. This will remove all fear from external callers/code having to deal with references in the first place, and will isolate it all to the mbuf code. Once this is done, I can also add a NetBSD-like MEXTMALLOC() macro, in addition to the just-added MEXTADD() macro. This would automate dynamic malloc()ing of external storage objects, and make it quite a bit cleaner/easier for the caller. * Patch up userland to deal with all of these changes. * Get some profiling / optimisation done. Since my initial post, I have received quite a few hits/requests for the posted code, and have even received a few comments/suggestions. These have been most helpful. I invite many more,... please! Regards, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 16:13:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dfw7-1.relay.mail.uu.net (dfw7-1.relay.mail.uu.net [199.171.54.106]) by hub.freebsd.org (Postfix) with ESMTP id 565AA37BEE8 for <freebsd-hackers@freebsd.org>; Tue, 27 Jun 2000 16:13:31 -0700 (PDT) (envelope-from shuang@alteon.com) Received: from dogbert.alteon.com by dfw7sosrv11.alter.net with SMTP (peer crosschecked as: alteon.com [208.200.21.146]) id QQivlk09372; Tue, 27 Jun 2000 23:13:14 GMT Received: from sharks.alteon.com by dogbert.alteon.com via smtpd (for mail.uu.net [199.171.54.106]) with SMTP; 27 Jun 2000 23:13:16 UT Received: from madrone.acteon.com by alteon.com (8.9.1b+Sun/SMI-SVR4) id QAA27331; Tue, 27 Jun 2000 16:13:12 -0700 (PDT) Received: from alteon.com (localhost [127.0.0.1]) by madrone.acteon.com (8.8.8+Sun/8.8.8) with ESMTP id QAA01854; Tue, 27 Jun 2000 16:13:11 -0700 (PDT) Message-ID: <39593506.D85B73A9@alteon.com> Date: Tue, 27 Jun 2000 16:13:10 -0700 From: Shih-Nan Huang <shuang@alteon.com> X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en-US MIME-Version: 1.0 To: Joy Ganguly <joy@niksun.com> Cc: openfw <openfw@alteon.com>, freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: Tigon firmware... References: <39592A14.23E1EDF0@falcon.niksun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Joy, Current Tigon firmware utilizes a feature provided by the DMA write engine to update the receive buffer consumer automatically. If the TG_DMA_STATE_UPDATE_RX_BUF_CONS bit (b19) is set in the DMA write state register for a DMA operation, the DMA write engine will update the receive buffer consumer to the local NIC DMA address prior to DMA starting. --shihnan Joy Ganguly wrote: > hi all, > > I have been looking into the Tigon firmware code and i am totalyy > puzzled about this: there is no place in the code where > trp->local_mem_conf.rx_buf_consumer is incremented. (except in > h_mac_rx_comp_nohost() which is not called) The tigon documentation says > that it should be incremented by the firmware after the frames have been > dma'd into the host. But h_dma_wr_assist() never does that. Setting a > watchpoint on this register i saw that the register changes when the > "dma write assist producer" register is updated in q_dma_to_host(). Isnt > this strange??.....or am i missing something?? can anybody explain?? > > thanx in advance > > joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 17:20:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id E309737BF9B for <hackers@freebsd.org>; Tue, 27 Jun 2000 17:20:22 -0700 (PDT) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id CAA37530 for <hackers@freebsd.org>; Wed, 28 Jun 2000 02:20:18 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id CAA14290 for <hackers@freebsd.org>; Wed, 28 Jun 2000 02:20:17 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 28 Jun 2000 02:20:17 +0200 (CEST) From: Marius Bendiksen <mbendiks@eunet.no> To: hackers@freebsd.org Subject: buffer cache question Message-ID: <Pine.BSF.4.05.10006280215070.14273-100000@login-1.eunet.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the following code, from /sys/kern/vfs_bio.c : bread(), it appears to me that it is possible for a null pointer to be deferenced? struct buf *bp; bp = getblk(vp, blkno, size, 0, 0); *bpp = bp; /* if not found in cache, do some I/O */ if ((bp->b_flags & B_CACHE) == 0) { It seems, from a very brief inspection of the code, as though getblk() might return a null pointer under certain circumstances. I'd expect my understanding of the code is flawed, as such a thing should have been discovered ages ago, were it a bug, but I feel I should ask. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 27 18:58:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 8365E37C4CF for <hackers@FreeBSD.ORG>; Tue, 27 Jun 2000 18:58:11 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id DAA40909; Wed, 28 Jun 2000 03:58:26 +0200 (CEST) (envelope-from assar) To: Marius Bendiksen <mbendiks@eunet.no> Cc: hackers@FreeBSD.ORG Subject: Re: buffer cache question References: <Pine.BSF.4.05.10006280215070.14273-100000@login-1.eunet.no> From: Assar Westerlund <assar@sics.se> Date: 28 Jun 2000 03:58:26 +0200 In-Reply-To: Marius Bendiksen's message of "Wed, 28 Jun 2000 02:20:17 +0200 (CEST)" Message-ID: <5lya3qh8hp.fsf@assaris.sics.se> Lines: 24 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marius Bendiksen <mbendiks@eunet.no> writes: > In the following code, from /sys/kern/vfs_bio.c : bread(), it appears to > me that it is possible for a null pointer to be deferenced? > > struct buf *bp; > > bp = getblk(vp, blkno, size, 0, 0); > *bpp = bp; > > /* if not found in cache, do some I/O */ > if ((bp->b_flags & B_CACHE) == 0) { > > It seems, from a very brief inspection of the code, as though getblk() > might return a null pointer under certain circumstances. I'd expect my > understanding of the code is flawed, as such a thing should have been > discovered ages ago, were it a bug, but I feel I should ask. Not really. getblk can return NULL if the buffer is busy and the sleep waiting for it time outs. But since slptimeo == 0 in the above call, tsleep cannot time out. It can also return NULL if getnewbuf returns NULL and (slpflag || slptimeo) the last of which is always false in the above call of getblk. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 0:10:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B45837B628 for <hackers@FreeBSD.ORG>; Wed, 28 Jun 2000 00:10:03 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id JAA33003 for hackers@FreeBSD.ORG; Wed, 28 Jun 2000 09:09:57 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id JAA71586 for <hackers@FreeBSD.ORG>; Wed, 28 Jun 2000 09:01:43 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 28 Jun 2000 09:01:42 +0200 (CEST) From: Leif Neland <leifn@neland.dk> Cc: hackers@FreeBSD.ORG Subject: Re: IrDA InfraRed Drivers. Would anyone use them? In-Reply-To: <Pine.BSF.4.21.0006101112410.23796-100000@gateway.posi.net> Message-ID: <Pine.BSF.4.05.10006280859150.56365-100000@arnold.neland.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Talking about IrDA, how much hardware is needed on a Asus P2B ? Is it something which can be build from parts from the local electronics dealer? Is a schematic available? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 1:37:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 92C5B37B8EB for <hackers@FreeBSD.ORG>; Wed, 28 Jun 2000 01:37:17 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id MAA01444; Wed, 28 Jun 2000 12:40:04 +0200 Message-ID: <3959B959.8CA6394D@i-clue.de> Date: Wed, 28 Jun 2000 10:37:45 +0200 From: Christoph Sold <so@server.i-clue.de> Organization: i-clue interactive GmbH X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Leif Neland <leifn@neland.dk> Cc: hackers@FreeBSD.ORG Subject: Re: IrDA InfraRed Drivers. Would anyone use them? References: <Pine.BSF.4.05.10006280859150.56365-100000@arnold.neland.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > Talking about IrDA, how much hardware is needed on a Asus P2B ? > Is it something which can be build from parts from the local electronics > dealer? Yes. Well, local... plan to do some shopping around. > Is a schematic available? c't (German computer bi-weekly) had one a few months ago [http://www.heise.de/ct/ -- beware: no english version available]. Let's see if I can dig it up... c't 25/99, p. 118. Here's a poor man's ascii rendering of the schematic: mainboard | IR-Receiver | Vcc +---------+ Vcc (+5V) -O----------O | | | | | Vo (out)| | IR in (IR Rx)-O----------O | | | | | GND | | -O---o------O | | | +---------+ | Y IR LED | | | Y low-current LED | | -O---+ | IR Receiver: Honeywell Optoelectronics SDP 8600 IR Transceiver: LD 274 (bad fit, limits sending range to ~30cm) LED: TLLR 4400 More explanations at http://home.t-online.de/home/Rainer.Brang/infrarot.html [in German]. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 2:10:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 0D58237B915 for <hackers@FreeBSD.ORG>; Wed, 28 Jun 2000 02:10:30 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id NAA01662; Wed, 28 Jun 2000 13:13:24 +0200 Message-ID: <3959C128.11EBB4B1@i-clue.de> Date: Wed, 28 Jun 2000 11:11:04 +0200 From: Christoph Sold <so@server.i-clue.de> Organization: i-clue interactive GmbH X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Christoph Sold <so@server.ms-agentur.de> Cc: Leif Neland <leifn@neland.dk>, hackers@FreeBSD.ORG Subject: Followup: IrDA InfraRed Drivers. Would anyone use them? References: <Pine.BSF.4.05.10006280859150.56365-100000@arnold.neland.dk> <3959B959.8CA6394D@i-clue.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Sold wrote: > > Leif Neland wrote: > > > > Talking about IrDA, how much hardware is needed on a Asus P2B ? > > Is it something which can be build from parts from the local electronics > > dealer? > Yes. Well, local... plan to do some shopping around. > > > Is a schematic available? Some additional info may be found at http://www.infrarotport.de/. [German language, too] HTH -Christoph Sold -- i-clue GmbH, Endersbacher Str. 57, D-71334 Waiblingen Fon: (0 71 51) 9 59 01-12, Fax: (0 71 51) 9 59 01-55 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 2:57:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from demos.su (mx.demos.su [194.87.0.32]) by hub.freebsd.org (Postfix) with ESMTP id 6F03B37B5A4 for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 02:57:47 -0700 (PDT) (envelope-from azher@sinbin.demos.su) Received: from sinbin.demos.su ([194.87.5.31] verified) by demos.su (CommuniGate Pro SMTP 3.2.4) with SMTP id 7303749 for freebsd-hackers@freebsd.org; Wed, 28 Jun 2000 13:58:25 +0400 Received: by sinbin.demos.su id NAA61564; (8.6.12/D) Wed, 28 Jun 2000 13:56:43 +0400 Received: by sinbin.demos.su id RAA12265; (8.6.12/D) Mon, 26 Jun 2000 17:35:09 +0400 Message-Id: <200006261335.RAA12265@sinbin.demos.su> Subject: new nfs client problems with 4.0-S To: hackers@freebsd.ru Date: Mon, 26 Jun 2000 17:35:08 +0400 (MSD) From: "Alex G. Bulushev" <bag@demos.su> Organization: Demos Internet 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 New problems with 4.0-S nfsv3 client (this problems not exist with 3.4-S) If file have write only permisson we can't append it properly, with read+write permissons all ok, this is serious error ... For demonstartion we use nfsserver and nfsclient mounted via nfsv3/udp: FreeBSD 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Jun 23 14:11:48 MSD 2000 /etc/exports: /mnt/test -maproot=0:0 nfsclient /etc/fstab: nfsserver:/mnt/test /mnt/test nfs rw,nfsv3,mntudp,intr,rdirplus > df Filesystem 512-blocks Used Avail Capacity Mounted n /dev/da0s1a 2781278 1484240 1074536 58% / procfs 8 8 0 100% /proc nfsserver:/mnt/test 52227808 43258416 4791168 90% /mnt/test > For demonstration we create user: test > id uid=10101(test) gid=10101(test) groups=10101(test) > cd > pwd /usr/home/test > ls -al total 4 drwx------ 2 test wheel 512 Jun 26 16:47 . drwxr-xr-x 10 root wheel 512 Jun 26 14:55 .. lrwxr-xr-x 1 root wheel 24 Jun 26 16:25 nfs_link -> /mnt/test -----w---- 1 root test 0 Jun 26 16:46 nonfs_file > file: ~test/nonfs_file created on local filesystem, and file: ~test/nfs_link/nfs_file created on nfs when we append file on nfs we append succesfully only first record, and next records not apended : > cd ~test/nfs_link/ > ls -al total 16 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 0 Jun 26 16:44 nfs_file > echo 000 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 4 Jun 26 16:59 nfs_file > echo 111 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 8 Jun 26 16:59 nfs_file > echo 222 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 8 Jun 26 16:59 nfs_file > echo 333 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 8 Jun 26 16:59 nfs_file > file contain only first record: # cat ~test/nfs_link/nfs_file 000 # and after reading we see new file size! > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. -----w---- 1 root test 4 Jun 26 16:59 nfs_file > with rw permissions no problems exists: > ls -al total 16 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. ----rw---- 1 root test 0 Jun 26 17:24 nfs_file > > echo 000 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. ----rw---- 1 root test 4 Jun 26 17:25 nfs_file > echo 111 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. ----rw---- 1 root test 8 Jun 26 17:25 nfs_file > echo 222 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. ----rw---- 1 root test 12 Jun 26 17:25 nfs_file > echo 333 >> nfs_file > ls -al total 24 drwx------ 2 test test 512 Jun 26 16:50 . dr-xr-xr-x 10 root olsites 512 Jun 26 16:30 .. ----rw---- 1 root test 16 Jun 26 17:26 nfs_file > # cat ~test/nfs_link/nfs_file 000 111 222 333 # without nfs no problems exists: > echo 000 >> nonfs_file > ls -al total 6 drwx------ 2 test wheel 512 Jun 26 16:47 . drwxr-xr-x 10 root wheel 512 Jun 26 14:55 .. lrwxr-xr-x 1 root wheel 24 Jun 26 16:25 nfs_link -> /mnt/pub/root/roots/tet -----w---- 1 root test 4 Jun 26 16:51 nonfs_file > echo 111 >> nonfs_file > ls -al total 6 drwx------ 2 test wheel 512 Jun 26 16:47 . drwxr-xr-x 10 root wheel 512 Jun 26 14:55 .. lrwxr-xr-x 1 root wheel 24 Jun 26 16:25 nfs_link -> /mnt/pub/root/roots/tet -----w---- 1 root test 8 Jun 26 16:51 nonfs_file > echo 222 >> nonfs_file > ls -al total 6 drwx------ 2 test wheel 512 Jun 26 16:47 . drwxr-xr-x 10 root wheel 512 Jun 26 14:55 .. lrwxr-xr-x 1 root wheel 24 Jun 26 16:25 nfs_link -> /mnt/pub/root/roots/tet -----w---- 1 root test 12 Jun 26 16:51 nonfs_file > # cat ~test/nonfs_file 000 111 222 # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 7:10:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9210337BA40; Wed, 28 Jun 2000 07:09:47 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA28568; Wed, 28 Jun 2000 10:09:38 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA82384; Wed, 28 Jun 2000 10:09:38 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin <gallatin@cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 28 Jun 2000 10:09:38 -0400 (EDT) To: Bosko Milekic <bmilekic@dsuper.net> Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-Reply-To: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> References: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14681.63578.312644.776689@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic writes: > This code includes all that was discussed in the previous Email, as > well as a better/actually working external storage facility for clusters. > Previously, it was very difficult to allocate external storage, attach it > to the mbuf, _and_ as well maintain a reference counter for it, primarily > due to the arguments that were taken by ext_free() and ext_buf(). These > have been changed to have a new void * pointer passed in as the second > argument (following the base address of the storage buffer). Also has > been included a void * multi-purpose ext_args pointer in the m_ext > struct, so the caller has much more flexibility now. In fact, the caller > can now attach a "management" or "reference" structure to the m_ext > struct via the ext_args pointer, and have it passed to his ext_free and > ext_buf routines. Naturally, for dynamically sized malloc() external YES! This is wonderful news. I started coding device drivers on Digital UNIX and have long missed this feature. I can't count the number of times I've gotten 90% of the way through doing something with ext mubfs & thought to myself "oh hell, now what am I going to do for an m_ext.ext_ref() function?" On a less enthusiastic note, the amount of whitespace changes make it very difficult to eyeball your diff. Could you re-roll your diffs with -b (to ignore your whitespace changes). ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 8:41:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id A48DE37BA77; Wed, 28 Jun 2000 08:41:27 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA23490; Wed, 28 Jun 2000 11:40:47 -0400 (EDT) Message-Id: <200006281540.LAA23490@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 28 Jun 2000 11:49:27 -0400 To: Andrew Gallatin <gallatin@cs.duke.edu>, Bosko Milekic <bmilekic@dsuper.net> From: Dennis <dennis@etinc.com> Subject: Re: mbuf re-write(s): v 0.2: request-for-comments Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <14681.63578.312644.776689@grasshopper.cs.duke.edu> References: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.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 10:09 AM 6/28/00 -0400, Andrew Gallatin wrote: > >Bosko Milekic writes: > > > This code includes all that was discussed in the previous Email, as > > well as a better/actually working external storage facility for clusters. > > Previously, it was very difficult to allocate external storage, attach it > > to the mbuf, _and_ as well maintain a reference counter for it, primarily > > due to the arguments that were taken by ext_free() and ext_buf(). These > > have been changed to have a new void * pointer passed in as the second > > argument (following the base address of the storage buffer). Also has > > been included a void * multi-purpose ext_args pointer in the m_ext > > struct, so the caller has much more flexibility now. In fact, the caller > > can now attach a "management" or "reference" structure to the m_ext > > struct via the ext_args pointer, and have it passed to his ext_free and > > ext_buf routines. Naturally, for dynamically sized malloc() external > >YES! This is wonderful news. > >I started coding device drivers on Digital UNIX and have long missed >this feature. I can't count the number of times I've gotten 90% of >the way through doing something with ext mubfs & thought to myself >"oh hell, now what am I going to do for an m_ext.ext_ref() function?" > >On a less enthusiastic note, the amount of whitespace changes make it >very difficult to eyeball your diff. Could you re-roll your diffs with >-b (to ignore your whitespace changes). Its not really "wonderful" to those that have already implemented something using the old method. What version is this "patch" likely to find its way into the mainstream code (or will it), as its likely to break our drivers..... Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 8:46:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E7FAD37BA9C; Wed, 28 Jun 2000 08:45:58 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id NAA00459; Wed, 28 Jun 2000 13:26:54 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id OAA01657; Tue, 27 Jun 2000 14:50:40 GMT (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 27 Jun 2000 14:50:40 +0000 From: Nik Clayton <nik@freebsd.org> To: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Cc: Nik Clayton <nik@freebsd.org>, doc@freebsd.org, hackers@freebsd.org, jkh@freebsd.org, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@freebsd.org, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Re: Documentation selection in sysinstall Message-ID: <20000627145040.J1582@kilt.nothing-going-on.org> References: <20000625195203.C470@kilt.nothing-going-on.org> <2884.962037460@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: FreeBSD Project <URL:http://www.freebsd.org/> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 26, 2000 at 09:37:40AM -0700, Jordan K. Hubbard wrote: > > In theory, this is a doddle. sysinstall already lets the user choose from > > packages to install. In practice, I think it's a little more difficult, > > because: > > I'm still wondering why the docs bits can't be, at a minimum, > "front-ended" by the ports collection in a new doc category? We could do this -- I'd probably use the ports collection to front-end the binary packages. Otherwise, the user might as well just go and CVSup the doc/ collection themselves, and build it that way. > > I'm thinking of initially presenting a dialog box that looks > > like this: > > I'm certain that once you start writing code for libdialog, my > suggestions above will start sounding a lot less icky than they > probably do to you right now. :-) I have no intention of going anywhere near libdialog -- like I say, I can either put forward proposals and ideas, and assist with them, or I can try and do one thing at a time. At the moment, keeping up with the -doc mail is almost a full time job in itself. What happened to the plans to move to the TurboVision library? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 8:47:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id CFF2137BDE7; Wed, 28 Jun 2000 08:47:13 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA49472; Tue, 27 Jun 2000 19:07:56 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id JAA00484; Tue, 27 Jun 2000 09:53:33 GMT (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 27 Jun 2000 09:53:33 +0000 From: Nik Clayton <nik@freebsd.org> To: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Cc: Nik Clayton <nik@freebsd.org>, doc@freebsd.org, hackers@freebsd.org, jkh@freebsd.org, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@freebsd.org, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Re: Documentation selection in sysinstall Message-ID: <20000627095332.A316@kilt.nothing-going-on.org> References: <20000625195203.C470@kilt.nothing-going-on.org> <2884.962037460@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <2884.962037460@localhost>; from jkh@zippy.osd.bsdi.com on Mon, Jun 26, 2000 at 09:37:40AM -0700 Organization: FreeBSD Project <URL:http://www.freebsd.org/> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 26, 2000 at 09:37:40AM -0700, Jordan K. Hubbard wrote: > > In theory, this is a doddle. sysinstall already lets the user choose from > > packages to install. In practice, I think it's a little more difficult, > > because: > > I'm still wondering why the docs bits can't be, at a minimum, > "front-ended" by the ports collection in a new doc category? We could do this -- I'd probably use the ports collection to front-end the binary packages. Otherwise, the user might as well just go and CVSup the doc/ collection themselves, and build it that way. > > I'm thinking of initially presenting a dialog box that looks > > like this: > > I'm certain that once you start writing code for libdialog, my > suggestions above will start sounding a lot less icky than they > probably do to you right now. :-) I have no intention of going anywhere near libdialog -- like I say, I can either put forward proposals and ideas, and assist with them, or I can try and do one thing at a time. At the moment, keeping up with the -doc mail is almost a full time job in itself. What happened to the plans to move to the TurboVision library? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 8:52:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 754FC37BD4C; Wed, 28 Jun 2000 08:52:19 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JR58IA9F6O0008QZ@research.kpn.com>; Wed, 28 Jun 2000 17:52:16 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <NV6219JD>; Wed, 28 Jun 2000 17:52:15 +0100 Content-return: allowed Date: Wed, 28 Jun 2000 17:52:15 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> Subject: RE: mbuf re-write(s): v 0.2: request-for-comments To: 'Dennis' <dennis@etinc.com> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D76C9@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Its not really "wonderful" to those that have already > implemented something using the old method. > Unless you get to rip out your own workarounds for the missing functionality and get someone else to support those for you. I think I'll call it delegation through innovation. :-) Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 9: 1: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9CFD437B9B5; Wed, 28 Jun 2000 09:00:58 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA00698; Wed, 28 Jun 2000 12:00:51 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA82559; Wed, 28 Jun 2000 12:00:51 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin <gallatin@cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 28 Jun 2000 12:00:50 -0400 (EDT) To: Dennis <dennis@etinc.com> Cc: Bosko Milekic <bmilekic@dsuper.net>, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-Reply-To: <200006281540.LAA23490@etinc.com> References: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> <14681.63578.312644.776689@grasshopper.cs.duke.edu> <200006281540.LAA23490@etinc.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14682.7393.3441.596574@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: > > Its not really "wonderful" to those that have already implemented something > using the old method. > Speaking as somebody who maintains 3 out-of-tree network drivers & a bunch of local code, all of which makes heavy use of external mbufs, I certainly consider it to be "wonderful." > What version is this "patch" likely to find its way into the mainstream > code (or will it), as its likely to break our drivers..... I presume that the reason it is being presented here is to collect input. This input may influence the patch. I would imagine that it would go into 5.0-CURRENT first. At any rate, you might not need to make changes to anything other than your function prototypes, depending on how your ext_free and ext_ref functions are implemented. He's basically changed the second arg of those functions to take a void * which nobody else is going to look at, so you can cast it to an int & use it as a simple counter or use it as a pointer to a private data structure if you need more state. Currently, that second arg is the ext_size, which was always pretty useless (at least for me..). Its hard to say what other changes are there since there are so many whitespace changes that I cannot easily read it. Perhaps you noticed some other change which could break your drivers? Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 9:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3D6A137BA31; Wed, 28 Jun 2000 09:37:47 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id JAA14313; Wed, 28 Jun 2000 09:38:14 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Nik Clayton <nik@freebsd.org> Cc: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>, doc@freebsd.org, hackers@freebsd.org, jkh@freebsd.org, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@freebsd.org, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Re: Documentation selection in sysinstall In-reply-to: Your message of "Tue, 27 Jun 2000 14:50:40 -0000." <20000627145040.J1582@kilt.nothing-going-on.org> Date: Wed, 28 Jun 2000 09:38:14 -0700 Message-ID: <14310.962210294@localhost> From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What happened to the plans to move to the TurboVision library? We're still working on it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 9:54: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 2F61B37BC30; Wed, 28 Jun 2000 09:53:52 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 137L4Z-00087Z-00; Wed, 28 Jun 2000 18:52:23 +0200 Received: from p3e9d38b7.dip0.t-ipconnect.de ([62.157.56.183] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 137L4Y-0001ZG-00; Wed, 28 Jun 2000 18:52:22 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id C0A62AC27; Wed, 28 Jun 2000 18:52:19 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id E082114B05; Wed, 28 Jun 2000 18:52:12 +0200 (CEST) Date: Wed, 28 Jun 2000 18:52:12 +0200 To: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Cc: Nik Clayton <nik@FreeBSD.ORG>, doc@FreeBSD.ORG, hackers@FreeBSD.ORG, jkh@FreeBSD.ORG, dgl@bsdi.com, jim@cdrom.com, papowell@astart.com, wpaul@FreeBSD.ORG, ceren@magnesium.net, ryan@ryan.net, murray@bsdi.com Subject: Re: Documentation selection in sysinstall Message-ID: <20000628185212.A58389@cichlids.cichlids.com> References: <20000627145040.J1582@kilt.nothing-going-on.org> <14310.962210294@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14310.962210294@localhost>; from jkh@zippy.osd.bsdi.com on Wed, Jun 28, 2000 at 09:38:14AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Jordan K. Hubbard (jkh@zippy.osd.bsdi.com): > > What happened to the plans to move to the TurboVision library? > We're still working on it. Yes, someone should encourage John Baldwin to fix that. For example by promising some cakes or something :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 10:43:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id D294B37BED7; Wed, 28 Jun 2000 10:43:02 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWV00ADTL421R@field.videotron.net>; Wed, 28 Jun 2000 13:40:50 -0400 (EDT) Date: Wed, 28 Jun 2000 13:42:49 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-reply-to: <200006281540.LAA23490@etinc.com> X-Sender: bmilekic@jehovah.technokratis.com To: Dennis <dennis@etinc.com> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-id: <Pine.BSF.4.21.0006281317230.2743-100000@jehovah.technokratis.com> 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, 28 Jun 2000, Dennis wrote: > >YES! This is wonderful news. > > > >I started coding device drivers on Digital UNIX and have long missed > >this feature. I can't count the number of times I've gotten 90% of > >the way through doing something with ext mubfs & thought to myself > >"oh hell, now what am I going to do for an m_ext.ext_ref() function?" > > > >On a less enthusiastic note, the amount of whitespace changes make it > >very difficult to eyeball your diff. Could you re-roll your diffs with > >-b (to ignore your whitespace changes). > > Its not really "wonderful" to those that have already implemented something > using the old method. > > What version is this "patch" likely to find its way into the mainstream > code (or will it), as its likely to break our drivers..... > > Dennis You can cast the void * argument to basically anything you like, so there is little chance that it will break your drivers to the order which you appear to be suggesting. All it would really do is reduce coad bloat and make things less scattered. Actually, network device drivers were one of the motivations for this part of the patch: Bill Paul implements jumbo bufs in if_sk, for example, and has to literally "hide" the address of the softc structure inside the buffer so that he can use it inside his ext_{free, ref} calls. All that this would do is clean things up for him. As this patch is rather big, and does more than just this (i.e. it also completely changes the way mbufs are allocated and freed and thus allows pages allocated from mb_map to be freed back to the map, therefore freeing physical pages as a consequence, etc. -- and there are more changes to come), I think that it's safe to say that there is still a little bit before this goes through. Regards, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 11: 9:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 446BF37C270; Wed, 28 Jun 2000 11:09:08 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWV00CQ1MDC7D@falla.videotron.net>; Wed, 28 Jun 2000 14:08:00 -0400 (EDT) Date: Wed, 28 Jun 2000 14:09:59 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-reply-to: <14681.63578.312644.776689@grasshopper.cs.duke.edu> X-Sender: bmilekic@jehovah.technokratis.com To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Message-id: <Pine.BSF.4.21.0006281358010.2856-100000@jehovah.technokratis.com> 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, 28 Jun 2000, Andrew Gallatin wrote: > YES! This is wonderful news. > > I started coding device drivers on Digital UNIX and have long missed > this feature. I can't count the number of times I've gotten 90% of > the way through doing something with ext mubfs & thought to myself > "oh hell, now what am I going to do for an m_ext.ext_ref() function?" I can imagine. As I've previously mentionned, I'm thinking of adopting NetBSD's reference idea, as it seems very handy here. What it basically assumes is that if you're going to increase the reference count to an object, that you know one of the mbufs also referencing that object (since what you're doing is probably "copying" the data without having to actually perform a memory-to-memory copy -- the reason we have reference counts in the first place). So, if you know the mbuf referencing the same object, you will pass it to the macro and it will "increase a reference count" for it itself. What actually occurs is that the m_ext structure holds a forward/backward pointer (in the style of doubly-linked list) and is linked to all the other mbufs referencing the same object. This would isolate the referencing of external objects to the mbuf subsystem, such that callers don't have to worry about it at all, and can essentially get rid of the ext_ref() routine alltogether. > On a less enthusiastic note, the amount of whitespace changes make it > very difficult to eyeball your diff. Could you re-roll your diffs with > -b (to ignore your whitespace changes). Yeah, I made some "appearence/consistency/cleanliness" changes in /sys/sys/mbuf.h in order to maintain consistency and ensure easy readability of the final product. However, for readability purposes, I posted the no-whitespace-changes diff to the same place: http://www.technokratis.com/code/mbuf/ I should have done this immediately; thanks for the advice! Hope this helps. :-) > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 Cheers, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 12:21:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from griffin.aciri.org (griffin.aciri.org [192.150.187.12]) by hub.freebsd.org (Postfix) with ESMTP id 0C65F37C0EB for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 12:21:07 -0700 (PDT) (envelope-from wilbertdg@hetnet.nl) Received: from hetnet.nl (localhost.aciri.org [127.0.0.1]) by griffin.aciri.org (8.9.3/8.9.3) with ESMTP id MAA86341 for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 12:21:03 -0700 (PDT) (envelope-from wilbertdg@hetnet.nl) Message-ID: <395A501F.50CA476E@hetnet.nl> Date: Wed, 28 Jun 2000 12:21:03 -0700 From: Wilbert de Graaf <wilbertdg@hetnet.nl> X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Getting the plain void* through the generic ioctl processing Content-Type: multipart/alternative; boundary="------------651756F39847F164F7E0CB33" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------651756F39847F164F7E0CB33 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Could anybody advise me on this: For an implementation of IGMPv3, I had to extend the socket api following the draft(s). I had to add two ioctl commands: SIO_GET_MULTICAST_FILTER and SIO_SET_MULTICAST_FILTER. The argument is a structure that has a variable size. FreeBSD uses some macros, and the one I added looks like #define SIO_SET_MULTICAST_FILTER _IOWR('s', 63, struct ip_msfilter*) I couldn't use 'struct ip_msfilter' since this structure has a variable size. Now this macro makes a unsigned long from all this, where the length of the structure is encoded using sizeof(struct ip_msfilter*). This makes the ioctl pre-processing (sys_generic.c) copy 4 bytes from this pointer into the kernel. But this data is worthless to me, since it is the first 4 bytes of the structure itself. What I want is the pointer itself. I understand that I can do this by making people pass the address of a pointer to ioctl(), but this is kind of ugly I think. And besides, the other OS'es don't need this. But the good news is that I found a way around, but the question is if this is okay. If I follow the code, I can make the generic ioctl() preprocessing giving me the datapointer itself when the length equals zero. One way to make the length zero is to change the macro into #define SIO_SET_MULTICAST_FILTER _IOWR('s', 63, struct {}) since sizeof(struct {}) returns zero. My question is, is the ioctl() code in sys_generic.c meant to be able to handle cases where size = 0, or is this a dirty 'trick' that probably won't make it in a next version. Any reason not do solve it like this? - Wilbert --------------651756F39847F164F7E0CB33 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <font face="Courier New,Courier">Could anybody advise me on this:</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">For an implementation of IGMPv3, I had to extend the socket api</font> <br><font face="Courier New,Courier">following the draft(s). I had to add two ioctl commands:</font> <br><font face="Courier New,Courier">SIO_GET_MULTICAST_FILTER and SIO_SET_MULTICAST_FILTER. The argument is a</font> <br><font face="Courier New,Courier">structure that has a variable size. FreeBSD uses some macros, and the</font> <br><font face="Courier New,Courier">one I added looks like</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">#define SIO_SET_MULTICAST_FILTER    _IOWR('s', 63, struct ip_msfilter*)</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">I couldn't use 'struct ip_msfilter' since this structure has a variable</font> <br><font face="Courier New,Courier">size. Now this macro makes a unsigned long from all this, where the</font> <br><font face="Courier New,Courier">length of the structure is encoded using sizeof(struct ip_msfilter*).</font> <br><font face="Courier New,Courier">This makes the ioctl pre-processing (sys_generic.c) copy 4 bytes from</font> <br><font face="Courier New,Courier">this pointer into the kernel. But this data is worthless to me, since it</font> <br><font face="Courier New,Courier">is the first 4 bytes of the structure itself. What I want is the pointer</font> <br><font face="Courier New,Courier">itself. I understand that I can do this by making people pass the</font> <br><font face="Courier New,Courier">address of a pointer to ioctl(), but this is kind of ugly I think. And</font> <br><font face="Courier New,Courier">besides, the other OS'es don't need this.</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">But the good news is that I found a way around, but the question is if</font> <br><font face="Courier New,Courier">this is okay. If I follow the code, I can make the generic ioctl()</font> <br><font face="Courier New,Courier">preprocessing giving me the datapointer itself when the length equals</font> <br><font face="Courier New,Courier">zero. One way to make the length zero is to change the macro into</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">#define SIO_SET_MULTICAST_FILTER    _IOWR('s', 63, struct {})</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">since sizeof(struct {}) returns zero. My question is, is the ioctl()</font> <br><font face="Courier New,Courier">code in sys_generic.c meant to be able to handle cases where size = 0,</font> <br><font face="Courier New,Courier">or is this a dirty 'trick' that probably won't make it in a next</font> <br><font face="Courier New,Courier">version. Any reason not do solve it like this?</font><font face="Courier New,Courier"></font> <p><font face="Courier New,Courier">- Wilbert</font> <br><font face="Courier New,Courier"></font>  <br> </html> --------------651756F39847F164F7E0CB33-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 14:48:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 464C137C150; Wed, 28 Jun 2000 14:48:11 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA53212; Wed, 28 Jun 2000 15:47:40 -0600 (MDT) (envelope-from ken) Date: Wed, 28 Jun 2000 15:47:40 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Dennis <dennis@etinc.com>, Bosko Milekic <bmilekic@dsuper.net>, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: mbuf re-write(s): v 0.2: request-for-comments Message-ID: <20000628154740.A53117@panzer.kdm.org> References: <Pine.BSF.4.21.0006271756020.535-100000@jehovah.technokratis.com> <14681.63578.312644.776689@grasshopper.cs.duke.edu> <200006281540.LAA23490@etinc.com> <14682.7393.3441.596574@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14682.7393.3441.596574@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jun 28, 2000 at 12:00:50PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 28, 2000 at 12:00:50 -0400, Andrew Gallatin wrote: > Dennis writes: > > > > Its not really "wonderful" to those that have already implemented something > > using the old method. > > > > Speaking as somebody who maintains 3 out-of-tree network drivers & a > bunch of local code, all of which makes heavy use of external mbufs, I > certainly consider it to be "wonderful." > > > What version is this "patch" likely to find its way into the mainstream > > code (or will it), as its likely to break our drivers..... > > I presume that the reason it is being presented here is to collect > input. This input may influence the patch. I would imagine that it > would go into 5.0-CURRENT first. > > At any rate, you might not need to make changes to anything other than > your function prototypes, depending on how your ext_free and ext_ref > functions are implemented. He's basically changed the second arg of > those functions to take a void * which nobody else is going to look > at, so you can cast it to an int & use it as a simple counter or use > it as a pointer to a private data structure if you need more state. > Currently, that second arg is the ext_size, which was always pretty > useless (at least for me..). FWIW, I'm in favor of a pointer argument as well. The way I implemented it was actually with a third argument, instead of changing the int to void. i.e.: /* description of external storage mapped into mbuf, valid if M_EXT set */ struct m_ext { caddr_t ext_buf; /* start of buffer */ void (*ext_free) /* free routine if not the usual */ #ifdef EXTRA_MBUF_ARG __P((caddr_t, u_int, void *)); #else __P((caddr_t, u_int)); #endif u_int ext_size; /* size of buffer, for ext_free */ void (*ext_ref) /* add a reference to the ext object */ #ifdef EXTRA_MBUF_ARG __P((caddr_t, u_int, void *)); void *ext_arg; #else __P((caddr_t, u_int)); #endif }; I don't feel too strongly about it either way -- I suppose it's about the same amount of work to port older code. (I just put an ifdef in the sendfile code, which doesn't use the third argument in my tree.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 14:52: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 394E437B971 for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 14:51:56 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id PAA31110 for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 15:51:49 -0600 (MDT) Date: Wed, 28 Jun 2000 15:51:49 -0600 (MDT) From: Nick Rogness <nick@rapidnet.com> To: freebsd-hackers@freebsd.org Subject: 2 routes/same net Message-ID: <Pine.BSF.4.21.0006281550280.30173-100000@rapidnet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe someone on this list knows the answer... How do you add 2 static routes to the same network through different gateways with different metric sizes? (FBSD 4.0-RELEASE,3.3-RELEASE) This is legal to do in routing... Example: # route add -net 192.168.0.0 -netmask 255.255.255.252 192.168.1.1 # route add -net 192.168.0.0 -netmask 255.255.255.252 192.168.1.2 route: writing to routing socket: File exists add net 192.168.0.0: gateway 192.168.1.2: File exists I thought (at 1 time) there was a -metric switch to route(8)? Is -hopcount associated with that? Can you even add 2 routes to the same network? Thanks in adv. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 16:56: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id CA9E737B69C for <freebsd-hackers@freebsd.org>; Wed, 28 Jun 2000 16:55:45 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny12-31.ix.netcom.com [198.211.18.223]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA22650; Wed, 28 Jun 2000 19:55:30 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA06792; Wed, 28 Jun 2000 19:55:28 -0400 (EDT) (envelope-from vsilyaev) Date: Wed, 28 Jun 2000 19:55:28 -0400 From: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> To: Wilbert de Graaf <wilbertdg@hetnet.nl> Cc: freebsd-hackers@freebsd.org Subject: Re: Getting the plain void* through the generic ioctl processing Message-ID: <20000628195528.A6739@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have to declare ioctl as the next: #define SIO_SET_MULTICAST_FILTER _IO ('s', 63) And after that in your code mannualy via functions documented in copy(9) and fetch(9) manpages, to access that user space structure, user space pointer will be available for you as third arument in your ioctl handler. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 16:55:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id BEFDE37C2D5; Wed, 28 Jun 2000 16:55:48 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWW00HYJ21VWG@field.videotron.net>; Wed, 28 Jun 2000 19:46:43 -0400 (EDT) Date: Wed, 28 Jun 2000 19:48:43 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-reply-to: <395A4434.1E513102@chiaro.com> X-Sender: bmilekic@jehovah.technokratis.com To: Dave Baukus <dbaukus@chiaro.com> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-id: <Pine.BSF.4.21.0006281946210.3363-100000@jehovah.technokratis.com> 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, 28 Jun 2000, Dave Baukus wrote: > All this talk of mbuf prompts me to point a small bug in M_PREPEND that > was introduced somewhere between 3.3 and 4.0; maybe its also in 5.x. > [...] > If m_prepend() fails then .... No longer an issue in 5.0-CURRENT, and I'm looking at version 1.50 of mbuf.h Although you pointing it out did lead me to looking at m_prepend() itself, and noticing some bad style issues, like casting on NULLs (ick!) which I'll fix in the patch along with adding the new reference stuff. Thanks! > -- > Dave Baukus > dbaukus@chiaro.com > Chiaro Networks ltd. > Richardson, Texas, USA. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 28 16:57:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 6F69637C234; Wed, 28 Jun 2000 16:57:40 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWW00GP61WUFU@falla.videotron.net>; Wed, 28 Jun 2000 19:43:43 -0400 (EDT) Date: Wed, 28 Jun 2000 19:45:42 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: mbuf re-write(s): v 0.2: request-for-comments In-reply-to: <20000628154740.A53117@panzer.kdm.org> X-Sender: bmilekic@jehovah.technokratis.com To: "Kenneth D. Merry" <ken@kdm.org> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-id: <Pine.BSF.4.21.0006281943470.3355-100000@jehovah.technokratis.com> 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, 28 Jun 2000, Kenneth D. Merry wrote: > FWIW, I'm in favor of a pointer argument as well. The way I implemented it > was actually with a third argument, instead of changing the int to void. > i.e.: [...] > I don't feel too strongly about it either way -- I suppose it's about the > same amount of work to port older code. (I just put an ifdef in the > sendfile code, which doesn't use the third argument in my tree.) The u_int is really unnecessary. If the caller needs more important information, he can pass anything he likes, including a data structure, or even a pointer to the mbuf. So this information can be extracted in either case. > > Ken > -- > Kenneth Merry > ken@kdm.org > > -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 0:37:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (ppp-247.dialup.clari.net.au [203.57.253.247]) by hub.freebsd.org (Postfix) with ESMTP id A527437B94D for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 00:37:13 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA01760; Thu, 29 Jun 2000 00:43:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200006290743.AAA01760@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilbert de Graaf <wilbertdg@hetnet.nl> Cc: freebsd-hackers@freebsd.org Subject: Re: Getting the plain void* through the generic ioctl processing In-reply-to: Your message of "Wed, 28 Jun 2000 12:21:03 PDT." <395A501F.50CA476E@hetnet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Jun 2000 00:43:32 -0700 From: Mike Smith <msmith@freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could anybody advise me on this: > > For an implementation of IGMPv3, I had to extend the socket api > following the draft(s). I had to add two ioctl commands: > SIO_GET_MULTICAST_FILTER and SIO_SET_MULTICAST_FILTER. The argument is a > > structure that has a variable size. FreeBSD uses some macros, and the > one I added looks like > > #define SIO_SET_MULTICAST_FILTER _IOWR('s', 63, struct ip_msfilter*) > > I couldn't use 'struct ip_msfilter' since this structure has a variable > size. Now this macro makes a unsigned long from all this, where the > length of the structure is encoded using sizeof(struct ip_msfilter*). > This makes the ioctl pre-processing (sys_generic.c) copy 4 bytes from > this pointer into the kernel. But this data is worthless to me, since it > > is the first 4 bytes of the structure itself. What I want is the pointer > > itself. This is what this should give you - a pointer to the structure _in_user_space_. > I understand that I can do this by making people pass the > address of a pointer to ioctl(), but this is kind of ugly I think. And > besides, the other OS'es don't need this. The ioctl interface is standard, everyone does it this way. If you think about it for a moment, when you're defining an _IOWR() ioctl, you're telling the macros that you want the kernel to be able to modify the pointer that you're passing in, so of course it has to have storage space in user space. If you're passing in a pointer to a structure elsewhere, you should be using _IOR() anyway, since you don't want the pointer copied back out. In this case, the interface is the same purely for orthagonality's sake. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 6:32:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C4C0B37B861 for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 06:32:18 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id GAA25048; Thu, 29 Jun 2000 06:21:29 -0700 (PDT) Message-Id: <200006291321.GAA25048@implode.root.com> To: Bosko Milekic <bmilekic@dsuper.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Tue, 20 Jun 2000 13:43:42 EDT." <Pine.BSF.4.21.0006201313440.3697-100000@jehovah.technokratis.com> From: David Greenman <dg@root.com> Reply-To: dg@root.com Date: Thu, 29 Jun 2000 06:21:28 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In an attempt to eliminate or significantly reduce the hogging of > physical memory by unused mbufs, I have begun re-writing some of the mbuf > subsystem. I've re-written the allocator and designed an actual free > routine, and have also considerably re-written the MGET, MGETHDR, and > MFREE macros. I still have some work to do with this, notably > optimisation, but I have not been able to do any profiling whatsoever as > profiling, I repeat, seems presently broken on -CURRENT. > > This is particularily useful for machines which see "peak" mbuf usage > periods, where many mbufs are allocated, only to be freed a little while > later, but which will unfortunately remain on the free list, holding on > to physical memory (for a graphical example, see the THIRD graph at > http://www.technokratis.com/stats/mbuf.html). We used to do this in FreeBSD, but found that it was a bad idea for performance reasons. Freeing and reallocating memory from the high-level VM system is quite expensive and the trend in NICs these days is towards needing the code to be even faster, not slower. Further, if the 'peak' is reached often, then you're probably not really gaining much by freeing the memory back to the common pool. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 6:36:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 14FDE37B8B7 for <hackers@freebsd.org>; Thu, 29 Jun 2000 06:36:32 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 137eUW-0006xJ-00 for hackers@FreeBSD.org; Thu, 29 Jun 2000 15:36:28 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: hackers@FreeBSD.org Subject: Building a debugging libc Date: Thu, 29 Jun 2000 15:36:27 +0200 Message-ID: <26740.962285787@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I need to build a debuggable libc, ideally a static library. I thought it'd be as simple as ``cd /usr/src/lib/libc; make obj depend all''. However, doing so scores me the following error: cc -O -g -pipe -c /a/usr/src/lib/libc/../libc/gen/_spinlock_stub.c -o _spinlock_stub.o /a/usr/src/lib/libc/../libc/gen/_spinlock_stub.c:40: spinlock.h: No such file or directory /a/usr/src/lib/libc/../libc/gen/_spinlock_stub.c:53: syntax error before `*' /a/usr/src/lib/libc/../libc/gen/_spinlock_stub.c:61: syntax error before `*' This is with a clean obj tree with sources supped at 10H30 GMT last night. Any ideas? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 6:45:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id A70C337B7D7 for <hackers@freebsd.org>; Thu, 29 Jun 2000 06:45:43 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 137edQ-00070o-00 for hackers@FreeBSD.org; Thu, 29 Jun 2000 15:45:40 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: hackers@FreeBSD.org Subject: Re: Building a debugging libc In-reply-to: Your message of "Thu, 29 Jun 2000 15:36:27 +0200." <26740.962285787@axl.ops.uunet.co.za> Date: Thu, 29 Jun 2000 15:45:40 +0200 Message-ID: <26957.962286340@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jun 2000 15:36:27 +0200, Sheldon Hearn wrote: > I need to build a debuggable libc, ideally a static library. I thought > it'd be as simple as ``cd /usr/src/lib/libc; make obj depend all''. > However, doing so scores me the following error: Bleh, nevermind. I was doing ``make CFLAGS='-O -g -pipe' obj depend all''. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 8: 9:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from marao.utad.pt (marao.utad.pt [193.136.40.3]) by hub.freebsd.org (Postfix) with ESMTP id B09A037B578 for <freebsd-hackers@FreeBSD.org>; Thu, 29 Jun 2000 08:09:01 -0700 (PDT) (envelope-from jsilva@utad.pt) Received: from apache (pceii041.utad.pt [193.137.96.76]) by marao.utad.pt (8.9.3/8.9.3) with SMTP id QAA23705; Thu, 29 Jun 2000 16:06:20 +0200 (MET DST) Message-Id: <200006291406.QAA23705@marao.utad.pt> X-Sender: sasilva@gcom.utad.pt X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 29 Jun 2000 16:06:04 +0100 To: freebsd-hackers@FreeBSD.org From: "Jorge Sa' Silva" <jsilva@utad.pt> Subject: kernel function Cc: sasilva@gcom.utad.pt 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 tried to use the sysctl() function in the kernel space, but when I do the "kernel make" it doesn't recognize the sysctl(). I did the include of <sys/sysctl.h> and <sys/types.h>. Do you know where is the problem? Thanks in advance Jorge sasilva@gcom.utad.pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 8:58:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id AE88137BC82 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 08:58:08 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id LAA05504 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 11:58:04 -0400 (EDT) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id LAA26180 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 11:58:05 -0400 (EDT) Received: from rac9.wam.umd.edu (howardjp@localhost) by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA26175 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 11:58:05 -0400 (EDT) Message-Id: <200006291558.LAA26175@rac9.wam.umd.edu> X-Authentication-Warning: rac9.wam.umd.edu: howardjp owned process doing -bs To: freebsd-hackers@freebsd.org Subject: /etc/security -> /etc/periodic/security ? Date: Thu, 29 Jun 2000 11:58:04 -0400 From: James Howard <howardjp@wam.umd.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will we be seeing a move in this direction towards a more configurable security script? Is anyone planning it? I am porting the scripts to Linux and will hold off on security if nothing is being planned or make the changes myself. I just do not want to duplicate efforts. Also, I found a bug with a patch in conf/19567. Please apply :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 9: 3:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id D327937BDF4 for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 09:03:36 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWX000EMB32F7@field.videotron.net> for freebsd-hackers@FreeBSD.ORG; Thu, 29 Jun 2000 11:59:26 -0400 (EDT) Date: Thu, 29 Jun 2000 12:01:26 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: <200006291321.GAA25048@implode.root.com> X-Sender: bmilekic@jehovah.technokratis.com To: David Greenman <dg@root.com> Cc: freebsd-hackers@FreeBSD.ORG Message-id: <Pine.BSF.4.21.0006291154100.3622-100000@jehovah.technokratis.com> 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, 29 Jun 2000, David Greenman wrote: > We used to do this in FreeBSD, but found that it was a bad idea for > performance reasons. Freeing and reallocating memory from the high-level > VM system is quite expensive and the trend in NICs these days is towards > needing the code to be even faster, not slower. Further, if the 'peak' is > reached often, then you're probably not really gaining much by freeing > the memory back to the common pool. > > -DG What was previously done at some point was use the kernel malloc() to allocate mbufs. As you know, this is a general purpose allocator that has to first determine what algorithm to use and then store the object correctly according to its size. This allocator is faster than that one. This allocator knows that it only has to deal with mbufs and knows that all of these mbufs are of the same size. I am not proposing to return to malloc(), I am proposing the new allocator. Also, the "peak" in this case is not reached often, obviously. It is designed with just that idea in mind. But, if the administrator feels that it is, I have provided the following mechanism: { jehovah:/home/bmilekic }>> sysctl -A | grep min_on_avail kern.ipc.min_on_avail: 0 With this sysctl, the administrator can set a "minimum required" count for mbufs. In other words, it is possible to easily tell the system to keep as many mbufs as you'd like cached on the free lists. > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > Manufacturer of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. -Bosko -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 9:30:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 06F2237BC23 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 09:30:32 -0700 (PDT) (envelope-from Konstantin.Chuguev@dante.org.uk) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 137hCx-00010f-00 for freebsd-hackers@freebsd.org; Thu, 29 Jun 2000 17:30:31 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 137hCq-0001DI-00 for freebsd-hackers@freebsd.org; Thu, 29 Jun 2000 17:30:24 +0100 Message-ID: <395B79A0.AB99EA21@dante.org.uk> Date: Thu, 29 Jun 2000 17:30:24 +0100 From: Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk> Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.73 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Periodic scripts [Was: Re: /etc/security -> /etc/periodic/security ?] References: <200006291558.LAA26175@rac9.wam.umd.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Howard wrote: > Will we be seeing a move in this direction towards a more configurable > security script? Is anyone planning it? > > I am porting the scripts to Linux and will hold off on security if > nothing is being planned or make the changes myself. I just do not want > to duplicate efforts. > I have administered quite a big network of FreeBSD servers and routers for more than 3 years. These periodic scripts are one of the most attractive features for a sysadmin/netadmin in FreeBSD. I really enjoyed just reading a few dozens messages from my FreeBSD boxes every morning, telling me about problems or that everything is all right. Fortunately, all right was much more often :-) Unfortunately, the OK-messages are of the same size as any alerts, so one needs to read them carefully to notice any suspicious conditions. IMO, introducing a sort of silent mode to these periodic scripts would help sysadmins. The idea is as follows: At present there are groups of scripts (daily, weekly, monthly, security) that write their reports to one email message per group. Often that message consists just of OK or empty lines from every script. In the silent mode, scripts produce no output in case of success (each script knows its success condition itself). Or they can output something, but then they should return the 0 result code for success, non-zero otherwise. A meta-script (periodic) intercepts their output, waits for their results and sends the output to mail agent only if the results are non-zero. If all scripts finished successfully, the meta-script can send just one line (or even empty message, indicating that everything is OK) to a sysadmin. The silent mode could be enabled in rc.conf for instance... Your suggestions? Regards, Konstantin. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 10:52:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.intrepid.net (elvis.intrepid.net [209.190.164.163]) by hub.freebsd.org (Postfix) with ESMTP id 44A4837C07F for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 10:52:43 -0700 (PDT) (envelope-from mark@elvis.intrepid.net) Received: (from mark@localhost) by elvis.intrepid.net (8.9.3/8.9.3) id NAA11191 for freebsd-hackers@freebsd.org; Thu, 29 Jun 2000 13:52:36 -0400 (EDT) (envelope-from mark) Date: Thu, 29 Jun 2000 13:52:36 -0400 From: Mark Conway Wirt <mark@intrepid.net> To: freebsd-hackers@freebsd.org Subject: Kernel locking problems in 4.0-stable? Message-ID: <20000629135236.G5671@intrepid.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I last upgraded -stable from source (18 June), my box stopped local delivering mail reliably. Upon investigation, it looks like procmail is acquiring a lock and then hanging. By turning on verbose messages in procmail, sometimes the mail goes though, and sometimes a lock is acquired and just hangs. Have there been any changes to the kernel locking mechanism lately? I've written the the procmail maintainer to see if he had any suggestions, but did not hear back. I don't know what could be causing this, but if anyone has any suggestions for debugging the problem, I'd like to know. TIA. --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 11:28:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id C383937B9DA; Thu, 29 Jun 2000 11:27:59 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 137hYE-000Lxm-00; Thu, 29 Jun 2000 17:52:30 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 137hYE-000BzC-00; Thu, 29 Jun 2000 17:52:30 +0100 Date: Thu, 29 Jun 2000 17:52:30 +0100 From: Ben Smithurst <ben@scientia.demon.co.uk> To: James Howard <howardjp@wam.umd.edu>, brian@FreeBSD.org Cc: freebsd-hackers@freebsd.org Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000629175230.A48373@strontium.scientia.demon.co.uk> References: <200006291558.LAA26175@rac9.wam.umd.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006291558.LAA26175@rac9.wam.umd.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable James Howard wrote: > Will we be seeing a move in this direction towards a more configurable > security script? Is anyone planning it? I hope so. I've wondered for a while why security wasn't changed in the way {daily,weekly,monthly} were. This seems easy enough to break into separate files so I could probably do it myself if no-one else has planned it. Brian? As creator of periodic.conf, what do you think? --=20 Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 352rD7WVwL3qk3eGi90TKRyrD3my1L41 iQCVAwUBOVt+zSsPVtiZOS99AQHnXgP/aY6rBLjKIbxJF1AUPjT3S4q0BWUV63ML jTSukDEs/Jylx7urYdDBAF0KjzCFwM3zyekYyCZI7mqCcJ9nQI4Z4vQF9eegvGPV 838dUxN+oMg6YnljVhqYy75ho/TtXNu5TxKES9xrIPwR+qMFKJvIqLyS7yecDhFH iRQQCoMbdIc= =Sqyj -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 11:50:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 62EE737B82D for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 11:50:27 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA02851; Thu, 29 Jun 2000 19:46:12 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA00460; Thu, 29 Jun 2000 18:27:06 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006291727.SAA00460@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: James Howard <howardjp@wam.umd.edu> Cc: freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: /etc/security -> /etc/periodic/security ? In-Reply-To: Message from James Howard <howardjp@wam.umd.edu> of "Thu, 29 Jun 2000 11:58:04 EDT." <200006291558.LAA26175@rac9.wam.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Jun 2000 18:27:06 +0100 From: Brian Somers <brian@Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Will we be seeing a move in this direction towards a more configurable > security script? Is anyone planning it? > > I am porting the scripts to Linux and will hold off on security if > nothing is being planned or make the changes myself. I just do not want > to duplicate efforts. > > Also, I found a bug with a patch in conf/19567. Please apply :) I've changed /etc/security in -current by adding switches to the scripts command line and making those switches configurable in /etc/periodic.conf. If you want to take this further, I would think it best to keep it controllable from periodic.conf - but feel free to argue about specifics :-) I wouldn't mind if you wanted to pass any patches by me. > Jamie Cheers. -- Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 12:35:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.networkrichmond.com (kronos.networkrichmond.com [64.240.180.22]) by hub.freebsd.org (Postfix) with ESMTP id 0FB9837BFDE for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 12:35:06 -0700 (PDT) (envelope-from kbyanc@posi.net) X-Provider: Network Richmond, LLC. http://www.networkrichmond.com/ Received: from localhost (kbyanc@localhost) by kronos.networkrichmond.com (8.9.3/8.9.3/antispam) with ESMTP id PAA10691; Thu, 29 Jun 2000 15:34:53 -0400 (EDT) Date: Thu, 29 Jun 2000 15:34:53 -0400 (EDT) From: Kelly Yancey <kbyanc@posi.net> X-Sender: kbyanc@kronos.networkrichmond.com To: "Jorge Sa' Silva" <jsilva@utad.pt> Cc: freebsd-hackers@FreeBSD.ORG, sasilva@gcom.utad.pt Subject: Re: kernel function In-Reply-To: <200006291406.QAA23705@marao.utad.pt> Message-ID: <Pine.BSF.4.05.10006291530310.9682-100000@kronos.networkrichmond.com> 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, 29 Jun 2000, Jorge Sa' Silva wrote: > Hi > > I tried to use the sysctl() function in the kernel space, > but when I do the "kernel make" it doesn't recognize the sysctl(). I did the > include of <sys/sysctl.h> and <sys/types.h>. > Do you know where is the problem? > In theory, you don't need to use sysctl in kernel space. The purpose of sysctl is to present kernel data to userland in a structured manner. Presumably, kernel code can already access kernel data :) Just grep the code for the SYSCTL definition you would like to access and see which variable or function it refers to. Then just access that variable/call that function yourself. Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 14:23:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 1A37737C16C for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 14:23:13 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 137kdo-000MBM-00; Thu, 29 Jun 2000 21:10:28 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 137kdo-000BT0-00; Thu, 29 Jun 2000 21:10:28 +0100 Date: Thu, 29 Jun 2000 21:10:28 +0100 From: Ben Smithurst <ben@scientia.demon.co.uk> To: Brian Somers <brian@Awfulhak.org> Cc: James Howard <howardjp@wam.umd.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000629211028.B48373@strontium.scientia.demon.co.uk> References: <howardjp@wam.umd.edu> <200006291727.SAA00460@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5G06lTa6Jq83wMTw" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006291727.SAA00460@hak.lan.Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5G06lTa6Jq83wMTw Content-Type: multipart/mixed; boundary="Bn2rw/3z4jIqBvZU" Content-Disposition: inline --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Brian Somers wrote: >> Will we be seeing a move in this direction towards a more configurable >> security script? Is anyone planning it? >>=20 >> I am porting the scripts to Linux and will hold off on security if >> nothing is being planned or make the changes myself. I just do not want >> to duplicate efforts. >>=20 >> Also, I found a bug with a patch in conf/19567. Please apply :) >=20 > I've changed /etc/security in -current by adding switches to the=20 > scripts command line and making those switches configurable in=20 > /etc/periodic.conf. >=20 > If you want to take this further, I would think it best to keep it=20 > controllable from periodic.conf - but feel free to argue about=20 > specifics :-) >=20 > I wouldn't mind if you wanted to pass any patches by me. Try the attached. They haven't been thoroughly tested, but that's what -CURRENT is for, right? :-) I even remembered to update the manual page this time... --=20 Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="security.diff" Content-Transfer-Encoding: quoted-printable Index: ../man5/periodic.conf.5 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/share/man/man5/periodic.conf.5,v retrieving revision 1.4 diff -u -r1.4 periodic.conf.5 --- periodic.conf.5 2000/06/27 12:04:43 1.4 +++ periodic.conf.5 2000/06/29 20:09:19 @@ -34,7 +34,7 @@ .Sh DESCRIPTION The file .Nm periodic.conf -contains a description of how daily, weekly and montly system maintenance +contains a description of how daily, weekly and monthly system maintenance jobs should run. It resides in the .Pa /etc/defaults @@ -216,7 +216,7 @@ .Dq YES if you want to run .Pa /etc/uuclean.daily . -.it Ar daily_status_disks_enable +.It Ar daily_status_disks_enable (bool) Set to .Dq YES if you want to run @@ -271,28 +271,17 @@ .It Ar daily_status_security_enable (bool) Set to .Dq YES -if you want to run -.Pa /etc/security . +if you want to run the scripts in +.Pa /etc/periodic/security . .It Ar daily_status_security_inline (bool) Set to .Dq YES -if you want to run -.Pa /etc/security -inline. +if you want to include the output of the scripts in +.Pa /etc/periodic/security +inline in the daily report. The alternative is to run it as a background job, mailing the output to -.An root . -.It Ar daily_status_security_noamd -(bool) Set to -.Dq YES -if you want to ignore -.Xr amd 8 -mounts when comparing against yesterdays filesystem mounts. -.It Ar daily_status_security_nomfs -(bool) Set to -.Dq YES -if you want to ignore -.Xr mfs 8 -mounts when comparing against yesterdays filesystem mounts. +.An root +separately. .It Ar daily_status_mail_rejects_enable (bool) Set to .Dq YES @@ -303,6 +292,23 @@ (str) Set to a list of extra scripts that should be run after all other daily scripts. All scripts must be absolute path names. +.El +.Pp +The following variables are used by the standard scripts that reside in +.Pa /etc/periodic/security : +.Bl -tag -offset 4n -width 2n +.It Ar security_mount_ignore_amd +(bool) Set to +.Dq YES +if you want to ignore +.Xr amd 8 +mounts when comparing against yesterdays filesystem mounts. +.It Ar security_mount_ignore_mfs +(bool) Set to +.Dq YES +if you want to ignore +.Xr mfs 8 +mounts when comparing against yesterdays filesystem mounts. .El .Pp The following variables are used by the standard scripts that reside in Index: defaults/periodic.conf =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/etc/defaults/periodic.conf,v retrieving revision 1.4 diff -u -r1.4 periodic.conf --- periodic.conf 2000/06/28 06:51:37 1.4 +++ periodic.conf 2000/06/29 17:23:33 @@ -99,14 +99,19 @@ # 450.status-security daily_status_security_enable=3D"YES" # Security check daily_status_security_inline=3D"NO" # Run inline ? -daily_status_security_noamd=3D"NO" # Don't check amd mounts -daily_status_security_nomfs=3D"NO" # Don't check mfs mounts =20 # 460.status-mail-rejects daily_status_mail_rejects_enable=3D"YES" # Check mail rejects =20 # 999.local daily_local=3D"/etc/daily.local" # Local scripts + + +# Security options + +# 110.mount-changes +security_mount_ignore_amd=3D"NO" # Don't check amd mounts +security_mount_ignore_mfs=3D"NO" # Don't check mfs mounts =20 =20 # Weekly options Index: periodic/daily/450.status-security =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/etc/periodic/daily/450.status-security,v retrieving revision 1.4 diff -u -r1.4 450.status-security --- 450.status-security 2000/06/23 01:18:23 1.4 +++ 450.status-security 2000/06/29 17:31:30 @@ -13,30 +13,28 @@ =20 case "$daily_status_security_enable" in [Yy][Ee][Ss]) - if [ -f /etc/security -a -x /usr/sbin/sendmail ] + if [ -d /etc/periodic/security -a -x /usr/sbin/sendmail ] then echo "" echo "Security check:" =20 - case "$daily_status_security_noamd" in - [Yy][Ee][Ss]) - args=3D-a;; - *) - args=3D;; - esac + ou=3D$(umask) + umask 027 =20 - case "$daily_status_security_nomfs" in - [Yy][Ee][Ss]) - args=3D"$args -m";; - esac - case "$daily_status_security_inline" in [Yy][Ee][Ss]) - sh /etc/security -s $args;; + # XXX duplication of /usr/sbin/periodic + for file in /etc/periodic/security/*; do + if [ -x $file -a ! -d $file ]; then + $file + fi + done ;; =20 *) echo " (output mailed separately)" - sh /etc/security $args 2>&1 | sendmail root;; + periodic security 2>&1 | sendmail root ;; esac + + umask $ou fi;; esac --Bn2rw/3z4jIqBvZU Content-Type: application/x-tar-gz Content-Disposition: attachment; filename="security.tar.gz" Content-Transfer-Encoding: base64 H4sIAPyHWzkAA+1Z+2/bNhDOr9FfcVWEulmqh99bA2fA1nUIsG4F2mEY8nBlibKJyJIqSnG9 JPvbd6QkW45lK1syD0P5AYks8nhHUvf4REUkpqFLHZMRJ41pMjf3nhzQsfrdLuwBNPtdi18B Wp3smsEC6Ddbvb6Ff10Ua3U73T3oPv1U1pGyxI4B9kYk2CqHYp63iwntFtHa82+2LOMPEod6 St2nsdG0rF6ns/n5t9rd4vlb/XYLxTrdfmcPrKcxvx1f+PM/eGaOaGCyiXKgHID2Jibku/ev NXH3/YQ4V+CFMdiOE6ZBwmBGkwnY8Ovpawg94G6CkgpxJiGoan51+DAajMVIdCLGRa1XqmLP rkB/8woaWnswsOAmimmQgNZ8qbXvGmCSxDGnNktIbEQ2YzNX+a835wtARfxblsFI8mTRXxv/ TV4cFvHfsnj8t7s9Gf+7wMPi35nYwZgwoAFkrgEe9fHeDlxwyTV1CFOUn375cWBe27Hph2Pl w9t32U2cBuZQOBcxNE2ZhCwZaC/4JbCn5HBj8thkB/MITu11GDQSmNjXBAIx5CWM0gSSCWXg hjgimRAgn1J6bfsEkwxmIN7ihNMp3hIXQpQe+aFzZaC2n8OEYL+NcgEpZMOYjmlg+xDF4cgn U/ZSNEchY3REfQwVLhlekxiXGOCUUREXsOMxmg/BxwE4G5ZQ34cJweUbaEvBffk45ckU9ARS j8EtjGMSgX4NKgQhw0Wr2MZwjg12bOKqzePn8XED23j+bNxAnjbbcNf4qOA2gXbz9t2dMpvg VsEZaAegjwk04eIYt0LZF8YGWlPZZxPqJcq+R3E3tXwOn9EAzmQeEfDgXNnfP38BOiaFKejp 0WfQ8eHnt+PV2xBvzw/XhrDVIYzL6GLGluLy3b2Fz2KHdAv0ADDaffztf3D5msM4gaNv4ARX 9IEvSaEeLugZ6B62oHvdmZlXGEno2nO+QNzwQNkvXCj/EYRV4tjtRLnmqn7Fo8LgM3CmUaW9 fOyJeChB6vsb7Gs33L3vChd2qedxt93nP0AfbdGNT+t6Q3e5bU54leRzzuS3Lok/CNw/lKmq pxX5/2vLSJxoFtsRduozO+bOzR6RY+r4X7vdWeb/Ls//favXlPl/F9iW/99PwhmgKwxzX4Dc F2BKGLOxHnDut5L167J7ERkx8VKe4ZwwCIiT0DDgAfKHgxmY+yrqNAsbhvXVasMiYVJQL7VF KBhf3VOqSvr4AFTEf9MyRHHQ86r/aBs18d+yuv3S+z9//+v22pL/7QS18V+ifpzdzLAYCU42 x7ibIjOLCQhvIe5aNng4BzyAU0G6UBlSJhvGfjhC5pUZ4QHt0XEa2zxRCOsvgaVITWmC0+Kk SvAEPc7eIV3i2amfMLPwbYMrgAtFFGvuccY2QSHBwjR2yLDoGPIOljGEcRDGZMDnPLKdK0yJ PONMI5xcxgqVV1iKi2gair0ZZoOG9tR9NdBcm/rzIfpTkrLhQjAIsfduy+ApkojNg7EX+ZJj M4JZdqN1FfdLrO/s9/nF2Q/k4uw9uzhU9vNFqVr24/aSz1SF42OFMNup0YumH6yXL6Kk94xz wKJXhQt4/hzZlztQScGJtZus8+D2DmnxrejFMsGfeM5gIywIGjYXBPJEcJ2CmpUYpCgifMx9 +rjkbyUCeU+ad3L6iKrX+pD3+UvieN+MGLLkjNA6ed7caFnjQVGOuTy2yjHHqeSSS1aZw37O C9e6lg0lBilEq5eF/l7PICX+z6io/20rO38LYxd97vHlv57/W+Xz3w6v/92+Jev/LvBPzn8x PRYOwt9xa06Ay760UFQ+Df75DebsJk/9WhOe/Qnm5dnBkX5hipbWYKCqi6NiS54TPzEq4r9j GS4JKHH1CAkOSR6dAerOf5H13zv/7WIakPG/Czws/nNHgMwvYDQHGnmzRxB+pEtcA+g2cEa0 ZEe3kFE/FU3Nb2OC+eU2DWJiOxN1cTBYQe6ywy+u80Hs7r54Qe9WjtKW3asMb83WxoPBdX6X H4DkG5nv6yqj26R+sTWXJ2pO2ypEly33Od7GtUma9+WiIv93LYN7h44R7dMpTR5to47/9Zbn P0X+77Xl+e9OUHv+I9J0nPKvcLMJdSbZRzeRkDGB8SMh9BMQjsLrwaYSoJy+e/PbEFPP8KfT t6cfBh/xZdZJfP7+H5DEoOJfZGBSuibxKGRkKFRibYBFVv2YnfNo34JOPoHFiwcm1FXFdyqq JNi5yP/LOpMfHKtixvwjGzq/mIFOxHeshnl57h6ds6MXeDk0j/MvbWj0BTLTkwE0tFVjjcPG 8mNVVo10xufEG9QtJUjMabFvxW6KMsDPwAuNO0jMFfHfs4wrEgfE5xngKWzUxX+/vxb/zaaM /52gNv4zVxDOuvGzz9/ifS6qGa9wvlpaJ4b8DV5Xkq8kdqX+KmZXNrdG7WrO73J+V7FrVSSv wtJGlrcqW2rayvNWllqRTyriv28ZOG8a6J5NfXyS//b7H7StUvx3euL9T57/7Aa18S9cAQpX +MdffFfVPP5j74o++alXQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkLiC8VfphGa JwBQAAA= --Bn2rw/3z4jIqBvZU-- --5G06lTa6Jq83wMTw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: N12c67a9SmFjDedyMNpsB5giUEpxVB63 iQCVAwUBOVutMysPVtiZOS99AQHnrgQAi9J0pwmZYWl56mnedaHq6SR5yWSI8pz6 1iaiJzkyxPxtuwXHeFRgh8z4QcVT6pvuHUDY0xFCf3x61u5T/5vP2HBFIOAVOVwJ KtOG7AEsQL1WCuhuRjilWRKX0McVJ+CzvZI3Dd+yB6iDM9ulixpVFYKTpaYcQRNN JD7RqZlOOsE= =tern -----END PGP SIGNATURE----- --5G06lTa6Jq83wMTw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15: 7:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id DA18637B645 for <hackers@freebsd.org>; Thu, 29 Jun 2000 15:07:29 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 63665 invoked from network); 29 Jun 2000 22:07:25 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 29 Jun 2000 22:07:25 -0000 Date: Thu, 29 Jun 2000 15:00:59 -0700 (PDT) From: Jaye Mathisen <mrcpu@internetcds.com> X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: vinum and superblocks. Message-ID: <Pine.BSF.4.21.0006291456180.18895-100000@schizo.cdsnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure what the right thing to do here is, or even if it's a real problem, but: I have 8 75GB IBM drives striped in a big raid 0 for monkeying with. newfs -i 131072 -v /dev/vinum/bighonkindisk seems to very nicely put all the data that newfs write out on to the first disk... It least, only the first disk gets any io, accoring to systat and iostat. Which would seem to me to be problematic in terms of using fsck -b, and also just for the fact that it would seem that you would have to hit that disk more often than the others, even though it's striped. I realize there's no protection with the raid 0, but the load doesn't seem evenly distributed on a transaction basis, even though the data is evenly spread. What's the right thing to do here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:22:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id 57F8F37C155 for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 15:22:34 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id PAA10225 for freebsd-hackers@FreeBSD.ORG; Thu, 29 Jun 2000 15:22:53 -0700 (PDT) (envelope-from joe) From: Joe McGuckin <joe@via.net> Message-Id: <200006292222.PAA10225@monk.via.net> Date: Thu, 29 Jun 2000 15:22:53 -0700 (PDT) To: freebsd-hackers@FreeBSD.ORG Subject: Re[2]: mbuf re-write(s), v 0.1 In-Reply-To: <Pine.BSF.4.21.0006291154100.3622-100000@jehovah.technokratis.com> X-Mailer: Ishmail 1.3.1-970608-bsdi <http://www.ishmail.com> MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about a slab allocator (e.g. http://www.cnds.jhu.edu/~jesus/418/SlabAllocator.pdf) Joe Bosko Milekic <bmilekic@dsuper.net> wrote: > > On Thu, 29 Jun 2000, David Greenman wrote: > > > We used to do this in FreeBSD, but found that it was a bad idea for > > performance reasons. Freeing and reallocating memory from the high-level > > VM system is quite expensive and the trend in NICs these days is towards > > needing the code to be even faster, not slower. Further, if the 'peak' is > > reached often, then you're probably not really gaining much by freeing > > the memory back to the common pool. > > > > -DG > > What was previously done at some point was use the kernel malloc() to > allocate mbufs. As you know, this is a general purpose allocator that has > to first determine what algorithm to use and then store the object > correctly according to its size. This allocator is faster than that > one. This allocator knows that it only has to deal with mbufs and knows > that all of these mbufs are of the same size. > I am not proposing to return to malloc(), I am proposing the new > allocator. > Also, the "peak" in this case is not reached often, obviously. It is > designed with just that idea in mind. But, if the administrator feels > that it is, I have provided the following mechanism: > > { jehovah:/home/bmilekic }>> sysctl -A | grep min_on_avail > kern.ipc.min_on_avail: 0 > > With this sysctl, the administrator can set a "minimum required" count > for mbufs. In other words, it is possible to easily tell the system to > keep as many mbufs as you'd like cached on the free lists. > > > David Greenman > > Co-founder, The FreeBSD Project - http://www.freebsd.org > > Manufacturer of high-performance Internet servers - http://www.terasolutions.com > > Pave the road of life with opportunities. > > -Bosko > > -- > Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 > bmilekic@technokratis.com * http://www.technokratis.com/ > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:26: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from incandescent.firedrake.org (incandescent.firedrake.org [195.157.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C48D37C155 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 15:26:04 -0700 (PDT) (envelope-from float@firedrake.org) Received: from float by incandescent.firedrake.org with local (Exim 2.05 #1 (Debian)) id 137mks-0006J2-00; Thu, 29 Jun 2000 23:25:54 +0100 Date: Thu, 29 Jun 2000 23:25:54 +0100 To: Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: Periodic scripts [Was: Re: /etc/security -> /etc/periodic/security ?] Message-ID: <20000629232554.A24199@firedrake.org> References: <200006291558.LAA26175@rac9.wam.umd.edu> <395B79A0.AB99EA21@dante.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <395B79A0.AB99EA21@dante.org.uk>; from Konstantin.Chuguev@dante.org.uk on Thu, Jun 29, 2000 at 05:30:24PM +0100 From: void <float@firedrake.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 29, 2000 at 05:30:24PM +0100, Konstantin Chuguev wrote: > > IMO, introducing a sort of silent mode to these periodic scripts would help > sysadmins. [snip] > Your suggestions? As far as I'm concerned, this would greatly increase the utility of these scripts. I would love to see this happen. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:30:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id BE42437C1D3 for <freebsd-hackers@FreeBSD.org>; Thu, 29 Jun 2000 15:30:15 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny9-20.ix.netcom.com [198.211.18.20]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA14824; Thu, 29 Jun 2000 18:30:10 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id SAA00463; Thu, 29 Jun 2000 18:30:05 -0400 (EDT) (envelope-from vsilyaev) Date: Thu, 29 Jun 2000 18:30:05 -0400 From: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> To: "Jorge Sa' Silva" <jsilva@utad.pt> Cc: freebsd-hackers@FreeBSD.org Subject: Re: kernel function Message-ID: <20000629183005.A439@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the kernel space you are have to use not the sysctl, but the kernel_sysctl function. But for this function (as and for sysctl BTW) you are need to specify MIB. To found MIB via name you are need to use some magic. Vladimir >Hi >I tried to use the sysctl() function in the kernel space, >but when I do the "kernel make" it doesn't recognize the sysctl(). I did the >include of <sys/sysctl.h> and <sys/types.h>. >Do you know where is the problem? >Thanks in advance >Jorge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:32: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EAFF337B5C3 for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 15:31:59 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e5TMVxd20900; Thu, 29 Jun 2000 15:31:59 -0700 (PDT) Date: Thu, 29 Jun 2000 15:31:59 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Joe McGuckin <joe@via.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re[2]: mbuf re-write(s), v 0.1 Message-ID: <20000629153159.Y275@fw.wintelcom.net> References: <Pine.BSF.4.21.0006291154100.3622-100000@jehovah.technokratis.com> <200006292222.PAA10225@monk.via.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006292222.PAA10225@monk.via.net>; from joe@via.net on Thu, Jun 29, 2000 at 03:22:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joe McGuckin <joe@via.net> [000629 15:23] wrote: > > What about a slab allocator > (e.g. http://www.cnds.jhu.edu/~jesus/418/SlabAllocator.pdf) Which completely fails to address the concepts behind mbufs. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:33:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 6172E37B7A3; Thu, 29 Jun 2000 15:33:18 -0700 (PDT) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-343.hrz.uni-bielefeld.de [129.70.37.87]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0FWX007G9TBDRS@mail.uni-bielefeld.de>; Fri, 30 Jun 2000 00:33:15 +0200 (MET DST) Received: from broccoli.no-support.loc (broccoli.no-support.loc [192.168.43.99]) by frolic.no-support.loc (8.9.3/8.9.3) with ESMTP id AAA00666; Thu, 29 Jun 2000 00:58:03 +0200 (CEST envelope-from bjoern@no-support.loc) Received: (from bjoern@localhost) by broccoli.no-support.loc (8.9.3/8.9.3) id AAA00606; Thu, 29 Jun 2000 00:58:02 +0200 (CEST envelope-from bjoern@no-support.loc) Date: Thu, 29 Jun 2000 00:58:02 +0200 From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE> Subject: socket option IP_MULTICAST_LOOP has no effect? To: freebsd-net@FreeBSD.org, freebsd-hackers@FreeBSD.org Message-id: <20000629005801.A251@broccoli.no-support.loc> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline Content-transfer-encoding: 7BIT User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good morning, I got the impression that the socket option IP_MULTICAST_LOOP has no effect on 4.0-STABLE. Multicast packages are not looped back to the originating host. Looping back should be the default behavior of the socket API (Stevens, Unix Network Programming). I tried to explicitly switch it on with IP_MULTICAST_LOOP, but it didn't work either. Of course the socket is subscribed to the group (IP_ADD_MEMBERSHIP). Am I missing something or should this be a bug? Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 15:43:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id A2ED637C2A9 for <hackers@freebsd.org>; Thu, 29 Jun 2000 15:43:45 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by portnoy.lbl.gov (8.10.0/8.10.0) id e5TMhim19889 for hackers@freebsd.org; Thu, 29 Jun 2000 15:43:44 -0700 (PDT) Date: Thu, 29 Jun 2000 15:43:44 -0700 (PDT) From: Jin Guojun (DSD staff) <jin@george.lbl.gov> Message-Id: <200006292243.e5TMhim19889@portnoy.lbl.gov> To: hackers@freebsd.org Subject: possible doing context switch between network and link layers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Try to control the NIC output, instead of dropping the packet, I would like to do context switch on current sending process. tsleep() seems not to be a right mechanism for this purpose because it will panic in the kernel wherever between the network and link layers the tsleep() is put -- e.g. ether_output() { ... if (IF_QFULL) { tsleep(m, PSOCK, "pause NIC", 1); if (IF_QFULL) DROP_Q; } ... } Is there other context switch mechanism for this purpose? or is it impossible to do the context switch at network and link layers? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 17:11: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [204.118.244.94]) by hub.freebsd.org (Postfix) with SMTP id 0450437C29C for <hackers@freebsd.org>; Thu, 29 Jun 2000 17:10:52 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 95000 invoked from network); 30 Jun 2000 00:10:45 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-04-real.cdsnet.net with SMTP; 30 Jun 2000 00:10:45 -0000 Date: Thu, 29 Jun 2000 17:04:18 -0700 (PDT) From: Jaye Mathisen <mrcpu@internetcds.com> X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Funky scheduler stuff under heavy I/O. Message-ID: <Pine.BSF.4.21.0006291657100.18895-100000@schizo.cdsnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Noticing something a tad odd here, under 4.0-stable, as of 6/27. 8 identical drives, (all IDE, all connected to identical IDE PCI controllers). 8 parallel DD's started at the same type creating 2GB cycbuffs (as fast as & can put them in the background). (dd if=/dev/zero bs=1m count=2000 of=blahblah) The amount of data actually written to the buffs varies widely. both the Master and Slave drives on the first channel of each controller are about 200MB's ahead of the master and slave drives on the second channel of each controller, and the gap is growing. Also, the number of tps on the slower set is about 2/3 the # of tps on the faster set... Originally I was using vinum, and thought it was in there, but this is just going straight through UFS, no vinum inbetween... Any brilliant ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 18:46:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from itsdsv1.enc.edu (fw1.enc.edu [63.85.52.127]) by hub.freebsd.org (Postfix) with ESMTP id 1AB6E37C2AF for <hackers@freebsd.org>; Thu, 29 Jun 2000 18:46:42 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from enc.edu (r2s1.r.its.enc.edu [10.100.0.21]) by itsdsv1.enc.edu (8.7.5/8.7.3) with ESMTP id VAA05021; Thu, 29 Jun 2000 21:46:15 -0400 (EDT) Message-ID: <395BFDAA.B5059F3@enc.edu> Date: Thu, 29 Jun 2000 21:53:46 -0400 From: "Charles N. Owens" <owensc@enc.edu> Organization: Eastern Nazarene College X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: sysinstall script disklabel problems -- help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I'm trying to automate most of the FreeBSD installation process via sysinstall's scripting mechanism. Its showing signs of life, but keeps barfing on the disklabel step. Below is appended my script. Any ideas as to what is wrong? Could someone also perhaps post some examples that do work? I've followed the example install.cfg script as best I can, but no dice. I've also search the list archives but have found zero related postings! Anyhow, when I try to load the script, I get the error message (in a dialog pop-up) "No root device found - you must label a partition as / in the label editor." Hitting enter gets me a similar message about there being no swap device. The script then aborts. There are no error messages in the debug window (ALT-F2) to help explain what's wrong with the disklabel specification. I'm wondering if the syntax for the disklabel stuff has changed... I've begun staring at sysinstall's C code but am hoping that someone here will save me from the inevitable headache. Thanks much! cno The script: ################################# # sysinstall script ################################# debug=yes #### Host specific stuff hostname=myserv domainname=foo.enc.edu ipaddr=10.x.x.x netmask=255.255.0.0 defaultrouter=10.x.x.x nameserver=10.x.x.x netDev=fxp0 # nfs install path common value nfs=serverfoo:/u/big/FreeBSD/install mediaSetNFS #### distributions dists=bin crypto distSetCustom #### fdisk stuff # the disks... disk=da0 partition=all bootManager=standard diskPartitionEditor disk=da1 partition=all bootManager=standard diskPartitionEditor #### disk label da0s1-1=ufs 102400 / da0s1-2=swap 1050624 none da0s1-3=ufs 1050624 /usr da0s1-4=ufs 1050624 /usr/local da0s1-5=ufs 204800 /var diskLabelEditor # Main sysinstall script # ######### the big commit! installCommit #### Add some packages #package=tcsh-6.09.00.tgz #packageAdd #package=screen-3.9.5.tgz #packageAdd #package=rsaref-2.0.tgz #packageAdd #package=cfengine-1.5.3.tgz #packageAdd #package=lynx-2.8.2rel.1.tgz #packageAdd #package=unzip-5.4.0.tgz #packageAdd # play command=df system shutdown -- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 19:18:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.osd.bsdi.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5A7EF37B5C2 for <hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 19:18:39 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA21483; Thu, 29 Jun 2000 19:18:27 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: "Charles N. Owens" <owensc@enc.edu> Cc: hackers@FreeBSD.ORG Subject: Re: sysinstall script disklabel problems -- help In-reply-to: Your message of "Thu, 29 Jun 2000 21:53:46 EDT." <395BFDAA.B5059F3@enc.edu> Date: Thu, 29 Jun 2000 19:18:27 -0700 Message-ID: <21480.962331507@localhost> From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to automate most of the FreeBSD installation process via > sysinstall's scripting mechanism. Its showing signs of life, but keeps > barfing on the disklabel step. Below is appended my script. Do this instead: > # the disks... > disk=da0 > partition=all > bootManager=standard > diskPartitionEditor > > #### disk label > da0s1-1=ufs 102400 / > da0s1-2=swap 1050624 none > da0s1-3=ufs 1050624 /usr > da0s1-4=ufs 1050624 /usr/local > da0s1-5=ufs 204800 /var > diskLabelEditor > > disk=da1 > partition=all > bootManager=standard > diskPartitionEditor You want to do each disk "completely" before you move on to the next one rather than fdisking one, labelling it, then jumping back to fdisk. If you understood how truly evil a hack sysinstall's "scripting" was, you probably wouldn't need to ask why. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 20:28:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C3EEC37C1E9 for <hackers@freebsd.org>; Thu, 29 Jun 2000 20:28:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA28942; Thu, 29 Jun 2000 20:28:51 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: <XFMail.000629202850.jdp@polstra.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:000629202850:24129=_" Date: Thu, 29 Jun 2000 20:28:50 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra <jdp@polstra.com> To: hackers@freebsd.org Subject: Please run this test on an 80386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:000629202850:24129=_ Content-Type: text/plain; charset=us-ascii I am making some changes to FreeBSD's dynamic linker which require the ability to find out whether the CPU running the program supports the cmpxchg instruction. This instruction was introduced with the 80486; it did not exist on the 80386. The attached program attempts to determine whether the cmpxchg instruction is supported. Unfortunately, I don't have an 80386 to test it on. I would appreciate it if somebody with FreeBSD running on an 80386 would compile the program, run it, and send me the output. To compile it, just type: cc -o sigill sigill.c and then run it with ./sigill On an 80386 it should print out This CPU does not support the cmpxchg instruction Thanks in advance! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa --_=XFMail.1.3.p0.FreeBSD:000629202850:24129=_ Content-Disposition: attachment; filename="sigill.c" Content-Transfer-Encoding: 7bit Content-Description: sigill.c Content-Type: text/plain; charset=us-ascii; name=sigill.c; SizeOnDisk=1194 #include <err.h> #include <setjmp.h> #include <signal.h> #include <stdio.h> #include <string.h> #ifdef TEST #define cmpxchgl(old, new, m) ({ \ __asm volatile (".byte 0x0f; .byte 0x0f"); \ 0; }) #else #define cmpxchgl(old, new, m) ({ \ unsigned int __eax; \ __asm volatile ("lock; cmpxchgl %2, %0" \ : "=m"(m), "=a"(__eax) \ : "r"(new), "0"(m), "1"(old) \ : "cc"); \ (__eax); }) #endif static jmp_buf sigill_env; static void sigill(int sig) { longjmp(sigill_env, 1); } static int cpu_supports_cmpxchg(void) { struct sigaction act, oact; int result = 1; int lock = 0; memset(&act, 0, sizeof act); act.sa_handler = sigill; sigemptyset(&act.sa_mask); act.sa_flags = 0; if (sigaction(SIGILL, &act, &oact) == -1) err(1, "sigaction failed"); if (setjmp(sigill_env) == 0) cmpxchgl(0, 1, lock); else result = 0; if (sigaction(SIGILL, &oact, NULL) == -1) err(1, "sigaction failed"); return result; } int main(int argc, char *argv[]) { if (cpu_supports_cmpxchg()) printf("This CPU supports the cmpxchg instruction\n"); else printf("This CPU does not support the cmpxchg instruction\n"); return 0; } --_=XFMail.1.3.p0.FreeBSD:000629202850:24129=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 20:38: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jestocost.cosc.morrisville.edu (jestocoast.cosc.morrisville.edu [136.204.176.67]) by hub.freebsd.org (Postfix) with ESMTP id 2A6A537B555; Thu, 29 Jun 2000 20:38:04 -0700 (PDT) (envelope-from mrbond@jestocost.cosc.morrisville.edu) Received: (from mrbond@localhost) by jestocost.cosc.morrisville.edu (8.9.3/8.9.3) id XAA03117; Thu, 29 Jun 2000 23:33:24 -0400 (EDT) (envelope-from mrbond) Date: Thu, 29 Jun 2000 23:33:24 -0400 (EDT) From: "James 'Bond' Halstead" <mrbond@jestocost.cosc.morrisville.edu> Message-Id: <200006300333.XAA03117@jestocost.cosc.morrisville.edu> To: freebsd-hackers@freebsd.org Subject: ports/19591: ssh2 port ignores 'ignorenologin' from login.conf Cc: freebsd-ports@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wanted to add that it is ssh2d version 2.0.13. -James ps, sorry for cross-posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 20:44:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 24AD937BA33 for <hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 20:44:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e5U3ibo05218; Thu, 29 Jun 2000 20:44:38 -0700 (PDT) Date: Thu, 29 Jun 2000 20:44:37 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: "Charles N. Owens" <owensc@enc.edu> Cc: hackers@FreeBSD.ORG Subject: Re: sysinstall script disklabel problems -- help In-Reply-To: <395BFDAA.B5059F3@enc.edu> Message-ID: <Pine.BSF.4.21.0006292044040.36897-100000@resnet.uoregon.edu> 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, 29 Jun 2000, Charles N. Owens wrote: > I'm trying to automate most of the FreeBSD installation process via > sysinstall's scripting mechanism. Its showing signs of life, but keeps > barfing on the disklabel step. Below is appended my script. Any ideas > as to what is wrong? Could someone also perhaps post some examples that > do work? Hint: don't. :-) I suggest looking at the PicoBSD install disk for a tried-and-true way of doing this. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 20:59:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 7080537B6E6 for <hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 20:59:48 -0700 (PDT) (envelope-from rmuir@looksharp.net) Received: from localhost (rmuir@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA67578; Thu, 29 Jun 2000 23:59:28 -0400 (EDT) (envelope-from rmuir@looksharp.net) Date: Thu, 29 Jun 2000 23:59:28 -0400 (EDT) From: Robert Muir <rmuir@looksharp.net> To: John Polstra <jdp@polstra.com> Cc: hackers@FreeBSD.ORG Subject: Re: Please run this test on an 80386 In-Reply-To: <XFMail.000629202850.jdp@polstra.com> Message-ID: <Pine.BSF.4.21.0006292359290.67498-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, it prints: This CPU does not support the cmpxchg instruction Robert Muir rmuir@looksharp.net On Thu, 29 Jun 2000, John Polstra wrote: > I am making some changes to FreeBSD's dynamic linker which require > the ability to find out whether the CPU running the program supports > the cmpxchg instruction. This instruction was introduced with > the 80486; it did not exist on the 80386. The attached program > attempts to determine whether the cmpxchg instruction is supported. > Unfortunately, I don't have an 80386 to test it on. I would > appreciate it if somebody with FreeBSD running on an 80386 would > compile the program, run it, and send me the output. To compile it, > just type: >=20 > cc -o sigill sigill.c >=20 > and then run it with >=20 > ./sigill >=20 > On an 80386 it should print out >=20 > This CPU does not support the cmpxchg instruction >=20 > Thanks in advance! >=20 > John > -- > John Polstra jdp@polstra.= com > John D. Polstra & Co., Inc. Seattle, Washington = USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam Tr= ungpa >=20 >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 21: 1:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EDFB037C32A for <hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 21:01:18 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA29073; Thu, 29 Jun 2000 21:00:56 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: <XFMail.000629210055.jdp@polstra.com> 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: <Pine.BSF.4.21.0006292359290.67498-100000@turtle.looksharp.net> Date: Thu, 29 Jun 2000 21:00:55 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra <jdp@polstra.com> To: Robert Muir <rmuir@looksharp.net> Subject: Re: Please run this test on an 80386 Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Muir wrote: > yes, it prints: > This CPU does not support the cmpxchg instruction Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 21:16:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id F3B7A37C30E for <freebsd-hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 21:16:48 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FWY003I693XRQ@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Fri, 30 Jun 2000 00:14:21 -0400 (EDT) Date: Fri, 30 Jun 2000 00:16:22 -0400 (EDT) From: Bosko Milekic <bmilekic@dsuper.net> Subject: Re: Re[2]: mbuf re-write(s), v 0.1 In-reply-to: <200006292222.PAA10225@monk.via.net> X-Sender: bmilekic@jehovah.technokratis.com To: Joe McGuckin <joe@via.net> Cc: freebsd-hackers@FreeBSD.ORG Message-id: <Pine.BSF.4.21.0006300005240.6772-100000@jehovah.technokratis.com> 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, 29 Jun 2000, Joe McGuckin wrote: > > What about a slab allocator > (e.g. http://www.cnds.jhu.edu/~jesus/418/SlabAllocator.pdf) > > Joe What's your motivation behind this recommendation? What you're essentially suggesting is a replacement for our kernel malloc(). This will not make mbuf allocations faster by any means. The mbuf allocator that I presented in code a week or so ago does something very simple, as there is no point in making same-sized object allocations complicated, really, especially when they are small objects; in other words, I did NOT suggest going back to using malloc() for mbufs. I wrote a new, simpler and faster customized allocator which does essentially this: * Check free list, which is a doubly-linked list of "mb_map page descriptor structures" (new structure, mbpl_pg_descr). This structure contains very basic and essential information, such as the address of the VM page, the number of mbufs that are "in use" on that page, etc. If there is a node present on that general free list, then there is a free mbuf, and allocation from the map is not necessary. Grab free mbuf. If node now no longer contains any free mbufs, detach it from this list and attach it to free list. * If nothing on free list, allocate from map, also allocate memory for mbpl_pg_descr node for the obtained page and break page down into n objects, attaching it to the free list. Future allocations can allocate from that page until we run out. Freeing is equally simple: * Compute index into global array of pointers to mbpl_pg_descr structures based on the address of the mbuf. Locate node and determine on which list its on. * Place mbuf back on that mbpl_pg_descr's free list and if the node was previously on the empty list, move it to the free list, as there is now at least one free mbuf available on it. * If the freed mbuf completes the page, the page can be freed back to the map, but ONLY free it back if min_on_avail is met (sysctl). So you see, it is possible in this way to control the free list, and have many objects cached on the free list, essentially going back to the behavior we presently have, if that's what the sysadmin wants, with only the little overhead of having to deal with the linked lists (which isn't much, as they are both doubly-linked, so insertion/removal is fast). That's it, roughly. I hope this clears up some things for those of you who didn't look at the actual code. Regards, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 22:42:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 098F737C331 for <freebsd-hackers@freebsd.org>; Thu, 29 Jun 2000 22:42:30 -0700 (PDT) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 27D571F7D; Fri, 30 Jun 2000 07:42:29 +0200 (CEST) Date: Fri, 30 Jun 2000 07:42:28 +0200 From: Pascal Hofstee <daeron@shadowmere.student.utwente.nl> To: freebsd-hackers@freebsd.org Subject: "Sticky" Keys ? Message-ID: <20000630074228.A2512@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A co-worker of mine who is mobilly handicapped, uses a Windows "Accessibillity option" called "Sticky Keys" ... so he can still operate his keyboard normally, using ... let's call it a "straw" and his mouth. What this does is basically the following: - Pressing SHIFT/CONTROL/ALT once makes that key "active" until the next keystroke. - Pressing SHIFT/CONTROL/ALT twice makes that key "active" until it is pressed a third time. He and I have been wondering if such functionality would also be available already or "easily" to be implemented, so he might actually be able to use a Unix environment to work with instead of a Windows one. -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 29 23:10:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id EB2F437B6A6 for <hackers@FreeBSD.ORG>; Thu, 29 Jun 2000 23:10:17 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JR7GRE7SJ60008QC@research.kpn.com> for hackers@FreeBSD.ORG; Fri, 30 Jun 2000 08:10:15 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <NV62FHNY>; Fri, 30 Jun 2000 08:10:15 +0100 Content-return: allowed Date: Fri, 30 Jun 2000 08:10:08 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> Subject: RE: Funky scheduler stuff under heavy I/O. To: 'Jaye Mathisen' <mrcpu@internetcds.com> Cc: hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D76D5@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > both the Master and Slave drives on the first channel of > each controller are about 200MB's ahead of the master > and slave drives on the second channel of each > controller, and the gap is growing. > Umm. This sounds more like your controllers are doing this. You could stick in another two IDE controllers and see if that cures the problem. You have one of those 10 PCI bus boards, right? :-) Come to think of it, that would still not show if it's the hardware or FreeBSD dropping the bucket. Just curious, but is using vinum actually improving performance? (Assuming that's what you're trying to achieve) I've bonnied two Maxtor DiamondMax 15GB drives in my box, and I found that when I stripe them, performance drops to 15MB/s, whereas a single Maxtor will fling 25MB/s onto the platter. Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 0: 4:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8AFA137C36C for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 00:04:29 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA85601; Fri, 30 Jun 2000 09:04:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt <sos@freebsd.dk> Message-Id: <200006300704.JAA85601@freebsd.dk> Subject: Re: vinum and superblocks. In-Reply-To: <Pine.BSF.4.21.0006291456180.18895-100000@schizo.cdsnet.net> from Jaye Mathisen at "Jun 29, 2000 03:00:59 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Fri, 30 Jun 2000 09:04:25 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jaye Mathisen wrote: > Not sure what the right thing to do here is, or even if it's a real > problem, but: > > I have 8 75GB IBM drives striped in a big raid 0 for monkeying with. > > newfs -i 131072 -v /dev/vinum/bighonkindisk seems to very nicely put all > the data that newfs write out on to the first disk... It least, only the > first disk gets any io, accoring to systat and iostat. > > Which would seem to me to be problematic in terms of using fsck -b, and > also just for the fact that it would seem that you would have to hit that > disk more often than the others, even though it's striped. > > I realize there's no protection with the raid 0, but the load doesn't seem > evenly distributed on a transaction basis, even though the data is evenly > spread. > > What's the right thing to do here? You need to adjust your stripe size so that the superblocks etc are not all put on the same disk, ie some odd stripe size is often best to distribute those to hopefully all disks... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 0:17:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skaarup.org (skaarup.org [130.228.230.140]) by hub.freebsd.org (Postfix) with ESMTP id 8D5EC37B62B for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 00:17:30 -0700 (PDT) (envelope-from rasmus@gal.dk) Received: from localhost (skaarup@localhost) by skaarup.org (8.9.3/8.9.3) with ESMTP id JAA54518; Fri, 30 Jun 2000 09:16:33 +0200 (CEST) (envelope-from rasmus@gal.dk) Date: Fri, 30 Jun 2000 09:16:33 +0200 (CEST) From: Rasmus Skaarup <rasmus@gal.dk> X-Sender: skaarup@skaarup.org To: Soren Schmidt <sos@freebsd.dk> Cc: Jaye Mathisen <mrcpu@internetcds.com>, hackers@FreeBSD.ORG Subject: Re: vinum and superblocks. In-Reply-To: <200006300704.JAA85601@freebsd.dk> Message-ID: <Pine.BSF.4.21.0006300910360.37775-100000@skaarup.org> 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 On Fri, 30 Jun 2000, Soren Schmidt wrote: > It seems Jaye Mathisen wrote: > > > > I have 8 75GB IBM drives striped in a big raid 0 for monkeying with. > > > > newfs -i 131072 -v /dev/vinum/bighonkindisk seems to very nicely put all > > the data that newfs write out on to the first disk... It least, only the > > first disk gets any io, accoring to systat and iostat. > > You need to adjust your stripe size so that the superblocks etc are > not all put on the same disk, ie some odd stripe size is often best > to distribute those to hopefully all disks... By 'odd', you mean small, Søren? If this is the case, be careful not to make the size too small, which will degrade the perfomance because of the Jaye, are you sure you doing a large (preferrebly at least one GB) sequential read or write from/to your disks? If you are only doing small random I/O, this could result in only one disk getting hit. But it does sound strange that when making the filsystem, only the first disk gets initialized.. Are you positively sure about this? The size of the vinum volume corresponds to approx 8 * 75GB ? Best regards Rasmus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 0:20:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skaarup.org (skaarup.org [130.228.230.140]) by hub.freebsd.org (Postfix) with ESMTP id B01A537B724 for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 00:20:54 -0700 (PDT) (envelope-from rasmus@gal.dk) Received: from localhost (skaarup@localhost) by skaarup.org (8.9.3/8.9.3) with ESMTP id JAA61078; Fri, 30 Jun 2000 09:19:29 +0200 (CEST) (envelope-from rasmus@gal.dk) Date: Fri, 30 Jun 2000 09:19:29 +0200 (CEST) From: Rasmus Skaarup <rasmus@gal.dk> X-Sender: skaarup@skaarup.org To: sos@freebsd.dk Cc: Jaye Mathisen <mrcpu@internetcds.com>, hackers@FreeBSD.ORG Subject: Re: vinum and superblocks. Message-ID: <Pine.BSF.4.21.0006300916530.37775-100000@skaarup.org> 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 Rasmus Skaarup wrote: > By 'odd', you mean small, Søren? If this is the case, be careful not to > make the size too small, which will degrade the perfomance because of > the .. beacuse of the drive geometry. Best regards Rasmus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 1: 6: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 8E88B37B55C for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 01:06:03 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA15140; Fri, 30 Jun 2000 01:05:59 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <395C54E7.7FAC7371@gorean.org> Date: Fri, 30 Jun 2000 01:05:59 -0700 From: Doug Barton <DougB@gorean.org> Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0629 i386) X-Accept-Language: en MIME-Version: 1.0 To: daeron@shadowmere.student.utwente.nl Cc: freebsd-hackers@freebsd.org Subject: Re: "Sticky" Keys ? References: <20000630074228.A2512@shadowmere.student.utwente.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pascal Hofstee wrote: > > Hi, > > A co-worker of mine who is mobilly handicapped, uses a Windows > "Accessibillity option" called "Sticky Keys" I vaguely remember a discussion about this.... have you searched the mail archives? Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 1:40:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front.linuxcare.com.au (linuxcare.com.au [203.29.91.49]) by hub.freebsd.org (Postfix) with ESMTP id B1DD937B60C for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 01:40:31 -0700 (PDT) (envelope-from grog@sydney.worldwide.lemis.com) Received: from sydney.worldwide.lemis.com ([203.17.0.42]) by front.linuxcare.com.au (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id SAA29964; Fri, 30 Jun 2000 18:40:28 +1000 X-Authentication-Warning: front.linuxcare.com.au: Host [203.17.0.42] claimed to be sydney.worldwide.lemis.com Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.9.3/8.9.3) id SAA08588; Fri, 30 Jun 2000 18:40:23 +1000 (EST) (envelope-from grog) Date: Fri, 30 Jun 2000 18:40:22 +1000 From: Greg Lehey <grog@lemis.com> To: Rasmus Skaarup <rasmus@gal.dk> Cc: Soren Schmidt <sos@freebsd.dk>, Jaye Mathisen <mrcpu@internetcds.com>, hackers@FreeBSD.ORG Subject: Re: vinum and superblocks. Message-ID: <20000630184022.G7687@sydney.worldwide.lemis.com> References: <200006300704.JAA85601@freebsd.dk> <Pine.BSF.4.21.0006300910360.37775-100000@skaarup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <Pine.BSF.4.21.0006300910360.37775-100000@skaarup.org> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 June 2000 at 9:16:33 +0200, Rasmus Skaarup wrote: > On Fri, 30 Jun 2000, Soren Schmidt wrote: > >> It seems Jaye Mathisen wrote: >>> >>> I have 8 75GB IBM drives striped in a big raid 0 for monkeying with. >>> >>> newfs -i 131072 -v /dev/vinum/bighonkindisk seems to very nicely put all >>> the data that newfs write out on to the first disk... It least, only the >>> first disk gets any io, accoring to systat and iostat. >> >> You need to adjust your stripe size so that the superblocks etc are >> not all put on the same disk, ie some odd stripe size is often best >> to distribute those to hopefully all disks... > > By 'odd', you mean small, Søren? If this is the case, be careful not to > make the size too small, which will degrade the perfomance because of the Of the? But yes, you don't want stripes of less than about 256 kB. > Jaye, are you sure you doing a large (preferrebly at least one > GB) sequential read or write from/to your disks? If you are only doing > small random I/O, this could result in only one disk getting hit. > > But it does sound strange that when making the filsystem, only the > first disk gets initialized.. Are you positively sure about this? It sounds right to me. It seems I can't find the text I had intended to put in the man page; I'll follow up with this some time soon. But indeed, the access pattern for newfs will write only to the first subdisk if the stripe size is, say, 512 kB. I'm currently recommending odd stripe sizes like 273 kB; calculate something which will put superblocks 32 MB apart onto consecutive subdisks. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 2:33:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B732137C403 for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 02:33:28 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id <aa84258@salmon>; 30 Jun 2000 10:33:27 +0100 (BST) Date: Fri, 30 Jun 2000 10:33:26 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Rasmus Skaarup <rasmus@gal.dk> Cc: Soren Schmidt <sos@freebsd.dk>, Jaye Mathisen <mrcpu@internetcds.com>, hackers@FreeBSD.ORG Subject: Re: vinum and superblocks. Message-ID: <20000630103326.A38784@walton.maths.tcd.ie> References: <200006300704.JAA85601@freebsd.dk> <Pine.BSF.4.21.0006300910360.37775-100000@skaarup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.2i In-Reply-To: <Pine.BSF.4.21.0006300910360.37775-100000@skaarup.org>; from rasmus@gal.dk on Fri, Jun 30, 2000 at 09:16:33AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 30, 2000 at 09:16:33AM +0200, Rasmus Skaarup wrote: > By 'odd', you mean small, Søren? If this is the case, be careful not to > make the size too small, which will degrade the perfomance because of the I presumed he ment 'odd' as in 'not even'.... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 2:38:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dzungle.ms.mff.cuni.cz (dzungle.ms.mff.cuni.cz [195.113.19.80]) by hub.freebsd.org (Postfix) with ESMTP id 614F237BA4E for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 02:38:38 -0700 (PDT) (envelope-from horcicka@dzungle.ms.mff.cuni.cz) Received: from localhost (horcicka@localhost) by dzungle.ms.mff.cuni.cz (8.9.3/8.9.3) with SMTP id LAA02402 for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 11:38:36 +0200 (CEST) (envelope-from horcicka@dzungle.ms.mff.cuni.cz) Date: Fri, 30 Jun 2000 11:38:36 +0200 (CEST) From: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz> To: freebsd-hackers@freebsd.org Subject: style(9) Message-ID: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> 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 just reading the style(9) man page and I don't understand to two rules: 1. Citation: ============ The kernel has a name associated with parameter types, e.g., in the kernel use: void function(int fd); In header files visible to user land applications, prototypes that are visible must use either protected names or no names with the types. It is preferable to use protected names. e.g., use: void function(int); or: void function(int _fd); ============ Why is that necessary? 2. Citation: ============ Indentation is an 8 character tab. Second level indents are four spaces. while (cnt < 20) z = a + really + long + statement + that + needs + two lines + gets + indented + four + spaces + on + the + second + and + subsequent + lines. ============ a. What does it mean `second level indents'? Is it the indentation of expressions that cannot fit to one line (as in the example above) or is it any indentation except of the first tab? b. Aren't 8 characters too many? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 2:49:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 410C037C415 for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 02:49:34 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 137xQK-000KYa-00; Fri, 30 Jun 2000 11:49:24 +0200 Date: Fri, 30 Jun 2000 11:49:24 +0200 From: Neil Blakey-Milner <nbm@mithrandr.moria.org> To: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz> Cc: freebsd-hackers@freebsd.org Subject: Re: style(9) Message-ID: <20000630114924.A78968@mithrandr.moria.org> References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz>; from horcicka@dzungle.ms.mff.cuni.cz on Fri, Jun 30, 2000 at 11:38:36AM +0200 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-06-30 (11:38), Martin Horcicka wrote: > 2. Citation: > ============ > Indentation is an 8 character tab. Second level indents are four spaces. > > while (cnt < 20) > z = a + really + long + statement + that + needs + > two lines + gets + indented + four + spaces + > on + the + second + and + subsequent + lines. > a. What does it mean `second level indents'? Is it the indentation of > expressions that cannot fit to one line (as in the example above) or > is it any indentation except of the first tab? It's continuation lines, as the example states. All new statements occur on tab boundaries, whereas continuation lines are tabs to the previous tab boundary, plus 4 spaces. while (cnt < 20) if (foo == bar) baz(); > b. Aren't 8 characters too many? No. Anyway, you can set your tab size to whatever you want. So long as it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the margin constantly, you should simplify your code, or break it up into (preferably reusable) functions that perform one task. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 4:16: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id E700037B55C for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 04:15:58 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 50102 invoked from network); 30 Jun 2000 11:15:58 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 30 Jun 2000 11:15:58 -0000 Date: Fri, 30 Jun 2000 04:09:31 -0700 (PDT) From: Jaye Mathisen <mrcpu@internetcds.com> X-Sender: mrcpu@schizo.cdsnet.net To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: hackers@FreeBSD.ORG Subject: RE: Funky scheduler stuff under heavy I/O. In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D76D5@l04.research.kpn.com> Message-ID: <Pine.BSF.4.21.0006300405160.18895-100000@schizo.cdsnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I ran it by Soren, he didn't think so. And Originally when I noticed it, I thought it was vinum (although I'm not using vinum in this case), and mentioned it to greg, and he was leaning that way as well... I'm not sure I buy the controller argument anyway. For each pair of drives on each controller (Master/Slave), the 1st PCI Card/1st Controller Master == the 1st PCI card/1st Controller Slave which == the 2nd PCI card/1st Controller Master, etc... And the matching 2nd controllers stay almost locksteped with each other, but getting many fewer transactions than the 1st controllers on each card... So I don't see how it can be hardware. I don't believe there's any more cost to the IDE controller whether it's the 1st one on the card or not. The othe rthing is that Soren mentioned he was seeing the same thing on SCSI drives as well, which would eliminate the ATA code. Personally, I would've guessed that all the masters would've run faster than all the slaves, but it ain't so... On Fri, 30 Jun 2000, Koster, K.J. wrote: > > > > both the Master and Slave drives on the first channel of > > each controller are about 200MB's ahead of the master > > and slave drives on the second channel of each > > controller, and the gap is growing. > > > Umm. This sounds more like your controllers are doing this. You could stick > in another two IDE controllers and see if that cures the problem. You have > one of those 10 PCI bus boards, right? :-) > > Come to think of it, that would still not show if it's the hardware or > FreeBSD dropping the bucket. > > Just curious, but is using vinum actually improving performance? (Assuming > that's what you're trying to achieve) > > I've bonnied two Maxtor DiamondMax 15GB drives in my box, and I found that > when I stripe them, performance drops to 15MB/s, whereas a single Maxtor > will fling 25MB/s onto the platter. > > Kees Jan > > ================================================= > TV is the worst of both worlds. It's not as > good at words as radio is because the pictures > are a distraction which demand attention, and > it's not as good as cinema because the pictures > are not nearly as good. > Douglas Adams > > > 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 Jun 30 4:22:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 2868937B97A for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 04:22:44 -0700 (PDT) (envelope-from fotis@ripe.net) Received: from x21.ripe.net (x21.ripe.net [193.0.1.21]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id NAA02938; Fri, 30 Jun 2000 13:22:42 +0200 (CEST) Received: from localhost (fotis@localhost) by x21.ripe.net (8.8.8/8.8.5) with ESMTP id NAA25101; Fri, 30 Jun 2000 13:22:42 +0200 (CEST) Date: Fri, 30 Jun 2000 13:22:42 +0200 (CEST) From: Fotis Georgatos <fotis@ripe.net> To: Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: Periodic scripts [Was: Re: /etc/security -> /etc/periodic/security ?] In-Reply-To: <395B79A0.AB99EA21@dante.org.uk> Message-ID: <Pine.BSI.4.05L.10006301309170.24628-100000@x21.ripe.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, > > Will we be seeing a move in this direction towards a more configurable > > security script? Is anyone planning it? What about a configuration language? On Thu, 29 Jun 2000, Konstantin Chuguev wrote: > IMO, introducing a sort of silent mode to these periodic scripts would help > sysadmins. The idea is as follows: [...] I've been using the tool Cfengine lately, and I am surprised that it's not more standard in the BSD family (++). Why bother with complex shell scripts when you can have most needed functionality in a single C program? I've found myself replacing 10-20 lines of shell code with a single line. Remember that shell scripts involve all shorts of small utilities, and have to fork and play with memory space quite much, many times. I'd like to hear other people's ideas on this, because I'm in an effort to replace them anyway... Please, keep me cc. cheers, Fotis -- The statistician drowned in a lake averaging only 2 feet in depth. Fotis Georgatos <fotis@ripe.net>, nic-hdl: FMG21-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 5:29:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id 848B837C500 for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 05:29:46 -0700 (PDT) (envelope-from uabfra@uab.ericsson.se) Received: from ms.uab.ericsson.se (ms.uab.ericsson.se [134.138.201.16]) by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e5UCThs16632; Fri, 30 Jun 2000 14:29:43 +0200 (MET DST) Received: from uab.ericsson.se (ulinpc01 [134.138.184.201]) by ms.uab.ericsson.se (8.10.0/8.10.0/uab-2.26) with ESMTP id e5UCTZT07909; Fri, 30 Jun 2000 14:29:35 +0200 (MET DST) Message-ID: <395C92AF.302B9939@uab.ericsson.se> Date: Fri, 30 Jun 2000 14:29:35 +0200 From: Anders Franzen <uabfra@uab.ericsson.se> X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Horcicka wrote: > Hi, > > I'm just reading the style(9) man page and I don't understand to two > rules: > > 1. Citation: > ============ > The kernel has a name associated with parameter types, e.g., in the kernel > use: > > void function(int fd); > > In header files visible to user land applications, prototypes that are > visible must use either protected names or no names with the types. It is > preferable to use protected names. e.g., use: > > void function(int); > > or: > > void function(int _fd); > ============ > Why is that necessary? IMHO, I would guess that it can prevent userland from typedefing own types. I.e. If a program makes an own type : typedef int fd: and then includes a header file saying : void function(int fd): the compiler would complain about the the type fd. /Anders Franzen > > > 2. Citation: > ============ > Indentation is an 8 character tab. Second level indents are four spaces. > > while (cnt < 20) > z = a + really + long + statement + that + needs + > two lines + gets + indented + four + spaces + > on + the + second + and + subsequent + lines. > ============ > a. What does it mean `second level indents'? Is it the indentation of > expressions that cannot fit to one line (as in the example above) or > is it any indentation except of the first tab? > > b. Aren't 8 characters too many? > > Martin > > 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 Jun 30 5:41:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 7FCCE37C4BD for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 05:41:44 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from barracuda (barracuda [208.11.247.5]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id IAA19344 for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 08:41:42 -0400 (EDT) Date: Fri, 30 Jun 2000 08:41:42 -0400 (EDT) From: Thomas Stromberg <tstromberg@rtci.com> X-Sender: tstromberg@barracuda.aquarium.rtci.com To: freebsd-hackers@freebsd.org Subject: XFree86 4.0 - What are people using for dual-head video? Message-ID: <Pine.GSO.4.20.0006300835280.19036-100000@barracuda.aquarium.rtci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This discussion comes up every once in a while on the lists, and I guess it's time for an update. I havent seen anything since the 3.9.17 beta, so here we go.. What dual head video combinations are people using with XFree86 4.0 and FreeBSD? I've got a -CURRENT box right now with an AGP Riva TNT 2, and really want to setup dual-head with it for programming (after first seeing it on IRIX several years ago, I got hooked). Are people mixing different vendors (Riva & Matrox?) and or AGP and PCI? It's my understanding that there still isn't support for the dual-head cards from Matrox, unless you go with a commercial X server. If anyone could point me to a dual-head compatibility list, that'd help too. ------------------------------------------------------------------------ thomas r. stromberg tstromberg@rtci.com senior systems administrator http://www.afterthought.org/ research triangle commerce, inc. 1.919.657.1317 'FreeBSD - the power to serve' 'Perl - the power to hack' ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 5:46:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id ACC3037B7AA for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 05:46:20 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from bone.nectar.com (bone.nectar.com [10.0.1.105]) by gw.nectar.com (Postfix) with ESMTP id C0BA89B31; Fri, 30 Jun 2000 07:46:19 -0500 (CDT) Received: by bone.nectar.com (Postfix, from userid 1001) id 69D881DCB; Fri, 30 Jun 2000 07:46:19 -0500 (CDT) Date: Fri, 30 Jun 2000 07:46:19 -0500 From: "Jacques A. Vidrine" <n@nectar.com> To: Thomas Stromberg <tstromberg@rtci.com> Cc: freebsd-hackers@freebsd.org Subject: Re: XFree86 4.0 - What are people using for dual-head video? Message-ID: <20000630074619.D65332@bone.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" <n@nectar.com>, Thomas Stromberg <tstromberg@rtci.com>, freebsd-hackers@freebsd.org References: <Pine.GSO.4.20.0006300835280.19036-100000@barracuda.aquarium.rtci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <Pine.GSO.4.20.0006300835280.19036-100000@barracuda.aquarium.rtci.com>; from tstromberg@rtci.com on Fri, Jun 30, 2000 at 08:41:42AM -0400 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 30, 2000 at 08:41:42AM -0400, Thomas Stromberg wrote: > It's my understanding that there still isn't support for the dual-head > cards from Matrox, unless you go with a commercial X server. If anyone > could point me to a dual-head compatibility list, that'd help too. I use XFree86 4.0 (on 4-STABLE) with: pci0: <Matrox MGA Millennium II 2164W graphics accelerator> at 15.0 irq 9 pci1: <Matrox MGA Millennium II 2164WA-B AG graphics accelerator> at 0.0 irq 3 One is AGP, one is PCI. Not enough window managers understand multiple displays. Happily, WindowMaker does. -- Jacques Vidrine / n@nectar.com / nectar@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 Jun 30 7:43:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 6662C37B9E2 for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 07:43:45 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id IAA07616; Fri, 30 Jun 2000 08:43:24 -0600 (MDT) Date: Fri, 30 Jun 2000 08:43:24 -0600 (MDT) From: Nick Rogness <nick@rapidnet.com> To: Fotis Georgatos <fotis@ripe.net> Cc: Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk>, freebsd-hackers@freebsd.org Subject: Re: Periodic scripts [Was: Re: /etc/security -> /etc/periodic/security ?] In-Reply-To: <Pine.BSI.4.05L.10006301309170.24628-100000@x21.ripe.net> Message-ID: <Pine.BSF.4.21.0006300829350.98393-100000@rapidnet.com> 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, 30 Jun 2000, Fotis Georgatos wrote: > Why bother with complex shell scripts when you can have most > needed functionality in a single C program? > I've found myself replacing 10-20 lines of shell code with a single line. WHAT? Are you crazy? I've found just the opposite. What shell scripting are you using? Example to find # of duplicate usernames in your password file: #!/usr/local/bin/ksh VAR1=`awk -F: '{print $1}' /etc/passwd|grep -cx $1` print "Number of occurences of $1 in /etc/passwd: $VAR1" Let me see you replicate that in C in less than 2 lines... Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 8: 4: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8C38037BDE7 for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 08:04:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA02907; Fri, 30 Jun 2000 17:03:47 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Rogness <nick@rapidnet.com> Cc: Fotis Georgatos <fotis@ripe.net>, Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk>, freebsd-hackers@FreeBSD.ORG Subject: Re: Periodic scripts [Was: Re: /etc/security -> /etc/periodic/security ?] In-reply-to: Your message of "Fri, 30 Jun 2000 08:43:24 MDT." <Pine.BSF.4.21.0006300829350.98393-100000@rapidnet.com> Date: Fri, 30 Jun 2000 17:03:47 +0200 Message-ID: <2905.962377427@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <Pine.BSF.4.21.0006300829350.98393-100000@rapidnet.com>, Nick Rognes s writes: >On Fri, 30 Jun 2000, Fotis Georgatos wrote: > >> Why bother with complex shell scripts when you can have most >> needed functionality in a single C program? >> I've found myself replacing 10-20 lines of shell code with a single line. > > WHAT? Are you crazy? I've found just the opposite. > What shell scripting are you using? Example to find # of > duplicate usernames in your password file: > > #!/usr/local/bin/ksh > VAR1=`awk -F: '{print $1}' /etc/passwd|grep -cx $1` > print "Number of occurences of $1 in /etc/passwd: $VAR1" > > Let me see you replicate that in C in less than 2 lines... Nick, I can do it in one line, but it will suck style wise because I cannot use #includes. Can we stop this pissing contest now before anybody starts flouting APL single-liners ? Thanks. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 8:50:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6CEAB37B7F6 for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 08:50:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA91134; Fri, 30 Jun 2000 09:50:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA41895; Fri, 30 Jun 2000 09:50:27 -0600 (MDT) Message-Id: <200006301550.JAA41895@harmony.village.org> To: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz> Subject: Re: style(9) Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 30 Jun 2000 11:38:36 +0200." <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Date: Fri, 30 Jun 2000 09:50:27 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Martin Horcicka writes: : 1. Citation: : ============ : The kernel has a name associated with parameter types, e.g., in the kernel : use: : : void function(int fd); : : In header files visible to user land applications, prototypes that are : visible must use either protected names or no names with the types. It is : preferable to use protected names. e.g., use: : : void function(int); : : or: : : void function(int _fd); : ============ : Why is that necessary? Because the user is free to do this: #define fd Something Bad #include <sys/header.h> : 2. Citation: : ============ : Indentation is an 8 character tab. Second level indents are four spaces. : : while (cnt < 20) : z = a + really + long + statement + that + needs + : two lines + gets + indented + four + spaces + : on + the + second + and + subsequent + lines. : ============ : a. What does it mean `second level indents'? Is it the indentation of : expressions that cannot fit to one line (as in the example above) or : is it any indentation except of the first tab? Yes. Second level indents are continued lines. : b. Aren't 8 characters too many? Don't get us going. No, it isn't. If you run out of room, GW says you are almost certainly doing something wrong. Besides, 8 is the official tab width size, so it makes it really easy for anybody with any editor to get the indentation right. It is also tradition and most of the code is written that way. I personally like 4 myself, but let's not get into a stupid tab width war were people argue about values from 2 to 6 that ends in the resolution that 8 might not be right, but reformatting everything would suck too bad to change it and introducing new code that isn't formatted at 8 would be confusing. OK? We've done that before. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 8:51:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8F60537BAAE for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 08:51:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA91143; Fri, 30 Jun 2000 09:51:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA41922; Fri, 30 Jun 2000 09:51:51 -0600 (MDT) Message-Id: <200006301551.JAA41922@harmony.village.org> To: Anders Franzen <uabfra@uab.ericsson.se> Subject: Re: style(9) Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 30 Jun 2000 14:29:35 +0200." <395C92AF.302B9939@uab.ericsson.se> References: <395C92AF.302B9939@uab.ericsson.se> <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Date: Fri, 30 Jun 2000 09:51:51 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <395C92AF.302B9939@uab.ericsson.se> Anders Franzen writes: : IMHO, I would guess that it can prevent userland from typedefing own types. : I.e. If a program : makes an own type : typedef int fd: : : and then includes a header file saying : void function(int fd): : the compiler would complain about the the type fd. Actually, that's legal. Think preprocessor macros. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 8:53: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 765A737BF08 for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 08:52:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA91152; Fri, 30 Jun 2000 09:52:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA41949; Fri, 30 Jun 2000 09:52:55 -0600 (MDT) Message-Id: <200006301552.JAA41949@harmony.village.org> Subject: Re: style(9) Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 30 Jun 2000 09:50:27 MDT." <200006301550.JAA41895@harmony.village.org> References: <200006301550.JAA41895@harmony.village.org> <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> Date: Fri, 30 Jun 2000 09:52:55 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006301550.JAA41895@harmony.village.org> Warner Losh writes: : Don't get us going. No, it isn't. If you run out of room, GW says Actually that should be CW not GW. CW == Conventional Wisdom. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 9:30: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id B7DF737B618 for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 09:29:43 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id BAA21764 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 01:29:41 +0900 (JST) To: hackers@FreeBSD.ORG Subject: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 01:29:41 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 170 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The invlpg instruction causes strange signal 11 problem on some PentiumPro box. This problem seems to hapen when (1) mother board is very old and (2) BIOS update is not available and (3) cpuid < 0x619. Following patch automatically disables invlpg when PentiumPro with cpuid < 0x619 is found. Please comment to this patch. ---------- BEGIN ---------- *** sys/i386/isa/initcpu.c.ORIG Sat Jul 1 01:03:40 2000 --- sys/i386/isa/initcpu.c Sat Jul 1 01:06:28 2000 *************** *** 46,51 **** --- 46,55 ---- void enable_K6_2_wt_alloc(void); #endif + #ifdef I686_CPU + extern int invlpgbug; + #endif + #ifdef I486_CPU static void init_5x86(void); static void init_bluelightning(void); *************** *** 449,454 **** --- 453,462 ---- apicbase = rdmsr(0x1b); apicbase &= ~0x800LL; wrmsr(0x1b, apicbase); + #endif + #ifndef CPU_DONT_DISABLE_INVLPG + if (cpu_id < 0x619) + invlpgbug = 1; #endif } *** sys/i386/isa/pmap.c.ORIG Sat Jul 1 01:06:46 2000 --- sys/i386/isa/pmap.c Sat Jul 1 01:13:37 2000 *************** *** 171,176 **** --- 171,181 ---- static struct pv_entry *pvinit; /* + * When invlpgbug = 1, we don't use invlpg instruction. + */ + int invlpgbug; + + /* * All those kernel PT submaps that BSD is so fond of */ pt_entry_t *CMAP1 = 0; *************** *** 358,364 **** pgeflag = 0; #if !defined(SMP) ! if (cpu_feature & CPUID_PGE) { pgeflag = PG_G; } #endif --- 363,369 ---- pgeflag = 0; #if !defined(SMP) ! if (cpu_feature & CPUID_PGE && !invlpg) { pgeflag = PG_G; } #endif *************** *** 581,587 **** } else #endif { ! invlpg(va); } } --- 586,595 ---- } else #endif { ! if (invlpgbug) ! invltlb(); ! else ! invlpg(va); } } *************** *** 884,890 **** */ *(ptek + i) = VM_PAGE_TO_PHYS(m) | PG_RW | PG_V | pgeflag; if (oldpte) { ! if ((oldpte & PG_G) || (cpu_class > CPUCLASS_386)) { invlpg((vm_offset_t) up + i * PAGE_SIZE); } else { updateneeded = 1; --- 892,899 ---- */ *(ptek + i) = VM_PAGE_TO_PHYS(m) | PG_RW | PG_V | pgeflag; if (oldpte) { ! if (((oldpte & PG_G) || (cpu_class > CPUCLASS_386)) && ! !invlpgbug) { invlpg((vm_offset_t) up + i * PAGE_SIZE); } else { updateneeded = 1; *************** *** 925,931 **** oldpte = *(ptek + i); *(ptek + i) = 0; ! if ((oldpte & PG_G) || (cpu_class > CPUCLASS_386)) invlpg((vm_offset_t) p->p_addr + i * PAGE_SIZE); vm_page_unwire(m, 0); vm_page_free(m); --- 934,940 ---- oldpte = *(ptek + i); *(ptek + i) = 0; ! if (((oldpte & PG_G) || (cpu_class > CPUCLASS_386)) && !invlpgbug) invlpg((vm_offset_t) p->p_addr + i * PAGE_SIZE); vm_page_unwire(m, 0); vm_page_free(m); *************** *** 933,938 **** --- 942,950 ---- #if defined(I386_CPU) if (cpu_class <= CPUCLASS_386) invltlb(); + #else + if (invlpgbug) + invltlb(); #endif } *************** *** 2785,2792 **** } else #endif { ! invlpg((u_int)CADDR1); ! invlpg((u_int)CADDR2); } bcopy(CADDR1, CADDR2, PAGE_SIZE); --- 2797,2808 ---- } else #endif { ! if (invlpgbug) ! invltlb(); ! else { ! invlpg((u_int)CADDR1); ! invlpg((u_int)CADDR2); ! } } bcopy(CADDR1, CADDR2, PAGE_SIZE); ---------- END ---------- -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 9:32:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 4A02437B883 for <hackers@freebsd.org>; Fri, 30 Jun 2000 09:32:21 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.9.3/8.9.3) with ESMTP id JAA00738; Fri, 30 Jun 2000 09:32:14 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <395CCB95.BD90BDAF@vpop.net> Date: Fri, 30 Jun 2000 09:32:21 -0700 From: Matthew Reimer <mreimer@vpop.net> Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Stromberg <tstromberg@rtci.com> Cc: hackers@freebsd.org Subject: Re: XFree86 4.0 - What are people using for dual-head video? References: <lists.freebsd.hackers.Pine.GSO.4.20.0006300835280.19036-100000@barracuda.aquarium.rtci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Stromberg wrote: > > This discussion comes up every once in a while on the lists, and I guess > it's time for an update. I havent seen anything since the 3.9.17 beta, so > here we go.. > > What dual head video combinations are people using with XFree86 4.0 and > FreeBSD? I've got a -CURRENT box right now with an AGP Riva TNT 2, and > really want to setup dual-head with it for programming (after first seeing > it on IRIX several years ago, I got hooked). Are people mixing different > vendors (Riva & Matrox?) and or AGP and PCI? > > It's my understanding that there still isn't support for the dual-head > cards from Matrox, unless you go with a commercial X server. If anyone > could point me to a dual-head compatibility list, that'd help too. I've had success with an AGP TNT2 Ultra with a Matrox Millenium. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 13:20: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 2F73837BC16 for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 13:19:57 -0700 (PDT) (envelope-from walker@usc.edu) Received: from skat.usc.edu (root@skat.usc.edu [128.125.253.131]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id NAA25101; Fri, 30 Jun 2000 13:19:56 -0700 (PDT) Received: from skat.usc.edu (walker@skat.usc.edu [128.125.253.131]) by skat.usc.edu (8.10.1/8.10.1/usc) with ESMTP id e5UKJs101902; Fri, 30 Jun 2000 13:19:54 -0700 (PDT) Date: Fri, 30 Jun 2000 13:19:53 -0700 (PDT) From: Mike Walker <walker@usc.edu> To: Pascal Hofstee <daeron@shadowmere.student.utwente.nl> Cc: freebsd-hackers@freebsd.org Subject: Re: "Sticky" Keys ? In-Reply-To: <20000630074228.A2512@shadowmere.student.utwente.nl> Message-ID: <Pine.GSO.4.21.0006301251280.23885-100000@skat.usc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You want accessx for X-windows. Solaris, Compaq/Digital, and SGI provide it, but I didn't see anything at www.xfree86.org Searching around the web found a version for Linux http://slappy.cs.uiuc.edu/fall98/Linux/download.html Apple has long provided good support with Easy Access. Also, Microsoft's "accessibility" support gets much better under Windows 2000, but still geared toward having you buy something better/commercial. Sticky keys allows you to press key combinations one key at a time. There are many other controls: - Slow keys makes the keys not respond until they've been held down a long time so bumping other keys won't trigger them. - Slow mouse slows mouse cursor movement. - Some of these packages allow you to use the keypad as a mouse replacement with adjustable speed. - Magnifiers - Software to read aloud menus and text Good luck, Mike >Hi, > > A co-worker of mine who is mobilly handicapped, uses a Windows > "Accessibillity option" called "Sticky Keys" ... so he can still > operate his keyboard normally, using ... let's call it a "straw" and > his mouth. > > What this does is basically the following: > >- Pressing SHIFT/CONTROL/ALT once makes that key "active" until the next > keystroke. >- Pressing SHIFT/CONTROL/ALT twice makes that key "active" until it is > pressed a third time. > > He and I have been wondering if such functionality would also be > available already or "easily" to be implemented, so he might > actually be able to use a Unix environment to work with instead of a > Windows one. >-- > Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > > Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 18: 5: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 6A24D37C36F for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 18:04:59 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA24087; Fri, 30 Jun 2000 18:04:38 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 30 Jun 2000 18:04:37 -0700 (PDT) From: Doug Barton <Doug@gorean.org> X-Sender: doug@dt052n3e.san.rr.com To: Warner Losh <imp@village.org> Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) In-Reply-To: <200006301552.JAA41949@harmony.village.org> Message-ID: <Pine.BSF.4.21.0006301804110.23584-100000@dt052n3e.san.rr.com> 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, 30 Jun 2000, Warner Losh wrote: > In message <200006301550.JAA41895@harmony.village.org> Warner Losh writes: > : Don't get us going. No, it isn't. If you run out of room, GW says > > Actually that should be CW not GW. CW == Conventional Wisdom. I was going to point that out, but I didn't want to be accused of fostering a debate.... Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 19: 8:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 8BB6D37B655 for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 19:08:41 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FWZ00LXQXY2ND@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Fri, 30 Jun 2000 21:08:27 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id VAA66505; Fri, 30 Jun 2000 21:06:02 -0500 (CDT envelope-from chris) Date: Fri, 30 Jun 2000 21:06:01 -0500 From: Chris Costello <chris@calldei.com> Subject: Re: style(9) In-reply-to: <20000630114924.A78968@mithrandr.moria.org> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000630210601.J20702@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> <20000630114924.A78968@mithrandr.moria.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, June 30, 2000, Neil Blakey-Milner wrote: > No. Anyway, you can set your tab size to whatever you want. So long as > it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the > margin constantly, you should simplify your code, or break it up into > (preferably reusable) functions that perform one task. Setting a tab width to something other than 8 would tend to break formatting for people with normal editors. Just try viewing bsd.port.mk in vi with default settings and not seeing clutter. -- |Chris Costello <chris@calldei.com> |Random access is the optimum of the mass storages. `-------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 22:10:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 6594037B605; Fri, 30 Jun 2000 22:10:07 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id WAA31862; Fri, 30 Jun 2000 22:13:05 -0700 (PDT) Message-ID: <395D7D2B.48B90842@khmere.com> Date: Fri, 30 Jun 2000 22:10:04 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" <freebsd-net@FreeBSD.ORG>, "hackers@FreeBSD.ORG" <hackers@FreeBSD.ORG> Subject: loader and rootdev help !! 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 FreeBSD 4.0-RELEASE (on i386) What I am trying to do is nfs root boot from the loader (?) I do: ok> unload kernel ok> load diskless_kernel ok> set kernel=diskless_kernel ok> boot -r -h Now what I understand is the -r flag will tell the kernel to overide the rootdev and use the "staticly linked device" from when you made the kernel ? Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, NFS_ROOT .... etc.. ) compiled in. But when I boot like this is just tries to mount /dev/ad0s1a ... (normal device ) even though it gets the proper reply from the bootp server that its rootfs=<nfs mount> it even prints : rootfs is <my nfs mount > Mounting root from ufs:/dev/ad0s1a but still mounts the ufs ! How do if force it to boot root fs on nfs ? I have tried to do a boot -a then when I prompts me for root fs I enter the proper nfs mount and it is cool ...... but I need it to do it with out promting... I have tried to : ok> set rootdev=nfs:<my nfs server ip : mount > ok> boot -h ok> can't determine root device I have also passed it kernel flags ? (mybe wrong ones ... ? ) Now I have looked at the /usr/src/sys/boot/i386/libi386/bootinfo.c and I see where it checks the roodev to see if it is proper ..... but I cannot determine what type of device I can name so that this will not die on me ??? set rootdev=??? how do I have the kernel to load the nfs root instead of use the currdev ? What does etherboot do when it loads the kernel ? does it pass it special parameters ?? If you are wondering why I just don't boot from etherboot ....etc...(I do ) but... I want to be able to boot my remote systems without a floppie and chose how to boot from loader (via serail console ...I don't have serial access for the bios but I can get serial console with FreeBSD !! ). Either default (use local drive) or load the diskless kernel , then boot diskless. This way I almost the same options ..... and maybe automate it... Any help would be great !! thank you kindly.... nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 23:25:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from isua5.iastate.edu (isua5.iastate.edu [129.186.1.205]) by hub.freebsd.org (Postfix) with ESMTP id 2288D37B85D for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 23:25:39 -0700 (PDT) (envelope-from ccsanady@iastate.edu) Received: from localhost (ccsanady@localhost) by isua5.iastate.edu (8.8.8/8.8.5) with SMTP id BAA30984 for <freebsd-hackers@freebsd.org>; Sat, 1 Jul 2000 01:25:37 -0500 (CDT) Message-Id: <200007010625.BAA30984@isua5.iastate.edu> To: freebsd-hackers@freebsd.org Subject: Bridging problems.. (WaveLan related?) Date: Sat, 01 Jul 2000 01:25:37 CDT From: Chris Csanady <ccsanady@iastate.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying for over a week now to get bridging working, but without success. I have tried both 4.0 and current, but with no luck. Anyways, my setup is as follows.. On one end is a Lucent WavePoint attached to the outside world. (Some sort of switch I believe. I really don't understand the setup--they are using some sort of vlan stuff) I'm tempted to replace the WavePoint with a PC, but I don't have the hardware for that now. On my end, I have a box with a wi0 and fxp0--I was hoping to set it up to do transparent bridging. So far however, I can't get anything on this side of the bridge box to talk to the outside world. I can see all the network traffic from my box, however I can't talk through the bridge. Basically, any arp request that goes out, seems to disappear. If I run tcpdump on the wavelan interface, it shows the arp requests, but never any replies. I can see incoming arp requests for my box, and it seems to send the reply, only to be lost somewhere as well. Another interesting thing occurs from the bridge box itself. If I ping the network broadcast, only things on the wavelan side reply. This may be some irrelevant quirk, I'm not sure. Has anyone ever set up a box like this? Will it work with a WavePoint attached to a switch on the other side? I can't see why it shouldn't, but maybe I am missing something. Does the wavelan network need to be "ad-hoc" instead of BSS mode? All I know is this is becoming really irritating. (Not FreeBSD, but the fact that we don't have direct access to the network on the other side.) We have been trying to get this set up since May, and it has been a nightmare to deal with the politics and to debug it from one side. Ugh. Any theories/etc would be very welcome.. Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 23:27:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 47C4037B5EF for <freebsd-hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 23:27:51 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA04272; Sat, 1 Jul 2000 00:27:34 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <395D8FD7.484D9896@softweyr.com> Date: Sat, 01 Jul 2000 00:29:43 -0600 From: Wes Peters <wes@softweyr.com> Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> <20000630114924.A78968@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > On Fri 2000-06-30 (11:38), Martin Horcicka wrote: > > > b. Aren't 8 characters too many? > > No. Anyway, you can set your tab size to whatever you want. So long as > it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the > margin constantly, you should simplify your code, or break it up into > (preferably reusable) functions that perform one task. Or simply get a wider editor. Seriously. Writing code in 80 columns is an anachronism. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 23:54:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2DD1137B5EF for <hackers@FreeBSD.ORG>; Fri, 30 Jun 2000 23:54:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA08486; Sat, 1 Jul 2000 08:54:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 01:29:41 +0900." <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 08:54:00 +0200 Message-ID: <8484.962434440@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ es: >The invlpg instruction causes strange signal 11 problem on some >PentiumPro box. This problem seems to hapen when (1) mother board is >very old and (2) BIOS update is not available and (3) cpuid < 0x619. > >Following patch automatically disables invlpg when PentiumPro with >cpuid < 0x619 is found. > >Please comment to this patch. I'm against this patch. This is so specific and marginal to a out-of-spec hardware configuration, that it should not be put in the FreeBSD tree. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 23:56:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from isua4.iastate.edu (isua4.iastate.edu [129.186.1.204]) by hub.freebsd.org (Postfix) with ESMTP id 0B71637B8DB for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 23:56:54 -0700 (PDT) (envelope-from ccsanady@iastate.edu) Received: from localhost (ccsanady@localhost) by isua4.iastate.edu (8.8.8/8.8.5) with SMTP id BAA06648; Sat, 1 Jul 2000 01:56:51 -0500 (CDT) Message-Id: <200007010656.BAA06648@isua4.iastate.edu> To: freebsd-hackers@freebsd.org Cc: wpaul@ctr.columbia.edu Subject: Re: Bridging problems.. (WaveLan related?) In-reply-to: Your message of Sat, 01 Jul 2000 01:25:37 -0500. Date: Sat, 01 Jul 2000 01:56:51 CDT From: Chris Csanady <ccsanady@iastate.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It never fails.. I always post stuff just minutes too soon. Anyways, it seems that the problem is with the WaveLan network. In ad-hoc, or infrastructure mode, the card can only send frames with its own mac address as the source. Apparrently, the card needs to be set up as an access point (or something) to do bridging. Is there a way to do this in the current driver? If not, are there plans? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 30 23:57:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id A992037B9AB for <freebsd-hackers@freebsd.org>; Fri, 30 Jun 2000 23:57:07 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 393B35D1D; Sat, 1 Jul 2000 08:57:02 +0200 (CEST) Date: Sat, 1 Jul 2000 08:57:02 +0200 (CEST) From: Blaz Zupan <blaz@amis.net> X-Sender: blaz@titanic.medinet.si To: Chris Csanady <ccsanady@iastate.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: Bridging problems.. (WaveLan related?) In-Reply-To: <200007010625.BAA30984@isua5.iastate.edu> Message-ID: <Pine.BSF.4.21.0007010854530.83066-100000@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On my end, I have a box with a wi0 and fxp0--I was hoping to set it > up to do transparent bridging. So far however, I can't get anything > on this side of the bridge box to talk to the outside world. I > can see all the network traffic from my box, however I can't talk > through the bridge. Forget it, this won't work. You can only "talk" with one single MAC address on the WaveLan side, and for bridging to work you'd have to talk with multiple (all the MAC's from the other side of the bridge). The WaveLan stuff is just not like normal ethernet. There is no support for bridging in the wi driver because there is no point in supporting it. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 0:22: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id E37A037B5A5 for <freebsd-hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 00:22:01 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id QAA48673; Sat, 1 Jul 2000 16:51:11 +0930 (CST) (envelope-from newton) Date: Sat, 1 Jul 2000 16:51:11 +0930 From: Mark Newton <newton@internode.com.au> To: Chris Csanady <ccsanady@iastate.edu> Cc: freebsd-hackers@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: Bridging problems.. (WaveLan related?) Message-ID: <20000701165111.A48648@internode.com.au> References: <200007010656.BAA06648@isua4.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200007010656.BAA06648@isua4.iastate.edu> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 01, 2000 at 01:56:51AM -0500, Chris Csanady wrote: > It never fails.. I always post stuff just minutes too soon. > Anyways, it seems that the problem is with the WaveLan network. > In ad-hoc, or infrastructure mode, the card can only send > frames with its own mac address as the source. Apparrently, > the card needs to be set up as an access point (or something) > to do bridging. You can make it run as an access point... if and only if you're prepared to produce an 802.11 protocol suite to run in the FreeBSD kernel, because you won't be able to use the one in the card's firmware. Of course, if you want to do something as insane as that, I'm sure your efforts will be welcommed with open legs^H^H^H^Harms. Being able to replace an access point with a FreeBSD box which costs a third as much would be tres cool. This is particularly true in the case of the Aironet 802.11 gear, which has even worse restrictions wrt bridging and even more expensive access points. (FWIW: With the Aironet kit, when you place the card into "monitor mode" you can't transmit frames at all). - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 0:46:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dialup1.lemis.com [192.109.197.1]) by hub.freebsd.org (Postfix) with ESMTP id 98AE537B960 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 00:46:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA02229; Sat, 1 Jul 2000 00:50:51 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007010750.AAA02229@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 08:54:00 +0200." <8484.962434440@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jul 2000 00:50:51 -0700 From: Mike Smith <msmith@freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ > es: > >The invlpg instruction causes strange signal 11 problem on some > >PentiumPro box. This problem seems to hapen when (1) mother board is > >very old and (2) BIOS update is not available and (3) cpuid < 0x619. > > > >Following patch automatically disables invlpg when PentiumPro with > >cpuid < 0x619 is found. > > > >Please comment to this patch. > > I'm against this patch. This is so specific and marginal to a > out-of-spec hardware configuration, that it should not be put in > the FreeBSD tree. I'd disagree with that. This is just the same as the 0xf00f workaround, saving only in degree. If it's something that can be done as eg. a KLD we might want to do that instead, or through some other mechanism for handling these sort of CPU quirks. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 0:55:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 953ED37B99C; Sat, 1 Jul 2000 00:55:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA08890; Sat, 1 Jul 2000 09:55:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith <msmith@FreeBSD.ORG> Cc: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 00:50:51 PDT." <200007010750.AAA02229@mass.osd.bsdi.com> Date: Sat, 01 Jul 2000 09:55:03 +0200 Message-ID: <8886.962438103@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007010750.AAA02229@mass.osd.bsdi.com>, Mike Smith writes: >> In message <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ >> es: >> >The invlpg instruction causes strange signal 11 problem on some >> >PentiumPro box. This problem seems to hapen when (1) mother board is >> >very old and (2) BIOS update is not available and (3) cpuid < 0x619. >> > >> >Following patch automatically disables invlpg when PentiumPro with >> >cpuid < 0x619 is found. >> > >> >Please comment to this patch. >> >> I'm against this patch. This is so specific and marginal to a >> out-of-spec hardware configuration, that it should not be put in >> the FreeBSD tree. > >I'd disagree with that. This is just the same as the 0xf00f workaround, >saving only in degree. If it's something that can be done as eg. a KLD >we might want to do that instead, or through some other mechanism for >handling these sort of CPU quirks. Please Mike, just because you see my name you shouldn't take a contrary positition until you have actually looked into matters. Look at the first paragraph: This is for Pentium Pro cpus running in motherboards where the BIOS does not contain the needed microcode updates. The patch disables invlpg on all cpuid's < 0x619, despite the fact that they work just fine if your motherboards BIOS have the right microcode update for your cpu stepping. This hack should be maintained by the person who need it, it should not be lobotomizing FreeBSD in general. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 1:13:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id DF71937B84D; Sat, 1 Jul 2000 01:13:23 -0700 (PDT) (envelope-from mustafa@palnet.com) Received: from nawari (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with SMTP id LAA52097; Sat, 1 Jul 2000 11:19:17 +0300 (IDT) From: "Mustafa Deeb" <mustafa@palnet.com> To: <freebsd-hackers@freebsd.org>, <freebsd-isp@freebsd.org> Subject: Invalidating PACK!!! Date: Sat, 1 Jul 2000 11:11:47 +0200 Message-ID: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, we build our own servers, we've always used the intel N440BX and the Barracuda disks.. and we liked it so much, this time we bought intel's L440GX+ and the chettah disks from seagate (Ultra2 DIsks) and I'm getting these errors, ofcourse the server goes nuts when an error like this happens.. after looking into the mailling lists, nobody gave a direct reason for this problem or even a solution, anyways, I want to replace the Hard Drives, is there someone who've used the L440GX+ motherboard with 18G disks and he is happy with it Best Regards... Mustafa N. Deeb da0 at ahc0 bus 0 target 1 lun 0 da0: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device da0: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da2 at ahc0 bus 0 target 4 lun 0 da2: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device da2: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 2 lun 0 da1: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device da1: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb (da2:ahc0:0:4:0): Queuing a BDR SCB (da2:ahc0:0:4:0): no longer in timeout, status = 34a (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): Invalidating pack (da2:ahc0:0:4:0): SCB 0xc - timed out while idle, SEQADDR == 0x9 (da2:ahc0:0:4:0): Queuing a BDR SCB (da2:ahc0:0:4:0): no longer in timeout, status = 34a (da2:ahc0:0:4:0): Invalidating pack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 1:56:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id DAF2337B95A; Sat, 1 Jul 2000 01:56:11 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000701085549.RTJR26299.relay02@chello.nl>; Sat, 1 Jul 2000 10:55:49 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id KAA16715; Sat, 1 Jul 2000 10:56:02 +0200 (CEST) (envelope-from wkb) Date: Sat, 1 Jul 2000 10:56:02 +0200 From: Wilko Bulte <wkb@chello.nl> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Mike Smith <msmith@FreeBSD.ORG>, KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box Message-ID: <20000701105601.B16590@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <200007010750.AAA02229@mass.osd.bsdi.com> <8886.962438103@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <8886.962438103@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Jul 01, 2000 at 09:55:03AM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 01, 2000 at 09:55:03AM +0200, Poul-Henning Kamp wrote: > In message <200007010750.AAA02229@mass.osd.bsdi.com>, Mike Smith writes: > >> In message <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ > >> es: > >> >The invlpg instruction causes strange signal 11 problem on some > >> >PentiumPro box. This problem seems to hapen when (1) mother board is > >> >very old and (2) BIOS update is not available and (3) cpuid < 0x619. > >> > > >> >Following patch automatically disables invlpg when PentiumPro with > >> >cpuid < 0x619 is found. > >> > > >> >Please comment to this patch. > >> > >> I'm against this patch. This is so specific and marginal to a > >> out-of-spec hardware configuration, that it should not be put in > >> the FreeBSD tree. > > > >I'd disagree with that. This is just the same as the 0xf00f workaround, > >saving only in degree. If it's something that can be done as eg. a KLD > >we might want to do that instead, or through some other mechanism for > >handling these sort of CPU quirks. > > Please Mike, just because you see my name you shouldn't take a contrary > positition until you have actually looked into matters. > > Look at the first paragraph: This is for Pentium Pro cpus running > in motherboards where the BIOS does not contain the needed microcode > updates. > > The patch disables invlpg on all cpuid's < 0x619, despite the fact > that they work just fine if your motherboards BIOS have the right > microcode update for your cpu stepping. > > This hack should be maintained by the person who need it, it should > not be lobotomizing FreeBSD in general. Maybe make it conditional via an option in the kernel config file? Off by default of course. Looking at LINT/NOTES I see very obscure things for Cyrix and Bluelightning CPUs already. -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 2:27:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 33FE837B9AD; Sat, 1 Jul 2000 02:27:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA09191; Sat, 1 Jul 2000 11:27:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: wilko@FreeBSD.ORG Cc: Mike Smith <msmith@FreeBSD.ORG>, KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 10:56:02 +0200." <20000701105601.B16590@freebie.wbnet> Date: Sat, 01 Jul 2000 11:27:37 +0200 Message-ID: <9189.962443657@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701105601.B16590@freebie.wbnet>, Wilko Bulte writes: >> Look at the first paragraph: This is for Pentium Pro cpus running >> in motherboards where the BIOS does not contain the needed microcode >> updates. >> >> The patch disables invlpg on all cpuid's < 0x619, despite the fact >> that they work just fine if your motherboards BIOS have the right >> microcode update for your cpu stepping. >> >> This hack should be maintained by the person who need it, it should >> not be lobotomizing FreeBSD in general. > >Maybe make it conditional via an option in the kernel config file? >Off by default of course. Looking at LINT/NOTES I see very obscure things >for Cyrix and Bluelightning CPUs already. But Wilko, Those hacks are because the silicon, when used as directed, has flaws. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 2:37:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id F2A5B37B888; Sat, 1 Jul 2000 02:37:17 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000701093657.RZVJ26299.relay02@chello.nl>; Sat, 1 Jul 2000 11:36:57 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id LAA17030; Sat, 1 Jul 2000 11:36:58 +0200 (CEST) (envelope-from wkb) Date: Sat, 1 Jul 2000 11:36:58 +0200 From: Wilko Bulte <wkb@chello.nl> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: wilko@FreeBSD.ORG, Mike Smith <msmith@FreeBSD.ORG>, KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box Message-ID: <20000701113658.B16983@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <20000701105601.B16590@freebie.wbnet> <9189.962443657@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <9189.962443657@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Jul 01, 2000 at 11:27:37AM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 01, 2000 at 11:27:37AM +0200, Poul-Henning Kamp wrote: > In message <20000701105601.B16590@freebie.wbnet>, Wilko Bulte writes: > > >> Look at the first paragraph: This is for Pentium Pro cpus running > >> in motherboards where the BIOS does not contain the needed microcode > >> updates. > >> > >> The patch disables invlpg on all cpuid's < 0x619, despite the fact > >> that they work just fine if your motherboards BIOS have the right > >> microcode update for your cpu stepping. > >> > >> This hack should be maintained by the person who need it, it should > >> not be lobotomizing FreeBSD in general. > > > >Maybe make it conditional via an option in the kernel config file? > >Off by default of course. Looking at LINT/NOTES I see very obscure things > >for Cyrix and Bluelightning CPUs already. > > But Wilko, > > Those hacks are because the silicon, when used as directed, has flaws. OK, I understand that. But it appears to me that this patch allows the use of Si that should have had it's problems correct by the BIOS but in fact has not (because a corrected BIOS is not available). I'm one of those people who prefer a built-in, docuemted, switchable patch/hack over one that needs to be hunted down on the Net and applied. Heck, if I wanted to do that I would have chosen Linux ;-) -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 2:45:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E0E1937B9AD; Sat, 1 Jul 2000 02:45:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA09280; Sat, 1 Jul 2000 11:45:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: wilko@FreeBSD.ORG Cc: Mike Smith <msmith@FreeBSD.ORG>, KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 11:36:58 +0200." <20000701113658.B16983@freebie.wbnet> Date: Sat, 01 Jul 2000 11:45:28 +0200 Message-ID: <9278.962444728@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701113658.B16983@freebie.wbnet>, Wilko Bulte writes: >> >Maybe make it conditional via an option in the kernel config file? >> >Off by default of course. Looking at LINT/NOTES I see very obscure things >> >for Cyrix and Bluelightning CPUs already. >> >> But Wilko, >> >> Those hacks are because the silicon, when used as directed, has flaws. > >OK, I understand that. But it appears to me that this patch allows the use >of Si that should have had it's problems correct by the BIOS but in fact has >not (because a corrected BIOS is not available). I'm one of those people >who prefer a built-in, docuemted, switchable patch/hack over one that needs >to be hunted down on the Net and applied. Heck, if I wanted to do that I >would have chosen Linux ;-) I'm sorry, but I still don't think this patch belongs in FreeBSD. What guarantee do you have that this is enough to make those CPUs run reliably anyway ? As far as I know Intel never released the errata which the microcode updates fixes anyway. I'm still against. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 2:47: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 3D87D37B9A9 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 02:47:02 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id SAA25703; Sat, 1 Jul 2000 18:44:20 +0900 (JST) To: phk@critter.freebsd.dk Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <8484.962434440@critter.freebsd.dk> References: <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp> <8484.962434440@critter.freebsd.dk> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 18:44:20 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > I'm against this patch. This is so specific and marginal to a > out-of-spec hardware configuration, that it should not be put in > the FreeBSD tree. I'm not 100% sure but I think the signal 11 problem is result from the CPU errata. There is the invlpg related errata and it has been fixed in stepping sB0 (cpuid = 0x619). I have both sA0 (cpuid = 0x617) and sB0 steppings and the signal 11 problem occurs only with the sA0 stepping. So, I think it is same as the 0xf00f hacking. -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 3: 3:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C24EA37B888 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 03:03:11 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA09400; Sat, 1 Jul 2000 12:03:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 18:44:20 +0900." <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 12:03:03 +0200 Message-ID: <9398.962445783@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ es: >Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > >> I'm against this patch. This is so specific and marginal to a >> out-of-spec hardware configuration, that it should not be put in >> the FreeBSD tree. > >I'm not 100% sure but I think the signal 11 problem is result from the >CPU errata. There is the invlpg related errata and it has been fixed >in stepping sB0 (cpuid = 0x619). I have both sA0 (cpuid = 0x617) and >sB0 steppings and the signal 11 problem occurs only with the sA0 >stepping. If we are talking about errata #34 the correct solution is to not use 4MB pages. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 3:56: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id D783C37B6FF for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 03:55:59 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id TAA25829; Sat, 1 Jul 2000 19:53:37 +0900 (JST) To: phk@critter.freebsd.dk Cc: kato@ganko.eps.nagoya-u.ac.jp, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <9398.962445783@critter.freebsd.dk> References: <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> <9398.962445783@critter.freebsd.dk> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000701195337N.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 19:53:37 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 13 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > If we are talking about errata #34 the correct solution is to not use > 4MB pages. Is FreeBSD #29-safe? -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 4:28:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 1215C37BA54 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 04:28:19 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id UAA25868; Sat, 1 Jul 2000 20:25:56 +0900 (JST) To: phk@critter.freebsd.dk, hackers@FreeBSD.ORG Cc: kato@ganko.eps.nagoya-u.ac.jp Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> References: <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp> <8484.962434440@critter.freebsd.dk> <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000701202556Z.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 20:25:56 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > in stepping sB0 (cpuid = 0x619). I have both sA0 (cpuid = 0x617) and > sB0 steppings and the signal 11 problem occurs only with the sA0 > stepping. Oops, sA0 -> sA1 and sB0 -> sB1. -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 6:33:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 28DCF37B51E for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 06:33:10 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id WAA26049; Sat, 1 Jul 2000 22:30:41 +0900 (JST) To: phk@critter.freebsd.dk Cc: kato@ganko.eps.nagoya-u.ac.jp, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <20000701195337N.kato@gneiss.eps.nagoya-u.ac.jp> References: <20000701184420G.kato@gneiss.eps.nagoya-u.ac.jp> <9398.962445783@critter.freebsd.dk> <20000701195337N.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000701223041W.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 22:30:41 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > > > If we are talking about errata #34 the correct solution is to not use > > 4MB pages. > > Is FreeBSD #29-safe? variable MTTRs are set as follows: MSR (200): 0000000000000006 MSR (201): 0000000ffc000800 MSR (202): 0000000004000006 MSR (203): 0000000fff000800 MSR (204): 0000000000f00000 MSR (205): 0000000ffff00800 * MSR (206): 0000000000000000 MSR (207): 0000000000000000 MSR (208): 0000000000000000 MSR (209): 0000000000000000 MSR (20a): 0000000000000000 MSR (20b): 0000000000000000 MSR (20c): 0000000000000000 MSR (20d): 0000000000000000 MSR (20e): 0000000000000000 MSR (20f): 0000000000000000 One variable MTTR (marked *) has non-4MB aligned mask and errata #29 affects this system. -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 10:47:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 39FF137B61A; Sat, 1 Jul 2000 10:47:20 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id CAA26892; Sun, 2 Jul 2000 02:44:54 +0900 (JST) To: phk@critter.freebsd.dk Cc: msmith@FreeBSD.ORG, kato@ganko.eps.nagoya-u.ac.jp, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <8886.962438103@critter.freebsd.dk> References: <200007010750.AAA02229@mass.osd.bsdi.com> <8886.962438103@critter.freebsd.dk> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000702024454G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 02 Jul 2000 02:44:54 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 17 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > Look at the first paragraph: This is for Pentium Pro cpus running > in motherboards where the BIOS does not contain the needed microcode > updates. I have one question. Does microcode update modify a CPU permanently? I used a CPU on the M/B with correct microcode update and then moved the CPU to the M/B which has signal 11 problem. Signal 11 didn't disappear. -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 10:51:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id A38AD37B8A4 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 10:51:10 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-194-8-195-240.netcologne.de [194.8.195.240]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id TAA14994 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 19:51:08 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e61HojQ00338 for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 19:50:45 +0200 (CEST) Date: Sat, 1 Jul 2000 19:50:44 +0200 (CEST) From: Paul Herman <pherman@frenchfries.net> To: hackers@FreeBSD.ORG Subject: vmstats for pages that go inactive->active Message-ID: <Pine.BSF.4.21.0007011933460.224-100000@bagabeedaboo.security.at12.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, vmmeter->cnt.v_reactivated counts the number of cache pages that get promoted to either active or inactive queues. My read (and I could be wrong) from vm/vm_page.c is, there is no statistic to count the inactive pages that get "reclaimed" into the active queue. I would think this would be interessant/useful/enlightening/tasty for Joe Sysadmin. Any takers? It should be a very simple patch (he says.) Just thought I'd ask before I go merily a-hackin. Actually, I'm just looking for a way to _completely_ fill up the 'systat -v' screen. :) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 10:56:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 8197737B889; Sat, 1 Jul 2000 10:56:11 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id CAA26914; Sun, 2 Jul 2000 02:56:09 +0900 (JST) To: msmith@freebsd.org Cc: phk@critter.freebsd.dk, kato@ganko.eps.nagoya-u.ac.jp, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> In-Reply-To: <200007010750.AAA02229@mass.osd.bsdi.com> References: <8484.962434440@critter.freebsd.dk> <200007010750.AAA02229@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000702025609D.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 02 Jul 2000 02:56:09 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 16 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith <msmith@freebsd.org> wrote: > If it's something that can be done as eg. a KLD > we might want to do that instead, or through some other mechanism for > handling these sort of CPU quirks. It sounds good. If binary-format quriks is supported, we can supply update modules for new CPU and newly found errata like the update module for AMD K6-2 CPU of Windows 95. -----------------------------------------------+--------------------------+ KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 11:54: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id 0F49537B69A; Sat, 1 Jul 2000 11:54:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA00878; Sat, 1 Jul 2000 20:53:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp> Cc: msmith@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sun, 02 Jul 2000 02:44:54 +0900." <20000702024454G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 20:53:56 +0200 Message-ID: <876.962477636@critter.freebsd.dk> From: Poul-Henning Kamp <phk@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000702024454G.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ es: >Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > >> Look at the first paragraph: This is for Pentium Pro cpus running >> in motherboards where the BIOS does not contain the needed microcode >> updates. > >I have one question. Does microcode update modify a CPU permanently? No, it needs to be loaded at every reboot. >I used a CPU on the M/B with correct microcode update and then moved >the CPU to the M/B which has signal 11 problem. Signal 11 didn't >disappear. This must have other reasons. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:19:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 169F337B69A for <hackers@freebsd.org>; Sat, 1 Jul 2000 12:19:46 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id PAA04481 for <hackers@freebsd.org>; Sat, 1 Jul 2000 15:19:45 -0400 (EDT) Message-Id: <200007011919.PAA04481@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 01 Jul 2000 15:27:51 -0400 To: hackers@freebsd.org From: Dennis <dennis@etinc.com> Subject: stray interrupts in 4.0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the same hardware reports nothing. The interrupt its complaining about is IRQ7 even though parallel port is disabled and no other device. It happens on more than 1 MB. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:43:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 689EE37B612; Sat, 1 Jul 2000 12:43:15 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e61JhAZ81729; Sat, 1 Jul 2000 21:43:10 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA06884; Sat, 1 Jul 2000 21:25:46 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Jul 2000 21:25:45 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Mustafa Deeb <mustafa@palnet.com> Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Invalidating PACK!!! Message-ID: <20000701212545.F26119@daemon.ninth-circle.org> References: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com>; from mustafa@palnet.com on Sat, Jul 01, 2000 at 11:11:47AM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000701 11:18], Mustafa Deeb (mustafa@palnet.com) wrote: >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb >(da2:ahc0:0:4:0): Queuing a BDR SCB >(da2:ahc0:0:4:0): no longer in timeout, status = 34a Last times it happened to me it was either: - bad cabling - faulty HD/firmware - system ran way too hot I haven't really had a chance to blame the SCSI subsystem present in FreeBSD and trust me, I have had my share of these messages. Hope this helps, -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai> And the price of a Memory is the Memory of the Sorrow it brings... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:43:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 07C5D37B845 for <freebsd-hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 12:43:20 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e61JhCZ81734; Sat, 1 Jul 2000 21:43:12 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA06892; Sat, 1 Jul 2000 21:29:53 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Jul 2000 21:29:53 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Warner Losh <imp@village.org> Cc: Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) Message-ID: <20000701212953.H26119@daemon.ninth-circle.org> References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> <200006301550.JAA41895@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006301550.JAA41895@harmony.village.org>; from imp@village.org on Fri, Jun 30, 2000 at 09:50:27AM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000630 19:34], Warner Losh (imp@village.org) wrote: > >I personally like 4 myself, but let's not get into a stupid tab width >war were people argue about values from 2 to 6 that ends in the >resolution that 8 might not be right, but reformatting everything >would suck too bad to change it and introducing new code that isn't >formatted at 8 would be confusing. OK? We've done that before. For more wisdom on that read NetBSD-kernel and NetBSD-misc archives of this year, february IIRC. They just went through the whole debate. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai> An expert is one who knows more and more about less and less... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:43:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id DDB5337B97C for <freebsd-hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 12:43:20 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e61JhGZ81737; Sat, 1 Jul 2000 21:43:16 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA06888; Sat, 1 Jul 2000 21:28:18 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Jul 2000 21:28:18 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Wes Peters <wes@softweyr.com> Cc: Neil Blakey-Milner <nbm@mithrandr.moria.org>, Martin Horcicka <horcicka@dzungle.ms.mff.cuni.cz>, freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) Message-ID: <20000701212818.G26119@daemon.ninth-circle.org> References: <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> <20000630114924.A78968@mithrandr.moria.org> <395D8FD7.484D9896@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <395D8FD7.484D9896@softweyr.com>; from wes@softweyr.com on Sat, Jul 01, 2000 at 12:29:43AM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000701 09:25], Wes Peters (wes@softweyr.com) wrote: > >Or simply get a wider editor. Seriously. Writing code in 80 columns is >an anachronism. Tastes do differ for that. Often the 80 column boundary reminds me not to use functions_which_have_crazy_long_names_with_underscores(), but be a little more brief, but not too. ;) -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai> Here's a mirror, there's a screen, on both ways you can get in... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:49:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 4FF5237B9D9; Sat, 1 Jul 2000 12:49:48 -0700 (PDT) (envelope-from jon@mail.csh.rit.edu) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id 67D8F2DB; Sat, 1 Jul 2000 15:49:46 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id PAA25780; Sat, 1 Jul 2000 15:49:39 -0400 (EDT) Date: Sat, 1 Jul 2000 15:49:39 -0400 From: Jon Parise <jon@csh.rit.edu> To: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Invalidating PACK!!! Message-ID: <20000701154939.A25753@csh.rit.edu> Mail-Followup-To: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org References: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com>; from mustafa@palnet.com on Sat, Jul 01, 2000 at 11:11:47AM +0200 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 01, 2000 at 11:11:47AM +0200, Mustafa Deeb wrote: > is there someone who've used the L440GX+ motherboard with 18G disks > and he is happy with it No problems here with assorted 18G and 9G IBM Ultrastars and some 9G Cheetahs. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 12:53:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id E8C1D37B89F; Sat, 1 Jul 2000 12:53:48 -0700 (PDT) (envelope-from mustafa@palnet.com) Received: from palnet.com (mustafa.palnet.com [192.116.17.10]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id WAA93616; Sat, 1 Jul 2000 22:59:40 +0300 (IDT) Message-ID: <395E5946.527C8759@palnet.com> Date: Sat, 01 Jul 2000 22:49:11 +0200 From: "Mustafa N. Deeb" <mustafa@palnet.com> Organization: Palnet Communications Ltd. X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Invalidating PACK!!! References: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com> <20000701212545.F26119@daemon.ninth-circle.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, well I think I've eliminated most of these things, I've the disks out of the server and made the cooler point the air to it.. and It does not look like bad cables... about the BAD hd, I've the problem on 5/5 new drives that I bought.. I'll try upgrading the firmeware and BIOS.. and see.. cheers Jeroen Ruigrok/Asmodai wrote: > -On [20000701 11:18], Mustafa Deeb (mustafa@palnet.com) wrote: > >(da2:ahc0:0:4:0): Invalidating pack > >(da2:ahc0:0:4:0): Invalidating pack > >(da2:ahc0:0:4:0): Invalidating pack > >(da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb > >(da2:ahc0:0:4:0): Queuing a BDR SCB > >(da2:ahc0:0:4:0): no longer in timeout, status = 34a > > Last times it happened to me it was either: > > - bad cabling > > - faulty HD/firmware > > - system ran way too hot > > I haven't really had a chance to blame the SCSI subsystem present in > FreeBSD and trust me, I have had my share of these messages. > > Hope this helps, > > -- > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best > The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai> > And the price of a Memory is the Memory of the Sorrow it brings... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" 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 Jul 1 13: 1:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from allied.reck.com (allied.reck.com [208.220.150.162]) by hub.freebsd.org (Postfix) with ESMTP id 2830337B819; Sat, 1 Jul 2000 13:01:47 -0700 (PDT) (envelope-from joeym@allied.reck.com) Received: (from joeym@localhost) by allied.reck.com (8.10.0/8.10.0) id e61K3ss22262; Sat, 1 Jul 2000 13:03:54 -0700 (MST) Date: Sat, 1 Jul 2000 13:03:54 -0700 From: Joey Miller <joeym@inficad.com> To: Mustafa Deeb <mustafa@palnet.com> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Invalidating PACK!!! Message-ID: <20000701130353.F708@inficad.com> Reply-To: joeym@inficad.com References: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <CFEOIJDJKKPECJCHODEHKECBCGAA.mustafa@palnet.com>; from mustafa@palnet.com on Sat, Jul 01, 2000 at 11:11:47AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG had the same problems. make sure you are using LVD ribbon cables. On Sat, Jul 01, 2000 at 11:11:47AM +0200, Mustafa Deeb wrote: // hi all, // // we build our own servers, we've always used the intel N440BX and the // Barracuda disks.. and we liked it so much, // this time we bought intel's L440GX+ and the chettah disks from seagate // (Ultra2 DIsks) // and I'm getting these errors, // ofcourse the server goes nuts when an error like this happens.. // after looking into the mailling lists, nobody gave a direct reason for this // problem or even a solution, anyways, I want to replace the Hard Drives, // // is there someone who've used the L440GX+ motherboard with 18G disks and he // is happy with it // // Best Regards... // Mustafa N. Deeb // // // // da0 at ahc0 bus 0 target 1 lun 0 // da0: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device // da0: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // da2 at ahc0 bus 0 target 4 lun 0 // da2: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device // da2: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // da1 at ahc0 bus 0 target 2 lun 0 // da1: <SEAGATE ST318404LW 0002> Fixed Direct Access SCSI-3 device // da1: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb // (da2:ahc0:0:4:0): Queuing a BDR SCB // (da2:ahc0:0:4:0): no longer in timeout, status = 34a // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): SCB 0xc - timed out while idle, SEQADDR == 0x9 // (da2:ahc0:0:4:0): Queuing a BDR SCB // (da2:ahc0:0:4:0): no longer in timeout, status = 34a // (da2:ahc0:0:4:0): Invalidating pack // // // // To Unsubscribe: send mail to majordomo@FreeBSD.org // with "unsubscribe freebsd-isp" in the body of the message -- Joey Miller Sr. Systems Engineer iBIZ Technology Corp. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 13:26:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 12D9D37B798; Sat, 1 Jul 2000 13:26:37 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA98172; Sat, 1 Jul 2000 14:26:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA53819; Sat, 1 Jul 2000 14:26:29 -0600 (MDT) Message-Id: <200007012026.OAA53819@harmony.village.org> To: wilko@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Mike Smith <msmith@FreeBSD.ORG>, KATO Takenori <kato@ganko.eps.nagoya-u.ac.jp>, hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 Jul 2000 10:56:02 +0200." <20000701105601.B16590@freebie.wbnet> References: <20000701105601.B16590@freebie.wbnet> <200007010750.AAA02229@mass.osd.bsdi.com> <8886.962438103@critter.freebsd.dk> Date: Sat, 01 Jul 2000 14:26:29 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701105601.B16590@freebie.wbnet> Wilko Bulte writes: : Maybe make it conditional via an option in the kernel config file? : Off by default of course. Looking at LINT/NOTES I see very obscure things : for Cyrix and Bluelightning CPUs already. I was going to make that same argument. There's a need to have these centrally located. It should be conditional, however... Then again, on the hardware we have for Timing Solutions, we have to turn off the FOOF hack because it gets in the way of intercepting NMI traps... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 13:29:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E3A3837B9D6 for <freebsd-hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 13:29:40 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA98197; Sat, 1 Jul 2000 14:29:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA53865; Sat, 1 Jul 2000 14:29:33 -0600 (MDT) Message-Id: <200007012029.OAA53865@harmony.village.org> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Subject: Re: style(9) Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 Jul 2000 21:28:18 +0200." <20000701212818.G26119@daemon.ninth-circle.org> References: <20000701212818.G26119@daemon.ninth-circle.org> <Pine.BSF.3.96.1000630113615.2357A-100000@dzungle.ms.mff.cuni.cz> <20000630114924.A78968@mithrandr.moria.org> <395D8FD7.484D9896@softweyr.com> Date: Sat, 01 Jul 2000 14:29:32 -0600 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000701212818.G26119@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: : Often the 80 column boundary reminds me not to use : functions_which_have_crazy_long_names_with_underscores(), but be a : little more brief, but not too. ;) IKnowPeopleThatLikeToHaveParagraphFunctionNamesToo(); DrivesMeNutsBecauseTheirCodeIsHardToReadAndModify(); TooMuchVerbosityIsSoMuchWorseThanTooLittleAndRepeitionCanBeBadToo(); Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 14:23:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 434B037B57A for <hackers@FreeBSD.ORG>; Sat, 1 Jul 2000 14:23:52 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e61LNoV02918; Sat, 1 Jul 2000 14:23:50 -0700 (PDT) Date: Sat, 1 Jul 2000 14:23:49 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Dennis <dennis@etinc.com> Cc: hackers@FreeBSD.ORG Subject: Re: stray interrupts in 4.0 In-Reply-To: <200007011919.PAA04481@etinc.com> Message-ID: <Pine.BSF.4.21.0007011422460.97028-100000@resnet.uoregon.edu> 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, 1 Jul 2000, Dennis wrote: > We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the > same hardware reports nothing. The interrupt its complaining about is IRQ7 > even though parallel port is disabled and no other device. It happens on > more than 1 MB. This is in the archives and the FAQ at www.freebsd.org. This is normal. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 14:30:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from monica.et.bocholt.fh-gelsenkirchen.de (monica.et.bocholt.fh-gelsenkirchen.de [193.175.197.63]) by hub.freebsd.org (Postfix) with ESMTP id AA1C637B57A; Sat, 1 Jul 2000 14:30:40 -0700 (PDT) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Received: from musashi.et.bocholt.fh-ge.de (reserve.et.bocholt.fh-gelsenkirchen.de [193.175.197.95] (may be forged)) by monica.et.bocholt.fh-gelsenkirchen.de (8.9.3/8.9.3) with ESMTP id XAA16997; Sat, 1 Jul 2000 23:30:39 +0200 Received: from localhost (localhost.et.bocholt.fh-ge.de [127.0.0.1]) by musashi.et.bocholt.fh-ge.de (8.9.3/8.9.3) with ESMTP id XAA88896; Sat, 1 Jul 2000 23:31:04 +0200 (CEST) (envelope-from hank@musashi.et.bocholt.fh-ge.de) Message-Id: <200007012131.XAA88896@musashi.et.bocholt.fh-ge.de> From: gouders@et.bocholt.fh-gelsenkirchen.de To: freebsd-doc@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: ECU files and MLB BIOS Reply-To: gouders@et.bocholt.fh-gelsenkirchen.de Date: Sat, 01 Jul 2000 23:31:04 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am having understanding/translation problems, again. Can anyone help me with the terms "ECU files" and "MLB BIOS" (Hackers section of the FAQ)? Thanks, Dirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 16:37:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id 51E6A37B6A3 for <hackers@freebsd.org>; Sat, 1 Jul 2000 16:37:25 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id TAA12690; Sat, 1 Jul 2000 19:43:58 -0400 (EDT) (envelope-from cokane) Date: Sat, 1 Jul 2000 19:43:57 -0400 From: Coleman Kane <cokane@one.net> To: Matthew Reimer <mreimer@vpop.net> Cc: Thomas Stromberg <tstromberg@rtci.com>, hackers@freebsd.org Subject: Re: XFree86 4.0 - What are people using for dual-head video? Message-ID: <20000701194357.A12638@cokane.yi.org> References: <lists.freebsd.hackers.Pine.GSO.4.20.0006300835280.19036-100000@barracuda.aquarium.rtci.com> <395CCB95.BD90BDAF@vpop.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <395CCB95.BD90BDAF@vpop.net>; from mreimer@vpop.net on Fri, Jun 30, 2000 at 12:33:00PM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using a Matrox MGA G200 and a matrox Mystique 220. The mystique card has a shot bios chip, so it only works as a secondary video board. Besides, the G200 is far better to put on my 19" KDS VS-195e. My Mystique is connected to an older NEC SVGA monitor, 14" at 1024x768@60Hz. Matthew Reimer had the audacity to say: > > Thomas Stromberg wrote: > > > > This discussion comes up every once in a while on the lists, and I guess > > it's time for an update. I havent seen anything since the 3.9.17 beta, so > > here we go.. > > > > What dual head video combinations are people using with XFree86 4.0 and > > FreeBSD? I've got a -CURRENT box right now with an AGP Riva TNT 2, and > > really want to setup dual-head with it for programming (after first seeing > > it on IRIX several years ago, I got hooked). Are people mixing different > > vendors (Riva & Matrox?) and or AGP and PCI? > > > > It's my understanding that there still isn't support for the dual-head > > cards from Matrox, unless you go with a commercial X server. If anyone > > could point me to a dual-head compatibility list, that'd help too. > > I've had success with an AGP TNT2 Ultra with a Matrox Millenium. > > Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 16:48:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id 7333337BB01; Sat, 1 Jul 2000 16:48:20 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id TAA12785; Sat, 1 Jul 2000 19:55:47 -0400 (EDT) (envelope-from cokane) Date: Sat, 1 Jul 2000 19:55:47 -0400 From: Coleman Kane <cokane@one.net> To: hackers@FreeBSD.org, multimedia@FreeBSD.org Subject: UDF (DVD fs) Message-ID: <20000701195547.A12762@cokane.yi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hello, is anyone currently working on code to implement the UDF filesystem? For those not familiar with it, it is the filesystem that DVDs use. I'd like to look into getting the support under FreeBSD, since the players already seem to work. If no one is working on this, then I could probably use some help in writing the code to support this fs. --=20 Coleman Kane President,=20 UC Free O.S. Users Group - http://pohl.ececs.uc.edu --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5XoUDERViMObJ880RAZPfAJ9fN9LA/8lbB9vQBaJRRaCnA9t4ewCeOs5m US/e8zeTIPYMXVCOx7f8b0k= =jkR+ -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 16:50:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id EE0B937BAE8 for <freebsd-hackers@freebsd.org>; Sat, 1 Jul 2000 16:50:39 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Sat Jul 01 19:48:56 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id <N3K7998F>; Sat, 1 Jul 2000 19:48:50 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C924@SN1EXCHMBX> From: Nick Evans <nevans@nextvenue.com> To: "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org> Subject: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance Date: Sat, 1 Jul 2000 19:48:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE3B6.E7BEAFD0" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE3B6.E7BEAFD0 Content-Type: text/plain; charset="iso-8859-1" Does anyone know if the FXP driver in 4.0-STABLE supports the AFT Fault Tolerance features of this network card? I know the fault tolerance is set in the driver under WindowsNT but I'm not quite sure whether or not it is supported, or will be supported, on FreeBSD. ------_=_NextPart_001_01BFE3B6.E7BEAFD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2652.35"> <TITLE>Intel Pro/100+ Dual Port Server Adapter and Fault = Tolerance

Does anyone know if the FXP driver in = 4.0-STABLE supports the AFT Fault Tolerance features of this network = card? I know the fault tolerance is set in the driver under WindowsNT = but I'm not quite sure whether or not it is supported, or will be = supported, on FreeBSD.

------_=_NextPart_001_01BFE3B6.E7BEAFD0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 17:26:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C23A137B695; Sat, 1 Jul 2000 17:26:38 -0700 (PDT) (envelope-from jhb@bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA82574; Sat, 1 Jul 2000 17:26:21 -0700 (PDT) (envelope-from jhb@bsdi.com) Received: from bsdi.com (jhb@localhost [127.0.0.1]) by foo.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA95289; Sat, 1 Jul 2000 17:26:07 -0700 (PDT) (envelope-from jhb@bsdi.com) Message-ID: <395E8C1F.675AA7D1@bsdi.com> Date: Sat, 01 Jul 2000 17:26:07 -0700 From: John Baldwin Organization: BSD, Inc. X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: phk@FreeBSD.org Cc: hackers@FreeBSD.org Subject: Why do we always create a malloc disk for md? 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 attempting to resolve why sysinstall keeps dying in -current at the moment. It seems that the problem is that md_drvinit() always creates a malloc disk during initialization: static void md_drvinit(void *unused) { ... [ load preloaded disks such as mfsroot.tgz from install floppy ] printf("md%d: Malloc disk\n", mdunits); mdcreate_malloc(); } This results in having two md devices during boot: md0: Preloaded image mumble bytes at 0xmumble md1: Malloc disk This ends up registering md1 with disk_create, and thus md1 is returned as a disk through kern.disks into the list returned by Disk_Names(), and sysinstall blows up when it tries to open it. I think the reason it blows up is because /dev/md1 isn't around, although I think I may be able to fix that by adding 'md' as a disk device in the table in sysinstall/devices.c.\ However, I'm curious if md1 should be created in this case? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 17:46: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 774D837B819 for ; Sat, 1 Jul 2000 17:46:06 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-17.nnj.dialup.bellatlantic.net [151.198.117.17]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA05521; Sat, 1 Jul 2000 20:45:30 -0400 (EDT) Message-ID: <395E90EE.61CB5B66@bellatlantic.net> Date: Sat, 01 Jul 2000 20:46:38 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: chris@calldei.com Cc: Neil Blakey-Milner , Martin Horcicka , freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) References: <20000630114924.A78968@mithrandr.moria.org> <20000630210601.J20702@holly.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > On Friday, June 30, 2000, Neil Blakey-Milner wrote: > > No. Anyway, you can set your tab size to whatever you want. So long as > > it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the > > margin constantly, you should simplify your code, or break it up into > > (preferably reusable) functions that perform one task. > > Setting a tab width to something other than 8 would tend to > break formatting for people with normal editors. Just try > viewing bsd.port.mk in vi with default settings and not seeing > clutter. Troubles start when people start using spaces at the beginning of the lines. As long as _only_ tabs occur at the begining of the lines everything is fine with any tab width (and I personally prefer to set the tab width equal to 4). The worst thing that can happen is the lines over 80 characters and that's no big deal. On the other hand using tabs inside the lines tends to break into ugly things. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 23:37:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h017.c014.sfo.cp.net [209.228.12.81]) by hub.freebsd.org (Postfix) with SMTP id 68A2037BD45 for ; Sat, 1 Jul 2000 23:37:41 -0700 (PDT) (envelope-from gharris@flashcom.net) Received: (cpmta 7551 invoked from network); 1 Jul 2000 23:37:40 -0700 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net with SMTP; 1 Jul 2000 23:37:40 -0700 X-Sent: 2 Jul 2000 06:37:40 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id XAA03537; Sat, 1 Jul 2000 23:35:39 -0700 (PDT) (envelope-from gharris) Date: Sat, 1 Jul 2000 23:35:39 -0700 From: Guy Harris To: Mike Walker Cc: Pascal Hofstee , freebsd-hackers@freebsd.org Subject: Re: "Sticky" Keys ? Message-ID: <20000701233539.C340@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6us Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You want accessx for X-windows. Solaris, Compaq/Digital, and SGI > provide it, but I didn't see anything at www.xfree86.org > Searching around the web found a version for Linux > http://slappy.cs.uiuc.edu/fall98/Linux/download.html AccessX appears to have been developed, at least in part, by the Trace Research and Development Center at the University of Wisconsin-Madison. The page at http://trace.wisc.edu/docs/x_win_access/x_access.htm says, in the audience question section: Audience: Will AccessX be in X11R6? Will: AccessX was developed by Digital, Trace, and SUN and we did it for X11R5. Digital and SUN will be releasing it with the next version of their operating systems which include the X11R5 server. DACX has worked closely with Silicon Graphics, who are working to develop the XKB extension for X11R6. It is a much larger extension that deals with the keyboard and is a logical place to put the AccessX code. So for X11R6, AccessX will be a part of a larger extension called XKB. The answer is yes it will be there but it will be a different name. Earl: One additional item. The fact that the underlying is changing, AccessX to XKB, the user interface will still be the same, so to use the R5 version on a SUN or DEC and when you transition to R6 version of the window server, the user interface will look the same, the interaction will be the same. So you won't have to change how you interact with the systems. XKB is part of X11R6.1 and later, so I infer that the low-level X server support for sticky keys is built into recent versions of XFree86. I don't know whether the UI stuff to control it is part of X11R6.x, or of XFree86, though. The Linux AccessX page you cite has a tarball of "the pristine source" for their package, which appears to contain a Tcl script which may be their control application, plus some C and C++ source; that page seems to imply that there are features over and above the XKB-based features of the Digital/Trace/Sun AccessX project, e.g.: o Video Mode Changing lets users change their video screen mode on demand. o Control Panel allows the user to apply the settings before saving, save the user's settings, tab through the panel (for those who cannot use a mouse), give the user the option to restore the to the default settings, and more. o Soon, the AccessX package will also include screen magnification. (I don't know whether the Video Mode Changing lets you change resolution on the fly without changing your desktop - in which case it'd probably be of interest even to people *without* limited vision - or not; it may just be an interface to the video-mode changing extensions of XFree86). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 1 23:46:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 7138137BD5A; Sat, 1 Jul 2000 23:46:13 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA22131; Sat, 1 Jul 2000 23:46:12 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id XAA33812; Sat, 1 Jul 2000 23:47:05 -0700 (PDT) (envelope-from john) Message-Id: <200007020647.XAA33812@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <8886.962438103@critter.freebsd.dk> Date: Sat, 01 Jul 2000 23:47:05 -0700 (PDT) From: John Baldwin To: Poul-Henning Kamp Subject: Re: invlpg produces strange sig11 on PentiumPro box Cc: hackers@FreeBSD.ORG, KATO Takenori , Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Jul-00 Poul-Henning Kamp wrote: > In message <200007010750.AAA02229@mass.osd.bsdi.com>, Mike Smith writes: >>> In message <20000701012941S.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ >>> es: >>> >The invlpg instruction causes strange signal 11 problem on some >>> >PentiumPro box. This problem seems to hapen when (1) mother board is >>> >very old and (2) BIOS update is not available and (3) cpuid < 0x619. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Please Mike, just because you see my name you shouldn't take a contrary > positition until you have actually looked into matters. > > Look at the first paragraph: This is for Pentium Pro cpus running > in motherboards where the BIOS does not contain the needed microcode > updates. *ahem* You might want to read the first paragraph as well. It is for situations where one _can't_ update one's BIOS. I don't see why making it a tweakable kernel compile time know that is off by default would be so incredibly bad. We have precedents already for this type of thing. And yes, in this case, the CPU is not performing as advertised. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message