From owner-freebsd-hackers Sun Jul 16 1: 1:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 71DC537BB47; Sun, 16 Jul 2000 01:01:19 -0700 (PDT) (envelope-from freebsd@planet.nl) Received: from ipc379907b.dial.wxs.nl ([195.121.144.123]) by smtp05.wxs.nl (Netscape Messaging Server 4.15) with ESMTP id FXS6AA02.95F; Sun, 16 Jul 2000 10:01:22 +0200 Date: Sun, 16 Jul 2000 10:01:14 +0200 (CEST) From: Marc Veldman X-Sender: freebsd@kwetal.lurkie.org To: "Kenneth D. Merry" Cc: Essenz Consulting , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 160/m support... In-Reply-To: <20000711150153.A38521@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 On Tue, 11 Jul 2000, Kenneth D. Merry wrote: > > Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be > > worked on? aka, has adaptec released any info to those FreeBSD team > > members who work on the SCSI drivers? Is it possible that maybe within the > > next 4 months 160/m support will exist in FreeBSD 4/5? > > It's working, but isn't in the tree yet. AFAIK, the aic-7892 works just fine in 4.0-STABLE, and it has worked fine for a few months now. I'm not sure if the actual 160/m works though. This is from my dmesg: ahc0: port 0xfc00-0xfcff mem 0xfffbf000-0xfffbffff irq 7 at device 13.0 on pci0 ahc0: aic7892 Wide Channel A, SCSI Id=15, 16/255 SCBs ..... da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Could some kind committer add a line to RELNOTES.TXT that the 19160 adapter is supported (or at least works partially) ? =========================================================================== Get off the keyboard you furry feline ! Marc Veldman, CFBSDN (Certified FreeBSD Newbie) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 1:55:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.32.0]) by hub.freebsd.org (Postfix) with ESMTP id 0F0B537B8E6; Sun, 16 Jul 2000 01:55:08 -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 KAA01886; Sun, 16 Jul 2000 10:55:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: nsayer@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: sysctl interface for apm? In-reply-to: Your message of "Sat, 15 Jul 2000 23:25:04 PDT." <200007160625.XAA92886@freefall.freebsd.org> Date: Sun, 16 Jul 2000 10:55:03 +0200 Message-ID: <1884.963737703@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri tes: >So what does everyone think? Is it suitable to add a read only >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, >-1 = N/A)? Or should we not bother? :-) yes it is suitable. -- 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 Jul 16 4:27:13 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 6064537B8D5 for ; Sun, 16 Jul 2000 04:27:04 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 15295962 invoked from network); 16 Jul 2000 11:27:02 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 16 Jul 2000 11:27:02 -0000 Message-ID: <39719CC5.3554B6C5@cybercable.fr> Date: Sun, 16 Jul 2000 13:30:13 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: config and config -r References: <3970AB23.F76B05CB@cybercable.fr> <200007160541.XAA50804@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <3970AB23.F76B05CB@cybercable.fr> Maxime Henrion writes: > : But after rebooting on this new kernel, I had a page fault before > : any kernel message :/ Is there anything to check in order to know if I > : can use a config instead of a config -r ? If using a config without the > : -r option is dangerous, I think it shouldn't be the default. Is it the > : case ? > > Make depend is required if you ever want to build kernels more than > once. > > Warner Of course, I did a make depend ! I think that if config could be dangerous this way, -r should be its default behaviour. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 4:55:34 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 AE7BB37B9B1 for ; Sun, 16 Jul 2000 04:55:27 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 15267933 invoked from network); 16 Jul 2000 11:55:25 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 16 Jul 2000 11:55:25 -0000 Message-ID: <3971A36C.AAE5C436@cybercable.fr> Date: Sun, 16 Jul 2000 13:58:36 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: config and config -r Content-Type: multipart/mixed; boundary="------------98842E9E9E87ED802C13B9BA" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------98842E9E9E87ED802C13B9BA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------98842E9E9E87ED802C13B9BA Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3971A336.86490A09@cybercable.fr> Date: Sun, 16 Jul 2000 13:57:42 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Larry Rosenman Subject: Re: config and config -r References: <200007161136.e6GBaxN00600@lerami.lerctr.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The problem is that I _DID_ a make depend after the config -r, and this haven't prevent me to get a kernel which panic'ed. Larry Rosenman wrote: > config without the -r reminds you to run a make depend. > > Larry > > Warner Losh wrote: > > > > > In message <3970AB23.F76B05CB@cybercable.fr> Maxime Henrion writes: > > > : But after rebooting on this new kernel, I had a page fault before > > > : any kernel message :/ Is there anything to check in order to know if I > > > : can use a config instead of a config -r ? If using a config without the > > > : -r option is dangerous, I think it shouldn't be the default. Is it the > > > : case ? > > > > > > Make depend is required if you ever want to build kernels more than > > > once. > > > > > > Warner > > > > Of course, I did a make depend ! > > I think that if config could be dangerous this way, -r should be its default > > behaviour. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 --------------98842E9E9E87ED802C13B9BA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 10: 2:48 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 BB68C37B538; Sun, 16 Jul 2000 10:02:44 -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 LAA76140; Sun, 16 Jul 2000 11:02:42 -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 LAA54309; Sun, 16 Jul 2000 11:02:20 -0600 (MDT) Message-Id: <200007161702.LAA54309@harmony.village.org> To: Maxime Henrion Subject: Re: config and config -r Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org In-reply-to: Your message of "Sun, 16 Jul 2000 13:30:13 +0200." <39719CC5.3554B6C5@cybercable.fr> References: <39719CC5.3554B6C5@cybercable.fr> <3970AB23.F76B05CB@cybercable.fr> <200007160541.XAA50804@harmony.village.org> Date: Sun, 16 Jul 2000 11:02:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39719CC5.3554B6C5@cybercable.fr> Maxime Henrion writes: : Of course, I did a make depend ! : I think that if config could be dangerous this way, -r should be its default : behaviour. No. I've done literally 1000's of kernel builds and have never, ever had a problem with config's output that would have been solved by doing a config -r. I did used to use config -r to solve these problems, but found that make depend followed by make or worst case make clean (in the case of .o file corruption) followed by a make will fix these problems. I've not used config -r except maybe once or twice in the last two years. Both times it was because the previous config ran out of disk space and created too many zero length files which a new config didn't clean up exactly right. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 10:13:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 860AB37B719; Sun, 16 Jul 2000 10:13:19 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000716171318.AEW11071.mail.rdc1.il.home.com@math.missouri.edu>; Sun, 16 Jul 2000 10:13:18 -0700 Message-ID: <3971ECE2.6639D65A@math.missouri.edu> Date: Sun, 16 Jul 2000 12:12:02 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Maxime Henrion Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: config and config -r References: <3970AB23.F76B05CB@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a similar problem once when I changed the processor on my motherboard from a 486 to a 586. I recompiled the kernel but I also got those page faults. I asked on these newsgroups and people suggested the processor was broken. Then I tried config -r (well I didn't know the -r option so I did the equivalent - deleting the compile/XXX directory) and then it worked great. I think that config -r has to be done very occasionally. I guess when it has to be done, it is obvious. Maxime Henrion wrote: > > Hello, > > .......... > > As I didn't want to recompile the whole stuff, I used a config and > not a config -r to build a new kernel, after having changed its > configuration. I removed several devices and I thought that won't cause > any problem, as the objects files for these devices won't be linked into > the kernel. > But after rebooting on this new kernel, I had a page fault before > any kernel message :/ Is there anything to check in order to know if I > can use a config instead of a config -r ? If using a config without the > -r option is dangerous, I think it shouldn't be the default. Is it the > case ? > -- Stephen Montgomery-Smith Department of Mathematics, University of Missouri, Columbia, MO 65211 Phone 573-882-4540, fax 573-882-1869 http://www.math.missouri.edu/~stephen stephen@math.missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 10:47:44 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 A7D3637B5F9; Sun, 16 Jul 2000 10:47:40 -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 LAA08121; Sun, 16 Jul 2000 11:45:07 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <3971F574.B492B904@softweyr.com> Date: Sun, 16 Jul 2000 11:48:36 -0600 From: Wes Peters 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: Poul-Henning Kamp Cc: nsayer@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: sysctl interface for apm? References: <1884.963737703@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri > tes: > > >So what does everyone think? Is it suitable to add a read only > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, > >-1 = N/A)? Or should we not bother? :-) > > yes it is suitable. Perhaps machdep.apm.powerstate, leaving room in the namespace for other apm parameters? Charging state and battery life leap immediately to mind. -- "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 Sun Jul 16 11:38:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 0603B37BF88 for ; Sun, 16 Jul 2000 11:38:16 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13DtIk-00049I-00; Sun, 16 Jul 2000 20:38:06 +0200 Received: from p3e9c1125.dip0.t-ipconnect.de ([62.156.17.37] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13DtIj-0006hR-00; Sun, 16 Jul 2000 20:38:05 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id BDAB3AB91; Sun, 16 Jul 2000 20:39:27 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 3E39514A62; Sun, 16 Jul 2000 20:37:55 +0200 (CEST) Date: Sun, 16 Jul 2000 20:37:55 +0200 To: Bill Fumerola Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000716203755.A1361@cichlids.cichlids.com> References: <200007060057.RAA98519@netplex.com.au> <20000705210823.V4034@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000705210823.V4034@jade.chc-chimes.com>; from billf@chimesnet.com on Wed, Jul 05, 2000 at 09:08:23PM -0400 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 Bill Fumerola (billf@chimesnet.com): > > > > PS. No, it's not something stupid like file flags or something. > > > No, it was something even stupider. Completely ignore this. > > Oh, come on now, tell us the details! :-) > It involves this running in another window: > [hawk-billf] $ while `true`; do make clean; sleep 5; make; sleep 5; done BWAHAAHAHAAHAH! coool :-) 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 Sun Jul 16 12:15: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gelemna.org (cc466188-a.pinev1.in.home.com [24.17.49.208]) by hub.freebsd.org (Postfix) with ESMTP id 9D3FD37BF80 for ; Sun, 16 Jul 2000 12:15:03 -0700 (PDT) (envelope-from croyle@gelemna.org) Received: (from croyle@localhost) by gelemna.org (8.9.3/8.9.3) id OAA95510; Sun, 16 Jul 2000 14:14:58 -0500 (EST) (envelope-from croyle@gelemna.org) To: hackers@freebsd.org Subject: Bootstrapping problem From: Don Croyle Date: 16 Jul 2000 14:14:58 -0500 Organization: Minimal at best Message-ID: <86vgy599al.fsf@emerson.gelemna.org> Lines: 13 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 been trying to get the CITRUS project's i18n stuff to build within a buildworld, and I've run into this bootstrapping problem: Locales have to be built with the new mklocale because the source files use new keywords. Because of structure changes and new types the new mklocale requires the new rune.h (and runetype.h and machine/ansi.h, etc.), so just making mklocale a bootstrap, build or crossbuild tool doesn't work. Any suggestions? -- I've always wanted to be a dilettante, but I've never quite been ready to make the commitment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 12:54: 7 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 D67E537B5ED for ; Sun, 16 Jul 2000 12:53:59 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15680830 invoked from network); 16 Jul 2000 19:53:56 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 16 Jul 2000 19:53:56 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id VAA17959; Sun, 16 Jul 2000 21:53:55 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Sun, 16 Jul 2000 21:53:55 +0200 (CEST) To: Poul-Henning Kamp Cc: nsayer@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: sysctl interface for apm? References: <1884.963737703@critter.freebsd.dk> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 16 Jul 2000 21:53:53 +0200 In-Reply-To: Poul-Henning Kamp's message of "Sun, 16 Jul 2000 10:55:03 +0200" Message-ID: Lines: 18 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri > tes: > > >So what does everyone think? Is it suitable to add a read only > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, > >-1 = N/A)? Or should we not bother? :-) > > yes it is suitable. isn't it the job of one of the apm options ? such as apm -l ? 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 Sun Jul 16 14:14:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 939B637B7DE for ; Sun, 16 Jul 2000 14:14:18 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id QAA39276 for hackers@freebsd.org; Sun, 16 Jul 2000 16:31:25 -0500 (CDT) From: Joe Greco Message-Id: <200007162131.QAA39276@aurora.sol.net> Subject: Sun mouse on FreeBSD...? To: hackers@freebsd.org Date: Sun, 16 Jul 2000 16:31:25 -0500 (CDT) 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 I was disappointed to find out that Mouse Systems seems to be out of business. Has anyone hacked up a Sun optical mouse to work with FreeBSD? The electronics shouldn't be difficult, but I was wondering if someone had hacks to make moused understand the Sun mouse protocol. I seem to recall it as being fairly simple... I looked and XFree86 doesn't seem to support the Sun format, but running through moused would be just as good, I think, and easier to hack on. -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 14:49: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id C517D37B845 for ; Sun, 16 Jul 2000 14:48:58 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13DwHR-0004RF-00; Sun, 16 Jul 2000 21:48:57 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA00540; Sun, 16 Jul 2000 23:48:56 +0200 (CEST) (envelope-from wkb) Date: Sun, 16 Jul 2000 23:48:56 +0200 From: Wilko Bulte To: Joe Greco Cc: hackers@freebsd.org Subject: Re: Sun mouse on FreeBSD...? Message-ID: <20000716234856.A526@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <200007162131.QAA39276@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007162131.QAA39276@aurora.sol.net>; from jgreco@ns.sol.net on Sun, Jul 16, 2000 at 04:31:25PM -0500 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 Sun, Jul 16, 2000 at 04:31:25PM -0500, Joe Greco wrote: > I was disappointed to find out that Mouse Systems seems to be out of > business. > > Has anyone hacked up a Sun optical mouse to work with FreeBSD? > > The electronics shouldn't be difficult, but I was wondering if someone had > hacks to make moused understand the Sun mouse protocol. I seem to recall > it as being fairly simple... There are converters who do it the other way around: PS/2 mouse to Sun. So I suppose it cannot be too difficult to translate one into the other (all 'mouse beeps' born equal? ;-). I don't have details on how it is done though. You might want to try http://www.sunhelp.org -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 15:43:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 1077637B6E3; Sun, 16 Jul 2000 15:43:12 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id PAA09104; Sun, 16 Jul 2000 15:43:10 -0700 (PDT) (envelope-from dillon) Date: Sun, 16 Jul 2000 15:43:10 -0700 (PDT) From: Matt Dillon Message-Id: <200007162243.PAA09104@earth.backplane.com> To: Ben Smithurst Cc: hackers@FreeBSD.ORG Subject: Re: PR 18593: *is* VOP_LOOKUP a 'VFS entry point' ? References: <20000716003252.T84045@strontium.scientia.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :PR 18593 says that VOP_LOOKUP is not a 'VFS entry point', so like a fool :I believed it and committed the manpage diff within it. :-( : :All the other VOP* manual pages just say "entry point", but :VOP_LOOKUP(9) said "VFS entry point", the patch changed that to be :consistent with the rest. Can someone confirm one way or the other, and :pass me the pointy hat for the first time if needed? Hmm, pointy hat :within a week, not good. :-( : :thanks. : :--=20 :Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D :FreeBSD Documentation Project / Committers who mess with VOP_LOOKUP (docs or otherwise), and make a mistake, are automatically pardoned due to the fact that VOP_LOOKUP is massively convoluted and messy that it has been known to be mistaken for a turkish artichoke at times. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 17:25:31 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 E471F37B644 for ; Sun, 16 Jul 2000 17:25:12 -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 13DxRz-0009OA-00; Mon, 17 Jul 2000 00:03:55 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13DxRy-000EFV-00; Mon, 17 Jul 2000 00:03:54 +0100 Date: Mon, 17 Jul 2000 00:03:54 +0100 From: Ben Smithurst To: Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: PR 18593: *is* VOP_LOOKUP a 'VFS entry point' ? Message-ID: <20000717000354.E84045@strontium.scientia.demon.co.uk> References: <20000716003252.T84045@strontium.scientia.demon.co.uk> <200007162243.PAA09104@earth.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="i/VKSWANvDZSIhsB" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007162243.PAA09104@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --i/VKSWANvDZSIhsB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Matt Dillon wrote: > Committers who mess with VOP_LOOKUP (docs or otherwise), and make > a mistake, are automatically pardoned due to the fact that VOP_LOOKUP > is massively convoluted and messy that it has been known to be mistak= en=20 > for a turkish artichoke at times. *rofl* I'll take that as a "don't worry, you don't need the pointy hat yet" then. :-) --=20 Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / --i/VKSWANvDZSIhsB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: Cxm7Pb/3mbwzN4shVU5RG65unsWXPwpF iQCVAwUBOXI/WisPVtiZOS99AQEOuAP7BoUAQGIgoOnUHjg4o9HNDJoiY+TQTlIq hTfVWSONCSuZOamw3v0UOclSNL45alKHO2GpNHoKsa4+aNiQxl/L1fCtrJ6j2BHj oSMzo8o56VXdxaJ4E3YP38ifK0xvglXGHultYtr6/B0Tsnwt4QRm7jW2qUqXMS82 lBHDtg/9Qyg= =UHkQ -----END PGP SIGNATURE----- --i/VKSWANvDZSIhsB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 20:22:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-130.adsl.one.net [216.23.15.130]) by hub.freebsd.org (Postfix) with ESMTP id D11FE37BA2B; Sun, 16 Jul 2000 20:22:04 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id WAA06213; Sun, 16 Jul 2000 22:53:43 -0400 (EDT) (envelope-from cokane) Date: Sun, 16 Jul 2000 22:53:42 -0400 From: Coleman Kane To: Adrian Chadd Cc: Boris Popov , Poul-Henning Kamp , Coleman Kane , hackers@FreeBSD.ORG Subject: Re: DEVFS Message-ID: <20000716225342.A6069@cokane.yi.org> References: <4007.963643480@critter.freebsd.dk> <20000715174654.E22865@ywing.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000715174654.E22865@ywing.creative.net.au>; from adrian@FreeBSD.ORG on Sat, Jul 15, 2000 at 11:42:39AM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a great idea. We need a good, well drawn out description of what DEVFS is supposed to accomplish and how we'd like it to work. I will be glad to help out, and perhaps we can get some movement on this. Personally, I'd like to see DEVFS completely replace the current system of nodes in /dev. One nice feature would also be to be able to define aliases of certain devices, such as cdrom, modem, etc... I suppose these could get handled in rc/rc.conf. Also, I really like the idea of being able to create a 'limited' devfs mount for a chroot'd environment. Adrian Chadd had the audacity to say: > > Ok, how about you, phk and julian throw up a list of what devfs should do? > I am forming some ideas on how to solve the namespace and device cloning > issues, we might make some forward work on this finally? :-) > > > Adrian > > -- > Adrian Chadd Build a man a fire, and he's warm for the > rest of the evening. Set a man on fire and > he's warm for the rest of his life. > -- 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 Sun Jul 16 20:45:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id 27D7F37BA11 for ; Sun, 16 Jul 2000 20:45:33 -0700 (PDT) (envelope-from dave.preece@kbgroup.co.nz) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115201>; Mon, 17 Jul 2000 16:04:42 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id <37KXQTD6>; Mon, 17 Jul 2000 15:54:53 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B36173D@internet.kbgroup.co.nz> From: "Dave Preece (KB Group)" To: freebsd-hackers@freebsd.org Subject: gcc 2.95.2, placement new hassles. MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 17 Jul 2000 16:04:36 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Possibly off topic, but here goes. I'm trying to use placement new with gcc 2.95.2 on FBSD4.0-Release and can't get it to go with an error: :11: too many arguments to function `void * operator new(unsigned int)' Disclaimer: I've never tried to use placement new before, but I've RTFM'd fairly heavily around this one and I'm sure both the source and version of gcc are OK. Said offending lines of source are below: void* pShared=shm::GetSharedMemoryPtr(); //FYI a static member function shm* pObject=new(pShared) shm(); Any ideas? Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 21: 4:52 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 CACEE37B994; Sun, 16 Jul 2000 21:04:49 -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 <0FXT0044KQ0AB6@mta4.rcsntx.swbell.net>; Sun, 16 Jul 2000 23:04:59 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id XAA48799; Sun, 16 Jul 2000 23:03:28 -0500 (CDT envelope-from chris) Date: Sun, 16 Jul 2000 23:03:27 -0500 From: Chris Costello Subject: Re: DEVFS In-reply-to: <20000715174654.E22865@ywing.creative.net.au> To: Adrian Chadd Cc: Boris Popov , Poul-Henning Kamp , Coleman Kane , hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000716230327.A48019@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <4007.963643480@critter.freebsd.dk> <20000715174654.E22865@ywing.creative.net.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, July 15, 2000, Adrian Chadd wrote: > Ok, how about you, phk and julian throw up a list of what devfs should do? > I am forming some ideas on how to solve the namespace and device cloning > issues, we might make some forward work on this finally? :-) I'm not Boris, phk or Julian, but I'd like to add that it should probably integrate the fdesc code. Especially since I'm working on (and am soon going to hopefully commit) code to do more relatively major repairs to fdesc[1]. -- |Chris Costello |[1] Removing all references to DTYPE_* macros. `---------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 22:11:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 4141837BA5C for ; Sun, 16 Jul 2000 22:11:15 -0700 (PDT) (envelope-from ngr@9fs.org) Received: from cotswold.demon.co.uk ([194.222.75.186] helo=blue) by anchor-post-34.mail.demon.net with smtp (Exim 2.12 #1) id 13E3BS-0005sX-0Y for freebsd-hackers@freebsd.org; Mon, 17 Jul 2000 06:11:14 +0100 From: "Nigel Roles" To: Subject: rfork(RFMEM) behaviour Date: Mon, 17 Jul 2000 06:10:01 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting strange behaviour with rfork(RFMEM) on a ~2 week old kernel. The following code illustrates it. For all the world, the stack appears to be shareable after the fork. This is clearly wrong, since pid was at some point different in parent and child for them to take the right case. I'm sure this is down to my stupidity. I'd be grateful for any feedback. Also, I understand that rfork(RFMEM) was not supported in 3.3 under SMP. My reading of the kernel source suggests that there is no longer such a limitation. At which version did this change? Thanks, Nigel Roles --------------------------------------- #include #include int child_has_run; int main(int argc, char **argv) { int pid; int value = 3; pid = rfork(RFPROC | RFMEM); switch (pid) { case 0: pid = -1; printf("child has run\n"); fflush(0); child_has_run = 1; exit(0); case -1: printf("rfork failed\n"); exit(1); default: while (!child_has_run) ; printf("parent pid = %d\n", pid); } exit(1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 22:33:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id 3D7D037BB08 for ; Sun, 16 Jul 2000 22:33:30 -0700 (PDT) (envelope-from dave.preece@kbgroup.co.nz) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115201>; Mon, 17 Jul 2000 17:52:45 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id <37KXQT10>; Mon, 17 Jul 2000 17:42:59 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B36173E@internet.kbgroup.co.nz> From: "Dave Preece (KB Group)" To: freebsd-hackers@freebsd.org Subject: RE: gcc 2.95.2, placement new hassles - solved. MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 17 Jul 2000 17:52:42 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Panic over, #include solved that. You learn something new every day. No pun intended. Apologies for offtopicness. 50 lines of "I will look on deja next time". Dave :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 22:55:16 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 4731937BB55 for ; Sun, 16 Jul 2000 22:55:14 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6H5tA513746; Sun, 16 Jul 2000 22:55:10 -0700 (PDT) Date: Sun, 16 Jul 2000 22:55:10 -0700 From: Alfred Perlstein To: Nigel Roles Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: rfork(RFMEM) behaviour Message-ID: <20000716225510.L25571@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from ngr@9fs.org on Mon, Jul 17, 2000 at 06:10:01AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nigel Roles [000716 22:11] wrote: > I am getting strange behaviour with rfork(RFMEM) on a ~2 week old > kernel. The following code illustrates it. For all the world, the > stack appears to be shareable after the fork. This is clearly wrong, > since pid was at some point different in parent and child for them > to take the right case. Dig a bit harder on the mailing lists, I bumped into this a couple of years back and was given example code to get around it. Another alternative is the linuxthreads port available in the ports collection. > I'm sure this is down to my stupidity. I'd be grateful for any > feedback. > > Also, I understand that rfork(RFMEM) was not supported in 3.3 under > SMP. My reading of the kernel source suggests that there is no longer > such a limitation. At which version did this change? I'm not sure, but the limitation wasn't in 4.0. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 16 23:44:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from facmail.cc.gettysburg.edu (facmail.gettysburg.edu [138.234.4.150]) by hub.freebsd.org (Postfix) with ESMTP id 733E537B64C; Sun, 16 Jul 2000 23:44:34 -0700 (PDT) (envelope-from s467338@gettysburg.edu) Received: from jupiter2 (jupiter2.cc.gettysburg.edu [138.234.4.6]) by facmail.cc.gettysburg.edu (8.9.3/8.9.3) with SMTP id CAA22108; Mon, 17 Jul 2000 02:44:07 -0400 (EDT) Date: Mon, 17 Jul 2000 02:44:07 -0400 (EDT) From: Andrew Reiter X-Sender: s467338@jupiter2 To: Coleman Kane Cc: Adrian Chadd , Boris Popov , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: DEVFS In-Reply-To: <20000716225342.A6069@cokane.yi.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 | |One nice feature would also be to be able to define aliases of certain |devices, such as cdrom, modem, etc... I suppose these could get handled |in rc/rc.conf. Also, I really like the idea of being able to create a |'limited' devfs mount for a chroot'd environment. Or via a symlink. --------------------------------------------------------- Andrew Reiter Computer Security Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 1: 0: 6 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 875B037B6AB; Mon, 17 Jul 2000 01:00:02 -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 <0FXU00AKI0WDEO@mta4.rcsntx.swbell.net>; Mon, 17 Jul 2000 03:00:13 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id CAA49471; Mon, 17 Jul 2000 02:58:42 -0500 (CDT envelope-from chris) Date: Mon, 17 Jul 2000 02:58:41 -0500 From: Chris Costello Subject: Re: DEVFS In-reply-to: <20000716225342.A6069@cokane.yi.org> To: Coleman Kane Cc: Adrian Chadd , Boris Popov , Poul-Henning Kamp , hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000717025841.C48019@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <4007.963643480@critter.freebsd.dk> <20000715174654.E22865@ywing.creative.net.au> <20000716225342.A6069@cokane.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, July 16, 2000, Coleman Kane wrote: > This is a great idea. We need a good, well drawn out description of > what DEVFS is supposed to accomplish and how we'd like it to work. I > will be glad to help out, and perhaps we can get some movement on this. > Personally, I'd like to see DEVFS completely replace the current system > of nodes in /dev. That's the point of it, or so I've heard. > One nice feature would also be to be able to define aliases of certain > devices, such as cdrom, modem, etc... I suppose these could get handled > in rc/rc.conf. Probably using symlinks: if [ "X$default_modem_device" != "X" ] then ln -sf /dev/defaultmodem ${default_modem_device} fi if [ "X$default_cdrom_device" != "X" ] then ln -sf /dev/cdrom ${default_cdrom_device} fi ... I would like to point out that if anyone does this, my advance suggestion is that you differentiate between data and audio CDROM. -- |Chris Costello |Swap read error. You lose your mind. `------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 7:22:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id E0C3537B9C8; Mon, 17 Jul 2000 07:22:07 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id KAA28198; Mon, 17 Jul 2000 10:28:00 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Mon, 17 Jul 2000 10:28:00 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: Marc Veldman Cc: "Kenneth D. Merry" , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 160/m support... 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 Marc, Do you know anyone who has tried the support of AIC-7899 chips? That chipset is used on some quad and dual XEON boards. -john v.e. On Sun, 16 Jul 2000, Marc Veldman wrote: > On Tue, 11 Jul 2000, Kenneth D. Merry wrote: > > > > Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be > > > worked on? aka, has adaptec released any info to those FreeBSD team > > > members who work on the SCSI drivers? Is it possible that maybe within the > > > next 4 months 160/m support will exist in FreeBSD 4/5? > > > > It's working, but isn't in the tree yet. > > AFAIK, the aic-7892 works just fine in 4.0-STABLE, and it has worked > fine for a few months now. I'm not sure if the actual 160/m works though. > > This is from my dmesg: > > ahc0: port 0xfc00-0xfcff mem 0xfffbf000-0xfffbffff irq 7 at device 13.0 on pci0 > ahc0: aic7892 Wide Channel A, SCSI Id=15, 16/255 SCBs > ..... > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) > > Could some kind committer add a line to RELNOTES.TXT that the > 19160 adapter is supported (or at least works partially) ? > > =========================================================================== > > Get off the keyboard you furry feline ! > > Marc Veldman, CFBSDN (Certified FreeBSD Newbie) > > > > 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 Jul 17 8:24:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by hub.freebsd.org (Postfix) with ESMTP id 807D437B75F for ; Mon, 17 Jul 2000 08:24:35 -0700 (PDT) (envelope-from sl5b@cs.virginia.edu) Received: from viper.cs.Virginia.EDU (viper.cs.Virginia.EDU [128.143.137.17]) by ares.cs.Virginia.EDU (8.9.2/8.9.2/UVACS-2000040300) with ESMTP id LAA17316 for ; Mon, 17 Jul 2000 11:23:55 -0400 (EDT) Received: from localhost (sl5b@localhost) by viper.cs.Virginia.EDU (8.9.2/8.9.2) with ESMTP id LAA13597 for ; Mon, 17 Jul 2000 11:23:54 -0400 (EDT) X-Authentication-Warning: viper.cs.Virginia.EDU: sl5b owned process doing -bs Date: Mon, 17 Jul 2000 11:23:54 -0400 (EDT) From: Song Li To: hackers@FreeBSD.ORG Subject: Re: different clocks in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could somebody give me suggestion? I believe many people know about this question. But I did not recieve any reply until now. If you think my question is not clear or can be solve by simply reading some man page/source code, please tell me. I am a newbie here. So please do not hesitate to give me some advice. thank you all! -Song > Hey, > > I want to get the accurate user-time and system-time used by a process > whenever I want. My code will run inside the kernel. I try to use the > getrusage from within the kernel, but the function didn't give right data. > Then I try to read the p_uticks in the proc structure. But it seems that > value is not accurate enough because it will be zero when the actual user > time is small(e.g., 20microsecond). I guess it is because the frequency > of the statclock is not high enough( stathz=128 from the kern_clockrate). > So, I have the following questions: > > 1. Can I use getrusage from within the kernel to get the utime and stime? > 2. Can I use the p_uticks and p_sticks as the utime and stime of the > system? What's the meaning of p_uu and p_su? What's the meaning of the > 'tick' in the comments of these variable? Stat tick or sched tick or > anything else? > 3. If I have to change the stathz(currently 128, as reported by > kern_clockrate), where should I change in the source code? > 4. Is it possible to get the accurate utime and stime at any time, but do > not have to change the stathz(I worry about it will not efficient). I plan > to insert some code when interrupt and context switch occured. Is it > difficult? > > > thank you! > > -Song > > > > > 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 Jul 17 8:55:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 5410E37B9CE for ; Mon, 17 Jul 2000 08:52:24 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id IAA93920; Mon, 17 Jul 2000 08:52:19 -0700 (PDT) (envelope-from dillon) Date: Mon, 17 Jul 2000 08:52:19 -0700 (PDT) From: Matt Dillon Message-Id: <200007171552.IAA93920@earth.backplane.com> To: "Nigel Roles" Cc: Subject: Re: rfork(RFMEM) behaviour References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I am getting strange behaviour with rfork(RFMEM) on a ~2 week old :kernel. The following code illustrates it. For all the world, the :stack appears to be shareable after the fork. This is clearly wrong, :since pid was at some point different in parent and child for them :to take the right case. : :I'm sure this is down to my stupidity. I'd be grateful for any :feedback. : :Also, I understand that rfork(RFMEM) was not supported in 3.3 under :SMP. My reading of the kernel source suggests that there is no longer :such a limitation. At which version did this change? : :Thanks, : :Nigel Roles You can't call rfork(RFPROC|RFMEM) from C, because the child process returns on the same stack. RFMEM means, literally, that the entire address space is shared... that, in fact, the *page table* itself is actually 100% shared. Under 3.x SMP this does not work because page table sharing is not possible between cpu's under 3.x. Under 3.x UP there isn't a problem. Under 4.x there is no problem (UP or SMP). -Matt : :--------------------------------------- : : :#include :#include : :int child_has_run; : :int :main(int argc, char **argv) :{ : int pid; : int value = 3; : pid = rfork(RFPROC | RFMEM); : switch (pid) { : case 0: : pid = -1; : printf("child has run\n"); : fflush(0); : child_has_run = 1; : exit(0); : case -1: : printf("rfork failed\n"); : exit(1); : default: : while (!child_has_run) : ; : printf("parent pid = %d\n", pid); : } : exit(1); :} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 9:40:26 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 D5E2D37B9B7; Mon, 17 Jul 2000 09:40:15 -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 13EDvd-0007y8-00; Mon, 17 Jul 2000 18:39:37 +0200 Received: from p3e9c116d.dip0.t-ipconnect.de ([62.156.17.109] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13EDvY-0003PQ-00; Mon, 17 Jul 2000 18:39:33 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id D0345AB91; Mon, 17 Jul 2000 18:40:52 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 8627C14A62; Mon, 17 Jul 2000 18:39:18 +0200 (CEST) Date: Mon, 17 Jul 2000 18:39:18 +0200 To: James Howard Cc: Ben Smithurst , Brian Somers , freebsd-hackers@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000717183918.A26484@cichlids.cichlids.com> References: <20000713132845.C48641@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from howardjp@glue.umd.edu on Thu, Jul 13, 2000 at 04:48:52PM -0400 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 James Howard (howardjp@glue.umd.edu): > fairings? Why does it matter what color the bikeshed is? What does What is this thing with the bikesheds??? It appears on every place I am, on IRC, now here. As a non-native English-speaker, I'd like to know what's up with the poor bikesheds. The poor ones :-( 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 Mon Jul 17 10:53: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (galileo.gw.poli.hu [195.199.8.25]) by hub.freebsd.org (Postfix) with ESMTP id 3799037BB7D for ; Mon, 17 Jul 2000 10:52:52 -0700 (PDT) (envelope-from mauzi@faber.poli.hu) Received: from aquarius.poli.hu (dial-6.poli.hu [195.199.8.22]) by galileo.poli.hu (8.9.3/8.9.3) with ESMTP id TAA00939; Mon, 17 Jul 2000 19:52:42 +0200 (CEST) (envelope-from mauzi@faber.poli.hu) Received: (from mauzi@localhost) by aquarius.poli.hu (8.9.3/8.9.3) id TAA00241; Mon, 17 Jul 2000 19:52:01 +0200 (CEST) (envelope-from mauzi) Date: Mon, 17 Jul 2000 19:52:01 +0200 (CEST) From: Gergely EGERVARY To: hackers@freebsd.org Cc: mauzi@faber.poli.hu Subject: panic: vm_map_entry_create: kernel resources exhausted Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello all, I have to set up a box able to run >5000 processes. I have the hardware for it (i386 architecture, lots of RAM, lots of CPU power) I'm playing with VM parameters, tuning everything possible, but can't get more than 3800 - 4000 processes without getting the box unstable. I need some help - kernel configuration of existing machines, like ftp.cdrom.com, and such. 3.4-STABLE and 4.0-RELEASE Thanks a lot... -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 10:54:13 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 D431F37BA81; Mon, 17 Jul 2000 10:54:07 -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 LAA81147; Mon, 17 Jul 2000 11:54:05 -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 LAA62543; Mon, 17 Jul 2000 11:53:40 -0600 (MDT) Message-Id: <200007171753.LAA62543@harmony.village.org> To: Wes Peters Subject: Re: sysctl interface for apm? Cc: Poul-Henning Kamp , nsayer@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 Jul 2000 11:48:36 MDT." <3971F574.B492B904@softweyr.com> References: <3971F574.B492B904@softweyr.com> <1884.963737703@critter.freebsd.dk> Date: Mon, 17 Jul 2000 11:53:40 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3971F574.B492B904@softweyr.com> Wes Peters writes: : Poul-Henning Kamp wrote: : > : > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri : > tes: : > : > >So what does everyone think? Is it suitable to add a read only : > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, : > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, : > >-1 = N/A)? Or should we not bother? :-) : > : > yes it is suitable. : : Perhaps machdep.apm.powerstate, leaving room in the namespace for other : apm parameters? Charging state and battery life leap immediately to : mind. No. DO NOT CALL IT APM. APM is i386 specific and is doing its best to die off in favor acpi. If you must call it apm, do *NOT* cause being on AC power to override the batery %. These are two different things and should be reported as such. machdep.apm.battery: 0..100 (for battery percentage) machdep.apm.runtime: 0.. (for the reported battery life remaining) machdep.apm.ac: 0 1 (1 means we're running off AC) machdep.apm.charging: 0 1 machdep.apm.batteries: 0.. (number of batteries apm says are there) But why bother? The apm command gives you this already. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 10:56:11 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 7922F37BB6F for ; Mon, 17 Jul 2000 10:56:03 -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 LAA81163; Mon, 17 Jul 2000 11:55:59 -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 LAA62573; Mon, 17 Jul 2000 11:55:34 -0600 (MDT) Message-Id: <200007171755.LAA62573@harmony.village.org> To: "Dave Preece (KB Group)" Subject: Re: gcc 2.95.2, placement new hassles. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 16:04:36 +1200." <67B808B0DD93D211ABEE0000B498356B36173D@internet.kbgroup.co.nz> References: <67B808B0DD93D211ABEE0000B498356B36173D@internet.kbgroup.co.nz> Date: Mon, 17 Jul 2000 11:55:34 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <67B808B0DD93D211ABEE0000B498356B36173D@internet.kbgroup.co.nz> "Dave Preece (KB Group)" writes: : Possibly off topic, but here goes. : : I'm trying to use placement new with gcc 2.95.2 on FBSD4.0-Release and can't : get it to go with an error: : : :11: too many arguments to function `void * operator new(unsigned : int)' : : Disclaimer: I've never tried to use placement new before, but I've RTFM'd : fairly heavily around this one and I'm sure both the source and version of : gcc are OK. Said offending lines of source are below: : : void* pShared=shm::GetSharedMemoryPtr(); //FYI a static member : function : shm* pObject=new(pShared) shm(); : : Any ideas? You are using boehem gcc or some other thing that #defines new in evil and unnatural ways? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 10:57:50 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 2372C37BAFF for ; Mon, 17 Jul 2000 10:57:47 -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 LAA81173; Mon, 17 Jul 2000 11:57:45 -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 LAA62597; Mon, 17 Jul 2000 11:57:20 -0600 (MDT) Message-Id: <200007171757.LAA62597@harmony.village.org> To: "Dave Preece (KB Group)" Subject: Re: gcc 2.95.2, placement new hassles - solved. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 17:52:42 +1200." <67B808B0DD93D211ABEE0000B498356B36173E@internet.kbgroup.co.nz> References: <67B808B0DD93D211ABEE0000B498356B36173E@internet.kbgroup.co.nz> Date: Mon, 17 Jul 2000 11:57:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <67B808B0DD93D211ABEE0000B498356B36173E@internet.kbgroup.co.nz> "Dave Preece (KB Group)" writes: : Panic over, #include solved that. You learn something new every day. : No pun intended. : : Apologies for offtopicness. 50 lines of "I will look on deja next time". You don't need to include new.h, and you shouldn't generally. It likely is masking some other problem. Unless you are redifining new globally.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 11: 1:34 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 11A3937BA7E; Mon, 17 Jul 2000 11:01:13 -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 MAA81199; Mon, 17 Jul 2000 12:01:10 -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 MAA62644; Mon, 17 Jul 2000 12:00:45 -0600 (MDT) Message-Id: <200007171800.MAA62644@harmony.village.org> To: alex@big.endian.de (Alexander Langer) Subject: Re: /etc/security -> /etc/periodic/security ? Cc: James Howard , Ben Smithurst , Brian Somers , freebsd-hackers@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 18:39:18 +0200." <20000717183918.A26484@cichlids.cichlids.com> References: <20000717183918.A26484@cichlids.cichlids.com> <20000713132845.C48641@strontium.scientia.demon.co.uk> Date: Mon, 17 Jul 2000 12:00:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000717183918.A26484@cichlids.cichlids.com> Alexander Langer writes: : What is this thing with the bikesheds??? Summary: phk sent out a long message about how one can do huge things w/o anybody complaining because they don't feel they are quailified to. One cannot do small things without getting bogged down in details because everybody who wants to make their mark does so there because tehy feel qualified to do so. His example was a bike shed. what color to paint it, where to put it, what architectural details to put on it etc. With all these questions, the bikeshed never got built. warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 11:16: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id EE78E37BAB9 for ; Mon, 17 Jul 2000 11:15:42 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id LAA12983; Mon, 17 Jul 2000 11:15:27 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id LAA00811; Mon, 17 Jul 2000 11:15:18 -0700 (PDT) (envelope-from nsayer@sftw.com) Message-ID: <39734D36.5FC7DDA@sftw.com> Date: Mon, 17 Jul 2000 11:15:18 -0700 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: Warner Losh Subject: Re: sysctl interface for apm? References: <3971F574.B492B904@softweyr.com> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> Content-Type: multipart/mixed; boundary="------------FC647A9E3C1149FDF9DA456E" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------FC647A9E3C1149FDF9DA456E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Warner Losh wrote: > In message <3971F574.B492B904@softweyr.com> Wes Peters writes: > : Poul-Henning Kamp wrote: > : > > : > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri > : > tes: > : > > : > >So what does everyone think? Is it suitable to add a read only > : > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, > : > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, > : > >-1 = N/A)? Or should we not bother? :-) > : > > : > yes it is suitable. > : > : Perhaps machdep.apm.powerstate, leaving room in the namespace for other > : apm parameters? Charging state and battery life leap immediately to > : mind. > > No. DO NOT CALL IT APM. APM is i386 specific and is doing its best > to die off in favor acpi. > > If you must call it apm, do *NOT* cause being on AC power to override > the batery %. These are two different things and should be reported > as such. > > machdep.apm.battery: 0..100 (for battery percentage) > machdep.apm.runtime: 0.. (for the reported battery life remaining) > machdep.apm.ac: 0 1 (1 means we're running off AC) > machdep.apm.charging: 0 1 > machdep.apm.batteries: 0.. (number of batteries apm says are there) > > But why bother? The apm command gives you this already. :-) > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message The "why bother" is easy -- one should not have to belong to group operator to determine the current battery state. Too many things already have to be sgid (at least) without making this another reason. I took a middle ground. I have two ints, machdep.apm_battlevel and machdep.apm_powerstate. The power state number is -1 to 5 for unknown, critical, low, medium, high (which four imply battery power), AC or charging (which two imply AC power). These patches are actually against -stable, but I will get this into -current shortly. Suggestions as to how to correct the errors I probably made in the sysctl interface are welcome. :-) --------------FC647A9E3C1149FDF9DA456E Content-Type: text/plain; charset=us-ascii; name="p" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="p" --- apm.c.orig Tue Feb 8 12:39:18 2000 +++ apm.c Mon Jul 17 10:47:13 2000 @@ -107,6 +107,65 @@ SYSCTL_INT(_machdep, OID_AUTO, apm_suspend_delay, CTLFLAG_RW, &apm_suspend_delay, 1, ""); SYSCTL_INT(_machdep, OID_AUTO, apm_standby_delay, CTLFLAG_RW, &apm_standby_delay, 1, ""); +static int apm_get_info(apm_info_t aip); + +/* + * 0-100 battery life remaining as percentage + * -1 unknown + */ +static int +sysctl_apm_battlevel SYSCTL_HANDLER_ARGS +{ + int val; + struct apm_info stat; + + if (apm_get_info(&stat)) + val=-1; + else { + if (stat.ai_batt_life>100) + val=-1; + else + val=stat.ai_batt_life; + } + return sysctl_handle_int(oidp, &val, sizeof(val), req); +} + +/* + * 5 = battery charging (implies AC power) + * 4 = AC power + * 3 = battery high + * 2 = battery low + * 1 = battery critical + * -1 = unknown + */ +static int +sysctl_apm_powerstate SYSCTL_HANDLER_ARGS +{ + int val; + struct apm_info stat; + + if (apm_get_info(&stat)) + val=-1; + else { + if (stat.ai_batt_stat == 0) + val = 5; + else if (stat.ai_acline) + val = 4; + else if (stat.ai_batt_stat > 3) + val=-1; + else + val=stat.ai_batt_stat; + } + return sysctl_handle_int(oidp, &val, sizeof(val), req); +} + +SYSCTL_PROC(_machdep, OID_AUTO, apm_battlevel, CTLTYPE_INT|CTLFLAG_RD, 0, + sizeof(sysctl_apm_battlevel), &sysctl_apm_battlevel, + "I", "Current APM battery level"); +SYSCTL_PROC(_machdep, OID_AUTO, apm_powerstate, CTLTYPE_INT|CTLFLAG_RD, 0, + sizeof(sysctl_apm_powerstate), &sysctl_apm_powerstate, + "I", "Current APM power state"); + /* * return 0 if the function successfull, * return 1 if the function unsuccessfull, --------------FC647A9E3C1149FDF9DA456E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 11:35:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id A023F37BB54; Mon, 17 Jul 2000 11:35:36 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:M6JZueHjb68uP36925Np2rgiA9eHm2ealH7KvcbzWGXJygJv3QNz89ltXim64Bqd@localhost [::1]) (authenticated) by peace.mahoroba.org (8.10.2/3.7W-peace) with ESMTP id e6HIZHh17001; Tue, 18 Jul 2000 03:35:17 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 18 Jul 2000 03:35:14 +0900 (JST) Message-Id: <20000718.033514.59474907.ume@mahoroba.org> To: nsayer@freebsd.org, nsayer@sftw.com Cc: freebsd-hackers@freebsd.org, imp@village.org Subject: Re: sysctl interface for apm? From: Hajimu UMEMOTO In-Reply-To: <39734D36.5FC7DDA@sftw.com> References: <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 17 Jul 2000 11:15:18 -0700 >>>>> Nick Sayer said: nsayer> The "why bother" is easy -- one should not have to belong to group nsayer> operator to determine the current battery state. Too many things nsayer> already have to be sgid (at least) without making this another reason. I love this feature. nsayer> I took a middle ground. I have two ints, machdep.apm_battlevel nsayer> and machdep.apm_powerstate. The power state number is nsayer> -1 to 5 for unknown, critical, low, medium, high (which four imply nsayer> battery power), AC or charging (which two imply AC power). Then, I cannot switch to use sysctl. Actually, GKrellM requires ai_batt_stat, ai_acline, ai_batt_life and ai_batt_time members of struct apm_info. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 12:12: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 2384737BB81; Mon, 17 Jul 2000 12:12: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 NAA81564; Mon, 17 Jul 2000 13:12:28 -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 NAA63248; Mon, 17 Jul 2000 13:12:23 -0600 (MDT) Message-Id: <200007171912.NAA63248@harmony.village.org> To: nsayer@freebsd.org Subject: Re: sysctl interface for apm? Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Mon, 17 Jul 2000 11:15:18 PDT." <39734D36.5FC7DDA@sftw.com> References: <39734D36.5FC7DDA@sftw.com> <3971F574.B492B904@softweyr.com> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> Date: Mon, 17 Jul 2000 13:12:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39734D36.5FC7DDA@sftw.com> Nick Sayer writes: : The "why bother" is easy -- one should not have to belong to group : operator to determine the current battery state. Too many things : already have to be sgid (at least) without making this another reason. You should already be a member of group operator so that you can suspend your machine :-). However, wouldn't it be much simpler and easier to make apm world readable instead? Hmmm, and hack apm.c to open readonly. Hmmm, there are other problems with that since you can do the nasty things... But those should be fixed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 12:14: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 D87B337BB12; Mon, 17 Jul 2000 12:14:30 -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 NAA81576; Mon, 17 Jul 2000 13:14: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 NAA63275; Mon, 17 Jul 2000 13:14:24 -0600 (MDT) Message-Id: <200007171914.NAA63275@harmony.village.org> To: Hajimu UMEMOTO Subject: Re: sysctl interface for apm? Cc: nsayer@freebsd.org, nsayer@sftw.com, freebsd-hackers@freebsd.org In-reply-to: Your message of "Tue, 18 Jul 2000 03:35:14 +0900." <20000718.033514.59474907.ume@mahoroba.org> References: <20000718.033514.59474907.ume@mahoroba.org> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> Date: Mon, 17 Jul 2000 13:14:24 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718.033514.59474907.ume@mahoroba.org> Hajimu UMEMOTO writes: : nsayer> The "why bother" is easy -- one should not have to belong to group : nsayer> operator to determine the current battery state. Too many things : nsayer> already have to be sgid (at least) without making this another reason. : I love this feature. Don't worry, he's not going to change this feature. I use it and will fix it back if someone "breaks" it.. : nsayer> I took a middle ground. I have two ints, machdep.apm_battlevel : nsayer> and machdep.apm_powerstate. The power state number is : nsayer> -1 to 5 for unknown, critical, low, medium, high (which four imply : nsayer> battery power), AC or charging (which two imply AC power). : : Then, I cannot switch to use sysctl. Actually, GKrellM requires : ai_batt_stat, ai_acline, ai_batt_life and ai_batt_time members of : struct apm_info. Yes. The right answer isn't to kludge this through a sysctl, but instead it is to fix apm to that it is safe to make it world read only. Is there a way inside a ioctl to see if you have something open for write access? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 12:40:12 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 ED81537BB6F; Mon, 17 Jul 2000 12:40:04 -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 NAA81720; Mon, 17 Jul 2000 13:40:03 -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 NAA63638; Mon, 17 Jul 2000 13:39:57 -0600 (MDT) Message-Id: <200007171939.NAA63638@harmony.village.org> Subject: Re: sysctl interface for apm? Cc: Hajimu UMEMOTO , nsayer@FreeBSD.ORG, nsayer@sftw.com, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 13:14:24 MDT." <200007171914.NAA63275@harmony.village.org> References: <200007171914.NAA63275@harmony.village.org> <20000718.033514.59474907.ume@mahoroba.org> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> Date: Mon, 17 Jul 2000 13:39:57 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007171914.NAA63275@harmony.village.org> Warner Losh writes: : Yes. The right answer isn't to kludge this through a sysctl, but : instead it is to fix apm to that it is safe to make it world read : only. Is there a way inside a ioctl to see if you have something open : for write access? OK. I found the answer. Here's my patch. Comments? This way we don't have two, incompatible power interfaces. Warner Index: etc/MAKEDEV =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/etc/MAKEDEV,v retrieving revision 1.260 diff -u -r1.260 MAKEDEV --- etc/MAKEDEV 2000/06/26 15:42:48 1.260 +++ etc/MAKEDEV 2000/07/17 19:39:37 @@ -1364,7 +1364,7 @@ apm) mknod apm c 39 0 root:operator - chmod 660 apm + chmod 664 apm ;; apmctl) Index: usr.sbin/apm/apm.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/usr.sbin/apm/apm.c,v retrieving revision 1.22 diff -u -r1.22 apm.c --- usr.sbin/apm/apm.c 2000/01/22 18:11:58 1.22 +++ usr.sbin/apm/apm.c 2000/07/17 19:39:37 @@ -412,7 +412,10 @@ argv += optind; } finish_option: - fd = open(APMDEV, O_RDWR); + if (haltcpu != -1 || enable != -1 || delta || sleep || standby) + fd = open(APMDEV, O_RDWR); + else + fd = open(APMDEV, O_RDONLY); if (fd == -1) err(1, "can't open %s", APMDEV); if (enable != -1) Index: sys/i386/apm/apm.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/apm/apm.c,v retrieving revision 1.114 diff -u -r1.114 apm.c --- sys/i386/apm/apm.c 2000/02/06 14:57:05 1.114 +++ sys/i386/apm/apm.c 2000/07/17 19:39:37 @@ -1169,6 +1169,8 @@ #endif switch (cmd) { case APMIO_SUSPEND: + if ((flag & FWRITE) != 0) + return (EPERM); if (sc->active) apm_suspend(PMST_SUSPEND); else @@ -1176,6 +1178,8 @@ break; case APMIO_STANDBY: + if ((flag & FWRITE) != 0) + return (EPERM); if (sc->active) apm_suspend(PMST_STANDBY); else @@ -1203,23 +1207,35 @@ error = ENXIO; break; case APMIO_ENABLE: + if ((flag & FWRITE) != 0) + return (EPERM); apm_event_enable(); break; case APMIO_DISABLE: + if ((flag & FWRITE) != 0) + return (EPERM); apm_event_disable(); break; case APMIO_HALTCPU: + if ((flag & FWRITE) != 0) + return (EPERM); apm_halt_cpu(); break; case APMIO_NOTHALTCPU: + if ((flag & FWRITE) != 0) + return (EPERM); apm_not_halt_cpu(); break; case APMIO_DISPLAY: + if ((flag & FWRITE) != 0) + return (EPERM); newstate = *(int *)addr; if (apm_display(newstate)) error = ENXIO; break; case APMIO_BIOS: + if ((flag & FWRITE) != 0) + return (EPERM); /* XXX compatibility with the old interface */ args = (struct apm_bios_arg *)addr; sc->bios.r.eax = args->eax; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 12:41:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 93D2737BB12; Mon, 17 Jul 2000 12:41:52 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:yGGjyRBkxt0YYve7e0DybgcB0u+UO/vaIZxZUrhlhSrLFeue8PMMjMa56NayND/J@localhost [::1]) (authenticated) by peace.mahoroba.org (8.10.2/3.7W-peace) with ESMTP id e6HJfOh17473; Tue, 18 Jul 2000 04:41:25 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 18 Jul 2000 04:41:21 +0900 (JST) Message-Id: <20000718.044121.71098397.ume@mahoroba.org> To: imp@village.org Cc: nsayer@freebsd.org, nsayer@sftw.com, freebsd-hackers@freebsd.org Cc: ume@mahoroba.org Subject: Re: sysctl interface for apm? From: Hajimu UMEMOTO In-Reply-To: <200007171914.NAA63275@harmony.village.org> References: <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> <200007171914.NAA63275@harmony.village.org> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 17 Jul 2000 13:14:24 -0600 >>>>> Warner Losh said: imp> In message <20000718.033514.59474907.ume@mahoroba.org> Hajimu UMEMOTO writes: imp> : nsayer> The "why bother" is easy -- one should not have to belong to group imp> : nsayer> operator to determine the current battery state. Too many things imp> : nsayer> already have to be sgid (at least) without making this another reason. imp> : I love this feature. imp> Don't worry, he's not going to change this feature. I use it and will imp> fix it back if someone "breaks" it.. I means sysctl doesn't require extra privilege to obtain required information. Sorry for my ambiguity. imp> : nsayer> I took a middle ground. I have two ints, machdep.apm_battlevel imp> : nsayer> and machdep.apm_powerstate. The power state number is imp> : nsayer> -1 to 5 for unknown, critical, low, medium, high (which four imply imp> : nsayer> battery power), AC or charging (which two imply AC power). imp> : imp> : Then, I cannot switch to use sysctl. Actually, GKrellM requires imp> : ai_batt_stat, ai_acline, ai_batt_life and ai_batt_time members of imp> : struct apm_info. imp> Yes. The right answer isn't to kludge this through a sysctl, but imp> instead it is to fix apm to that it is safe to make it world read imp> only. Is there a way inside a ioctl to see if you have something open imp> for write access? Indeed, I wish to have a method to obtain required information without extra privilege. We need safety way. Currentry, GKrellM opens /dev/apm with O_RDWR. I just tried to open with O_RDONLY and see it is sufficient for APMIO_GETINFO. I'll send the change to the author of GKrellM. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 12:45:42 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 9FFB237BACA; Mon, 17 Jul 2000 12:45: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 NAA81750; Mon, 17 Jul 2000 13:45:34 -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 NAA63703; Mon, 17 Jul 2000 13:45:29 -0600 (MDT) Message-Id: <200007171945.NAA63703@harmony.village.org> To: Hajimu UMEMOTO Subject: Re: sysctl interface for apm? Cc: nsayer@freebsd.org, nsayer@sftw.com, freebsd-hackers@freebsd.org In-reply-to: Your message of "Tue, 18 Jul 2000 04:41:21 +0900." <20000718.044121.71098397.ume@mahoroba.org> References: <20000718.044121.71098397.ume@mahoroba.org> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> <200007171914.NAA63275@harmony.village.org> Date: Mon, 17 Jul 2000 13:45:29 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718.044121.71098397.ume@mahoroba.org> Hajimu UMEMOTO writes: : Indeed, I wish to have a method to obtain required information without : extra privilege. We need safety way. : Currentry, GKrellM opens /dev/apm with O_RDWR. I just tried to open : with O_RDONLY and see it is sufficient for APMIO_GETINFO. I'll send : the change to the author of GKrellM. It is sufficient for APMIO_GETINFO, but it will introduce a security hole as the apm ioctls aren't careful enough about their sanity checking. I've added such sanity checking in my local copy of apm and will test it tonight when I have access to my laptop. The holes are introduced by the chmod 664 /dev/apm, not by doing the open rdonly :-). If you'll send me a pointer to gkrellm, I'll see about putting it up on my laptop and making sure that my stuff works with it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 13: 0:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 519D037B817; Mon, 17 Jul 2000 13:00:36 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:oIDB7bsyBCPAeFYZBodsY2wrSZ/0oE/hpQeDoOYGd1bgaCZba/VZ42A91Y55DvTl@localhost [::1]) (authenticated) by peace.mahoroba.org (8.10.2/3.7W-peace) with ESMTP id e6HK0Dh17533; Tue, 18 Jul 2000 05:00:13 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 18 Jul 2000 05:00:10 +0900 (JST) Message-Id: <20000718.050010.104040362.ume@mahoroba.org> To: imp@village.org Cc: nsayer@freebsd.org, nsayer@sftw.com, freebsd-hackers@freebsd.org Cc: ume@mahoroba.org Subject: Re: sysctl interface for apm? From: Hajimu UMEMOTO In-Reply-To: <200007171945.NAA63703@harmony.village.org> References: <39734D36.5FC7DDA@sftw.com> <200007171914.NAA63275@harmony.village.org> <200007171945.NAA63703@harmony.village.org> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 17 Jul 2000 13:45:29 -0600 >>>>> Warner Losh said: imp> It is sufficient for APMIO_GETINFO, but it will introduce a security imp> hole as the apm ioctls aren't careful enough about their sanity imp> checking. I've added such sanity checking in my local copy of apm and imp> will test it tonight when I have access to my laptop. imp> The holes are introduced by the chmod 664 /dev/apm, not by doing the imp> open rdonly :-). Oh, I see. It's a security hole. imp> If you'll send me a pointer to gkrellm, I'll see about putting it up imp> on my laptop and making sure that my stuff works with it. ports/sysutils/gkrellm/ :-) -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 13: 2: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 BCFCD37B5EB; Mon, 17 Jul 2000 13:02:25 -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 OAA81819; Mon, 17 Jul 2000 14:02:23 -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 OAA63827; Mon, 17 Jul 2000 14:02:18 -0600 (MDT) Message-Id: <200007172002.OAA63827@harmony.village.org> To: Hajimu UMEMOTO Subject: Re: sysctl interface for apm? Cc: nsayer@freebsd.org, nsayer@sftw.com, freebsd-hackers@freebsd.org In-reply-to: Your message of "Tue, 18 Jul 2000 05:00:10 +0900." <20000718.050010.104040362.ume@mahoroba.org> References: <20000718.050010.104040362.ume@mahoroba.org> <39734D36.5FC7DDA@sftw.com> <200007171914.NAA63275@harmony.village.org> <200007171945.NAA63703@harmony.village.org> Date: Mon, 17 Jul 2000 14:02:18 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718.050010.104040362.ume@mahoroba.org> Hajimu UMEMOTO writes: : ports/sysutils/gkrellm/ :-) ah. ok. I feel dumb now... :-) thank you umemoto-san. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 13:21:59 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 E9FAA37BB87 for ; Mon, 17 Jul 2000 13:21:56 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 50789 invoked from network); 17 Jul 2000 20:21:54 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-04-real.cdsnet.net with SMTP; 17 Jul 2000 20:21:54 -0000 Date: Mon, 17 Jul 2000 13:14:56 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: -stable message... Which param 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 newsfeed-inn2# Jul 17 10:14:07 newsfeed-inn2 /kernel: pmap_collect: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC Don't see this one in LINT. Anybody have any wild guesses as to good values? newsfeed-inn2# sysctl -a | grep shm kern.ipc.shmmax: 4194304 kern.ipc.shmmin: 1 kern.ipc.shmmni: 96 kern.ipc.shmseg: 64 kern.ipc.shmall: 1024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 13:52:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 1DA0D37BFBB for ; Mon, 17 Jul 2000 13:52:25 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA24624 for ; Mon, 17 Jul 2000 16:52:21 -0400 (EDT) Date: Mon, 17 Jul 2000 16:50:02 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: KLD, kernel threads, zone allocator Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am writing a KLD that gives me kernel fault each time I run 'ps' command after 'make unload'. The KLD has a system call to create several kernel threads by calling kthread_create(). During unload, I set flags to each threads so that they will call exit1() upon wakeup (sleep on a timeout). Before the last thread calls exit1(), it wakeup the kld unload process so that make 'unload' can finish. Is there anything wrong or better solutions? I also use vm_zone to allocate some data structes within the KLD. When unloading, I can use zfree() to free them except the zone header that I can not free(some_zone, M_ZONE). This is because M_ZONE is defined as *static* in vm_zone.c I wonder if this will cause memory leak after several loading and unloading the KLD. Finally, I want to know how to save the panic screen without hand writing it down. Any info on debugging under db> after fault? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 14:13:25 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 CC66137BDFA; Mon, 17 Jul 2000 14:11:08 -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 XAA04575; Mon, 17 Jul 2000 23:10:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: alex@big.endian.de (Alexander Langer) Cc: James Howard , Ben Smithurst , Brian Somers , freebsd-hackers@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? In-reply-to: Your message of "Mon, 17 Jul 2000 18:39:18 +0200." <20000717183918.A26484@cichlids.cichlids.com> Date: Mon, 17 Jul 2000 23:10:57 +0200 Message-ID: <4573.963868257@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000717183918.A26484@cichlids.cichlids.com>, Alexander Langer writ es: >Thus spake James Howard (howardjp@glue.umd.edu): > >> fairings? Why does it matter what color the bikeshed is? What does > >What is this thing with the bikesheds??? > >It appears on every place I am, on IRC, now here. > >As a non-native English-speaker, I'd like to know what's up with the >poor bikesheds. The poor ones :-( It's a reference to a particular apt description of how committees work and don't work from the excellent book: Parkinson's Law C. Northcote Parkinson Buccaneer Books ISBN 1-56849-015-1 -- 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 Mon Jul 17 14:30:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7C2DD37B529 for ; Mon, 17 Jul 2000 14:30:11 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6HLU3X11511 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Mon, 17 Jul 2000 23:30:05 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6HLTTq37482 for ; Mon, 17 Jul 2000 23:29:29 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id WAA17288; Mon, 17 Jul 2000 22:13:59 +0200 (CEST) (envelope-from ticso) Date: Mon, 17 Jul 2000 22:13:59 +0200 From: Bernd Walter To: Gergely EGERVARY Cc: hackers@FreeBSD.ORG Subject: Re: panic: vm_map_entry_create: kernel resources exhausted Message-ID: <20000717221358.A17266@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mauzi@faber.poli.hu on Mon, Jul 17, 2000 at 07:52:01PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 07:52:01PM +0200, Gergely EGERVARY wrote: > hello all, > > I have to set up a box able to run >5000 processes. I have the hardware > for it (i386 architecture, lots of RAM, lots of CPU power) > > I'm playing with VM parameters, tuning everything possible, but can't get > more than 3800 - 4000 processes without getting the box unstable. > > I need some help - kernel configuration of existing machines, like > ftp.cdrom.com, and such. I don't asume ftp.cdrom.com to do the same that your system is supossed to. Usually tuning is something you need to do depending on your needs. At least you should drop a note containing your current configuration and your current problems so people can make advises. In general I don't expect that you need to change much. Tuning VM parameters will of course bring you instability if you don't know for shure what they do. In real world it's mostly never needed. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 17 17: 3:13 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 D8B9F37B75A for ; Mon, 17 Jul 2000 17:03:08 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 15857679 invoked from network); 18 Jul 2000 00:03:06 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 18 Jul 2000 00:03:06 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id BAA12043; Tue, 18 Jul 2000 01:39:44 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Tue, 18 Jul 2000 01:39:44 +0200 (CEST) To: nsayer@freebsd.org Cc: FreeBSD-hackers@freebsd.org Subject: Re: sysctl interface for apm? References: <1884.963737703@critter.freebsd.dk> <39734DE0.46EF9B8C@sftw.com> <66q47g50.fsf@pc166.gits.fr> <39735688.6268C428@sftw.com> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 18 Jul 2000 01:39:43 +0200 In-Reply-To: Nick Sayer's message of "Mon, 17 Jul 2000 11:55:05 -0700" Message-ID: Lines: 54 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Sayer writes: > Cyrille Lefevre wrote: > > > Nick Sayer writes: > > > > > Cyrille Lefevre wrote: > > > > > > > Poul-Henning Kamp writes: > > > > > > > > > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri > > > > > tes: > > > > > > > > > > >So what does everyone think? Is it suitable to add a read only > > > > > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, > > > > > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, > > > > > >-1 = N/A)? Or should we not bother? :-) > > > > > > > > > > yes it is suitable. > > > > > > > > isn't it the job of one of the apm options ? such as apm -l ? > > > > > > The problem with that is that it requires permission to open /dev/apm, after which > > > one also has permission to suspend the machine or do other mischief. > > > A separate interface allows us to specify a means to look up read-only > > > information without special permissions. Also, sysctl is not only a command > > > line interface, it is available to programs as well, and is a simpler interface > > > then open/ioctl/close. > > > > what about : > > > > echo apm::70: >> /etc/group > > chgrp apm /dev/apm /usr/sbin/apm > > chmod g=640 /dev/apm > > chmod g+s /usr/sbin/apm > > Users or programs in group apm would still have permission to suspend the > machine. Suspending the machine is an operation demanding a far higher level > of machine access than simply checking the state of the batteries, in my > opinion. Once you have an open file descriptor on /dev/apm, you can perform > any ioctl you like on it. This way, privileges on /dev/apm can be closely held, > and mere power meters don't have to be sgid. well. as you said before, you just want a read-only sysctl. if the driver is not secure. it's not my fault. it shouldn't be so complicated to secure it. do you now if the permissions sets using make_dev() in i386/apm/apm.h are used at a upper level ? or if the driver must do the job itself. CC: to the original mailing-list. 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 Jul 17 17:21:46 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 1B12B37BC8B for ; Mon, 17 Jul 2000 17:21:38 -0700 (PDT) (envelope-from clefevre%no-spam@citeweb.net) Received: (qmail 16282422 invoked from network); 18 Jul 2000 00:21:34 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 18 Jul 2000 00:21:34 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id CAA15366; Tue, 18 Jul 2000 02:21:34 +0200 (CEST) (envelope-from clefevre%no-spam@citeweb.net) Posted-Date: Tue, 18 Jul 2000 02:21:34 +0200 (CEST) To: nsayer@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG, Warner Losh Subject: Re: sysctl interface for apm? References: <3971F574.B492B904@softweyr.com> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 18 Jul 2000 02:21:32 +0200 In-Reply-To: Nick Sayer's message of "Mon, 17 Jul 2000 11:15:18 -0700" Message-ID: <66q45lv7.fsf@pc166.gits.fr> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Sayer writes: > Warner Losh wrote: > > > In message <3971F574.B492B904@softweyr.com> Wes Peters writes: > > : Poul-Henning Kamp wrote: > > : > > > : > In message <200007160625.XAA92886@freefall.freebsd.org>, nsayer@FreeBSD.ORG wri > > : > tes: > > : > > > : > >So what does everyone think? Is it suitable to add a read only > > : > >sysctl 'machdep.apm_powerstate' that reports either AC, nn%, > > : > >or N/A ? Or should the format be numeric (999 = AC, <=100 = battery %, > > : > >-1 = N/A)? Or should we not bother? :-) > > : > > > : > yes it is suitable. > > : > > : Perhaps machdep.apm.powerstate, leaving room in the namespace for other > > : apm parameters? Charging state and battery life leap immediately to > > : mind. > > > > No. DO NOT CALL IT APM. APM is i386 specific and is doing its best > > to die off in favor acpi. > > > > If you must call it apm, do *NOT* cause being on AC power to override > > the batery %. These are two different things and should be reported > > as such. > > > > machdep.apm.battery: 0..100 (for battery percentage) > > machdep.apm.runtime: 0.. (for the reported battery life remaining) > > machdep.apm.ac: 0 1 (1 means we're running off AC) > > machdep.apm.charging: 0 1 > > machdep.apm.batteries: 0.. (number of batteries apm says are there) > > > > But why bother? The apm command gives you this already. :-) > > The "why bother" is easy -- one should not have to belong to group > operator to determine the current battery state. Too many things > already have to be sgid (at least) without making this another reason. > > I took a middle ground. I have two ints, machdep.apm_battlevel > and machdep.apm_powerstate. The power state number is > -1 to 5 for unknown, critical, low, medium, high (which four imply > battery power), AC or charging (which two imply AC power). > > These patches are actually against -stable, but I will get this > into -current shortly. > > Suggestions as to how to correct the errors I probably made in > the sysctl interface are welcome. :-) > > [snip] > + > +SYSCTL_PROC(_machdep, OID_AUTO, apm_battlevel, CTLTYPE_INT|CTLFLAG_RD, 0, > + sizeof(sysctl_apm_battlevel), &sysctl_apm_battlevel, > + "I", "Current APM battery level"); > +SYSCTL_PROC(_machdep, OID_AUTO, apm_powerstate, CTLTYPE_INT|CTLFLAG_RD, 0, > + sizeof(sysctl_apm_powerstate), &sysctl_apm_powerstate, > + "I", "Current APM power state"); > + > /* > * return 0 if the function successfull, > * return 1 if the function unsuccessfull, > could you implement the same thing using the sublevel machdep.apm.bla... ? 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 Jul 17 22:14: 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 96E1037B9A6; Mon, 17 Jul 2000 22:13:53 -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 XAA83895; Mon, 17 Jul 2000 23:13:48 -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 XAA68297; Mon, 17 Jul 2000 23:13:41 -0600 (MDT) Message-Id: <200007180513.XAA68297@harmony.village.org> To: clefevre@citeweb.net Subject: Re: sysctl interface for apm? Cc: nsayer@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG In-reply-to: Your message of "18 Jul 2000 01:39:43 +0200." References: <1884.963737703@critter.freebsd.dk> <39734DE0.46EF9B8C@sftw.com> <66q47g50.fsf@pc166.gits.fr> <39735688.6268C428@sftw.com> Date: Mon, 17 Jul 2000 23:13:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Cyrille Lefevre writes: : well. as you said before, you just want a read-only sysctl. if the driver is not : secure. it's not my fault. it shouldn't be so complicated to secure it. : do you now if the permissions sets using make_dev() in i386/apm/apm.h are : used at a upper level ? or if the driver must do the job itself. Driver is trivial to secure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 18 0:46:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 0588637BC39 for ; Tue, 18 Jul 2000 00:46:17 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id AAA16972; Tue, 18 Jul 2000 00:48:10 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Tue, 18 Jul 2000 00:48:09 -0700 (PDT) From: Kelly Yancey To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: -stable message... Which param In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Jaye Mathisen wrote: > newsfeed-inn2# Jul 17 10:14:07 newsfeed-inn2 > /kernel: pmap_collect: collecting pv entries -- suggest increasing > PMAP_SHPGPERPROC > > Don't see this one in LINT. > > Anybody have any wild guesses as to good values? > > newsfeed-inn2# sysctl -a | grep shm > kern.ipc.shmmax: 4194304 > kern.ipc.shmmin: 1 > kern.ipc.shmmni: 96 > kern.ipc.shmseg: 64 > kern.ipc.shmall: 1024 > There was quite some discussion about this about a month ago, you should be able to find in the archives by searching for SHMMAXPGS. The relavent LINT values are: options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=33 options SHMSEG=9 Generally, it is safe to increase SHMMAXPGS. Without knowing the specifics of your application, I would suggest increasing it to 2048 (i.e. double the default) and see if that does the trick. If not, keep increasing it by 1024 until it does. 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 Tue Jul 18 8:41:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [206.79.44.166]) by hub.freebsd.org (Postfix) with ESMTP id 706DC37BEA4; Tue, 18 Jul 2000 08:41:14 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id IAA09136; Tue, 18 Jul 2000 08:37:36 GMT (envelope-from nik) Date: Tue, 18 Jul 2000 08:37:36 +0000 From: Nik Clayton To: Warner Losh Cc: nsayer@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: sysctl interface for apm? Message-ID: <20000718083736.A9093@kilt.nothing-going-on.org> References: <39734D36.5FC7DDA@sftw.com> <3971F574.B492B904@softweyr.com> <1884.963737703@critter.freebsd.dk> <200007171753.LAA62543@harmony.village.org> <39734D36.5FC7DDA@sftw.com> <200007171912.NAA63248@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: <200007171912.NAA63248@harmony.village.org>; from imp@village.org on Mon, Jul 17, 2000 at 01:12:23PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 01:12:23PM -0600, Warner Losh wrote: > In message <39734D36.5FC7DDA@sftw.com> Nick Sayer writes: > : The "why bother" is easy -- one should not have to belong to group > : operator to determine the current battery state. Too many things > : already have to be sgid (at least) without making this another reason. > > You should already be a member of group operator so that you can > suspend your machine :-). Not necessarily. Fn+Esc (or Fn+F12) works quite nicely on this VAIO. > However, wouldn't it be much simpler and easier to make apm world > readable instead? Hmmm, and hack apm.c to open readonly. Hmmm, there > are other problems with that since you can do the nasty things... But > those should be fixed. I'd prefer getting the permissions right as well. Querying the current battery state shouldn't require special privs. 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 Tue Jul 18 9:47:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.147.249.166]) by hub.freebsd.org (Postfix) with ESMTP id C591537B633; Tue, 18 Jul 2000 09:47:04 -0700 (PDT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id MAA02389; Tue, 18 Jul 2000 12:47:03 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200007181647.MAA02389@spoon.beta.com> To: freebsd-qa@freebsd.org Cc: hackers@freebsd.org Subject: TOP output with 7/17 -STABLE snapshot Date: Tue, 18 Jul 2000 12:47:03 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an FYI. I don't know if this is a bug or not, so I'll let others decide.... On a 7/17 -STABLE snapshot, I'm running an Athlon 700 w/640MB of RAM (1x512MB + 1x128MB). I've got X going, and I'm running cvsup, etc. I'm down to 165MB of Free memory (as reported by top). The strange thing is the "Cache" value. Its sitting at 68K. My other (3.4) systems all report values in the MBs. The system has some fast SCSI disks, but I'd still expect the cache to grow, as the disks are being 100% utilized. Comments? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 18 10:10:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown3-3-80.adsl.one.net [216.23.29.80]) by hub.freebsd.org (Postfix) with ESMTP id 3BB4837B6B2; Tue, 18 Jul 2000 10:10:51 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id NAA07763; Tue, 18 Jul 2000 13:17:52 -0400 (EDT) (envelope-from cokane) Date: Tue, 18 Jul 2000 13:17:52 -0400 From: Coleman Kane To: Chris Costello Cc: Adrian Chadd , Boris Popov , Poul-Henning Kamp , Coleman Kane , hackers@FreeBSD.ORG Subject: Re: DEVFS Message-ID: <20000718131752.A7742@cokane.yi.org> References: <4007.963643480@critter.freebsd.dk> <20000715174654.E22865@ywing.creative.net.au> <20000716230327.A48019@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000716230327.A48019@holly.calldei.com>; from chris@calldei.com on Mon, Jul 17, 2000 at 12:05:33AM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to make sure we all know what's going on: Is someone currently tracking this thread and merging ideas into a write-up of what features DEVFS should have, as well as its implementation? I nice text would be fine to stick in the devfs tree to outline this, it would help facilitate work on this project. Chris Costello had the audacity to say: > > On Saturday, July 15, 2000, Adrian Chadd wrote: > > Ok, how about you, phk and julian throw up a list of what devfs should do? > > I am forming some ideas on how to solve the namespace and device cloning > > issues, we might make some forward work on this finally? :-) > > I'm not Boris, phk or Julian, but I'd like to add that it > should probably integrate the fdesc code. Especially since I'm > working on (and am soon going to hopefully commit) code to do > more relatively major repairs to fdesc[1]. > > -- > |Chris Costello > |[1] Removing all references to DTYPE_* macros. > `---------------------------------------------- > > > 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 Tue Jul 18 10:14:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f328.law7.hotmail.com [216.33.236.206]) by hub.freebsd.org (Postfix) with SMTP id 7EB4637B6E5 for ; Tue, 18 Jul 2000 10:14:38 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: (qmail 22496 invoked by uid 0); 18 Jul 2000 17:14:38 -0000 Message-ID: <20000718171438.22495.qmail@hotmail.com> Received: from 209.249.186.215 by www.hotmail.com with HTTP; Tue, 18 Jul 2000 10:14:38 PDT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: freebsd-hackers@FreeBSD.ORG Subject: rtld problem Date: Tue, 18 Jul 2000 13:14:38 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hackers, i'm having trouble with the runtime linker. it seems like a bug, but perhaps there's something mystical i'm supposed to do to make this work. the short version of what i'm seeing is this: my app references symbols in a shared lib. the shared lib uses symbols in another shared lib. if i like my app only against lib #1, it crashes while initializing static objects in lib #2. if i link my app against both lib #1 and lib #2, it runs fine. i believe the problem is that the runtime linker/loader is initializing objects out of order. okay, the longer version: i create shared lib A kinda like this: g++ obj1.o obj2.o ... -pthread -shared -Wl,-h,libA.so.5 -o libA.so.5 ln -s libA.so.5 libA.so then i create shared lib B sorta like this: g++ obj3.o obj4.o ... -pthread -shared -lA -Wl,-h,libB.so.5 -o libB.so.5 ln -s libB.so.5 libB.so then if i make the app like so: g++ app.o -lB -pthread -o app it cores at startup. if i make it like this: g++ app.o -lA -lB -pthread -o app it runs fine. this is not good. is there something i'm missing? if not, how do i go about building a debug version of the runtime linker so i can debug this bastage? thanks. btw: this works fine under linux (gcc 2.95.2, ld 2.9.5, glibc 2.1.3) and under solaris (sun's CC, ld, libc, etc), so i don't think i'm expecting too much. -- -greg ________________________________________________________________________ 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 Tue Jul 18 10:18:20 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 5C3E237B773; Tue, 18 Jul 2000 10:18: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 TAA10890; Tue, 18 Jul 2000 19:17:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Coleman Kane Cc: Chris Costello , Adrian Chadd , Boris Popov , hackers@FreeBSD.ORG Subject: Re: DEVFS In-reply-to: Your message of "Tue, 18 Jul 2000 13:17:52 EDT." <20000718131752.A7742@cokane.yi.org> Date: Tue, 18 Jul 2000 19:17:51 +0200 Message-ID: <10888.963940671@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000718131752.A7742@cokane.yi.org>, Coleman Kane writes: >Just to make sure we all know what's going on: > >Is someone currently tracking this thread and merging ideas into >a write-up of what features DEVFS should have, as well as its >implementation? I consider myself the coordinator for DEVFS, and I track the discussion and ideas that are floated. -- 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 Tue Jul 18 10:22: 4 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 140C937B79F for ; Tue, 18 Jul 2000 10:22:01 -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 KAA28355; Tue, 18 Jul 2000 10:22:00 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA12267; Tue, 18 Jul 2000 10:21:59 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 18 Jul 2000 10:21:59 -0700 (PDT) Message-Id: <200007181721.KAA12267@vashon.polstra.com> To: johnnyteardrop@hotmail.com Subject: Re: rtld problem In-Reply-To: <20000718171438.22495.qmail@hotmail.com> References: <20000718171438.22495.qmail@hotmail.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000718171438.22495.qmail@hotmail.com>, Greg Thompson wrote: > i'm having trouble with the runtime linker. What version of FreeBSD? > my app references symbols in a shared lib. the shared lib uses > symbols in another shared lib. if i like my app only against lib #1, > it crashes while initializing static objects in lib #2. if i link > my app against both lib #1 and lib #2, it runs fine. i believe the > problem is that the runtime linker/loader is initializing objects > out of order. Is your test case something that you can package up and send to me in a form that makes it easy for me to reproduce the problem? 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 Tue Jul 18 11:10:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f145.law7.hotmail.com [216.33.237.145]) by hub.freebsd.org (Postfix) with SMTP id 72A0937B6BA for ; Tue, 18 Jul 2000 11:10:46 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: (qmail 90152 invoked by uid 0); 18 Jul 2000 18:10:45 -0000 Message-ID: <20000718181045.90151.qmail@hotmail.com> Received: from 209.249.186.215 by www.hotmail.com with HTTP; Tue, 18 Jul 2000 11:10:45 PDT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: hackers@freebsd.org Subject: Re: rtld problem Date: Tue, 18 Jul 2000 14:10:45 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: John Polstra > >In article <20000718171438.22495.qmail@hotmail.com>, Greg Thompson > wrote: > > > i'm having trouble with the runtime linker. > >What version of FreeBSD? mortal sin #1. oops. 4.0-20000714-STABLE. >Is your test case something that you can package up and send to me in >a form that makes it easy for me to reproduce the problem? currently, no, but i'll try to whip up a small test case for you. thanks, john. -- -greg ________________________________________________________________________ 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 Tue Jul 18 15:20:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id B1E1637B6CF for ; Tue, 18 Jul 2000 15:20:44 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id PAA78456 for hackers@FreeBSD.org; Tue, 18 Jul 2000 15:20:44 -0700 (PDT) (envelope-from ulf) Date: Tue, 18 Jul 2000 15:20:44 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.org Subject: Maybe OT, maybe not Message-ID: <20000718152043.A18798@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I got a problem I need to get "solved" as fast as possible. I have here a firewall box (FreeBSD based, yeah!) and need to test this in conjunction with web crawling. Our current FW1 based Sun firewalls die very fast. I need to emulate about 9,000 or more concurrent open tcp sessions. Each session should be random sized from 500 to maybe 20,000 bytes data transferred. In addition to these I need x amount of initiated tcp sessions which never get answered. FW1 with its tcp connection table will create an entry for these "failed" sessions and hold it up to its time out. Our crawlers do not. So I am basicly looking for a load generator and a "server". Anyone got something laying around like that ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 18 16:31:55 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 E724537B843; Tue, 18 Jul 2000 16:31:51 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6INVqK07166; Tue, 18 Jul 2000 16:31:52 -0700 (PDT) Date: Tue, 18 Jul 2000 16:31:52 -0700 From: Alfred Perlstein To: hackers@freebsd.org Subject: new kernel MALLOC flag. Message-ID: <20000718163151.K13979@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if we could pass an additional flag to malloc M_NOPHYS that would mean the kernel is free to move the physical location of the memory. It would signify things that the memory: 1) won't be used for backing DMA. 2) won't be entered into another kernel memory map. This will allow us to have contigmalloc force-shuffle memory around by copying it and doing vm tricks to remap it allowing us to grab contig memory. We could help facilitate having large regions of M_NOPHYS memory by dividing the memory pool in half, M_NOPHYS allocations from one end and !M_NOPHYS from the other end when possible. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 18 20:39:15 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 4B33137B5EA for ; Tue, 18 Jul 2000 20:39:13 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id VAA50590; Tue, 18 Jul 2000 21:39:10 -0600 (MDT) Date: Tue, 18 Jul 2000 21:39:10 -0600 (MDT) From: Nick Rogness To: Ulf Zimmermann Cc: hackers@FreeBSD.org Subject: Re: Maybe OT, maybe not In-Reply-To: <20000718152043.A18798@PacHell.TelcoSucks.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 Tue, 18 Jul 2000, Ulf Zimmermann wrote: > So I am basicly looking for a load generator and a "server". Anyone got > something laying around like that ? Look in the ports under benchmarks. DBS may be what you are looking for, maybe not. At least it is a place to start. See also: http://www.freebsd.org/ports/benchmarks.html for more info. 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 Tue Jul 18 20:43:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown3-3-80.adsl.one.net [216.23.29.80]) by hub.freebsd.org (Postfix) with ESMTP id F222437B545; Tue, 18 Jul 2000 20:43:06 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id XAA09937; Tue, 18 Jul 2000 23:47:54 -0400 (EDT) (envelope-from cokane) Date: Tue, 18 Jul 2000 23:47:54 -0400 From: Coleman Kane To: Poul-Henning Kamp Cc: Coleman Kane , Chris Costello , Adrian Chadd , Boris Popov , hackers@FreeBSD.ORG Subject: Re: DEVFS Message-ID: <20000718234754.A9916@cokane.yi.org> References: <20000718131752.A7742@cokane.yi.org> <10888.963940671@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <10888.963940671@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Jul 18, 2000 at 01:18:03PM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excellent. I saw a large amount of traffic floating around, wanted to see if there was a major coordinator keeping track. Saw a few of your posts earlier, anyway I noted to jkh that I had an interest in helping work on this. It seemed to be on hold for a little while, but listed as unfinished. I'd like to help set a goal of getting it to a finished product before 4.2 and hopefully, getting inclusion in 4.3-R... Poul-Henning Kamp had the audacity to say: > > I consider myself the coordinator for DEVFS, and I track the > discussion and ideas that are floated. > > -- > 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. > -- 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 Tue Jul 18 21: 3:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 57B5F37B99B for ; Tue, 18 Jul 2000 21:03:31 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id VAA80288 for hackers@FreeBSD.org; Tue, 18 Jul 2000 21:03:29 -0700 (PDT) (envelope-from ulf) Date: Tue, 18 Jul 2000 21:03:28 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.org Subject: problem on 4.1-RC (4.0-stable) Message-ID: <20000718210328.A79232@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I updated via cvsup (cvsup from tuesday afternoon PDT), I went into single user mode, did make world, make buildkernel KERNEL=FOURTYTWO and make installkernel KERNEL=FOURTYTWO. Everything but one thing I can find seems to work fine, but ps doesn't. Trying to use ps: fourtytwo ulf home/ulf > ps ps: bad namelist Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. Anyone got an suggestion what to check or what maybe broken ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 18 21: 9:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id D828137BB4C for ; Tue, 18 Jul 2000 21:09:53 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id VAA01082; Tue, 18 Jul 2000 21:09:37 -0700 Message-ID: <39752A0B.9CE57DF3@urx.com> Date: Tue, 18 Jul 2000 21:09:47 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ulf@Alameda.net Cc: hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) References: <20000718210328.A79232@PacHell.TelcoSucks.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > > Hello, > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > I can find seems to work fine, but ps doesn't. Did you boot /FOURTYTWO or do the rename sequence to make it kernel? It sounds like your kernel and world might be a little out of sequence. Kent > > Trying to use ps: > > fourtytwo ulf home/ulf > ps > ps: bad namelist > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > Anyone got an suggestion what to check or what maybe broken ? > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 3:58:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from germes.levi.spb.ru (p1.levi.spb.ru [212.119.175.65]) by hub.freebsd.org (Postfix) with SMTP id 37A5D37B9AC for ; Wed, 19 Jul 2000 03:58:41 -0700 (PDT) (envelope-from dms@levi.spb.ru) Received: from levi.spb.ru (IDENT:dms@pike.levi.spb.ru [192.168.55.43]) by germes.levi.spb.ru (8.9.3/8.9.3) with ESMTP id OAA05435 for ; Wed, 19 Jul 2000 14:58:24 +0400 Message-ID: <397589D7.FF50E1D7@levi.spb.ru> Date: Wed, 19 Jul 2000 14:58:31 +0400 From: Dmitry samersoff Reply-To: dms@wplus.net Organization: Levi Soft X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: UFS inodes readig ... Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please Help! Does anyone have simple code reading ufs partion inode-by-inode with inode description too? (My designer remove some very significant files and it's my last chance ;-(( ) -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 4: 6:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E822F37BE3C for ; Wed, 19 Jul 2000 04:06:42 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 93F4A9B1C; Wed, 19 Jul 2000 07:06:41 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 84BCEBA11; Wed, 19 Jul 2000 07:06:41 -0400 (EDT) Date: Wed, 19 Jul 2000 07:06:41 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: dms@wplus.net Cc: freebsd-hackers@freebsd.org Subject: Re: UFS inodes readig ... In-Reply-To: <397589D7.FF50E1D7@levi.spb.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jul 2000, Dmitry samersoff wrote: > Please Help! > > Does anyone have simple code > reading ufs partion inode-by-inode with inode description too? > > (My designer remove some very significant files and > it's my last chance ;-(( ) > fsdb(8) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 4: 8: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 5A81A37BE8B for ; Wed, 19 Jul 2000 04:08:06 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 49C0DA833; Wed, 19 Jul 2000 21:08:20 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 461E55441; Wed, 19 Jul 2000 21:08:20 +1000 (EST) Date: Wed, 19 Jul 2000 21:08:20 +1000 (EST) From: andrew@ugh.net.au To: dms@wplus.net Cc: freebsd-hackers@freebsd.org Subject: Re: UFS inodes readig ... In-Reply-To: <397589D7.FF50E1D7@levi.spb.ru> Message-ID: X-WonK: *wibble* 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, 19 Jul 2000, Dmitry samersoff wrote: > Does anyone have simple code > reading ufs partion inode-by-inode with inode description too? fsdb(8)? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 4:29:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from germes.levi.spb.ru (p1.levi.spb.ru [212.119.175.65]) by hub.freebsd.org (Postfix) with SMTP id 6F41037BA49 for ; Wed, 19 Jul 2000 04:29:34 -0700 (PDT) (envelope-from dms@levi.spb.ru) Received: from levi.spb.ru (IDENT:dms@pike.levi.spb.ru [192.168.55.43]) by germes.levi.spb.ru (8.9.3/8.9.3) with ESMTP id PAA05725; Wed, 19 Jul 2000 15:28:57 +0400 Message-ID: <397590FF.E7550C2C@levi.spb.ru> Date: Wed, 19 Jul 2000 15:29:03 +0400 From: Dmitry samersoff Reply-To: dms@wplus.net Organization: Levi Soft X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: andrew@ugh.net.au Cc: dms@wplus.net, freebsd-hackers@freebsd.org Subject: Re: UFS inodes readig ... References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au wrote: > > On Wed, 19 Jul 2000, Dmitry samersoff wrote: > > > Does anyone have simple code > > reading ufs partion inode-by-inode with inode description too? > > fsdb(8)? It's very usable tool, but I'm looking for C/C++ code doing: while( read_next_inode ) { if (inode_is_deleted && inode_data_contains_some_text) { write(outfile, inode_data, inode_size); } } And I would be very thankfull if someone can send me source or pointer to good start for function "read_next_inode" Thank you. -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 4:39:47 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 4664737BB0B for ; Wed, 19 Jul 2000 04:39:44 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 Jul 2000 12:39:43 +0100 (BST) Date: Wed, 19 Jul 2000 12:39:42 +0100 From: David Malone To: dms@wplus.net Cc: andrew@ugh.net.au, freebsd-hackers@freebsd.org Subject: Re: UFS inodes readig ... Message-ID: <20000719123942.A46036@walton.maths.tcd.ie> References: <397590FF.E7550C2C@levi.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <397590FF.E7550C2C@levi.spb.ru>; from dms@levi.spb.ru on Wed, Jul 19, 2000 at 03:29:03PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 03:29:03PM +0400, Dmitry samersoff wrote: > It's very usable tool, but I'm looking for C/C++ code > doing: > > while( read_next_inode ) > { > if (inode_is_deleted && inode_data_contains_some_text) > { write(outfile, inode_data, inode_size); > } > } > > And I would be very thankfull > if someone can send me source or pointer to good start for > function "read_next_inode" You might be able to modify /sbin/dump to do this. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 5: 1:11 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 41BB637BA68 for ; Wed, 19 Jul 2000 05:00:57 -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.15 #1) id 13EsWu-00005b-00 for hackers@FreeBSD.org; Wed, 19 Jul 2000 14:00:48 +0200 From: Sheldon Hearn To: hackers@FreeBSD.org Subject: crash during sync(2) still damages filesystems Date: Wed, 19 Jul 2000 14:00:48 +0200 Message-ID: <346.964008048@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I recently added a syncer(4) manual page to 5.0-CURRENT, to replace the obsolete update(4) page. I want to know whether the BUGS section, which I copied from update(4), is still true: BUGS It is possible on some systems that a sync(2) occurring simultaneously with a crash may cause file system damage. See fsck(8). It seems reasonable that this would still be true, but I wouldn't have a clue either way. Anyone care to confirm or deny? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 7:45:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from atlas.pathcom.com (smtp.tor.axxent.ca [209.250.128.26]) by hub.freebsd.org (Postfix) with ESMTP id 6A9A337C0A1 for ; Wed, 19 Jul 2000 07:45:24 -0700 (PDT) (envelope-from lwh@pathcom.com) Received: from dial-0877.tor.axxent.ca (dial-0877.tor.axxent.ca [216.249.3.115]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id KAA24367 for ; Wed, 19 Jul 2000 10:45:20 -0400 (EDT) Date: Wed, 19 Jul 2000 10:45:20 -0400 (EDT) From: Luke Hollins Reply-To: lwh@pathcom.com To: hackers@freebsd.org Subject: module proposal Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering , if the only thing that uses USER_LDT is wine, would it be possible for there to be a module for it ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 10: 0:42 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 5D53C37B6C2 for ; Wed, 19 Jul 2000 10:00:38 -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 LAA92862; Wed, 19 Jul 2000 11:00:37 -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 LAA82438; Wed, 19 Jul 2000 11:00:26 -0600 (MDT) Message-Id: <200007191700.LAA82438@harmony.village.org> To: dms@wplus.net Subject: Re: UFS inodes readig ... Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jul 2000 14:58:31 +0400." <397589D7.FF50E1D7@levi.spb.ru> References: <397589D7.FF50E1D7@levi.spb.ru> Date: Wed, 19 Jul 2000 11:00:25 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <397589D7.FF50E1D7@levi.spb.ru> Dmitry samersoff writes: : Does anyone have simple code : reading ufs partion inode-by-inode with inode description too? : : (My designer remove some very significant files and : it's my last chance ;-(( ) You should look for icat in the archives. warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 12:57:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id B771037B6B1 for ; Wed, 19 Jul 2000 12:57:54 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id MAA85022; Wed, 19 Jul 2000 12:57:51 -0700 (PDT) (envelope-from ulf) Date: Wed, 19 Jul 2000 12:57:51 -0700 From: Ulf Zimmermann To: Kent Stewart Cc: ulf@Alameda.net, hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000719125751.B79232@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39752A0B.9CE57DF3@urx.com>; from kstewart@urx.com on Tue, Jul 18, 2000 at 09:09:47PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > Ulf Zimmermann wrote: > > > > Hello, > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > I can find seems to work fine, but ps doesn't. > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > It sounds like your kernel and world might be a little out of > sequence. I did the move. I rebuild the kernel again, same file size got created. Yes, I agree it sounds like stuff is out of sync, but I did the complete world after I cvsup and made the kernel. > > Kent > > > > > Trying to use ps: > > > > fourtytwo ulf home/ulf > ps > > ps: bad namelist > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > Bomber dropping fire retardant in front of Hanford Wild fire. > http://kstewart.urx.com/kstewart/bomber.jpg -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 13: 2:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 82D1837C012 for ; Wed, 19 Jul 2000 13:02:37 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id NAA03471; Wed, 19 Jul 2000 13:02:35 -0700 Message-ID: <39760973.CCFE2BB9@urx.com> Date: Wed, 19 Jul 2000 13:02:59 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ulf@Alameda.net Cc: hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > Ulf Zimmermann wrote: > > > > > > Hello, > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > I can find seems to work fine, but ps doesn't. > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > It sounds like your kernel and world might be a little out of > > sequence. > > I did the move. I rebuild the kernel again, same file size got created. > Yes, I agree it sounds like stuff is out of sync, but I did the complete > world after I cvsup and made the kernel. I thought it was something simple. I'm running 4.1-RC on 3 computers and ps works on all of them. Having something out of sequence could produce symptoms like that. FWIW, 4.1-RC is broken right now when you try to build the netinet section. So you can't cvsup to make sure didn't grab files in the middle of an upgrade. Kent > > > > > Kent > > > > > > > > Trying to use ps: > > > > > > fourtytwo ulf home/ulf > ps > > > ps: bad namelist > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > -- > > > Regards, Ulf. > > > > > > --------------------------------------------------------------------- > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kbstew99@hotmail.com > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > http://kstewart.urx.com/kstewart/bomber.jpg > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 13:40:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id C71BA37C034 for ; Wed, 19 Jul 2000 13:40:02 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id NAA85240; Wed, 19 Jul 2000 13:39:58 -0700 (PDT) (envelope-from ulf) Date: Wed, 19 Jul 2000 13:39:58 -0700 From: Ulf Zimmermann To: Kent Stewart Cc: ulf@Alameda.net, hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000719133958.C79232@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> <39760973.CCFE2BB9@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39760973.CCFE2BB9@urx.com>; from kstewart@urx.com on Wed, Jul 19, 2000 at 01:02:59PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 01:02:59PM -0700, Kent Stewart wrote: > > > Ulf Zimmermann wrote: > > > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > > > > Ulf Zimmermann wrote: > > > > > > > > Hello, > > > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > > I can find seems to work fine, but ps doesn't. > > > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > > It sounds like your kernel and world might be a little out of > > > sequence. > > > > I did the move. I rebuild the kernel again, same file size got created. > > Yes, I agree it sounds like stuff is out of sync, but I did the complete > > world after I cvsup and made the kernel. > > I thought it was something simple. I'm running 4.1-RC on 3 computers > and ps works on all of them. Having something out of sequence could > produce symptoms like that. > > FWIW, 4.1-RC is broken right now when you try to build the netinet > section. So you can't cvsup to make sure didn't grab files in the > middle of an upgrade. I did two times cvsup, because my system was 4.0-stable out of a time where softupdates was still in contrib and so the first run had problems because of the existing links. Second cvsup run only upgraded some readme files and freebsd.h for gcc. > > Kent > > > > > > > > > Kent > > > > > > > > > > > Trying to use ps: > > > > > > > > fourtytwo ulf home/ulf > ps > > > > ps: bad namelist > > > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > > > -- > > > > Regards, Ulf. > > > > > > > > --------------------------------------------------------------------- > > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > -- > > > Kent Stewart > > > Richland, WA > > > > > > mailto:kbstew99@hotmail.com > > > http://kstewart.urx.com/kstewart/index.html > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > > http://kstewart.urx.com/kstewart/bomber.jpg > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > Bomber dropping fire retardant in front of Hanford Wild fire. > http://kstewart.urx.com/kstewart/bomber.jpg -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 20:19: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 6C63037B848 for ; Wed, 19 Jul 2000 20:19:01 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id UAA08789 for ; Wed, 19 Jul 2000 20:19:00 -0700 (PDT) Message-ID: <39766FA4.C9C2EE1F@isi.edu> Date: Wed, 19 Jul 2000 20:19:00 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en, de MIME-Version: 1.0 To: hackers@freebsd.org Subject: clearing pages in the idle loop Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, if recently read [Dougan99], which describes optimizations to the memory management system of the PowerPC port of the Linux kernel. One of the mechanisms (Section 9) is pushing the clearing of pages to the idle task, like FreeBSD does. The authors report that on the PPC architecture, it is critical that the data and instruction cache be turned off before zeroing pages in the idle loop. Otherwise, cache pollution as a side-effect of idle-time activity would more than cancel out the gains from the zeroing. Wouldn't this be true on the i386 architecture as well? I have seen no calls in the FreeBSD idle loop that seem to do this. I'm not even sure if the i386 architecture supports turning off caches (but a quick glance at the Pentium references seems to indicate so.) Has anybody experimented with the idea before? Lars [Dougan99] Cort Dougan, Paul Mackerras and Victor Yodaiken. Optimizing the Idle Task and Other MMU Tricks. Proceedings 3rd USENIX Symposium on Operating Systems Design and Implementation (OSDI), February 1999, pp. 229-237. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 19 21:41:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B033D37B9DD for ; Wed, 19 Jul 2000 21:41:27 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id XAA03360; Wed, 19 Jul 2000 23:41:25 -0500 (CDT) Date: Wed, 19 Jul 2000 23:41:24 -0500 From: Alan Cox To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: clearing pages in the idle loop Message-ID: <20000719234124.H14543@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last year, I tried to reproduce some of the claims/results in this paper on FreeBSD/x86 and couldn't. I also tried limiting the idle loop to clearing pages of one particular color at a time. That way, the cache lines replaced by the second page you clear are the cache lines holding the first page you cleared, and so on for the third, fourth, ... pages cleared. Again, I saw no measurable effect on tests like "buildworld", which is a similar workload to the paper's if I recall correctly. Finally, it's possible that having these pre-zeroed pages in your L2 cache might be beneficial if they get allocated and used right away. FreeBSD's idle loop zeroes the pages that are next in line for allocation. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 1:16: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from idet.rsn.hk-r.se (idet.rsn.hk-r.se [194.47.142.179]) by hub.freebsd.org (Postfix) with ESMTP id A78C537BC0F for ; Thu, 20 Jul 2000 01:16:00 -0700 (PDT) (envelope-from bjorn@tornqvist.net) Received: from tornqvist.net ([194.52.130.37]) by idet.rsn.hk-r.se (8.9.3/8.9.3) with ESMTP id KAA83874 for ; Thu, 20 Jul 2000 10:12:44 +0200 (CEST) (envelope-from bjorn@tornqvist.net) Message-ID: <3976B539.77FB6626@tornqvist.net> Date: Thu, 20 Jul 2000 10:15:53 +0200 From: Bjorn Tornqvist Organization: West Entertainment Solutions & Technologies AB X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: SCHED_RR(root only!?) vs SCHED_FIFO(any user!?) 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! Can anyone please explain why I have to be root (or make the executable run as root) to be able to use SCHED_RR in my LinuxThreads (btw, same thing happens in pthreads) application? pthread_create() returns an "Operation not permitted" error if not run as root. My application *must not* run as root (there is no need for it to) but I also *must have* Round-Robin scheduling for overall system (application) stability and availability. Please help! (And, majordomo@freebsd.org doesn't respond to my subscribe requests so please reply in private) //Bjorn pthread_attr_t attr; /* Set scheduling policy to Round-Robin so that all threads will have a chance to run. In extreme environments, the default first-in first-out scheduler is used, and some threads might never get a chance to run. */ if ((status = pthread_attr_setschedpolicy(&attr, SCHED_RR)) != 0) { cerr << "WARNING: Thread scheduling policy defaults to FIFO!!! Some threads " "might never run!" << endl; cerr << " Reason given: " << strerror(status) << endl; } if ((status = pthread_create(&myThreadID, &attr, &thread_func, this)) != 0) { cout << strerror(status)<< endl; throw "Thread could not be created"; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 1:55:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id D474337BB93; Thu, 20 Jul 2000 01:55:14 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id JAA50829; Thu, 20 Jul 2000 09:55:13 +0100 (BST) (envelope-from geoffb) Date: Thu, 20 Jul 2000 09:55:13 +0100 From: Geoff Buckingham To: hackers@freebsd.org Cc: scsi@freebsd.org Subject: Multiple ro mounts of vinum volume Message-ID: <20000720095513.A50799@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody with a knowledge of the vinum code have an opinion on the amount of work involved in getting vinum to the point that several JBODs in a FC switched fabric could be managed, as a vinum volume, by one machine, and mounted ro by that machine and several others on the switch fabric. (writing to that volume is obviously a fs issue) -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 2: 4: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A2C1637BAA5; Thu, 20 Jul 2000 02:03:54 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id SAA87185; Thu, 20 Jul 2000 18:33:42 +0930 (CST) (envelope-from grog) Date: Thu, 20 Jul 2000 18:33:42 +0930 From: Greg Lehey To: Geoff Buckingham Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720183341.I30599@wantadilla.lemis.com> References: <20000720095513.A50799@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000720095513.A50799@chuggalug.clues.com> 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 Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > > Does anybody with a knowledge of the vinum code have an opinion on > the amount of work involved in getting vinum to the point that > several JBODs in a FC switched fabric could be managed, as a vinum > volume, by one machine, and mounted ro by that machine and several > others on the switch fabric. I'd say "no work at all" as far as Vinum is concerned. The real issue is getting the drivers to present the individual drives to the system. That's a device driver issue, and I don't know enough about the current state of FC drivers to make a sensible comment. But I'd certainly be interested to hear more. > (writing to that volume is obviously a fs issue) That depends if you want to put a file system on it. A thing that might bite you here is that ufs is currently limited to 1 TB per volume. Vinum doesn't have that restriction: if you want to create a 20 TB volume, and you know how to use the space, Vinum should work. The problem with ufs is that the block numbers in the inodes are 32 bit signed values. With 512 byte sectors, the only we can do it, that means a total address space of 2**9 * 2*31, or 1 TB. At some time I suspect we're going to need to fix that. 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 Thu Jul 20 2: 8:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C43A337BD8D; Thu, 20 Jul 2000 02:08:24 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id SAA89230; Thu, 20 Jul 2000 18:38:13 +0930 (CST) (envelope-from grog) Date: Thu, 20 Jul 2000 18:38:13 +0930 From: Greg Lehey To: Geoff Buckingham Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720183812.K30599@wantadilla.lemis.com> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000720183341.I30599@wantadilla.lemis.com> 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 Thursday, 20 July 2000 at 18:33:42 +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: >> >> Does anybody with a knowledge of the vinum code have an opinion on >> the amount of work involved in getting vinum to the point that >> several JBODs in a FC switched fabric could be managed, as a vinum >> volume, by one machine, and mounted ro by that machine and several >> others on the switch fabric. > > I'd say "no work at all" as far as Vinum is concerned. The real issue > is getting the drivers to present the individual drives to the > system. That's a device driver issue, and I don't know enough about > the current state of FC drivers to make a sensible comment. But I'd > certainly be interested to hear more. > >> (writing to that volume is obviously a fs issue) Oops, I missed the point here. Yes, the multiple R/O issue would make it very difficult to write to it. I suspect that it would be almost impossible to write while other systems had the volume open R/O. I'll think about how that could be done, but it's not simple, if it's at all possible. 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 Thu Jul 20 2:32: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 0714437B625; Thu, 20 Jul 2000 02:32:00 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA50932; Thu, 20 Jul 2000 10:31:50 +0100 (BST) (envelope-from geoffb) Date: Thu, 20 Jul 2000 10:31:50 +0100 From: Geoff Buckingham To: Greg Lehey Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720103150.A50907@chuggalug.clues.com> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> <20000720183812.K30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000720183812.K30599@wantadilla.lemis.com>; from Greg Lehey on Thu, Jul 20, 2000 at 06:38:13PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 06:38:13PM +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 18:33:42 +0930, Greg Lehey wrote: > > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > >> > >> Does anybody with a knowledge of the vinum code have an opinion on > >> the amount of work involved in getting vinum to the point that > >> several JBODs in a FC switched fabric could be managed, as a vinum > >> volume, by one machine, and mounted ro by that machine and several > >> others on the switch fabric. > > > > I'd say "no work at all" as far as Vinum is concerned. The real issue > > is getting the drivers to present the individual drives to the > > system. That's a device driver issue, and I don't know enough about > > the current state of FC drivers to make a sensible comment. But I'd > > certainly be interested to hear more. > > I believe all the disks should be visable to all the hosts, unless some aspect of your switch fabric has been configured to hide disks from NT4 boxes. > >> (writing to that volume is obviously a fs issue) > > Oops, I missed the point here. Yes, the multiple R/O issue would make > it very difficult to write to it. I suspect that it would be almost > impossible to write while other systems had the volume open R/O. I'll > think about how that could be done, but it's not simple, if it's at > all possible. > I would be happy with unmounting the FS everywhere mounting it rw on the 'management' machine , writing, then reversing back to having it mounted ro everywhere. I may have a play with this in a few months when I have a bit more kit, as I had imagined there would be more issues with multiple machines, each with an instance of vinum trying to manage the same single volume (particulary in degraded or repair situations) On the Fs front I must confess to having lost track of the XFS situation/ devate after the intial storm of interest when SGI first announced their interest. What happened? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 5:43:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 06D5D37BAE5 for ; Thu, 20 Jul 2000 05:43:41 -0700 (PDT) (envelope-from dick@tar.com) Received: from test.tar.com (test [204.95.187.4]) by ns.tar.com (8.9.3/8.9.3) with ESMTP id HAA63360; Thu, 20 Jul 2000 07:43:39 -0500 (CDT) (envelope-from dick@tar.com) Received: by test.tar.com (Postfix, from userid 1000) id 3F6BE81D88; Thu, 20 Jul 2000 07:43:38 -0500 (CDT) Date: Thu, 20 Jul 2000 07:43:38 -0500 From: "Richard Seaman, Jr." To: Bjorn Tornqvist Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCHED_RR(root only!?) vs SCHED_FIFO(any user!?) Message-ID: <20000720074338.A404@tar.com> References: <3976B539.77FB6626@tornqvist.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3976B539.77FB6626@tornqvist.net>; from bjorn@tornqvist.net on Thu, Jul 20, 2000 at 10:15:53AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 10:15:53AM +0200, Bjorn Tornqvist wrote: > > Hi all! > > Can anyone please explain why I have to be root (or make the executable > run as root) to be able to use SCHED_RR in my LinuxThreads (btw, same > thing happens in pthreads) application? 1) Note that the default scheduling policy in linuxthreads is SCHED_OTHER not SCHED_FIFO. SCHED_OTHER is a form of round robin scheduling. 2) SCHED_RR and SCHE_FIFO are "real time" policies in linuxthreads. FreeBSD (and Linux too, AFAIK) limit root to setting real time policies because setting such a policy can potentially monopolize a machine, effectively resulting in a local DoS. There may also be potential priority inversion problems that need to be dealt with when using real time policies. 3) I would have thought that FreeBSD user threads would let you manipulate policies as an ordinary user, but in any case, AFAIK the default policy in user threads is SCHED_RR. AFAIK, SCHED_RR and SCHED_FIFO are not "real time" policies in FreeBSD user threads (when applied to thread scheduling -- they are still real time policies when applied to the scheduling of the process). > My application *must not* run as root (there is no need for it to) but I > also *must have* Round-Robin scheduling for overall system (application) > stability and availability. Why is the default SCHED_OTHER not acceptable for your app? I would think stability and availability would be improved with SCHED_OTHER, except in very restricted situations? -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Nashotah WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 7:42: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9154F37B54D for ; Thu, 20 Jul 2000 07:42:02 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA13656 for ; Thu, 20 Jul 2000 10:42:00 -0400 (EDT) Date: Thu, 20 Jul 2000 10:39:36 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: memory type and its size Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does kernel memory of the same type (e.g., M_TEMP) must be allocated (using malloc()) with the same (range of) size? BTW, how to display mbuf cluster usages info. Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 9: 4:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cepheus.azstarnet.com (cepheus.azstarnet.com [169.197.56.195]) by hub.freebsd.org (Postfix) with ESMTP id 60AAE37B5CF for ; Thu, 20 Jul 2000 09:04:34 -0700 (PDT) (envelope-from bobkat@azstarnet.com) Received: from full.planing.jibe (dialup04ip103.tus.azstarnet.com [169.197.31.231]) by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id JAA07775 for ; Thu, 20 Jul 2000 09:04:29 -0700 (MST) X-Sent-via: StarNet http://www.azstarnet.com/ From: Bob Kot To: freebsd-hackers@FreeBSD.ORG Subject: T-Beach Multisound Monterey device driver upgraded to FBSD-4.0 Date: Thu, 20 Jul 2000 08:21:39 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00072009042803.00567@full.planing.jibe> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have upgraded my device driver for the subject soundcard. For features, capabilities, limitations and downloading see: http://www.treefort.org/~bobkat/msm20/9main.shtml This version has many bug fixes since the FBSD-3.x version. It is still dual mode. KLD module can be kldload/kldunload'd and is the preferred mode of use, but it can be compiled statically into a kernel. The KLD module mode of installation has been facilitated via a sh script. Are there any device driver authors out there who are implementing their driver as a KLD module and delivering/installing it as a port? This version is being released under the less restrictive FreeBSD free-software license. Fiji and Pinnacle models will not work with this driver. They are similar to the Monterey but the Turtle Beach interface to the hardware changed in later models. Push that mixer slider up and enjoy some tunes!! 1 3 0 1 3 13013 BOB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 15:40:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 463FB37B5B4 for ; Thu, 20 Jul 2000 15:40:06 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id PAA93519; Thu, 20 Jul 2000 15:39:53 -0700 (PDT) (envelope-from ulf) Date: Thu, 20 Jul 2000 15:39:53 -0700 From: Ulf Zimmermann To: Kent Stewart Cc: ulf@Alameda.net, hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000720153953.G79232@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> <39760973.CCFE2BB9@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39760973.CCFE2BB9@urx.com>; from kstewart@urx.com on Wed, Jul 19, 2000 at 01:02:59PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 19, 2000 at 01:02:59PM -0700, Kent Stewart wrote: > > > Ulf Zimmermann wrote: > > > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > > > > Ulf Zimmermann wrote: > > > > > > > > Hello, > > > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > > I can find seems to work fine, but ps doesn't. > > > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > > It sounds like your kernel and world might be a little out of > > > sequence. > > > > I did the move. I rebuild the kernel again, same file size got created. > > Yes, I agree it sounds like stuff is out of sync, but I did the complete > > world after I cvsup and made the kernel. > > I thought it was something simple. I'm running 4.1-RC on 3 computers > and ps works on all of them. Having something out of sequence could > produce symptoms like that. > > FWIW, 4.1-RC is broken right now when you try to build the netinet > section. So you can't cvsup to make sure didn't grab files in the > middle of an upgrade. Sigh, so I did another cvsup around 9am PDT today and did: make buildworld make buildkernel KERNEL=FOURTYTWO make installkernel KERNEL=FOURTYTWO make installworld then did the chflags, mv etc of the kernel, rebooted and still: fourtytwo ulf home/ulf > ps ps: bad namelist fourtytwo ulf home/ulf > which ps /bin/ps fourtytwo ulf home/ulf > ll /bin/ps 216 -r-xr-xr-x 1 root wheel 207748 Jul 20 15:30 /bin/ps fourtytwo ulf home/ulf > ll /kernel 2560 -r-xr-xr-x 1 root wheel 2605561 Jul 20 15:29 /kernel Anyone got any idea why ? > > Kent > > > > > > > > > Kent > > > > > > > > > > > Trying to use ps: > > > > > > > > fourtytwo ulf home/ulf > ps > > > > ps: bad namelist > > > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > > > -- > > > > Regards, Ulf. > > > > > > > > --------------------------------------------------------------------- > > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > -- > > > Kent Stewart > > > Richland, WA > > > > > > mailto:kbstew99@hotmail.com > > > http://kstewart.urx.com/kstewart/index.html > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > > http://kstewart.urx.com/kstewart/bomber.jpg > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > Bomber dropping fire retardant in front of Hanford Wild fire. > http://kstewart.urx.com/kstewart/bomber.jpg -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 15:48:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7C8F737B66F; Thu, 20 Jul 2000 15:48:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA15995; Thu, 20 Jul 2000 15:48:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 20 Jul 2000 15:48:23 -0700 (PDT) From: Kris Kennaway To: Ulf Zimmermann Cc: Kent Stewart , hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) In-Reply-To: <20000720153953.G79232@PacHell.TelcoSucks.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 Thu, 20 Jul 2000, Ulf Zimmermann wrote: > and still: > > fourtytwo ulf home/ulf > ps > ps: bad namelist You're not bypassing the loader when you boot are you? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 16:24: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 2254437C1D9; Thu, 20 Jul 2000 16:24:01 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id QAA93782; Thu, 20 Jul 2000 16:24:00 -0700 (PDT) (envelope-from ulf) Date: Thu, 20 Jul 2000 16:24:00 -0700 From: Ulf Zimmermann To: Kris Kennaway Cc: Ulf Zimmermann , Kent Stewart , hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000720162400.H79232@PacHell.TelcoSucks.org> Reply-To: ulf@alameda.net References: <20000720153953.G79232@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.ORG on Thu, Jul 20, 2000 at 03:48:23PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 03:48:23PM -0700, Kris Kennaway wrote: > On Thu, 20 Jul 2000, Ulf Zimmermann wrote: > > > and still: > > > > fourtytwo ulf home/ulf > ps > > ps: bad namelist > > You're not bypassing the loader when you boot are you? No, the machine is a pure FreeBSD machine, but uses the 3 stage boot loader. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 16:52:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camel.ethereal.net (camel.ethereal.net [216.200.22.209]) by hub.freebsd.org (Postfix) with ESMTP id F390F37B82A for ; Thu, 20 Jul 2000 16:52:48 -0700 (PDT) (envelope-from jkb@camel.ethereal.net) Received: (from jkb@localhost) by camel.ethereal.net (8.10.0.Beta10/8.10.0.Beta10) id e6KNpkO60676; Thu, 20 Jul 2000 16:51:46 -0700 (PDT) Date: Thu, 20 Jul 2000 16:51:46 -0700 From: Jan Koum To: Ulf Zimmermann Cc: Kent Stewart , hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000720165145.A36013@ethereal.net> References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> <39760973.CCFE2BB9@urx.com> <20000720153953.G79232@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.1i In-Reply-To: <20000720153953.G79232@PacHell.TelcoSucks.org>; from ulf@Alameda.net on Thu, Jul 20, 2000 at 03:39:53PM -0700 X-Operating-System: FreeBSD camel.ethereal.net 3.4-RELEASE FreeBSD 3.4-RELEASE X-Unix-Uptime: 10:43AM up 13 days, 3:32, 33 users, load averages: 0.19, 0.20, 0.18 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hey ulf, i bet your /dev/null is no longer nulling: # cd /dev # rm null # echo "fuck" > null # ps ax ps: bad namelist -- yan On Thu, Jul 20, 2000 at 03:39:53PM -0700, Ulf Zimmermann wrote: > On Wed, Jul 19, 2000 at 01:02:59PM -0700, Kent Stewart wrote: > > > > > > Ulf Zimmermann wrote: > > > > > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > > > > > > > Ulf Zimmermann wrote: > > > > > > > > > > Hello, > > > > > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > > > I can find seems to work fine, but ps doesn't. > > > > > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > > > It sounds like your kernel and world might be a little out of > > > > sequence. > > > > > > I did the move. I rebuild the kernel again, same file size got created. > > > Yes, I agree it sounds like stuff is out of sync, but I did the complete > > > world after I cvsup and made the kernel. > > > > I thought it was something simple. I'm running 4.1-RC on 3 computers > > and ps works on all of them. Having something out of sequence could > > produce symptoms like that. > > > > FWIW, 4.1-RC is broken right now when you try to build the netinet > > section. So you can't cvsup to make sure didn't grab files in the > > middle of an upgrade. > > Sigh, so I did another cvsup around 9am PDT today and did: > > make buildworld > make buildkernel KERNEL=FOURTYTWO > make installkernel KERNEL=FOURTYTWO > make installworld > > then did the chflags, mv etc of the kernel, rebooted > > and still: > > fourtytwo ulf home/ulf > ps > ps: bad namelist > fourtytwo ulf home/ulf > which ps > /bin/ps > fourtytwo ulf home/ulf > ll /bin/ps > 216 -r-xr-xr-x 1 root wheel 207748 Jul 20 15:30 /bin/ps > fourtytwo ulf home/ulf > ll /kernel > 2560 -r-xr-xr-x 1 root wheel 2605561 Jul 20 15:29 /kernel > > > Anyone got any idea why ? > > > > > Kent > > > > > > > > > > > > > Kent > > > > > > > > > > > > > > Trying to use ps: > > > > > > > > > > fourtytwo ulf home/ulf > ps > > > > > ps: bad namelist > > > > > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > > > > > -- > > > > > Regards, Ulf. > > > > > > > > > > --------------------------------------------------------------------- > > > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > -- > > > > Kent Stewart > > > > Richland, WA > > > > > > > > mailto:kbstew99@hotmail.com > > > > http://kstewart.urx.com/kstewart/index.html > > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > > > http://kstewart.urx.com/kstewart/bomber.jpg > > > > > > -- > > > Regards, Ulf. > > > > > > --------------------------------------------------------------------- > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kbstew99@hotmail.com > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > http://kstewart.urx.com/kstewart/bomber.jpg > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 18:53:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 1FCB837B565 for ; Thu, 20 Jul 2000 18:53:52 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id SAA94525; Thu, 20 Jul 2000 18:53:29 -0700 (PDT) (envelope-from ulf) Date: Thu, 20 Jul 2000 18:53:29 -0700 From: Ulf Zimmermann To: Jan Koum Cc: Ulf Zimmermann , Kent Stewart , hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) Message-ID: <20000720185329.I79232@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> <39760973.CCFE2BB9@urx.com> <20000720153953.G79232@PacHell.TelcoSucks.org> <20000720165145.A36013@ethereal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000720165145.A36013@ethereal.net>; from jkb@ethereal.net on Thu, Jul 20, 2000 at 04:51:46PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 04:51:46PM -0700, Jan Koum wrote: > hey ulf, i bet your /dev/null is no longer nulling: > > # cd /dev > # rm null > # echo "fuck" > null > # ps ax > ps: bad namelist Yep, you were right. /dev/null was a plain file. Strange > > > -- yan > > On Thu, Jul 20, 2000 at 03:39:53PM -0700, Ulf Zimmermann wrote: > > On Wed, Jul 19, 2000 at 01:02:59PM -0700, Kent Stewart wrote: > > > > > > > > > Ulf Zimmermann wrote: > > > > > > > > On Tue, Jul 18, 2000 at 09:09:47PM -0700, Kent Stewart wrote: > > > > > > > > > > > > > > > Ulf Zimmermann wrote: > > > > > > > > > > > > Hello, > > > > > > > > > > > > I updated via cvsup (cvsup from tuesday afternoon PDT), I went into > > > > > > single user mode, did make world, make buildkernel KERNEL=FOURTYTWO > > > > > > and make installkernel KERNEL=FOURTYTWO. Everything but one thing > > > > > > I can find seems to work fine, but ps doesn't. > > > > > > > > > > Did you boot /FOURTYTWO or do the rename sequence to make it kernel? > > > > > It sounds like your kernel and world might be a little out of > > > > > sequence. > > > > > > > > I did the move. I rebuild the kernel again, same file size got created. > > > > Yes, I agree it sounds like stuff is out of sync, but I did the complete > > > > world after I cvsup and made the kernel. > > > > > > I thought it was something simple. I'm running 4.1-RC on 3 computers > > > and ps works on all of them. Having something out of sequence could > > > produce symptoms like that. > > > > > > FWIW, 4.1-RC is broken right now when you try to build the netinet > > > section. So you can't cvsup to make sure didn't grab files in the > > > middle of an upgrade. > > > > Sigh, so I did another cvsup around 9am PDT today and did: > > > > make buildworld > > make buildkernel KERNEL=FOURTYTWO > > make installkernel KERNEL=FOURTYTWO > > make installworld > > > > then did the chflags, mv etc of the kernel, rebooted > > > > and still: > > > > fourtytwo ulf home/ulf > ps > > ps: bad namelist > > fourtytwo ulf home/ulf > which ps > > /bin/ps > > fourtytwo ulf home/ulf > ll /bin/ps > > 216 -r-xr-xr-x 1 root wheel 207748 Jul 20 15:30 /bin/ps > > fourtytwo ulf home/ulf > ll /kernel > > 2560 -r-xr-xr-x 1 root wheel 2605561 Jul 20 15:29 /kernel > > > > > > Anyone got any idea why ? > > > > > > > > Kent > > > > > > > > > > > > > > > > > Kent > > > > > > > > > > > > > > > > > Trying to use ps: > > > > > > > > > > > > fourtytwo ulf home/ulf > ps > > > > > > ps: bad namelist > > > > > > > > > > > > Rebuilding kerbel, libkvm or ps produce the same bins. "bad namelist" > > > > > > is in error inside of libkvm (kvm_i386.c) after using kvm_nlist. > > > > > > > > > > > > Anyone got an suggestion what to check or what maybe broken ? > > > > > > > > > > > > -- > > > > > > Regards, Ulf. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > -- > > > > > Kent Stewart > > > > > Richland, WA > > > > > > > > > > mailto:kbstew99@hotmail.com > > > > > http://kstewart.urx.com/kstewart/index.html > > > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > > > > http://kstewart.urx.com/kstewart/bomber.jpg > > > > > > > > -- > > > > Regards, Ulf. > > > > > > > > --------------------------------------------------------------------- > > > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > -- > > > Kent Stewart > > > Richland, WA > > > > > > mailto:kbstew99@hotmail.com > > > http://kstewart.urx.com/kstewart/index.html > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > Bomber dropping fire retardant in front of Hanford Wild fire. > > > http://kstewart.urx.com/kstewart/bomber.jpg > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 18:55: 8 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 07F5B37B565 for ; Thu, 20 Jul 2000 18:54: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 SAA16210; Thu, 20 Jul 2000 18:54:43 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 20 Jul 2000 18:54:43 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: Jan Koum Cc: Ulf Zimmermann , Kent Stewart , hackers@FreeBSD.ORG Subject: Re: problem on 4.1-RC (4.0-stable) In-Reply-To: <20000720165145.A36013@ethereal.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Jan Koum wrote: > hey ulf, i bet your /dev/null is no longer nulling: > > # cd /dev > # rm null > # echo "fuck" > null no... really. Tell us how you feel Jan. *chuckle* 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 Thu Jul 20 19:11:40 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 635EB37B608 for ; Thu, 20 Jul 2000 19:11:37 -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 <0FY00095HZCPQ1@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Thu, 20 Jul 2000 21:10:02 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id VAA61435; Thu, 20 Jul 2000 21:08:09 -0500 (CDT envelope-from chris) Date: Thu, 20 Jul 2000 21:08:05 -0500 From: Chris Costello Subject: Re: problem on 4.1-RC (4.0-stable) In-reply-to: <20000720185329.I79232@PacHell.TelcoSucks.org> To: Ulf Zimmermann Cc: Jan Koum , Kent Stewart , hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000720210805.G58968@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <20000718210328.A79232@PacHell.TelcoSucks.org> <39752A0B.9CE57DF3@urx.com> <20000719125751.B79232@PacHell.TelcoSucks.org> <39760973.CCFE2BB9@urx.com> <20000720153953.G79232@PacHell.TelcoSucks.org> <20000720165145.A36013@ethereal.net> <20000720185329.I79232@PacHell.TelcoSucks.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, July 20, 2000, Ulf Zimmermann wrote: > Yep, you were right. /dev/null was a plain file. Strange Just guessing here--ps probably uses /dev/null for all the files passed to kvm_open(3). I imagine it uses kvm_getprocs for its process listing, which is implemented using sysctl. -- |Chris Costello |Programmer: One who is too lacking in people skills | to be a software engineer. `--------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 20 20:20: 5 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 1E3EA37C168 for ; Thu, 20 Jul 2000 20:19:57 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny14-18.ix.netcom.com [198.211.19.82]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA18625; Thu, 20 Jul 2000 23:19:54 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id XAA02747; Thu, 20 Jul 2000 23:19:49 -0400 (EDT) (envelope-from vns) Date: Thu, 20 Jul 2000 23:19:49 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200007210319.XAA02747@jupiter.delta.ny.us> To: bobkat@azstarnet.com Cc: freebsd-hackers@freebsd.org Subject: Re: T-Beach Multisound Monterey device driver upgraded to FBSD-4.0 In-Reply-To: <00072009042803.00567@full.planing.jibe> References: <00072009042803.00567@full.planing.jibe> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In muc.lists.freebsd.hackers, you wrote: >Are there any device driver authors out there who are implementing >their driver as a KLD module and delivering/installing it as a port? You may look inside emulation/rtc or emulation/vmware port, it's not a drivers for hardware, but a KLD modules. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 2:28:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 709AC37B62F; Fri, 21 Jul 2000 02:28:27 -0700 (PDT) (envelope-from raw@fast.no) Received: from raw.gren.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id JAA88153; Fri, 21 Jul 2000 09:29:20 GMT (envelope-from raw@fast.no) Received: (from raw@localhost) by raw.gren.fast.no (8.9.3/8.9.3) id KAA16115; Fri, 21 Jul 2000 10:16:53 +0200 (CEST) (envelope-from raw) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14711.10742.914512.819982@raw.gren.fast.no> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid From: Raymond Wiker To: freebsd-hackers@freebsd.org Subject: dlopen() and friends from a statically-linked binary? Date: Thu, 20 Jul 2000 18:33:58 +0200 (CEST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Re-sent, as it seemed to get lost on my first try. ] Is it possible, at all, to use dlopen etc from a statically-linked executable? My experiments with FreeBSD-4.0 (see below) indicate that it's not possible. The reason that I'd like this to work is that SBCL (a Common Lisp implementation, see http://sbcl.sourceforge.net) needs the addresses of certain library symbols (e.g, errno) when building the initial lisp image. This seems to require static linking. On the other hand, SBCL is severely handicapped if it cannot subsequently use dlopen() to load foreign code into the running lisp system. raw : ~ $ cat dltest.c #include #include main() { void *handle; void *sym; handle = dlopen(0, RTLD_LAZY); if (handle == 0) { fprintf(stderr, "dlopen returned 0: %s\n", dlerror()); } else { fprintf(stderr, "Handle: %p, main: %p\n", handle, dlsym(handle, "main")); } fprintf(stderr, "Handle: %p, main: %p\n", 0, dlsym(0, "main")); return 0; } raw : ~ $ gcc -static dltest.c -o dltest raw : ~ $ ./dltest dlopen returned 0: Service unavailable Handle: 0x0, main: 0x0 raw : ~ $ gcc dltest.c -o dltest raw : ~ $ ./dltest Handle: 0x2805e000, main: 0x0 Handle: 0x0, main: 0x0 [ Note: this seems wrong; according to the manpage for dlsym, the second call should give the same output as the first. ] -- Raymond Wiker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 2:48:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pr.infosec.ru (pr.infosec.ru [194.135.141.98]) by hub.freebsd.org (Postfix) with ESMTP id F1E7A37B83B for ; Fri, 21 Jul 2000 02:48:19 -0700 (PDT) (envelope-from blaze@infosec.ru) Received: from blaze (WS_BLAZE [200.0.0.51]) by pr.infosec.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id PKZW3ZNA; Fri, 21 Jul 2000 13:48:20 +0400 Date: Fri, 21 Jul 2000 13:48:51 +0400 (MSD) From: Andrey Sverdlichenko X-Sender: blaze@blaze To: freebsd-hackers@freebsd.org Subject: open() error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I've noticed a strange error in open() syscall: when system booted with a CD as root (boot -C) the following code fails with EINVAL: fd = open(c, O_RDONLY | O_NONBLOCK | O_EXLOCK, 0) When root is hdd with UFS (mounted read-only), this works fine. Is it a bug or i missed something? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 3: 8:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 3331F37B6BA; Fri, 21 Jul 2000 03:08:32 -0700 (PDT) (envelope-from raw@fast.no) Received: from raw.gren.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id KAA88631; Fri, 21 Jul 2000 10:09:26 GMT (envelope-from raw@fast.no) Received: (from raw@localhost) by raw.gren.fast.no (8.9.3/8.9.3) id MAA16446; Fri, 21 Jul 2000 12:09:16 +0200 (CEST) (envelope-from raw) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14712.8524.305147.704022@raw.gren.fast.no> Date: Fri, 21 Jul 2000 12:09:16 +0200 (CEST) X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid From: Raymond Wiker To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: dlopen() and friends from a statically-linked binary? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > raw : ~ $ gcc dltest.c -o dltest > raw : ~ $ ./dltest > Handle: 0x2805e000, main: 0x0 > Handle: 0x0, main: 0x0 > > [ Note: this seems wrong; according to the manpage for dlsym, the > second call should give the same output as the first. ] Sorry about the confusion... the "main" symbol does not appear to work for this illustration (possibly because it doesn't come from a dynamic library?). If I try with "errno" instead, I get raw : ~ $ ./dltest Handle: 0x2805e000, errno: 0x280f5cd4 Handle: 0x0, errno: 0x0 raw : ~ $ --- according to the manpage for dlsym(), passing 0 for handle should have the same effect as passing 0 as the path to dlopen; i.e, to access the symbol table for the running program. -- Raymond Wiker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 3:19:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.isltd.insignia.com (gatekeeper.isltd.insignia.com [195.153.60.130]) by hub.freebsd.org (Postfix) with ESMTP id 0FC3037B906 for ; Fri, 21 Jul 2000 03:19:35 -0700 (PDT) (envelope-from martin.hopkins@insignia.com) Received: from saracen.isltd.insignia.com (saracen.isltd.insignia.com [193.112.17.171]) by gatekeeper.isltd.insignia.com (8.9.3/8.9.3) with ESMTP id LAA25675; Fri, 21 Jul 2000 11:18:54 +0100 (BST) Received: from whittard.home.isltd.insignia.com (dhcp16-223.isltd.insignia.com [193.112.16.223]) by saracen.isltd.insignia.com (8.8.4/BSCF-1.2) with SMTP id LAA13503; Fri, 21 Jul 2000 11:18:50 +0100 (BST) From: Martin Hopkins MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14712.8884.57869.666781@whittard.home> Date: Fri, 21 Jul 2000 11:15:16 +0100 (BST) To: Raymond Wiker Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dlopen() and friends from a statically-linked binary? In-Reply-To: <14711.10742.914512.819982@raw.gren.fast.no> References: <14711.10742.914512.819982@raw.gren.fast.no> X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Raymond" == Raymond Wiker writes: Raymond> raw : ~ $ cat dltest.c Raymond> #include Raymond> #include Raymond> main() Raymond> { Raymond> void *handle; Raymond> void *sym; Raymond> handle = dlopen(0, RTLD_LAZY); Raymond> if (handle == 0) Raymond> { Raymond> fprintf(stderr, "dlopen returned 0: %s\n", dlerror()); Raymond> } Raymond> else Raymond> { Raymond> fprintf(stderr, "Handle: %p, main: %p\n", handle, dlsym(handle, "main")); Raymond> } Raymond> fprintf(stderr, "Handle: %p, main: %p\n", 0, dlsym(0, "main")); Raymond> return 0; Raymond> } Raymond> raw : ~ $ gcc -static dltest.c -o dltest Raymond> raw : ~ $ ./dltest Raymond> dlopen returned 0: Service unavailable Raymond> Handle: 0x0, main: 0x0 Raymond> raw : ~ $ gcc dltest.c -o dltest Raymond> raw : ~ $ ./dltest Raymond> Handle: 0x2805e000, main: 0x0 Raymond> Handle: 0x0, main: 0x0 Raymond> [ Note: this seems wrong; according to the manpage for dlsym, the Raymond> second call should give the same output as the first. ] It does, it returns NULL. I'm not sure what your issues with SBCL are (I'll try to take a look later if I get time). I believe to get your sample code above to work you want... gcc dltest.c -Xlinker -export-dynamic -o dltest This then gives me Handle: 0x2805d000, main: 0x8048508 Handle: 0x0, main: 0x8048508 Hope this helps, Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 9:23:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id B340637BB99 for ; Fri, 21 Jul 2000 09:23:37 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id BAA79843; Sat, 22 Jul 2000 01:53:31 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id BAA00828; Sat, 22 Jul 2000 01:53:26 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14711.10742.914512.819982@raw.gren.fast.no> Date: Sat, 22 Jul 2000 01:53:22 +0930 (CST) From: "Daniel O'Connor" To: Raymond Wiker Subject: RE: dlopen() and friends from a statically-linked binary? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jul-00 Raymond Wiker wrote: > Is it possible, at all, to use dlopen etc from a > statically-linked executable? My experiments with FreeBSD-4.0 (see > below) indicate that it's not possible. You can't do it from a statically linked binary, however you can create a dynamic executable with no external unresolved references.. I forget how though :-/ > The reason that I'd like this to work is that SBCL (a Common > Lisp implementation, see http://sbcl.sourceforge.net) needs the > addresses of certain library symbols (e.g, errno) when building the > initial lisp image. This seems to require static linking. On the other > hand, SBCL is severely handicapped if it cannot subsequently use > dlopen() to load foreign code into the running lisp system. Well, I don't see why it would need static linking for that.. When the binary runs the libraries it uses will get loaded, and then it can use dlsym() to get the addresses it needs.. (ie what I am saying is I don't understand your explanation :) > raw : ~ $ gcc -static dltest.c -o dltest > raw : ~ $ ./dltest > dlopen returned 0: Service unavailable > Handle: 0x0, main: 0x0 > > raw : ~ $ gcc dltest.c -o dltest > raw : ~ $ ./dltest > Handle: 0x2805e000, main: 0x0 > Handle: 0x0, main: 0x0 > > [ Note: this seems wrong; according to the manpage for dlsym, the > second call should give the same output as the first. ] Agreed. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 9:25: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 3F41E37BC01; Fri, 21 Jul 2000 09:24:55 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id MAA66391; Fri, 21 Jul 2000 12:31:58 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Fri, 21 Jul 2000 12:31:58 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: hackers@freebsd.org, hardware@freebsd.org Subject: Intel 840 Chipset Discontinue Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was told by several of my distributors that all motherboards based off of the Intel 840 chipset are being discontinued. That means the Supermicro PIIDM3 and PIIIDME, and any other 840 board. Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to the 840 boards, but using some kind of "ServerWork LE" chipset. However, I have also been hearing bad news about these boards as well. Has anyone worked with these boards? Supermicro SAYS that they work fine under Linux and Solaris. However, one of my distributors says thay they are extremely touchy when it comes to memory. Only Registered PC133 ECC memory will work. If someone at freebsd.org wants to seriously test these boards, let me know, and I'll donate one. Without the 840 boards, server configs are now back to the 440GX days! -john v.e. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 9:45:58 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 7594637BBBA; Fri, 21 Jul 2000 09:45:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA30512; Fri, 21 Jul 2000 10:45:35 -0600 (MDT) (envelope-from ken) Date: Fri, 21 Jul 2000 10:45:35 -0600 From: "Kenneth D. Merry" To: Essenz Consulting Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Intel 840 Chipset Discontinue Message-ID: <20000721104535.A30468@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 john@essenz.com on Fri, Jul 21, 2000 at 12:31:58PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 21, 2000 at 12:31:58 -0400, Essenz Consulting wrote: > I was told by several of my distributors that all motherboards based off > of the Intel 840 chipset are being discontinued. That means the Supermicro > PIIDM3 and PIIIDME, and any other 840 board. Are you sure they don't just mean any 840 board that uses SDRAM? It looks like Supermicro has a RAMBUS 840 board on their web page now: http://www.supermicro.com/PRODUCT/MotherBoards/840/PIIIDR3a.htm > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > have also been hearing bad news about these boards as well. Not quite identical. They don't have AGP, which makes it difficult to get graphics boards. (If you want to use it for a workstation. Most graphics boards don't come in plain PCI anymore.) 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 Fri Jul 21 10: 6:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id E766037B731; Fri, 21 Jul 2000 10:06:10 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id NAA66729; Fri, 21 Jul 2000 13:13:05 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Fri, 21 Jul 2000 13:13:05 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: "Kenneth D. Merry" Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Intel 840 Chipset Discontinue In-Reply-To: <20000721104535.A30468@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 Apparently it affects all boards that the Intel 840 chipset. Yeah, it does suck that the 370DLx boards dont have AGP, but for a server you can still find old PCI video cards. On Fri, 21 Jul 2000, Kenneth D. Merry wrote: > On Fri, Jul 21, 2000 at 12:31:58 -0400, Essenz Consulting wrote: > > I was told by several of my distributors that all motherboards based off > > of the Intel 840 chipset are being discontinued. That means the Supermicro > > PIIDM3 and PIIIDME, and any other 840 board. > > Are you sure they don't just mean any 840 board that uses SDRAM? > > It looks like Supermicro has a RAMBUS 840 board on their web page now: > > http://www.supermicro.com/PRODUCT/MotherBoards/840/PIIIDR3a.htm > > > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > > have also been hearing bad news about these boards as well. > > Not quite identical. They don't have AGP, which makes it difficult to > get graphics boards. (If you want to use it for a workstation. Most > graphics boards don't come in plain PCI anymore.) > > Ken > -- > Kenneth Merry > ken@kdm.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 10:14:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 9C59237B731 for ; Fri, 21 Jul 2000 10:14:20 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 87861 invoked by uid 1001); 21 Jul 2000 17:14:07 +0000 (GMT) To: john@essenz.com Cc: hackers@freebsd.org, hardware@freebsd.org Subject: Re: Intel 840 Chipset Discontinue From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 21 Jul 2000 12:31:58 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 21 Jul 2000 19:14:07 +0200 Message-ID: <87859.964199647@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > have also been hearing bad news about these boards as well. The IBM Netfinity 3500 servers (possibly other Netfinity models also) use the Serverworks LE chipset, and work well with FreeBSD 4.0-STABLE. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 10:54:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 01BA037B9CC for ; Fri, 21 Jul 2000 10:54:18 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA16405; Fri, 21 Jul 2000 10:54:16 -0700 (PDT) Message-ID: <39788E48.60F8A59F@isi.edu> Date: Fri, 21 Jul 2000 10:54:16 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Alan Cox Cc: hackers@freebsd.org, cort@cs.nmt.edu Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Cort, the reason I'm CCing you is that I'm interested in using some of the mechanism described in your OSDI'99 paper for FreeBSD, and I've some questions about your Linux implementation, see below.) Alan Cox wrote: > Last year, I tried to reproduce some of the claims/results > in this paper on FreeBSD/x86 and couldn't. I also tried > limiting the idle loop to clearing pages of one particular > color at a time. That way, the cache lines replaced by > the second page you clear are the cache lines holding > the first page you cleared, and so on for the third, > fourth, ... pages cleared. Again, I saw no measurable > effect on tests like "buildworld", which is a similar > workload to the paper's if I recall correctly. Do you still have those FreeBSD patches, Alan? I'd be interested in doing some more experiments with that code. > Finally, it's possible that having these pre-zeroed pages > in your L2 cache might be beneficial if they get allocated > and used right away. FreeBSD's idle loop zeroes the pages > that are next in line for allocation. That makes sense. Other factors that may have an impact: * if you always have enough zeroed pages remaining over your benchmark (> ~1/2 free pages), FreeBSD will never do the idle-time zeroing * it looks to me as if Cort's Linux code will always zero whole pages, while the FreeBSD code is a little smarter and only zeroes used regions of a page (less impact on caches?) * cache size differences between PPC and i386? I'm looking at Cort's code (arch/ppc/kernel/idle.c), and while he turns off the caching for pages he zeroes, I don't see him disabling the L1/2 caches explicitly. Is this implicit with setting the non-cacheable flag on the PPC? Also, idle-time zeroing is commented out in the version I'm looking at (1.68, 1999/10/15), where problems found after the paper was published? Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 11:23: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hq.fsmlabs.com (hq.fsmlabs.com [209.155.42.197]) by hub.freebsd.org (Postfix) with ESMTP id 6B55F37BDDF for ; Fri, 21 Jul 2000 11:23:01 -0700 (PDT) (envelope-from cort@medea.fsmlabs.com) Received: from medea.fsmlabs.com (medea.fsmlabs.com [209.155.42.137]) by hq.fsmlabs.com (8.9.3/8.9.3) with ESMTP id MAA27598; Fri, 21 Jul 2000 12:22:39 -0600 Received: (from cort@localhost) by medea.fsmlabs.com (8.9.3/8.9.3) id MAA02384; Fri, 21 Jul 2000 12:14:57 -0600 Date: Fri, 21 Jul 2000 12:14:57 -0600 From: cort@fsmlabs.com To: Lars Eggert Cc: Alan Cox , hackers@freebsd.org Subject: Re: clearing pages in the idle loop Message-ID: <20000721121457.R26237@medea.fsmlabs.com> References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us In-Reply-To: <39788E48.60F8A59F@isi.edu>; from larse@ISI.EDU on Fri, Jul 21, 2000 at 10:54:16AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We started losing performance with the idle page clearing so I've disabled it and haven't done much with it in quite a while. The code has fallen into disrepair and some has been removed in the latest versions. I'd suggest looking at the early 2.3.x and 2.2.1[23] series of Linux kernels. That's where it was doing its best. We've also found that using dcbz, which zeros cache lines directly, actually improves performance. That is contradictory to one of the conclusions I drew in that paper. My conjecture was that the zero'd pages would not be used often since a process given a fresh page wouldn't read from it before a write. I still do think the idle page zero-ing can be useful, though. If you do some work with BSD on this please let me know. I'd like to follow along since I've been playing with BSD lately. } Do you still have those FreeBSD patches, Alan? I'd be interested in doing } some more experiments with that code. } } That makes sense. Other factors that may have an impact: } } * if you always have enough zeroed pages remaining over your } benchmark (> ~1/2 free pages), FreeBSD will never do the } idle-time zeroing How do you keep track of what parts of a page are used? In Linux I was just pulling pages off the free-list and zero-ing them. Do you have a bitmap of used regions within pages on BSD? } * it looks to me as if Cort's Linux code will always zero whole } pages, while the FreeBSD code is a little smarter and only zeroes } used regions of a page (less impact on caches?) } } * cache size differences between PPC and i386? Right, those won't be cached if the page is marked non-cacheable. } I'm looking at Cort's code (arch/ppc/kernel/idle.c), and while he turns off } the caching for pages he zeroes, I don't see him disabling the L1/2 caches } explicitly. Is this implicit with setting the non-cacheable flag on the } PPC? Also, idle-time zeroing is commented out in the version I'm looking at } (1.68, 1999/10/15), where problems found after the paper was published? I wanted a few bits for each page to describe its state: zero'd, non-zero'd, busy being zero'd. It would have taken some changes to the non-arch Linux code to do that and at the time we were moving to a more stable tree so I didn't continue with it. It sounds as though you have a framework for doing that sort of thing (and more) with BSD. Can you send me a pointer to the sources you're using? I'd like to look into it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 11:38:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law2-f220.hotmail.com [216.32.181.220]) by hub.freebsd.org (Postfix) with ESMTP id 40ED137B7E5; Fri, 21 Jul 2000 11:38:20 -0700 (PDT) (envelope-from odyseus00@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 21 Jul 2000 11:38:19 -0700 Received: from 63.24.202.231 by lw2fd.hotmail.msn.com with HTTP; Fri, 21 Jul 2000 GMT X-Originating-IP: [63.24.202.231] From: "David B" To: hackers@freebsd.org, hardware@freebsd.org Subject: Intel 815E Date: Fri, 21 Jul 2000 14:38:19 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 21 Jul 2000 18:38:19.0758 (UTC) FILETIME=[D77148E0:01BFF342] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if anyone is using a motherboard with the Intel 815E chipset. If so did you get the onboard video and sound to work?(not that is overly important, I would popin an ATI xpert 98 8MB if need be). And if so, which frebsd 3.4S, 5.0C or somewhere in between? I was thinking of the ABIT SE-6, in particular. To my knowlegde Intel, Asus and Abit are considered good manufacturers. What are some others? and which are the manufacturers to avoid? In particular, I was wondering about DFI they cost less but are their products stable or problematic? Thanks, David ________________________________________________________________________ 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 Fri Jul 21 11:50:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id B459D37B5A0 for ; Fri, 21 Jul 2000 11:50:38 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA25329; Fri, 21 Jul 2000 11:50:35 -0700 (PDT) Message-ID: <39789B7B.FB8F86ED@isi.edu> Date: Fri, 21 Jul 2000 11:50:35 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en, de MIME-Version: 1.0 To: cort@fsmlabs.com Cc: Alan Cox , hackers@freebsd.org Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <20000721121457.R26237@medea.fsmlabs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cort@fsmlabs.com wrote: > We started losing performance with the idle page clearing so > I've disabled it and haven't done much with it in quite a while. The code > has fallen into disrepair and some has been removed in the latest > versions. I'd suggest looking at the early 2.3.x and 2.2.1[23] series of > Linux kernels. That's where it was doing its best. Thanks. I'll get that version. > How do you keep track of what parts of a page are used? In Linux I was > just pulling pages off the free-list and zero-ing them. Do you have a > bitmap of used regions within pages on BSD? My mistake. FreeBSD zeroes the whole page as well. I traced through the code incorrectly. > I wanted a few bits for each page to describe its state: zero'd, > non-zero'd, busy being zero'd. It would have taken some changes to the > non-arch Linux code to do that and at the time we were moving to a more > stable tree so I didn't continue with it. It sounds as though you have a > framework for doing that sort of thing (and more) with BSD. Can you send > me a pointer to the sources you're using? I'd like to look into it. I'm running FreeBSD-stable right now, though I may switch to -current if I get promising results, to make it easier to merge. (There is a web interface to the FreeBSD CVS tree at http://www.freebsd.org/support.html#cvs). FYI, I'm interest in this for my thesis, which consists of two parts: (1) utilizing idle resources (cpu, memory, disk/network I/O, disk/memory space) for non-interfering background processing (i.e. run processes/threads using *only* idle capacities); and (2) to use that mechanism for speculative techniques. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 11:54: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hq.fsmlabs.com (hq.fsmlabs.com [209.155.42.197]) by hub.freebsd.org (Postfix) with ESMTP id 0D41337B7C2 for ; Fri, 21 Jul 2000 11:54:06 -0700 (PDT) (envelope-from cort@medea.fsmlabs.com) Received: from medea.fsmlabs.com (medea.fsmlabs.com [209.155.42.137]) by hq.fsmlabs.com (8.9.3/8.9.3) with ESMTP id MAA28041; Fri, 21 Jul 2000 12:53:42 -0600 Received: (from cort@localhost) by medea.fsmlabs.com (8.9.3/8.9.3) id MAA02492; Fri, 21 Jul 2000 12:46:11 -0600 Date: Fri, 21 Jul 2000 12:46:11 -0600 From: cort@fsmlabs.com To: Lars Eggert Cc: Alan Cox , hackers@freebsd.org Subject: Re: clearing pages in the idle loop Message-ID: <20000721124611.Y26237@medea.fsmlabs.com> References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <20000721121457.R26237@medea.fsmlabs.com> <39789B7B.FB8F86ED@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us In-Reply-To: <39789B7B.FB8F86ED@isi.edu>; from larse@ISI.EDU on Fri, Jul 21, 2000 at 11:50:35AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darn. I was hoping you had some mechanism for tracking that. Have you seen how quicklists work on Linux? They setup page directories after they've been freed so the whole things don't need to be cleared when allocated. I thought you could do something like that with page clearing instead if you had such a mechanism. } My mistake. FreeBSD zeroes the whole page as well. I traced through the } code incorrectly. Great, I'll take a look. Keep me up-to-date if you can, please. } I'm running FreeBSD-stable right now, though I may switch to -current if I } get promising results, to make it easier to merge. (There is a web } interface to the FreeBSD CVS tree at } http://www.freebsd.org/support.html#cvs). } } FYI, I'm interest in this for my thesis, which consists of two parts: (1) } utilizing idle resources (cpu, memory, disk/network I/O, disk/memory space) } for non-interfering background processing (i.e. run processes/threads using } *only* idle capacities); and (2) to use that mechanism for speculative } techniques. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 12: 6:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 9C3A037BE0A for ; Fri, 21 Jul 2000 12:06:26 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id MAA19989; Fri, 21 Jul 2000 12:06:16 -0700 (PDT) (envelope-from dillon) Date: Fri, 21 Jul 2000 12:06:16 -0700 (PDT) From: Matt Dillon Message-Id: <200007211906.MAA19989@earth.backplane.com> To: Lars Eggert Cc: Alan Cox , hackers@FreeBSD.ORG, cort@cs.nmt.edu Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Alan Cox wrote: :> Last year, I tried to reproduce some of the claims/results :> in this paper on FreeBSD/x86 and couldn't. I also tried :> limiting the idle loop to clearing pages of one particular :... : :> Finally, it's possible that having these pre-zeroed pages :> in your L2 cache might be beneficial if they get allocated :> and used right away. FreeBSD's idle loop zeroes the pages :> that are next in line for allocation. : :That makes sense. Other factors that may have an impact: : : * if you always have enough zeroed pages remaining over your : benchmark (> ~1/2 free pages), FreeBSD will never do the : idle-time zeroing : : * it looks to me as if Cort's Linux code will always zero whole : pages, while the FreeBSD code is a little smarter and only zeroes : used regions of a page (less impact on caches?) : : * cache size differences between PPC and i386? : :I'm looking at Cort's code (arch/ppc/kernel/idle.c), and while he turns off :the caching for pages he zeroes, I don't see him disabling the L1/2 caches :... :Lars :-- :Lars Eggert Information Sciences Institute Since the only effect of a cache miss is less efficient use of the cpu, and since the page zeroing only occurs when the cpu is idle, I would not expect to see much improvement from attempts to refine the page-zeroing operation (beyond the simple hysteresis that FreeBSD uses now and perhaps being able to bypass the cache). The hysteresis in the idle loop's page-zeroing effectively decouples the page-zeroing operation (and any loss of cache) from the processes benefiting from the availability of pre-zero'd pages. The real benefit occurs on a medium-to-heavily loaded machine which is NOT cpu bound. Since nearly all page allocations require zero'd pages, having a pool of pre-zero'd pages significantly reduces allocation latency at just the time the process doing the allocation can best benefit from it. In a cpu-bound system, the idle loop does not run as often (or at all) and no pre-zeroing occurs anyway. In regards to just zeroing the pieces of a page that need zeroing - this is NOT an optimization designed for the idle-loop page-zeroing code. I would not expect such an optimization to have any effect on idle-loop page zeroing performance. The partial-zeroing code is actually designed to handle filling in missing spots when a device-backed block (devices use a 512 byte base blocking factor) is mapped into memory (which requires a page-sized blocking factor). For example, when you map the end of a file and the file size is not page-aligned. The block device underlying the filesystem has a 512-byte native blocking factor and the filesystem itself (UFS) will typically have a 1K fragment blocking factor at the end of the file, which means that the physical disk I/O via the filesystem device may not cover an entire MMU page (4K for i386). The filesystem code doesn't give a damn whether the filesystem buffer it is reading the data into is zero'd beyond the EOF of the file. In fact, we don't even bother to zero that area... UNTIL that particular page is mapped by some user process. That is the point where the partial page-zeroing code comes into play. It has nothing to do with the idle loop pre-zeroing but since its a generic routine (part of the VM core), the idle loops happens to call it generically. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 12:10:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 840BE37BE0A; Fri, 21 Jul 2000 12:10:38 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id MAA20045; Fri, 21 Jul 2000 12:10:36 -0700 (PDT) (envelope-from dillon) Date: Fri, 21 Jul 2000 12:10:36 -0700 (PDT) From: Matt Dillon Message-Id: <200007211910.MAA20045@earth.backplane.com> To: Essenz Consulting Cc: "Kenneth D. Merry" , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Intel 840 Chipset Discontinue References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Apparently it affects all boards that the Intel 840 chipset. : :Yeah, it does suck that the 370DLx boards dont have AGP, but for a server :you can still find old PCI video cards. Voodoo 3 2000's (available for PCI or AGP) make great workstation video cards. About $100 and you get all the speed, resolution, and color depth you'll ever need for X short of playing hardcore games. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 12:44:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id A464F37BE6E for ; Fri, 21 Jul 2000 12:44:06 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id MAA01630; Fri, 21 Jul 2000 12:44:03 -0700 (PDT) Message-ID: <3978A802.E05CC45@isi.edu> Date: Fri, 21 Jul 2000 12:44:02 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Matt Dillon Cc: Alan Cox , hackers@FreeBSD.ORG, cort@cs.nmt.edu Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <200007211906.MAA19989@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > :Alan Cox wrote: > :> Last year, I tried to reproduce some of the claims/results > :> in this paper on FreeBSD/x86 and couldn't. I also tried > :> limiting the idle loop to clearing pages of one particular > :... > : > :> Finally, it's possible that having these pre-zeroed pages > :> in your L2 cache might be beneficial if they get allocated > :> and used right away. FreeBSD's idle loop zeroes the pages > :> that are next in line for allocation. > : > :That makes sense. Other factors that may have an impact: > : > : * if you always have enough zeroed pages remaining over your > : benchmark (> ~1/2 free pages), FreeBSD will never do the > : idle-time zeroing > : > : * it looks to me as if Cort's Linux code will always zero whole > : pages, while the FreeBSD code is a little smarter and only zeroes > : used regions of a page (less impact on caches?) > : > Since the only effect of a cache miss is less efficient use of > the cpu, and since the page zeroing only occurs when the cpu is idle, > I would not expect to see much improvement from attempts to refine > the page-zeroing operation (beyond the simple hysteresis that FreeBSD > uses now and perhaps being able to bypass the cache). The reason why I'm interested in Cort's results is that I'd like to extend processing in the idle loop to other things (see my other mail). Cort measured a performance decrease of foreground processing, due to polluted caches after idle-time processing. We're discussing if disabling caches during the idle loop may prevent that. > The real benefit occurs on a medium-to-heavily loaded machine which is > NOT cpu bound. Since nearly all page allocations require zero'd pages, > having a pool of pre-zero'd pages significantly reduces allocation > latency at just the time the process doing the allocation can best > benefit from it. In a cpu-bound system, the idle loop does not run > as often (or at all) and no pre-zeroing occurs anyway. I agree. However, on a medium-to-heavily loaded CPU, you'd probably see the largest decrease of foreground performance, as the idle times are short and bursty, and so your caches may get polluted more frequently. (Assuming cache pollution is in fact a problem; Allan seems to not think so.) If Allan still has his patches, I'll run some experiments, so we have some numbers to talk about. Maybe it doesn't matter. > In regards to just zeroing the pieces of a page that need zeroing - this > is NOT an optimization designed for the idle-loop page-zeroing code. I made a mistake tracing through the code. Sorry. But it may be interesting to speculate if this would speed things up. Would probably require MMU support though. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 13:44: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 27CA437C241 for ; Fri, 21 Jul 2000 13:43:55 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA18926 for ; Fri, 21 Jul 2000 16:42:44 -0400 (EDT) Date: Fri, 21 Jul 2000 16:40:22 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: memory type and its size In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jul 2000, Zhihui Zhang wrote: > > Does kernel memory of the same type (e.g., M_TEMP) must be allocated > (using malloc()) with the same (range of) size? BTW, how to display mbuf > cluster usages info. Thanks. A memory type can have memory blocks with different sizes. Use netstat -m to display mbuf cluster usages. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 13:46: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id DF4A937BF0B for ; Fri, 21 Jul 2000 13:45:55 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA19655 for ; Fri, 21 Jul 2000 16:45:53 -0400 (EDT) Date: Fri, 21 Jul 2000 16:43:30 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: KLD, kernel threads, zone allocator In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Zhihui Zhang wrote: > > I am writing a KLD that gives me kernel fault each time I run 'ps' command > after 'make unload'. The KLD has a system call to create several kernel > threads by calling kthread_create(). During unload, I set flags to each > threads so that they will call exit1() upon wakeup (sleep on a timeout). > Before the last thread calls exit1(), it wakeup the kld unload process so > that make 'unload' can finish. Is there anything wrong or better > solutions? > > I also use vm_zone to allocate some data structes within the KLD. When > unloading, I can use zfree() to free them except the zone header that I > can not free(some_zone, M_ZONE). This is because M_ZONE is defined as > *static* in vm_zone.c I wonder if this will cause memory leak after > several loading and unloading the KLD. > > Finally, I want to know how to save the panic screen without hand writing > it down. Any info on debugging under db> after fault? > > Any help is appreciated. Thanks to those who have helped me privately. It is not a good idea to use zone allocator with KLD. You must clear everything before unloading the KLD. Any kernel threads can be reparented to initproc to avoid 'ps' panic. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14: 4:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id A152337BF47 for ; Fri, 21 Jul 2000 14:04:10 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id OAA00411; Fri, 21 Jul 2000 14:04:08 -0700 (PDT) (envelope-from ulf) Date: Fri, 21 Jul 2000 14:04:08 -0700 From: Ulf Zimmermann To: Ulf Zimmermann Cc: hackers@FreeBSD.ORG Subject: Re: Maybe OT, maybe not Message-ID: <20000721140408.L79232@PacHell.TelcoSucks.org> Reply-To: ulf@alameda.net References: <20000718152043.A18798@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000718152043.A18798@PacHell.TelcoSucks.org>; from ulf@alameda.net on Tue, Jul 18, 2000 at 03:20:44PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 18, 2000 at 03:20:44PM -0700, Ulf Zimmermann wrote: > Hello, > > I got a problem I need to get "solved" as fast as possible. I have here > a firewall box (FreeBSD based, yeah!) and need to test this in conjunction > with web crawling. Our current FW1 based Sun firewalls die very fast. > > I need to emulate about 9,000 or more concurrent open tcp sessions. Each > session should be random sized from 500 to maybe 20,000 bytes data transferred. > In addition to these I need x amount of initiated tcp sessions which never > get answered. FW1 with its tcp connection table will create an entry for > these "failed" sessions and hold it up to its time out. Our crawlers do not. > > So I am basicly looking for a load generator and a "server". Anyone got > something laying around like that ? Ok, I got some suggestions, but let me the whole thing. What do I have to test ? I need to test the ability of the firewall, which keeps a session table, to handle several ten thousand entries. Why so many ? Our current crawlers will create 300 tcp session max. It will try to start a tcp session for a destination (tcp proctocol syn packet). The firewall will now create an entry in the session table. If the remote site never answers (not reachable, down, etc) the crawler will time out the tcp session after like 1 minute, but the firewall (because it never sees another packet) will not time it out before like 5 minutes (by default its even 30 minutes). So depending on how many dead sites we hit, we are having about 9,000 active tcp sessions (30 crawlers at 300 sessions a machine) plus several thousand to tenthousands of dead entries on the firewall. My current test scenario seems to run out to this: http servers (something light weight, serving files from memory, no logging) |||| [firewall] |||| load generator. The direction I am kinda thinking about the load generator is something like a main thread which spawns off maybe 2,000 threads (if I can do so many or maybe more), each thread using maybe libfetch to generate a http request to either a real server on the other side or by sending a request to a non existing ip to simulate dead sites. It then needs to timeout after lets say 30 seconds to leave the dead entry on the firewall. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14:44:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 3E23937B6F4; Fri, 21 Jul 2000 14:44:48 -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 OAA01169; Fri, 21 Jul 2000 14:54:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007212154.OAA01169@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Essenz Consulting Cc: hackers@freebsd.org, hardware@freebsd.org Subject: Re: Intel 840 Chipset Discontinue In-reply-to: Your message of "Fri, 21 Jul 2000 12:31:58 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 14:54:07 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was told by several of my distributors that all motherboards based off > of the Intel 840 chipset are being discontinued. That means the Supermicro > PIIDM3 and PIIIDME, and any other 840 board. I have mixed feelings about this, but on the whole I think it's probably for the best. I've had really patchy results with the i840, and performance hasn't been impressive. > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > have also been hearing bad news about these boards as well. We've had some issues with the RCC chipsets in Dell systems, yes. > Has anyone worked with these boards? Supermicro SAYS that they work fine > under Linux and Solaris. However, one of my distributors says thay they > are extremely touchy when it comes to memory. Only Registered PC133 ECC > memory will work. > > If someone at freebsd.org wants to seriously test these boards, let me > know, and I'll donate one. Without the 840 boards, server configs are now > back to the 440GX days! FreeBSD Test Labs would very much appreciate the opportunity to beat one of these boards up in the name of science. If you don't have a better taker, you can send us one at: FreeBSD Test Labs BSDi Open Source Solutions 4041 Pike Lane #F Concord, CA 94520 Thanks for the offer! -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14:49:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 200-191-156-142-as.acessonet.com.br (bsa-1-as02-7-a01.gd.uol.com.br [200.197.118.65]) by hub.freebsd.org (Postfix) with ESMTP id F2F0C37B76B for ; Fri, 21 Jul 2000 14:48:50 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 61280 invoked by uid 1001); 21 Jul 2000 20:58:19 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Fri, 21 Jul 2000 17:57:57 -0300 To: freebsd-hackers@freebsd.org Subject: sysutils/memtest and FreeBSD Message-ID: <20000721175757.B319@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just added sysutils/memtest to the FreeBSD ports tree a couple of days ago. It is a utility to test for faulty memory subsystem. However, I've been having some problems with it. They are not fatal, but really annoying. I am in contact with the author to try working them out. Nonetheless, I would like to see if ppl on the -hackers forum could help me out with the following problem: I noticed that using 'memtest all' would produce core dump on my -stable as of 18/07/2000. Backtracing showed that the problem was due to the malloc function inside the get_mem function. get_mem() is used to find out the largest possible memory segment. It incrementaly reduces the segment passed to malloc to alloc. It is the malloc function allright. It core dumps on the 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( #0 0x280dda41 in isatty () from /usr/lib/libc.so.4 #1 0x280ddd91 in isatty () from /usr/lib/libc.so.4 #2 0x280de4c5 in malloc () from /usr/lib/libc.so.4 #3 0x8049427 in get_mem () at memtest.c:338 #4 0x8048bc5 in main (argc=2, argv=0xbfbff62c) at memtest.c:175 #5 0x80488e1 in _start () Instead of just returning a null pointer, it core dumps. I am not using any /etc/malloc.conf options at all. I know that 'A' could produce this. Following some instructions from the author, I tried an odd change ... since that is his baby not mine. However, it did not work. On Thu, Jul 20, 2000 at 08:12:12PM -0600, Charles Cazabon wrote: > Mario Sergio Fujikawa Ferreira wrote: > > Try changing line 103 to allocate a buffer of 256 bytes instead of 100 bytes. > I haven't looked at that line in a long time. The output messages may be > longer than that now. > > If that's not it, it's crashing during the memory allocation phase. I twould > take some additional debugging to figure out where. It did not work. 'memtest all' still core dumps. By the way, one bug that is not FreeBSD related though, whenever I try 'memtest 4G': --- ./memtest 4G memtest v. 2.93.1 (C) 2000 Charles Cazabon Original v.1 (C) 1999 Simon Kirby ./memtest: amount of memory to allocate too small. --- Nonetheless, using 1G, 2G, 3G and 5G work. Just to mention. Don't worry about it. I am not touching the bit wise code now. I am leaving that to the author. I am worried about the core dump amongst other projects now. Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14:49:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 200-191-156-142-as.acessonet.com.br (bsa-1-as02-7-a01.gd.uol.com.br [200.197.118.65]) by hub.freebsd.org (Postfix) with ESMTP id 4BA9C37C1BD for ; Fri, 21 Jul 2000 14:49:36 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 56270 invoked by uid 1001); 21 Jul 2000 21:45:20 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Fri, 21 Jul 2000 18:44:58 -0300 To: freebsd-hackers@freebsd.org Subject: /etc/defaults/make.conf:LEAPSECONDS= true? Message-ID: <20000721184458.B68315@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if this should go inside /etc/defaults/make.conf. --- /usr/src/etc/defaults/make.conf Sun Jul 16 05:30:30 2000 +++ /tmp/make.conf Fri Jul 21 18:42:35 2000 @@ -41,6 +41,9 @@ # To build perl with thread support #PERL_THREADED= true # +# Compile zoneinfo with correct leap second handling +#LEAPSECONDS= true +# # To avoid building various parts of the base system: #NO_CVS= true # do not build CVS #NO_BIND= true # do not build BIND If it does not, where in the handbook should I drop a note about it, besides FAQ (of course). Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14:55:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hula.maui.net (ns1.maui.net [207.175.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 01AC737C0FE for ; Fri, 21 Jul 2000 14:55:33 -0700 (PDT) (envelope-from webtrix@maui.net) Received: from trix (trix.maui.net [207.12.26.142]) by hula.maui.net (8.8.7/8.8.5) with ESMTP id LAA02175 for ; Fri, 21 Jul 2000 11:55:29 -1000 (HST) Message-Id: <4.2.2.20000721115609.00affe10@pop.maui.net> X-Sender: selina2@pop.maui.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 21 Jul 2000 11:56:58 -1000 To: freebsd-hackers@FreeBSD.ORG From: Selina Subject: Please Remove Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please remove systech@maui.net, or sysadim@maui.net from you list.. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 14:56: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hula.maui.net (ns1.maui.net [207.175.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 9561C37BEA1 for ; Fri, 21 Jul 2000 14:56:04 -0700 (PDT) (envelope-from webtrix@maui.net) Received: from trix (trix.maui.net [207.12.26.142]) by hula.maui.net (8.8.7/8.8.5) with ESMTP id LAA02206 for ; Fri, 21 Jul 2000 11:56:02 -1000 (HST) Message-Id: <4.2.2.20000721115705.00b03260@pop.maui.net> X-Sender: selina2@pop.maui.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 21 Jul 2000 11:57:31 -1000 To: freebsd-hackers@FreeBSD.ORG From: Selina Subject: Fwd: /etc/defaults/make.conf:LEAPSECONDS= true? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Please remove To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 16:36: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mike.dhis.org (hiper4-d36.stk.cwnet.com [209.142.57.36]) by hub.freebsd.org (Postfix) with ESMTP id B61D937C171; Fri, 21 Jul 2000 16:35:55 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from ogre (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with SMTP id 6452DD5; Fri, 21 Jul 2000 16:35:43 -0700 (PDT) Message-ID: <001401bff36c$63943ca0$0164a8c0@lan> From: "Mike Muir" To: , , Subject: Specific video hardware support with the advent of the Linux A|W Maya port. Date: Fri, 21 Jul 2000 16:35:43 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently, Alias|Wavefront announced they would port Maya to Linux. Assuming FreeBSD can emulate the linux binary's (and I have no reason to think that it won't) then what about support for video hardware (high, mid and consumer -end) which requires more than just a suitable X server? Take the case of Nvidia's linux drivers which are comprised of a kernel module which interfaces with the XFree86 4.0/4.0.1 driver also provided. I havn't looked into the drivers as I lack the knowledge and experience to even fathom porting to a freebsd kernel module. I understand there is an element of closed source with these drivers but i'm unsure whether this is at the module, or the XFree driver.. to cut to the chase, my question is whether the porting of a driver such as these is the onus of a FreeBSD contributer, or is it at Nvidia's discretion? Assuming the element of closed source works under FreeBSD, then how easy would a port like this be? Or is somebody working on this case [nvidia's 5.xx linux drivers for Xfree86 4.*] as I comment? On a wider scale, if a vendor provides a driver, or server for X and their hardware (lets say a particularly high end piece of equipment such as an Intergraph Wildcat) perhaps specifically with the intention for a Linux distrubtion which is to be packaged along with this Intergraph system, would it be reasonable to assume this would also work under FreeBSD or would the vendor be required to specifically write a version of their driver or server for FreeBSD? The reason I ask is that I see no reason why the growing field of animators using tools such as A|W Maya shouldn't opt to use FreeBSD over Linux (red hat at that) while they're on their way migrating from NT -- OR kicking off their endevours. What are (if any) the road blocks which could stop this from happening? -mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 21 17: 2:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 71EC737C29E for ; Fri, 21 Jul 2000 17:02:45 -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 e6M02iD05553 for ; Fri, 21 Jul 2000 17:02:45 -0700 (PDT) Date: Fri, 21 Jul 2000 17:02:44 -0700 (PDT) From: Doug White To: hackers@freebsd.org Subject: suprising mount root behavior Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Some new root mount behavior in 4.0 just saved my bacon, but I'm curious as to how it's implemented. My custom installer accidentally created fstab entries for IDE disks on a SCSI-only system. Thus, fstab point to /dev/ad0s1a for / and /dev/ad0s1b for swap. I rebooted the system to try and fix it, and lo and behold it booted up correctly! I had no swap but root was mounted RW so I could fix the fstab. Now my question is: How did it know? I'm not setting vfs.root.mountfrom in the loader. Also, how did mount know to not override the / mountpoint to the one from fstab (and subsequently fail)? 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 Fri Jul 21 17:24:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 66C9337C51A for ; Fri, 21 Jul 2000 17:22:29 -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 RAA02106; Fri, 21 Jul 2000 17:31:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007220031.RAA02106@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug White Cc: hackers@freebsd.org Subject: Re: suprising mount root behavior In-reply-to: Your message of "Fri, 21 Jul 2000 17:02:44 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jul 2000 17:31:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Some new root mount behavior in 4.0 just saved my bacon, but I'm curious > as to how it's implemented. 8) > My custom installer accidentally created fstab entries for IDE disks on a > SCSI-only system. Thus, fstab point to /dev/ad0s1a for / and /dev/ad0s1b > for swap. > > I rebooted the system to try and fix it, and lo and behold it booted up > correctly! I had no swap but root was mounted RW so I could fix the > fstab. > > Now my question is: How did it know? I'm not setting vfs.root.mountfrom > in the loader. > > Also, how did mount know to not override the / mountpoint to the one from > fstab (and subsequently fail)? There's a complex order of battle associated with mounting /. 8) You can read /sys/kern/vfs_conf.c:vfs_mountroot() and associated stuff to get the gory details, but the bottom line is that there are several layers of fallback, and you were saved by the one that looks at the major and minor numbers passed in by the bootloader and tries them if the fstab entry fails. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 22 5:54:58 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 CCE3937B678 for ; Sat, 22 Jul 2000 05:54:55 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny4-09.ix.netcom.com [198.211.16.201]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id IAA00225; Sat, 22 Jul 2000 08:54:53 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id IAA00360; Sat, 22 Jul 2000 08:54:49 -0400 (EDT) (envelope-from vsilyaev) Date: Sat, 22 Jul 2000 08:54:49 -0400 (EDT) From: "Vladimir N. Silyaev" Message-Id: <200007221254.IAA00360@jupiter.delta.ny.us> To: blaze@infosec.ru Cc: hackers@freebsd.org Subject: Re: open() error In-Reply-To: References: Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suppose that iso9660 filesystem doesn't support locking ability, UFS does. Vladimir In muc.lists.freebsd.hackers, you wrote: >Hello. > >I've noticed a strange error in open() syscall: when system booted with a >CD as root (boot -C) the following code fails with EINVAL: > >fd = open(c, O_RDONLY | O_NONBLOCK | O_EXLOCK, 0) > >When root is hdd with UFS (mounted read-only), this works fine. > >Is it a bug or i missed something? > > > >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 Sat Jul 22 6:53:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 04CBC37B7FF; Sat, 22 Jul 2000 06:53:30 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6MDrCn19806 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sat, 22 Jul 2000 15:53:15 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6MDqhq59274; Sat, 22 Jul 2000 15:52:44 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id PAA27477; Sat, 22 Jul 2000 15:52:39 +0200 (CEST) (envelope-from ticso) Date: Sat, 22 Jul 2000 15:52:38 +0200 From: Bernd Walter To: Greg Lehey Cc: Geoff Buckingham , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000722155238.A27452@cicely8.cicely.de> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000720183341.I30599@wantadilla.lemis.com>; from grog@lemis.com on Thu, Jul 20, 2000 at 06:33:42PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 20, 2000 at 06:33:42PM +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > A thing that might bite you here is that ufs is currently limited to 1 > TB per volume. Vinum doesn't have that restriction: if you want to > create a 20 TB volume, and you know how to use the space, Vinum should > work. The problem with ufs is that the block numbers in the inodes > are 32 bit signed values. With 512 byte sectors, the only we can do > it, that means a total address space of 2**9 * 2*31, or 1 TB. At some > time I suspect we're going to need to fix that. Block numbers in inodes are not physical blocks (named sectorsize in UFS source) but logical which is equal to the size of an fragment and thus defaults to 1k. The problem is the driver and VM layer. If vinum would simulate 2k "physical" blocksize it may go up to 4TB if you set the fragment size to 4k. I don't know if any middle calculation might harm or VM is missbehaving. The point I never digged deeper here is because you already sugested changing the driver layer to 64bit byte numbers which was accepted if I remember right. Some of the systems I've setup are near this Limit so I spend some time to find out where the show stoppers are. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 22 7: 2:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id F412837B52F; Sat, 22 Jul 2000 07:02:44 -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 QAA00262; Sat, 22 Jul 2000 16:01:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bernd Walter Cc: Greg Lehey , Geoff Buckingham , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume In-reply-to: Your message of "Sat, 22 Jul 2000 15:52:38 +0200." <20000722155238.A27452@cicely8.cicely.de> Date: Sat, 22 Jul 2000 16:01:59 +0200 Message-ID: <260.964274519@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000722155238.A27452@cicely8.cicely.de>, Bernd Walter writes: >The point I never digged deeper here is because you already sugested >changing the driver layer to 64bit byte numbers which was accepted if >I remember right. Yes, I have this on my plate. -- 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 22 7:22:16 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 D217537B990; Sat, 22 Jul 2000 07:22:10 -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 KAA19661; Sat, 22 Jul 2000 10:22:09 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA57645; Sat, 22 Jul 2000 10:22:09 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 22 Jul 2000 10:22:08 -0400 (EDT) To: Essenz Consulting Cc: Mike Smith , hackers@freebsd.org, hardware@freebsd.org Subject: Re: Intel 840 Chipset Discontinue In-Reply-To: <200007212154.OAA01169@mass.osd.bsdi.com> References: <200007212154.OAA01169@mass.osd.bsdi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14713.42924.81417.759293@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > I was told by several of my distributors that all motherboards based off > > of the Intel 840 chipset are being discontinued. That means the Supermicro > > PIIDM3 and PIIIDME, and any other 840 board. Hurray! ;-) > I have mixed feelings about this, but on the whole I think it's probably > for the best. I've had really patchy results with the i840, and > performance hasn't been impressive. While, on the other hand, I cannot say enough good things about the performance of our Dell PowerEdge 2400 & 4400 machines (both use RCC chipsets). What else can you say about machines that will serve NFS over via gig ether at over 70MB/sec and not break a sweat ;) > > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > > have also been hearing bad news about these boards as well. > > We've had some issues with the RCC chipsets in Dell systems, yes. All of these are now resolved, aren't they? > > Has anyone worked with these boards? Supermicro SAYS that they work fine > > under Linux and Solaris. However, one of my distributors says thay they > > are extremely touchy when it comes to memory. Only Registered PC133 ECC > > memory will work. This memory requirement probably explains why they perform so well ;) The RCC chipsets, especially those which use interleaved memory like in the PE4400, have stunningly good I/O bandwidth for a PC. They have over 440MB/sec of I/O bandwidth to a 64-bit 66MHz PCI bus (I've actually measured it, yes). They run gig ether at 950Mb/sec with stock kernels and I've run protype Myrinet boards at over 2Gb/sec end-to-end with TCP using the zero-copy sockets framework that Ken Merry has been talking about. > > If someone at freebsd.org wants to seriously test these boards, let me > > know, and I'll donate one. Without the 840 boards, server configs are now > > back to the 440GX days! We've got a big purchase coming up & I'd love to get my hands on one of them for testing, but FreeBSD test labs should get priority. FWIW, I'm mainly an alpha port committer, but I'm the one who fixed the RCC peer bus probing issues when we got our Dell 2400 a few months back.. Anyway, we're looking to replace some of our cluster & would be looking for 16-24 nodes of them. We were originally planning to get Alpha DS10Ls, but the availability of RCC chipsets in a small form factor may change our minds as the RCC chipset is the only thing that can compete with the alpha's Tsunami chipset for I/O bandwidth. Do you know of anybody building 1U or 2U rackmount systems for a reasonable price ($2000/node or less) around these motherboards? It looks like most integrators are using the L44GX & its broken 32-bit 66MHz slot which runs at the wrong voltage (Myrinet claims they're violating the PCI spec). 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 Sat Jul 22 8: 2:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 420C237B5C5 for ; Sat, 22 Jul 2000 08:02:10 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p15-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.80]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA02730; Sun, 23 Jul 2000 00:01:59 +0900 (JST) Message-ID: <3979B777.A8AD8511@newsguy.com> Date: Sun, 23 Jul 2000 00:02:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sysutils/memtest and FreeBSD References: <20000721175757.B319@Fedaykin.here> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > > Backtracing showed that the problem was due > to the malloc function inside the get_mem function. > get_mem() is used to find out the largest possible memory segment. > It incrementaly reduces the segment passed to malloc to alloc. > It is the malloc function allright. It core dumps on the > 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( Because FreeBSD overcommits, malloc() will only fail in case of artificial limits being reached (like those of login.conf). If FreeBSD suddenly finds itself in a position of not being able to meet the previous commitments wrt to memory allocation, it will kill the application with the largest memory allocations. I'll bet you the fifth season of Babylon 5 this is what's happening. :-) Try limiting the maximum memory allocation to the total physical RAM. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 22 8: 4:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8591937B5C5 for ; Sat, 22 Jul 2000 08:04:31 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p15-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.80]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA03330; Sun, 23 Jul 2000 00:04:24 +0900 (JST) Message-ID: <3979B809.AEADE6E1@newsguy.com> Date: Sun, 23 Jul 2000 00:04:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/defaults/make.conf:LEAPSECONDS= true? References: <20000721184458.B68315@Fedaykin.here> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > > I was wondering if this should go inside > /etc/defaults/make.conf. Submit a PR. > --- /usr/src/etc/defaults/make.conf Sun Jul 16 05:30:30 2000 > +++ /tmp/make.conf Fri Jul 21 18:42:35 2000 > @@ -41,6 +41,9 @@ > # To build perl with thread support > #PERL_THREADED= true > # > +# Compile zoneinfo with correct leap second handling > +#LEAPSECONDS= true > +# > # To avoid building various parts of the base system: > #NO_CVS= true # do not build CVS > #NO_BIND= true # do not build BIND > > If it does not, where in the handbook should > I drop a note about it, besides FAQ (of course). > > Regards, > Mario Ferreira > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 22 10:39:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 0C5E437C2F5 for ; Sat, 22 Jul 2000 10:39:12 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id KAA31376; Sat, 22 Jul 2000 10:39:08 -0700 (PDT) (envelope-from dillon) Date: Sat, 22 Jul 2000 10:39:08 -0700 (PDT) From: Matt Dillon Message-Id: <200007221739.KAA31376@earth.backplane.com> To: Lars Eggert Cc: Alan Cox , hackers@FreeBSD.ORG, cort@cs.nmt.edu Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <200007211906.MAA19989@earth.backplane.com> <3978A802.E05CC45@isi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Since the only effect of a cache miss is less efficient use of :> the cpu, and since the page zeroing only occurs when the cpu is idle, :> I would not expect to see much improvement from attempts to refine :> the page-zeroing operation (beyond the simple hysteresis that FreeBSD :> uses now and perhaps being able to bypass the cache). : :The reason why I'm interested in Cort's results is that I'd like to extend :processing in the idle loop to other things (see my other mail). Cort :measured a performance decrease of foreground processing, due to polluted :caches after idle-time processing. We're discussing if disabling caches :during the idle loop may prevent that. I think what you are observing may not be cache-related at all, but may simply be the fact that zeroing a page takes a minimum amount of time during which another task will not be scheduled, verses that other task being scheduled instantly if all the idle loop were doing was checking for new tasks to run. :> The real benefit occurs on a medium-to-heavily loaded machine which is :> NOT cpu bound. Since nearly all page allocations require zero'd pages, :> having a pool of pre-zero'd pages significantly reduces allocation :> latency at just the time the process doing the allocation can best :> benefit from it. In a cpu-bound system, the idle loop does not run :> as often (or at all) and no pre-zeroing occurs anyway. : :I agree. However, on a medium-to-heavily loaded CPU, you'd probably see the :largest decrease of foreground performance, as the idle times are short and :bursty, and so your caches may get polluted more frequently. (Assuming :cache pollution is in fact a problem; Allan seems to not think so.) : :If Allan still has his patches, I'll run some experiments, so we have some :numbers to talk about. Maybe it doesn't matter. Another alternative is to have an idle process rather then try to do things in the idle loop. This has the advantage of being instantly interruptable if a 'real' process becomes runnable, but the disadvantage of having to do a context switch (albeit a relatively cheap one). The FreeBSD page zeroing code in the idle loop typically does not run all that often with an interactive load because interactive loads tend not to allocate memory at a high rate, so the hysteresis points do not get hit as often. Hmm. Maybe there's a bug in the hysteresis calculation, I'll check it out. -Matt :> In regards to just zeroing the pieces of a page that need zeroing - this :> is NOT an optimization designed for the idle-loop page-zeroing code. : :I made a mistake tracing through the code. Sorry. : :But it may be interesting to speculate if this would speed things up. Would :probably require MMU support though. : :Lars :-- :Lars Eggert Information Sciences Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 22 14:15:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bsa-1-as01-7-a52.gd.uol.com.br (bsa-1-as01-7-a52.gd.uol.com.br [200.197.118.52]) by hub.freebsd.org (Postfix) with ESMTP id E061737BA01 for ; Sat, 22 Jul 2000 14:15:16 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 511 invoked by uid 1001); 22 Jul 2000 21:13:52 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Sat, 22 Jul 2000 18:13:30 -0300 To: "Daniel C. Sobral" Cc: Mario Sergio Fujikawa Ferreira , freebsd-hackers@FreeBSD.ORG Subject: Re: sysutils/memtest and FreeBSD Message-ID: <20000722181330.A404@Fedaykin.here> References: <20000721175757.B319@Fedaykin.here> <3979B777.A8AD8511@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3979B777.A8AD8511@newsguy.com>; from dcs@newsguy.com on Sun, Jul 23, 2000 at 12:01:53AM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel, On Sun, Jul 23, 2000 at 12:01:53AM +0900, Daniel C. Sobral wrote: > Mario Sergio Fujikawa Ferreira wrote: > > > > Backtracing showed that the problem was due > > to the malloc function inside the get_mem function. > > get_mem() is used to find out the largest possible memory segment. > > It incrementaly reduces the segment passed to malloc to alloc. > > It is the malloc function allright. It core dumps on the > > 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( > > Because FreeBSD overcommits, malloc() will only fail in case of > artificial limits being reached (like those of login.conf). If FreeBSD > suddenly finds itself in a position of not being able to meet the > previous commitments wrt to memory allocation, it will kill the > application with the largest memory allocations. > > I'll bet you the fifth season of Babylon 5 this is what's happening. :-) Are you willing to bet the 3rd and 4th seasons as well? The 4th season rocks. ;-) > Try limiting the maximum memory allocation to the total physical RAM. The code sets limits appropriatily with RLIMIT_MEMLOCK and RLIMIT_RSS with setrlimit(). Furthermore, I am not using any limits for the user testing the program (a can do it all user :). Besides, a failing malloc should return NULL, shouldn't it? I would have expected core if I had malloc_options="X" which I do not (in fact, I have no malloc_options). Regards, Mario Ferreira ps: Perhaps you could check the code, it is only 11K long. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message