From owner-freebsd-hackers Sun Aug 8 2:54: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id D4D8514C40 for ; Sun, 8 Aug 1999 02:54:07 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id CAA13307 for ; Sun, 8 Aug 1999 02:53:01 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AD537D.DF91F6F0@gorean.org> Date: Sun, 08 Aug 1999 02:53:01 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: perl can't manify during make upgrade Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doing a make upgrade tonight I see the following errors (bunches of them). Manifying B::Showlex.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying B::Stackobj.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying B::Terse.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying B::Xref.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying B.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying O.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying DB_File.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Manifying Data::Dumper.3 ELF interpreter /usr/libexec/ld-elf.so.1 not found I suspect that this is due to the fact that the elf libraries have been built but not installed at this point in the program, but I thought y'all might like to know. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 3: 0:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id 8A3B914E86 for ; Sun, 8 Aug 1999 03:00:21 -0700 (PDT) (envelope-from plm@smtp7.xs4all.nl) Received: from localhost. (dc2-isdn103.dial.xs4all.nl [194.109.148.103]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA19833 for ; Sun, 8 Aug 1999 11:59:10 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.3) id LAA02522; Sun, 8 Aug 1999 11:59:09 +0200 To: freebsd-hackers@freebsd.org Subject: Re: [Fwd: Please support FreeBSD 3.x as host OS] References: <87oggi92yh.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 08 Aug 1999 11:02:14 +0200 In-Reply-To: Doug's message of "Fri, 6 Aug 1999 11:43:53 -0700 (PDT)" Message-ID: <87hfmair1l.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "D" == Doug writes: D> On Fri, 6 Aug 1999 john_wilson100@excite.com wrote: >> This is kinda different from what the original poster received. >> Keep badgering! D> But ONLY if you ARE willing to pay for it if they make one. We D> don't need a repeat of the CDE debacle. In fact I bought the Linux version, and at the moment I'm running it instead of FBSD because of vmware. But I keep telling them I'd like a FBSD version. Would it be so hard to port those two kernel modules (of which the source is available) to FreeBSD? Then the vmware executable itself might run in Linux emulation. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 5:44:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D044214F1D for ; Sun, 8 Aug 1999 05:44:25 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id IAA38155 for ; Sun, 8 Aug 1999 08:43:15 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 8 Aug 1999 08:43:15 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: rc addition proposal: mixer 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 envision something like the following being available in /etc/rc, since there are many people who set mixer default values at startup in some random way. It would be nice to provide an easy way to do this. I'd like to get a vote on whether this should be added or not. I'd do something like the following: if [ -n "$mixer_device" ]; do mixer="mixer -f $mixer_device" else mixer="mixer" done for cf in `$mixer | cut -d' ' -f2` recsrc; do if eval [ -n "mixer_$cf" ]; then eval \$mixer \$cf \$mixer_$cf fi done Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sun Aug 8 9:34:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D8B1C14BB8; Sun, 8 Aug 1999 09:34:08 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port34.netsvr1.cst.vastnet.net [207.252.73.34]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA02351; Sun, 8 Aug 1999 12:26:04 -0400 (EDT) Message-Id: <199908081626.MAA02351@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 09 Aug 1999 00:41:13 -0400 To: hackers@freebsd.org From: Dennis Subject: Routing Table Memory Cc: isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What flavor of memory tuning can be used to figure out how much the routing table will have (and what tool can be used to monitor it, other than the total usage shown in vmstat)? A machine with 64M refuses to allocate more than ~10M (about 36K routes) no matter how many users or clusters are allocated. NetBSD systems have no trouble holding full tables (17M) in a 64k system. Not that 128M is so expensive, but I'd like to know how to optimize it for more efficient usage of memory. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 10:55:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id B4604150DA; Sun, 8 Aug 1999 10:55:36 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id SAA01243; Sun, 8 Aug 1999 18:51:12 +0100 (BST) (envelope-from joe) Date: Sun, 8 Aug 1999 18:51:12 +0100 From: Josef Karthauser To: hackers@freebsd.org, fs@freebsd.org Subject: Disk label recovery - request for suggestions. Message-ID: <19990808185112.A99557@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few weeks ago I had a problem with a missing partition table and disklabel. Niall Smart forwarded me a small C program for scanning a drive for superblocks and rewriting a disklabel table. I'd like to do some work on integrating this into FreeBSD because it seems too useful to leave out. At the very least it could be a stand along tool that works on UFS slices, that'd be easy. What I'm wondering though is whether it should be an extension to the disklabel program. If so, what extra work is required to make it work with non UFS file systems - is 'disklabel' used on non UFS fs's? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 12:12:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 3F4FC14BD6; Sun, 8 Aug 1999 12:12:05 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 4DDAB29A; Sun, 8 Aug 1999 23:08:56 +0400 (MSD) Date: Sun, 8 Aug 1999 23:08:56 +0400 (MSD) From: Osokin Sergey To: "Brian F. Feldman" Cc: hackers@FreeBSD.ORG Subject: Re: rc addition proposal: mixer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Brian F. Feldman wrote: > I envision something like the following being available in /etc/rc, > since there are many people who set mixer default values at startup in > some random way. It would be nice to provide an easy way to do this. > I'd like to get a vote on whether this should be added or not. > > I'd do something like the following: > > if [ -n "$mixer_device" ]; do > mixer="mixer -f $mixer_device" > else > mixer="mixer" > done > for cf in `$mixer | cut -d' ' -f2` recsrc; do > if eval [ -n "mixer_$cf" ]; then > eval \$mixer \$cf \$mixer_$cf > fi > done > Now in current i use following script (aka mixer.sh) for install sound environment: #!/bin/sh mixer vol 36 mixer synth 36 mixer pcm 36 mixer line 36 mixer cd 68 Maybe add to rc.conf all features of mixer? (aka vol, bass & etc) Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 12:37:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mpp.pro-ns.net (mpp.pro-ns.net [208.200.182.72]) by hub.freebsd.org (Postfix) with ESMTP id 9DF7214F7A for ; Sun, 8 Aug 1999 12:37:47 -0700 (PDT) (envelope-from mpp@mpp.pro-ns.net) Received: (from mpp@localhost) by mpp.pro-ns.net (8.9.3/8.9.3) id OAA04278; Sun, 8 Aug 1999 14:35:15 -0500 (CDT) (envelope-from mpp) From: Mike Pritchard Message-Id: <199908081935.OAA04278@mpp.pro-ns.net> Subject: Re: cvs In-Reply-To: <199908080332.UAA01140@vashon.polstra.com> from John Polstra at "Aug 7, 1999 08:32:42 pm" To: jdp@polstra.com (John Polstra) Date: Sun, 8 Aug 1999 14:35:15 -0500 (CDT) Cc: billf@jade.chc-chimes.com, hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article , > Bill Fumerola wrote: > > On Sat, 7 Aug 1999, Mike Pritchard wrote: > > > > > *default umask=002 > > > > SetAttrs CVSROOT/commitlogs/other.981201.gz > > > > That seems to be doing the trick for everything. Thanks. > > Note, if you would have just _run_ the program with a umask of 2 > then it would have worked too. It honors the umask setting unless > overridden in the supfile. Yes, but if I ever run cvsup by hand I wind up with cvsup going through my whole tree and resetting attributes because my default umask isn't 2. I once started up a cvsup by hand, sat down to eat/watch TV, came back and realized that cvsup had reset all of my file permissions. Putting it in the cvsup file help to make sure you don't screw yourself up by accident. -- Mike Pritchard mpp@FreeBSD.ORG or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 12:38: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id 630BC14E52; Sun, 8 Aug 1999 12:37:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA12716; Sun, 8 Aug 1999 12:31:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908081931.MAA12716@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Cc: hackers@freebsd.org, isp@freebsd.org Subject: Re: Routing Table Memory In-reply-to: Your message of "Mon, 09 Aug 1999 00:41:13 EDT." <199908081626.MAA02351@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Aug 1999 12:31:15 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What flavor of memory tuning can be used to figure out how much the routing > table will have (and what tool can be used to monitor it, other than the > total usage shown in vmstat)? > > A machine with 64M refuses to allocate more than ~10M (about 36K routes) no > matter how many users or clusters are allocated. NetBSD systems have no > trouble holding full tables (17M) in a 64k system. > > Not that 128M is so expensive, but I'd like to know how to optimize it for > more efficient usage of memory. Route entries are just allocated out of the kernel memory pool; I would suggest upping VM_KMEM_SIZE (size of kernel memory in bytes), either as a compile-time option or using the kern.vm.kmem.size tunable as documented in 'help set tunables' inside the loader (may not be available in the version you're using depending on how you're set up). You might also try setting VM_KMEM_SIZE_SCALE to something smaller than 4 (memory size is divided by this to determine kernel VM size); this is a compile-only option, and for a machine that does almost nothing in userspace it may be more appropriate to use something like 2 (use up to half of physical memory for the kerne). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 13: 3:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D072614FD1 for ; Sun, 8 Aug 1999 13:03:48 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id QAA43929; Sun, 8 Aug 1999 16:02:05 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 8 Aug 1999 16:02:05 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Osokin Sergey Cc: hackers@FreeBSD.org Subject: Re: rc addition proposal: mixer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Osokin Sergey wrote: > > > > Now in current i use following script (aka mixer.sh) for install sound > environment: > > #!/bin/sh > mixer vol 36 > mixer synth 36 > mixer pcm 36 > mixer line 36 > mixer cd 68 > > Maybe add to rc.conf all features of mixer? > (aka vol, bass & etc) Yes, I've added all of them. Now, you'd want the following in rc.conf, in your case: mixers="0" # or whatever you want to call it mixer_0_dev="/dev/mixer0" # This is optional, of course mixer_0_vol="36" mixer_0_synth="36" mixer_0_pcm="36" mixer_0_line="36" mixer_0_cd="68" > > Rgdz, > Osokin Sergey aka oZZ, > osa@etrust.ru Here are all the diffs. --- src/etc/rc.orig Sun Aug 8 15:01:19 1999 +++ src/etc/rc Sun Aug 8 15:04:26 1999 @@ -168,6 +168,11 @@ . /etc/rc.pccard fi +# configure audio devices +if [ -f /etc/rc.audio ]; then + . /etc/rc.audio +fi + # start up the initial network configuration. if [ -f /etc/rc.network ]; then . /etc/rc.network # We only need to do this once. --- src/etc/defaults/rc.conf.orig Sun Aug 8 15:16:59 1999 +++ src/etc/defaults/rc.conf Sun Aug 8 15:37:01 1999 @@ -191,6 +191,19 @@ ############################################################## +### Sound device options ################################### +############################################################## + +#mixer_names="0 1" # List of mixer variable names. +#mixer_0_dev="" # Set this to your mixer device, or leave unset to + # get /dev/mixer. +#mixer_0_vol="80:80" # Set the master volume. +#mixer_1_dev="/dev/mixer1" +#mixer_1_vol="90:90" +#mixer_1_pcm="75:75" + # See mixer(8) for more possible mixer devices. + +############################################################## ### Miscellaneous administrative options ################### ############################################################## --- /dev/null Sun Aug 8 16:00:00 1999 +++ src/etc/rc.audio Sun Aug 8 16:01:10 1999 @@ -0,0 +1,23 @@ +#!/bin/sh +# +# Audio device configuration +# +# $Id$ +# + +for mname in "$mixers"; do + if eval [ -n \""\$mixer_$mname_dev"\" ]; then + eval mixer=\""mixer -f \$mixer_$mname_dev"\" + else + mixer="mixer" + fi + + mdevs=`$mixer 2>/dev/null | cut -d' ' -f2` + if [ -n "$mdevs" ]; then + for mdev in $mdevs recsrc; do + if eval [ -n \""\$mixer_${mname}_$mdev"\" ]; then + eval \$mixer \$mdev \"\$mixer_${mname}_$mdev\" + fi + done >/dev/null + fi +done Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Sun Aug 8 13:25:37 1999 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 90E9614EC1 for ; Sun, 8 Aug 1999 13:25:33 -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.1) with ESMTP id NAA06254; Sun, 8 Aug 1999 13:23:28 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA02835; Sun, 8 Aug 1999 13:23:28 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199908081935.OAA04278@mpp.pro-ns.net> Date: Sun, 08 Aug 1999 13:23:28 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Mike Pritchard Subject: Re: cvs Cc: hackers@FreeBSD.org, billf@jade.chc-chimes.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Pritchard wrote: >> >> Note, if you would have just _run_ the program with a umask of 2 >> then it would have worked too. It honors the umask setting unless >> overridden in the supfile. > > Yes, but if I ever run cvsup by hand I wind up with cvsup > going through my whole tree and resetting attributes because > my default umask isn't 2. I once started up a cvsup by hand, sat > down to eat/watch TV, came back and realized that cvsup had reset > all of my file permissions. That just shows that watching TV is _bad_. ;-) > Putting it in the cvsup file help to make sure you don't screw > yourself up by accident. Yep -- that's why I added the feature. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 13:25:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rhenium.btinternet.com (rhenium.btinternet.com [194.73.73.93]) by hub.freebsd.org (Postfix) with ESMTP id 5E2661509F for ; Sun, 8 Aug 1999 13:25:40 -0700 (PDT) (envelope-from duncanks@altavista.net) Received: from [212.140.97.153] (helo=duncan) by rhenium.btinternet.com with smtp (Exim 2.05 #1) id 11DZTf-0005kS-00 for freebsd-hackers@freebsd.org; Sun, 8 Aug 1999 21:23:32 +0100 Message-ID: <005901bee1db$9da24f20$0100a8c0@duncan> From: "Duncan Spooner" To: Subject: Parallel Zip Drive on FreeBSD 3.2-RELEASE Date: Sun, 8 Aug 1999 21:21:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and although the vpo0 is detected it does not see da0, and when I try "mount -t msdos /dev/da0s4 /mnt" it gives me the error message "msdos: /dev/da0s4: Device not configured". I have added scbus0 and da0 to the kernel as well. Below is a copy of the dmesg from the most recent boot. If wanted I can post the kernel configuration file as well. Many Thanks. ---- Start of dmesg.today file ---- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #6: Fri Aug 6 14:22:48 BST 1999 duncan@freebsd.duncanspooner.co.uk:/usr/src/sys/compile/FREEBSD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (133.12-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 13840384 (13516K bytes) Preloaded elf kernel "kernel" at 0xc02bd000. Probing for devices on PCI bus 0: chip0: rev 0x23 on pci0.0.0 chip1: rev 0x25 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 vga0: rev 0x00 on pci0.8.0 ed1: rev 0x00 int a irq 11 on pci0.10.0 ed1: address 00:e0:29:2b:16:06, type NE2000 (16 bit) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 519MB (1064448 sectors), 1056 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy acd0: drive speed 4153KB/sec, 120KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 15 seconds for SCSI devices to settle changing root device to wd0s1a ---- End of dmesg.today file ---- -- Duncan duncanks@altavista.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 14: 8:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id D5B6B14DBA for ; Sun, 8 Aug 1999 14:08:08 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA31895 for ; Sun, 8 Aug 1999 14:06:41 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37ADF162.E8A05193@gorean.org> Date: Sun, 08 Aug 1999 14:06:42 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Please review: New 'make upgrade' web page Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Making good on a promise I made quite a while back I've put up a web page with hopefully comprehensive instructions on going from 2.2.8 to 3.x via 'make upgrade.' This page is aimed at a less experienced user and gives a step by step list of procedures to follow to help ensure maximum possibilities of success and convenience. I would appreciate it very much if some of y'all that are familiar with this procedure would take a few minutes and read through the page with an eye toward offering constructive criticism. I have now done two 'make upgrade's following these instructions and both have been successful. I cobbled together the information from various posts to the lists over the last year and my experience doing the two upgrades. Some of the recommendations may seem overly paranoid, but please keep the target audience in mind. TIA, Doug http://home.san.rr.com/freebsd/make-upgrade.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 14:45: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rhenium.btinternet.com (rhenium.btinternet.com [194.73.73.93]) by hub.freebsd.org (Postfix) with ESMTP id 3046515051; Sun, 8 Aug 1999 14:44:44 -0700 (PDT) (envelope-from Duncan.Spooner_freebsd@btinternet.com) Received: from [212.140.97.153] (helo=duncan) by rhenium.btinternet.com with smtp (Exim 2.05 #1) id 11Daif-0006jv-00; Sun, 8 Aug 1999 22:43:05 +0100 Message-ID: <009001bee1e6$80a9ec60$0100a8c0@duncan> From: "Duncan Spooner" To: , References: <003b01bee10b$07297580$0100a8c0@duncan> <19990808143528.A376@dakota.shamz.net> Subject: Re: Parallel Zip Drive on FreeBSD 3.2-RELEASE Date: Sun, 8 Aug 1999 22:37:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. It's good that you included the dmesg, but without your kernel config > file, it's damn hard to know if you included everything correctly. ---------> Start of current kernel configuration: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options COMPAT_LINUX config kernel root on wd0 controller isa0 controller pnp0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 #controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? controller scbus0 # Zip Drive support device da0 # Zip Drive support #device sa0 #device pass0 #device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 #device sio2 at isa? disable port "IO_COM3" tty irq 5 #device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 controller vpo0 at ppbus? # Zip drive support device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? #device lpbb0 at ppbus? # # The following Ethernet NICs are all PCI devices. # #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device speaker # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter ---------> End of current kernel configuration: > > On Sat, Aug 07, 1999 at 08:28:02PM +0100, Duncan Spooner wrote: > #> I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and > #> although the vpo0 is detected it does not see da0, and when I try "mount -t > #> msdos /dev/da0s4 /mnt" it gives me the error message "msdos: /dev/da0s4: > #> Device not configured". > > Try to make a subdirectory that is unique to the zip drive like /mnt/zip > , in case you want to mount other things in the future. Then make sure that the > devices exist (i.e.: ls -l /dev/da*, if not make them as root in the /dev > directory with ./MAKEDEV da0 making sure the slice(s) you need are there > afterward as well (if not, use MAKEDEV again only with da0s[slice number]). > #> > #> I have added scbus0 and da0 to the kernel as well. Have tried that as well. > Here is a copy of what I use on a comparable config (only relevant > excerpts): > > controller ppbus0 > controller vpo0 at ppbus0 > controller scbus0 at vpo0 > device da0 > device lpt0 at ppbus0 > device ppi0 at ppbus0 > device ppc0 at isa? port 0x378 tty irq 7 #see your BIOS for parallel > #port address setting > #> > > Also, don't forget to see in your BIOS (DEL key at boot time), if the > parallel port is set for ECP/EPP mode 1.9, it's faster and _may_ help > with recognition (varies based on your parallel port chip set). Don't > forget to rtfm (read the f**ing man page) because all of these drivers > have one (albeit with a few errors). You could see from the dmesg file, that vpo0 loaded with EEP 1.9 mode. > #> The Regents of the University of California. All rights reserved. > #> FreeBSD 3.2-RELEASE #6: Fri Aug 6 14:22:48 BST 1999 > #> duncan@freebsd.duncanspooner.co.uk:/usr/src/sys/compile/FREEBSD > #> Timecounter "i8254" frequency 1193182 Hz > #> CPU: Pentium/P54C (133.12-MHz 586-class CPU) > #> Origin = "GenuineIntel" Id = 0x52c Stepping=12 > #> real memory = 16777216 (16384K bytes) > #> avail memory = 13840384 (13516K bytes) > Without being too pushy, try to get some more ram before they don't make > it anymore, 16mb works, but you can easily use more :) > #> Preloaded elf kernel "kernel" at 0xc02bd000. > #> Probing for devices on PCI bus 0: > #> chip0: rev 0x23 on pci0.0.0 > #> chip1: rev 0x25 on pci0.7.0 > #> ide_pci0: rev 0x06 on > #> pci0.7.1 > #> vga0: rev 0x00 on pci0.8.0 > #> ed1: rev 0x00 int a irq 11 on pci0.10.0 > #> ed1: address 00:e0:29:2b:16:06, type NE2000 (16 bit) > > I keep seeing this more often. There is a driver for the RealTek cards > called rl0. If you read /sys/i386/conf/LINT or even the GENERIC kernel > you will see that this is for ISA NE2000 compatible cards and unless the > man pages are out of date (mine should only be 2 days old) or I am > terribly misinformed (again man rl or man ed) you should be using it. > Seems to be newer users with this problem. Is it a sysinstall > recognition mistake? In any case, it is interesting that it works... Note, my card is a RealTek 8029, and the rl0 driver is for RealTek 8129/8139, and that works for me anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 15:15: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 132F514CA9 for ; Sun, 8 Aug 1999 15:15:00 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id E87FF1C0F; Sun, 8 Aug 1999 17:13:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id D517F3816; Sun, 8 Aug 1999 17:13:34 -0400 (EDT) Date: Sun, 8 Aug 1999 17:13:34 -0400 (EDT) From: Bill Fumerola To: John Polstra Cc: hackers@freebsd.org Subject: Re: cvs In-Reply-To: <199908080332.UAA01140@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 7 Aug 1999, John Polstra wrote: > > > *default umask=002 > > > > SetAttrs CVSROOT/commitlogs/other.981201.gz > > > > That seems to be doing the trick for everything. Thanks. > > Note, if you would have just _run_ the program with a umask of 2 > then it would have worked too. It honors the umask setting unless > overridden in the supfile. True, I hate changing my umask for different programs. It's nice to have the option to do it in the supfile. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 15:43:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id 3CCD41506A for ; Sun, 8 Aug 1999 15:43:37 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp222-pm6.humboldt1.com [207.104.21.215]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id PAA06594 for freebsd-hackers@freebsd.org; Sun, 8 Aug 1999 15:41:15 -0700 (PDT) Date: Sun, 8 Aug 1999 15:41:15 -0700 (PDT) Message-Id: <199908082241.PAA06594@home.humboldt1.com> From: Joe Groff To: freebsd-hackers@freebsd.org Reply-To: ognir@humboldt1.com Subject: New Joystick driver? X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe the joystick driver in FreeBSD could probably be redone, to support all the non-standard joysticks that many people (like me :) have. Having just recently converted to FreeBSD from Linux, though, I don't know the best way to go about it. Here are some ideas (sorry if my terminology is wrong): (1) Redefine the core joystick code as a controller, and then have all the different joystick types ride on top of it, like: controller joy0 at isa? port IO_GAME # Serves joystick port 0x201 #device jan0 at joy0 # Analog joystick device jgpp0 at joy0 # Gravis GamePad Pro etc... This would also allow for modules to be used for all the different joystick types, I think. (2) Have a monolithic joystick driver, with options to pick the proper type: device joy0 at isa? port IO_GAME # Just like it is now options JOY_ANALOG options JOY_GRAVIS etc... I also believe it should use the Linux joystick's device interface, so that folks that have already written their games to use the Linux joysticks can work in FreeBSD with minor effort. Any help or comments are appreciated. -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 16: 9:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 7FEF214D97 for ; Sun, 8 Aug 1999 16:09:53 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id BAA07652 for freebsd-hackers@FreeBSD.ORG; Mon, 9 Aug 1999 01:05:55 +0200 (CEST) (envelope-from olli) Date: Mon, 9 Aug 1999 01:05:55 +0200 (CEST) From: Oliver Fromme Message-Id: <199908082305.BAA07652@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: rc addition proposal: mixer Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman wrote in list.freebsd-hackers: > I envision something like the following being available in /etc/rc, > since there are many people who set mixer default values at startup in > some random way. It would be nice to provide an easy way to do this. > I'd like to get a vote on whether this should be added or not. > > I'd do something like the following: > > if [ -n "$mixer_device" ]; do > mixer="mixer -f $mixer_device" > else > mixer="mixer" > done > for cf in `$mixer | cut -d' ' -f2` recsrc; do > if eval [ -n "mixer_$cf" ]; then > eval \$mixer \$cf \$mixer_$cf > fi > done I'd like to propose a different approach. This is a slight modification of what I do on my own boxes (using a script in /usr/local/etc/rc.d). rc.conf (example): mixer_enable="YES" # (default = NO) mixer_config="/etc/mixer.conf" # (default) mixer_device="/dev/mixer" # (default) mixer.conf (example): # some comment vol 90 synth 50 # more comments... bass 75 treble 50 mic 0 line 50 cd 80 speaker 0 igain 50 ogain 70 rc: if [ "X${mixer_enable}" != X"NO" -a -f "${mixer_config}" ]; then echo -n ' mixer' slots=`mixer -f ${mixer_device} | cut -d' ' -f2 | tr '\n' '|'`recsrc sed 's/#.*$//' ${mixer_config} | egrep "$slots" | xargs mixer -f ${mixer_device} fi Just my 0.02 Euro... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 17:18:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 220A214E9E for ; Sun, 8 Aug 1999 17:18:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA11370; Sun, 8 Aug 1999 17:17:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Duncan Spooner" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Parallel Zip Drive on FreeBSD 3.2-RELEASE In-reply-to: Your message of "Sun, 08 Aug 1999 21:21:32 BST." <005901bee1db$9da24f20$0100a8c0@duncan> Date: Sun, 08 Aug 1999 17:17:01 -0700 Message-ID: <11366.934157821@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and > although the vpo0 is detected it does not see da0, and when I try "mount -t I'm not surprised, since da0 would be a SCSI device. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 17:24: 5 1999 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 4A8C214E23 for ; Sun, 8 Aug 1999 17:24:01 -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 SAA11067; Sun, 8 Aug 1999 18:20:01 -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 SAA02603; Sun, 8 Aug 1999 18:19:53 -0600 (MDT) Message-Id: <199908090019.SAA02603@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: Parallel Zip Drive on FreeBSD 3.2-RELEASE Cc: "Duncan Spooner" , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 08 Aug 1999 17:17:01 PDT." <11366.934157821@localhost> References: <11366.934157821@localhost> Date: Sun, 08 Aug 1999 18:19:53 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <11366.934157821@localhost> "Jordan K. Hubbard" writes: : > I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE and : > although the vpo0 is detected it does not see da0, and when I try "mount -t : : I'm not surprised, since da0 would be a SCSI device. But vpo0 is a SCSI controller. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 17:30:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 417581506E for ; Sun, 8 Aug 1999 17:30:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA11471; Sun, 8 Aug 1999 17:28:14 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Warner Losh Cc: "Jordan K. Hubbard" , "Duncan Spooner" , freebsd-hackers@FreeBSD.ORG Subject: Re: Parallel Zip Drive on FreeBSD 3.2-RELEASE In-reply-to: Your message of "Sun, 08 Aug 1999 18:19:53 MDT." <199908090019.SAA02603@harmony.village.org> Date: Sun, 08 Aug 1999 17:28:14 -0700 Message-ID: <11467.934158494@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I wasn't aware that the parallel port SCSI stuff had been CAM'd yet. - Jordan > In message <11366.934157821@localhost> "Jordan K. Hubbard" writes: > : > I have a parallel port Iomega Zip Drive. I have installed 3.2-RELEASE an d > : > although the vpo0 is detected it does not see da0, and when I try "mount -t > : > : I'm not surprised, since da0 would be a SCSI device. > > But vpo0 is a SCSI controller. > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 17:32:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 2B40314E23 for ; Sun, 8 Aug 1999 17:31:55 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id UAA40444 for hackers@freebsd.org; Sun, 8 Aug 1999 20:43:33 -0400 (EDT) Date: Sun, 8 Aug 1999 20:43:33 -0400 From: Dan Moschuk To: hackers@freebsd.org Subject: gethostbyaddr() and threads. Message-ID: <19990808204333.A40377@trinsec.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 Greetings, After quite an exhausting night (of all the ways I didn't want to spend my Sunday...) I've managed to track down a problem that has been frustrating me all night. The problem exists with multiple threads calling gethostbyaddr() (not necessarily at the same time). Here's a debug output from my program: Thread 134978048 sleeping... Thread 134978560 sleeping... Thread 134978048 awakened! Thread 134978048 checking status of 162.18.75.91 Thread 134978048 looking up 162.18.75.91 Thread 134978048 calling gethostbyaddr() Thread 134978560 awakened! Thread 134978560 checking status of 162.18.75.91 Thread 134978560 sleeping... Thread 134978560 awakened! Thread 134978560 checking status of 202.188.127.2 Thread 134978560 looking up 202.188.127.2 Thread 134978560 calling gethostbyaddr() Thread 134978560 finished gethostbyaddr() Thread 134978560 checking status of 200.231.47.8 Thread 134978560 looking up 200.231.47.8 Thread 134978560 calling gethostbyaddr() As you can see, gethostbyaddr() when called from the first thread never returns, while the last thread continues on. This happens no matter how many threads I create. Creating 200 threads produces much longer debug output, but the result is the same, the first 199 threads created never return from gethostbyaddr(), while the last one continues on its merry way. I am hoping someone can shed a little more light on this subject, and possibly explain why this is happening and perhaps how to fix it. I've tested this on both -stable and -current branches. Regards, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 17:56:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 26BE415092 for ; Sun, 8 Aug 1999 17:56:08 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id RAA33858 for ; Sun, 8 Aug 1999 17:53:00 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AE266D.D71D89EF@gorean.org> Date: Sun, 08 Aug 1999 17:53:01 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Fix/tuning to improve slow NFS writes? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well my NFS reliability at work has gone way up, to the point where we are now having time to look at the finer things in life, like performance tuning. Performance on reads has been quite good, but when the cgi scripts that the users are running on these machines have large writes to do (like re-indexing a database) the writes go really slow. So slow in fact that they sometimes time out, the CGI engine dies, and the job is never completed, causing it to be restarted by the user. So, the big question is whether there is anything we can tune to speed up the writes. The freebsd machines are NFS clients to the sun servers doing most of the web processing. Overall performance on the reads seems to be best with nfs v3 over udp, which is what I'm using now. All of the web server directories are soft mounted directly, with no amd currently in use. thanks, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 18:51:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from daedal.oneway.com (daedal.oneway.com [205.252.89.49]) by hub.freebsd.org (Postfix) with ESMTP id DA14614E7A; Sun, 8 Aug 1999 18:51:43 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by daedal.oneway.com (8.9.1/8.9.1) with ESMTP id VAA22573; Sun, 8 Aug 1999 21:49:41 -0400 (EDT) (envelope-from jay@oneway.com) Date: Sun, 8 Aug 1999 21:49:41 -0400 (EDT) From: Jay Kuri To: Kazutaka YOKOTA Cc: freebsd-small@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Access to keyboard without video. In-Reply-To: <199908070946.SAA14288@zodiac.mech.utsunomiya-u.ac.jp> 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 > In FreeBSD version 3.1 or later, the keyboard controller atkbdc(4) and > AT keyboard driver atkbd(4) will give you access to the keyboard even > when there is no video card. Thanks, I read the source and found the CDEV stuff... I had to disable the sc0 device to get access to it. and then I had to hack kbdcontrol to open /dev/kbd0 instead of stdin (which is what it currently does) Shouldn't you be able to specify the kbd you want to control with kbdcontrol? Maybe default to stdin.. but allow access to the keyboard device as specified? Jay - - - - - - - - - - - - - - - - - - - - - - - - - UNIX: because reboots are for hardware upgrades Jay Kuri jay@oneway.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 19:46:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id EAA5314D36; Sun, 8 Aug 1999 19:46:18 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:r7dbORY7NzORHmsvT70xohaEyI1GYP3+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id LAA06718; Mon, 9 Aug 1999 11:43:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA23264; Mon, 9 Aug 1999 11:47:31 +0900 (JST) Message-Id: <199908090247.LAA23264@zodiac.mech.utsunomiya-u.ac.jp> To: Jay Kuri Cc: freebsd-small@freebsd.org, freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Access to keyboard without video. In-reply-to: Your message of "Sun, 08 Aug 1999 21:49:41 -0400." References: Date: Mon, 09 Aug 1999 11:47:30 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In FreeBSD version 3.1 or later, the keyboard controller atkbdc(4) and >> AT keyboard driver atkbd(4) will give you access to the keyboard even >> when there is no video card. > Thanks, I read the source and found the CDEV stuff... I had to >disable the sc0 device to get access to it. and then I had to hack As I wrote before, when the console device, sc or vt, is present, the keyboard is exclusively used by the console driver. You can remove or disable the console driver to prevent this. Or pull out the video card. When a video card is not present, the console driver won't be installed. >kbdcontrol to open /dev/kbd0 instead of stdin (which is what it currently >does) > > Shouldn't you be able to specify the kbd you want to control with >kbdcontrol? Maybe default to stdin.. but allow access to the keyboard >device as specified? kbdcontrol _whatever_ < /dev/kbd0 Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 8 20:19:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from patriot.wipinfo.soft.net (patriot.wipinfo.soft.net [164.164.6.21]) by hub.freebsd.org (Postfix) with ESMTP id E2A1714F69; Sun, 8 Aug 1999 20:19:10 -0700 (PDT) (envelope-from bee@wipinfo.soft.net) Received: from wipro.tcpn.com ([172.31.40.11]) by patriot.wipinfo.soft.net (8.9.2/8.9.2) with ESMTP id IAA02429; Mon, 9 Aug 1999 08:45:52 -0500 (GMT) Received: from keeravani (keeravani.wipro.tcpn.com [172.31.41.136]) by wipro.tcpn.com (8.9.3/8.9.3) with SMTP id IAA19936; Mon, 9 Aug 1999 08:47:26 +0530 (IST) Reply-To: From: "Biju Susmer" To: "'Warner Losh'" , "'Brian F. Feldman'" Cc: "'Daniel O'Connor'" , "'Wes Peters'" , , "'Vince Vielhaber'" , "'Chris'" , Subject: RE: IDE quirk in 3.2-STABLE kernel ? Date: Mon, 9 Aug 1999 08:45:06 +0530 Message-ID: <003a01bee215$62f58240$88291fac@wipro.tcpn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <199908070508.XAA07305@harmony.village.org> Disposition-Notification-To: "Biju Susmer" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Odd, all of the machines that I've seen shipped lately have their > CDROMs on a secondary IDE controller as SLAVE with no master. Works > great, and the FreeBSD drivers work well when hacked to not require > a master fo there to be a slave.... i commented out one line in wd.c, wdprobe() and it works fine... The funny thing is it checks for slave, its signature etc if ATAPI is defined and then returns a 0 saying "drive 0 error" !! (In this case du->dk_error is 0x7f) -biju To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 0: 8:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id EF6111530F for ; Mon, 9 Aug 1999 00:08:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA59059; Mon, 9 Aug 1999 00:06:57 -0700 (PDT) (envelope-from dillon) Date: Mon, 9 Aug 1999 00:06:57 -0700 (PDT) From: Matthew Dillon Message-Id: <199908090706.AAA59059@apollo.backplane.com> To: Doug Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: <37AE266D.D71D89EF@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : So, the big question is whether there is anything we can tune to speed up :the writes. The freebsd machines are NFS clients to the sun servers doing :most of the web processing. Overall performance on the reads seems to be :best with nfs v3 over udp, which is what I'm using now. All of the web :server directories are soft mounted directly, with no amd currently in use. : :thanks, : :Doug Well, NFS buffers are usually sent over the network the moment they are full. If you are not running any nfsiod's, the RPC will be done synchronously and this will severely impact your performance. Try running: nfsiod -n 4 This will start up a couple of special background processes to handle NFS I/O asynchronously. Without any nfsiod's running my file tests weigh in at 2 MBytes/sec. With a couple running I get 8 MBytes/sec over my network with NFSv3. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 0:49:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 2421514E84 for ; Mon, 9 Aug 1999 00:49:32 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id AAA36356; Mon, 9 Aug 1999 00:45:51 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AE8730.886D4E72@gorean.org> Date: Mon, 09 Aug 1999 00:45:52 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: <37AE266D.D71D89EF@gorean.org> <199908090706.AAA59059@apollo.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 Matthew Dillon wrote: > > : So, the big question is whether there is anything we can tune to speed up > :the writes. The freebsd machines are NFS clients to the sun servers doing > :most of the web processing. Overall performance on the reads seems to be > :best with nfs v3 over udp, which is what I'm using now. All of the web > :server directories are soft mounted directly, with no amd currently in use. > : > :thanks, > : > :Doug > > Well, NFS buffers are usually sent over the network the moment they > are full. If you are not running any nfsiod's I should have mentioned, I have 20 nfsiod's running. I started so many initially to help in the stress testing I was doing, but I left them running because the servers are handling from 2-4 requests per second and we have lots of ram in the boxes. Is there a way to figure out how many are getting used concurrently, or is too many not a problem? Thanks, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 1:32: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id 07C0615157 for ; Mon, 9 Aug 1999 01:32:01 -0700 (PDT) (envelope-from wosch@cs.tu-berlin.de) Received: from freno.cs.tu-berlin.de (wosch@freno.cs.tu-berlin.de [130.149.17.167]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id KAA25870 for ; Mon, 9 Aug 1999 10:25:16 +0200 (MET DST) Received: (from wosch@localhost) by freno.cs.tu-berlin.de (8.9.1/8.9.0) id KAA02261 for hackers@freebsd.org; Mon, 9 Aug 1999 10:25:16 +0200 (MET DST) Date: Mon, 9 Aug 1999 10:25:15 +0200 From: Wolfram Schneider To: hackers@freebsd.org Subject: FYI [ymironoff@earthlink.net: C-Forge for FreeBSD] Message-ID: <19990809102514.E2015@freno.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Forwarded message from "Yuri Mironoff" ----- Reply-To: "Yuri Mironoff" From: "Yuri Mironoff" To: Subject: C-Forge for FreeBSD Date: Sun, 8 Aug 1999 22:42:50 -0400 Hello, We're recently ported the C-Forge Integrated Development Environment to FreeBSD (short description of product follows). Please add us to your list of commercial software vendors. Thank you very much in advance, Yuri Mironoff Code Forge, Inc http://www.codeforge.com -------------------------------------------------------------------------------- C-Forge (pronounced Code Forge) is a multi-user integrated development environment that provides full project management and complete edit/compile/debug cycle support. Features include complete abstraction of the "makefile" concept, a Project Manager for Visual presentation of project structure and component status using a dependency tree and a separate "desktop" area showing work in progress, support for C/C++, Perl, Oracle ProC/C++, Tcl, PHP, Java, Javascript, Python, Qt, Pascal, Free Pascal, FORTRAN, TeX/LaTeX, SGML, Modula-2 and Assembler, integrated revision control, fully configurable programmer's editor and much more. Evaluation version available for download. Please visit us at http://www.codeforge.com ----- End forwarded message ----- -- Wolfram Schneider http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 1:50: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 37D28151E1 for ; Mon, 9 Aug 1999 01:49:45 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA06476; Mon, 9 Aug 1999 04:50:53 -0400 (EDT) Date: Mon, 9 Aug 1999 04:50:51 -0400 (EDT) From: Alfred Perlstein To: Doug Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? In-Reply-To: <37AE8730.886D4E72@gorean.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 Mon, 9 Aug 1999, Doug wrote: > Matthew Dillon wrote: > > > > : So, the big question is whether there is anything we can tune to speed up > > :the writes. The freebsd machines are NFS clients to the sun servers doing > > :most of the web processing. Overall performance on the reads seems to be > > :best with nfs v3 over udp, which is what I'm using now. All of the web > > :server directories are soft mounted directly, with no amd currently in use. > > : > > :thanks, > > : > > :Doug > > > > Well, NFS buffers are usually sent over the network the moment they > > are full. If you are not running any nfsiod's > > I should have mentioned, I have 20 nfsiod's running. I started so many > initially to help in the stress testing I was doing, but I left them > running because the servers are handling from 2-4 requests per second and > we have lots of ram in the boxes. Is there a way to figure out how many are > getting used concurrently, or is too many not a problem? ? You need to run 'nfsd' on the servers, not nfsiod. nfsd - run on server nfsiod - run on client nfsd takes the same -n arg for the number to start. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 2: 8:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from forty-two.egroups.net (teapot.findmail.com [206.16.70.98]) by hub.freebsd.org (Postfix) with ESMTP id DD5BC1518B for ; Mon, 9 Aug 1999 02:08:33 -0700 (PDT) (envelope-from gsutter@forty-two.egroups.net) Received: (from gsutter@localhost) by forty-two.egroups.net (8.9.3/8.9.2) id CAA57584; Mon, 9 Aug 1999 02:06:28 -0700 (PDT) (envelope-from gsutter) Date: Mon, 9 Aug 1999 02:06:28 -0700 From: Gregory Sutter To: Alfred Perlstein Cc: Doug , freebsd-hackers@FreeBSD.ORG, dillon@backplane.com Subject: Re: Fix/tuning to improve slow NFS writes? Message-ID: <19990809020628.M51428@forty-two.egroups.net> References: <37AE8730.886D4E72@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Alfred Perlstein on Mon, Aug 09, 1999 at 04:50:51AM -0400 Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 09, 1999 at 04:50:51AM -0400, Alfred Perlstein wrote: > On Mon, 9 Aug 1999, Doug wrote: > > > Matthew Dillon wrote: > > > > > > : So, the big question is whether there is anything we can tune to speed up > > > :the writes. The freebsd machines are NFS clients to the sun servers doing > > > :most of the web processing. Overall performance on the reads seems to be > > > :best with nfs v3 over udp, which is what I'm using now. All of the web > > > :server directories are soft mounted directly, with no amd currently in use. Could tuning any of the NFS options in the kernel help? Matt, could you give any tips? > > I should have mentioned, I have 20 nfsiod's running. I started so many > > initially to help in the stress testing I was doing, but I left them > > running because the servers are handling from 2-4 requests per second and > > we have lots of ram in the boxes. Is there a way to figure out how many are > > getting used concurrently, or is too many not a problem? > > You need to run 'nfsd' on the servers, not nfsiod. > > nfsd - run on server > nfsiod - run on client He's talking about the client boxes, just measuring from the server side. Reference the second sentence at top. Greg -- Gregory S. Sutter Failing sardine factory cans employees! mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 5:29:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id 347B51525A; Mon, 9 Aug 1999 05:29:43 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11DoWM-000LLp-00; Mon, 09 Aug 1999 13:27:18 +0100 To: green@FreeBSD.org From: Tony Finch Cc: hackers@freebsd.org Subject: Re: quad_t and portability In-Reply-To: References: <199908080338.UAA01158@vashon.polstra.com> Message-Id: Date: Mon, 09 Aug 1999 13:27:18 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > >Is there anyone who is specifically checking for long long >C9X-compliancy in the source tree (mainly libc)? I started reviewing libc for C9X features in general -- a fair amount of work is required to update macros and typedefs in (plus the new ). Doing a thorough job is difficult because C9X is somewhat gratuitously incompatible with gnu C (e.g. the spelling of __complex__, zero-length arrays in structures, macro varargs, etc.) and gnu C doesn't yet support restrict. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 5:43:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id AFE1015226 for ; Mon, 9 Aug 1999 05:43:21 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11Dok0-000LN9-00; Mon, 09 Aug 1999 13:41:24 +0100 To: dan@trinsec.com From: Tony Finch Cc: hackers@freebsd.org Subject: Re: gethostbyaddr() and threads. In-Reply-To: <19990808204333.A40377@trinsec.com> Message-Id: Date: Mon, 09 Aug 1999 13:41:24 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > >After quite an exhausting night (of all the ways I didn't want to spend my >Sunday...) I've managed to track down a problem that has been frustrating me >all night. The problem exists with multiple threads calling gethostbyaddr() >(not necessarily at the same time). src/lib/libc/net/gethostbydns.c seems to use a load of static variables in a non-thread-safe fashion. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 6:55: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 70EEB15256 for ; Mon, 9 Aug 1999 06:55:03 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id KAA43935; Mon, 9 Aug 1999 10:06:26 -0400 (EDT) Date: Mon, 9 Aug 1999 10:06:26 -0400 From: Dan Moschuk To: Tony Finch Cc: hackers@freebsd.org Subject: Re: gethostbyaddr() and threads. Message-ID: <19990809100626.A43835@trinsec.com> References: <19990808204333.A40377@trinsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Tony Finch on Mon, Aug 09, 1999 at 01:41:24PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | >After quite an exhausting night (of all the ways I didn't want to spend my | >Sunday...) I've managed to track down a problem that has been frustrating me | >all night. The problem exists with multiple threads calling gethostbyaddr() | >(not necessarily at the same time). | | src/lib/libc/net/gethostbydns.c seems to use a load of static | variables in a non-thread-safe fashion. Yes, I noticed that as well. I also noticed that gethostbyaddr_r worked "less" than gethostbyaddr did (the result was that all threads ended up thrashing each other, and not of them continued on). I was going to use res_query, but noticed that it too used static buffers (although it looks pretty easy to fix). Would anyone be offended if I were to produce a few patches to fix up these routines once and for all? Should I just produce a few #ifdef _THREAD_SAFEs or try full blown routines (gethostbyaddr_r, res_query_r)? Thanks, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 8:22:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 38914150B1 for ; Mon, 9 Aug 1999 08:22:44 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id IAA39403; Mon, 9 Aug 1999 08:18:53 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AEF15E.ABF75AD2@gorean.org> Date: Mon, 09 Aug 1999 08:18:54 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > On Mon, 9 Aug 1999, Doug wrote: > > > Matthew Dillon wrote: > > > > > > : So, the big question is whether there is anything we can tune to speed up > > > :the writes. The freebsd machines are NFS clients to the sun servers doing > > > :most of the web processing. Overall performance on the reads seems to be > > > :best with nfs v3 over udp, which is what I'm using now. All of the web > > > :server directories are soft mounted directly, with no amd currently in use. > > > : > > > :thanks, > > > : > > > :Doug > > > > > > Well, NFS buffers are usually sent over the network the moment they > > > are full. If you are not running any nfsiod's > > > > I should have mentioned, I have 20 nfsiod's running. I started so many > > initially to help in the stress testing I was doing, but I left them > > running because the servers are handling from 2-4 requests per second and > > we have lots of ram in the boxes. Is there a way to figure out how many are > > getting used concurrently, or is too many not a problem? > > ? > > You need to run 'nfsd' on the servers, not nfsiod. Sorry I wasn't clear. That's what I get for writing posts like this when I'm tired. In that paragraph "servers" refers to the freebsd cgi/web servers that are acting as NFS clients to the sun boxes. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 8:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 688F0150B1 for ; Mon, 9 Aug 1999 08:31:13 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA62751; Mon, 9 Aug 1999 08:27:55 -0700 (PDT) (envelope-from dillon) Date: Mon, 9 Aug 1999 08:27:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199908091527.IAA62751@apollo.backplane.com> To: Doug Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: <37AE266D.D71D89EF@gorean.org> <199908090706.AAA59059@apollo.backplane.com> <37AE8730.886D4E72@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I should have mentioned, I have 20 nfsiod's running. I started so many :initially to help in the stress testing I was doing, but I left them :running because the servers are handling from 2-4 requests per second and :we have lots of ram in the boxes. Is there a way to figure out how many are :getting used concurrently, or is too many not a problem? : :Thanks, : :Doug You can look at their cpu utilization with ps. You should see high cpu use on a couple of them and then tapering off. The system allocates nfsiods in order depending on the number of outstanding asynchronous requests. If the web server is not bound by write bandwidth, it could be getting bound up in NFS stat calls. I think what you need to do at this point is run ktrace on some of the web server processes to see where the performance bottlenecks are. Let ktrace collect statistics for a while and then make sure to turn it off with 'ktrace -C', and then use 'kdump -R | less' to see the results. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 9: 0: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id BA6C314BF1 for ; Mon, 9 Aug 1999 09:00:02 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA63032; Mon, 9 Aug 1999 11:56:32 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 11:56:32 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Tony Finch Cc: hackers@FreeBSD.org Subject: Re: quad_t and portability In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Tony Finch wrote: > "Brian F. Feldman" wrote: > > > >Is there anyone who is specifically checking for long long > >C9X-compliancy in the source tree (mainly libc)? > > I started reviewing libc for C9X features in general -- a fair amount > of work is required to update macros and typedefs in > (plus the new ). Shall we work on it, then? > > Doing a thorough job is difficult because C9X is somewhat gratuitously > incompatible with gnu C (e.g. the spelling of __complex__, zero-length > arrays in structures, macro varargs, etc.) and gnu C doesn't yet > support restrict. But GNU has officially stated that they will fully support C9X, and they've started already. For instance, int *a = ((int [4]){1,2,3,4}); should work now, according to the infopages. Eventually, I'd be certain that GNU would rather be compliant with C9X than with GNU C. > > Tony. > -- > f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Mon Aug 9 11:59:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8B93515111 for ; Mon, 9 Aug 1999 11:59:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id LAA25926; Mon, 9 Aug 1999 11:54:43 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA20415; Mon, 9 Aug 1999 11:50:20 -0700 Received: from softweyr.com (dyn5.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA13499; Mon, 9 Aug 99 11:54:40 PDT Message-Id: <37AF23EF.8ADF5B2F@softweyr.com> Date: Mon, 09 Aug 1999 12:54:39 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dan Moschuk Cc: Tony Finch , hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <19990808204333.A40377@trinsec.com> <19990809100626.A43835@trinsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > > | >After quite an exhausting night (of all the ways I didn't want to spend my > | >Sunday...) I've managed to track down a problem that has been frustrating me > | >all night. The problem exists with multiple threads calling gethostbyaddr() > | >(not necessarily at the same time). > | > | src/lib/libc/net/gethostbydns.c seems to use a load of static > | variables in a non-thread-safe fashion. > > Yes, I noticed that as well. I also noticed that gethostbyaddr_r worked > "less" than gethostbyaddr did (the result was that all threads ended up > thrashing each other, and not of them continued on). I was going to use > res_query, but noticed that it too used static buffers (although it looks > pretty easy to fix). > > Would anyone be offended if I were to produce a few patches to fix up these > routines once and for all? Should I just produce a few #ifdef _THREAD_SAFEs > or try full blown routines (gethostbyaddr_r, res_query_r)? This is the second request for gethostbyaddr_r I've seen this week. I've been (oh so slowly) implementing the missing _r routines in our library and documenting the hidden ones I've already found. This is one of the uglier ones. Hacking up the mess we've got would be a waste of time, IMHO. If you're going to do it, go all the way and make a CLEAN implementation of the _r routines and then implement the non _r routines on top of them. If you need prototypes, email back and I'll find the ones you want to work on first. When you're done, send me files or diffs and I'll be very happy to test them for you. I'll even help with the man pages. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 13:34:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yoyo.bryce.net (yoyo.bryce.net [209.197.195.234]) by hub.freebsd.org (Postfix) with ESMTP id E00A3152AF for ; Mon, 9 Aug 1999 13:34:50 -0700 (PDT) (envelope-from lists@bryce.net) Received: from localhost (lists@localhost) by yoyo.bryce.net (8.9.3/8.9.3) with ESMTP id PAA21954 for ; Mon, 9 Aug 1999 15:32:33 -0500 (CDT) (envelope-from lists@bryce.net) Date: Mon, 9 Aug 1999 15:32:33 -0500 (CDT) From: Mailing Lists To: freebsd-hackers@freebsd.org Subject: fetchGetURL() (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't seem to get libfetch to properly link in. I've tinkered with the order to no avail & don't see what I'm missing. cc -O2 -pipe -g -o importquotes importquotes.o -L/usr/local/lib/mysql -lmysqlclient -lfetch -lcom_err -lstdc++ importquotes.o: In function `main': /usr/local/stock/importquotes.cpp(.text+0x217): undefined reference to `fetchGetURL(char *, char *)' *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 14: 7:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id B043B1520D for ; Mon, 9 Aug 1999 14:07:16 -0700 (PDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id RAA12660; Mon, 9 Aug 1999 17:04:47 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.pa.dtd.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id RAA06010; Mon, 9 Aug 1999 17:04:46 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <199908092104.RAA06010@bmcgover-pc.cisco.com> To: dan@trinsec.com Cc: hackers@freebsd.org Subject: Re: gethostbyaddr() and threads. Date: Mon, 09 Aug 1999 17:04:45 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] gethostbyaddr... actually, most of the gethostby* functions... are not thread safe. They all use a static buffer in the library. Therefore, with threads, if you don't take precautions, I'd expect your results to be odd. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 14:24:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id 9598214D75 for ; Mon, 9 Aug 1999 14:24:29 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp176-pm5.humboldt1.com [207.104.21.169]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id OAA21266; Mon, 9 Aug 1999 14:21:38 -0700 (PDT) Date: Mon, 9 Aug 1999 14:21:38 -0700 (PDT) Message-Id: <199908092121.OAA21266@home.humboldt1.com> From: Joe Groff To: bmcgover@cisco.com Cc: dan@trinsec.com, hackers@FreeBSD.ORG Reply-To: ognir@humboldt1.com Subject: Re: gethostbyaddr() and threads. In-Reply-To: <199908092104.RAA06010@bmcgover-pc.cisco.com> X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Brian McGovern said: > [snip] > > gethostbyaddr... actually, most of the gethostby* functions... are not > thread safe. They all use a static buffer in the library. > > Therefore, with threads, if you don't take precautions, I'd expect your > results to be odd. > -Brian > Couldn't this be easily fixed? I haven't looked at the source yet, but I believe you could replaced the static buffers with a dynamically-allocated list of buffers, with one for each thread using the gethost functions. Or perhaps you could just eliminate all the static stuff altogether? -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 15:43:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law2-f174.hotmail.com [216.32.181.174]) by hub.freebsd.org (Postfix) with SMTP id 9B45B150A7 for ; Mon, 9 Aug 1999 15:43:46 -0700 (PDT) (envelope-from steve_tarkalson@hotmail.com) Received: (qmail 39660 invoked by uid 0); 9 Aug 1999 22:41:20 -0000 Message-ID: <19990809224120.39659.qmail@hotmail.com> Received: from 207.225.138.17 by www.hotmail.com with HTTP; Mon, 09 Aug 1999 15:41:20 PDT X-Originating-IP: [207.225.138.17] From: "Steve Tarkalson" To: ognir@humboldt1.com, bmcgover@cisco.com Cc: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. Date: Mon, 09 Aug 1999 15:41:20 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is solved by one of two methods: 1-) require the caller of gethostbyaddr() to supply a pointer to a hostent struct which will be filled. or 2-) the library uses thread specific storage which is re-used in each call. >From: Joe Groff >Reply-To: ognir@humboldt1.com >To: bmcgover@cisco.com >CC: dan@trinsec.com, hackers@FreeBSD.ORG >Subject: Re: gethostbyaddr() and threads. >Date: Mon, 9 Aug 1999 14:21:38 -0700 (PDT) >MIME-Version: 1.0 >From owner-freebsd-hackers@freebsd.org Mon Aug 9 14:22:43 1999 >Received: by hub.freebsd.org (Postfix, from userid 538)id 13F1E152DC; Mon, >9 Aug 1999 14:24:36 -0700 (PDT) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid F31551CD65D; Mon, 9 Aug 1999 14:24:35 -0700 >(PDT)(envelope-from owner-freebsd-hackers) >Received: by hub.freebsd.org (bulk_mailer v1.12); Mon, 9 Aug 1999 14:24:35 >-0700 >Delivered-To: freebsd-hackers@freebsd.org >Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1])by >hub.freebsd.org (Postfix) with ESMTP id 9598214D75for >; Mon, 9 Aug 1999 14:24:29 -0700 (PDT)(envelope-from >ognir@humboldt1.com) >Received: from shovel.groff (ppp176-pm5.humboldt1.com [207.104.21.169])by >home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id OAA21266;Mon, 9 Aug >1999 14:21:38 -0700 (PDT) >Message-Id: <199908092121.OAA21266@home.humboldt1.com> >In-Reply-To: <199908092104.RAA06010@bmcgover-pc.cisco.com> >X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) >X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ >Sender: owner-freebsd-hackers@FreeBSD.ORG >X-Loop: FreeBSD.ORG >Precedence: bulk > >---Brian McGovern said: > > [snip] > > > > gethostbyaddr... actually, most of the gethostby* functions... are not > > thread safe. They all use a static buffer in the library. > > > > Therefore, with threads, if you don't take precautions, I'd expect your > > results to be odd. > > -Brian > > >Couldn't this be easily fixed? I haven't looked at the source yet, but I >believe you could replaced the static buffers with a dynamically-allocated >list >of buffers, with one for each thread using the gethost functions. Or >perhaps >you could just eliminate all the static stuff altogether? > >-Joe > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 15:58: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id 508BD153F0 for ; Mon, 9 Aug 1999 15:57:54 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp227-pm6.humboldt1.com [207.104.21.220]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id PAA08129; Mon, 9 Aug 1999 15:55:37 -0700 (PDT) Date: Mon, 9 Aug 1999 15:55:37 -0700 (PDT) Message-Id: <199908092255.PAA08129@home.humboldt1.com> From: Joe Groff To: steve_tarkalson@hotmail.com Cc: bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Reply-To: ognir@humboldt1.com Subject: Re: gethostbyaddr() and threads. In-Reply-To: <19990809224120.39659.qmail@hotmail.com> X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Steve Tarkalson said: > this is solved by one of two methods: > 1-) require the caller of gethostbyaddr() to supply a pointer to > a hostent struct which will be filled. > or 2-) the library uses thread specific storage which is re-used in > each call. > You could malloc() a struct hostent for each call to gethostby*(), each time registering the hostent in some list along with the thread's PID. If the same thread calls gethostby*, use the same buffer, or allocate a new one if another thread calls it. Have a static function be called atexit to free all the mallocs. -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 16:24:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id CA85C1536A for ; Mon, 9 Aug 1999 16:24:29 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id TAA68246; Mon, 9 Aug 1999 19:22:01 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199908092322.TAA68246@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ognir@humboldt1.com Cc: steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: gethostbyaddr() and threads. References: <199908092255.PAA08129@home.humboldt1.com> In-reply-to: Your message of "Mon, 09 Aug 1999 15:55:37 PDT." <199908092255.PAA08129@home.humboldt1.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Aug 1999 19:22:01 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ---Steve Tarkalson said: > > this is solved by one of two methods: > > 1-) require the caller of gethostbyaddr() to supply a pointer to > > a hostent struct which will be filled. > > or 2-) the library uses thread specific storage which is re-used in > > each call. > > > You could malloc() a struct hostent for each call to > gethostby*(), each time registering the hostent in some list along with the > thread's PID. If the same thread calls gethostby*, use the same buffer, or > allocate a new one if another thread calls it. Have a static function be called > atexit to free all the mallocs. Yuk! If you're writing a multithreaded program, a slightly different API for gethostbyname() is likely to be the least of your worries. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 16:56:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id BF1EE14FA2 for ; Mon, 9 Aug 1999 16:56:46 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp177-pm5.humboldt1.com [207.104.21.170]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id QAA18586; Mon, 9 Aug 1999 16:54:24 -0700 (PDT) Date: Mon, 9 Aug 1999 16:54:24 -0700 (PDT) Message-Id: <199908092354.QAA18586@home.humboldt1.com> From: Joe Groff To: louie@TransSys.COM Cc: steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Reply-To: ognir@humboldt1.com Subject: Re: gethostbyaddr() and threads. In-Reply-To: <199908092322.TAA68246@whizzo.transsys.com> X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Louis A. Mamakos said: >> You could malloc() a struct hostent for each call to >> gethostby*(), each time registering the hostent in some list along with the >> thread's PID. If the same thread calls gethostby*, use the same buffer, or >> allocate a new one if another thread calls it. Have a static function be > called >> atexit to free all the mallocs. > > Yuk! > > If you're writing a multithreaded program, a slightly different API for > gethostbyname() is likely to be the least of your worries. > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last resort, though, since we don't want to introduce to many FreeBSDisms into the already-fragmented-enough Unix world. Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps? -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 16:57: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 107911519C for ; Mon, 9 Aug 1999 16:57:00 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA14363; Mon, 9 Aug 1999 17:54:33 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA22388; Mon, 9 Aug 1999 17:54:32 -0600 Date: Mon, 9 Aug 1999 17:54:32 -0600 Message-Id: <199908092354.RAA22388@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Louis A. Mamakos" Cc: ognir@humboldt1.com, steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. In-Reply-To: <199908092322.TAA68246@whizzo.transsys.com> References: <199908092255.PAA08129@home.humboldt1.com> <199908092322.TAA68246@whizzo.transsys.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ---Steve Tarkalson said: > > > this is solved by one of two methods: > > > 1-) require the caller of gethostbyaddr() to supply a pointer to > > > a hostent struct which will be filled. > > > or 2-) the library uses thread specific storage which is re-used in > > > each call. > > > > > You could malloc() a struct hostent for each call to > > gethostby*(), each time registering the hostent in some list along with the > > thread's PID. If the same thread calls gethostby*, use the same buffer, or > > allocate a new one if another thread calls it. Have a static function be called > > atexit to free all the mallocs. > > Yuk! > > If you're writing a multithreaded program, a slightly different API for > gethostbyname() is likely to be the least of your worries. Agreed. gethostbyname_r() on solaris requires the caller to provide the address to write into, which is IMO the correct solution. Yes, it's a different API. But, the other alternatives are worse. The user must be able to control his memory allocation. For example, in a typical networking application, gethostbyname() could be called thousands or millions of times, and allocating memory everytime that can't be cleaned up until the program exits is completely unacceptable. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 17:56:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id C6DF414D75 for ; Mon, 9 Aug 1999 17:56:16 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp177-pm5.humboldt1.com [207.104.21.170]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id RAA28787; Mon, 9 Aug 1999 17:53:48 -0700 (PDT) Date: Mon, 9 Aug 1999 17:53:48 -0700 (PDT) Message-Id: <199908100053.RAA28787@home.humboldt1.com> From: Joe Groff To: louie@TransSys.COM Cc: steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Reply-To: ognir@humboldt1.com Subject: Re: gethostbyaddr() and threads. In-Reply-To: <199908092322.TAA68246@whizzo.transsys.com> X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Louis A. Mamakos said: >> ---Steve Tarkalson said: >> > this is solved by one of two methods: >> > 1-) require the caller of gethostbyaddr() to supply a pointer to >> > a hostent struct which will be filled. >> > or 2-) the library uses thread specific storage which is re-used in >> > each call. >> > >> You could malloc() a struct hostent for each call to >> gethostby*(), each time registering the hostent in some list along with the >> thread's PID. If the same thread calls gethostby*, use the same buffer, or >> allocate a new one if another thread calls it. Have a static function be > called >> atexit to free all the mallocs. > > Yuk! > > If you're writing a multithreaded program, a slightly different API for > gethostbyname() is likely to be the least of your worries. > Well, I guess we might as well change the API, since everyone else does. Unless someone comes up with a bettter idea, of course :) -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 18:10:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 83CA115341 for ; Mon, 9 Aug 1999 18:10:28 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id VAA47777; Mon, 9 Aug 1999 21:21:47 -0400 (EDT) Date: Mon, 9 Aug 1999 21:21:47 -0400 From: Dan Moschuk To: Joe Groff Cc: louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. Message-ID: <19990809212147.A47699@trinsec.com> References: <199908092322.TAA68246@whizzo.transsys.com> <199908100053.RAA28787@home.humboldt1.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908100053.RAA28787@home.humboldt1.com>; from Joe Groff on Mon, Aug 09, 1999 at 05:53:48PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Well, I guess we might as well change the API, since everyone else does. Unless | someone comes up with a bettter idea, of course :) | | -Joe The API should not change. There is already enough descrepency between UNIXs to warrant programs like autoconf, we should not introduce another. We should introduce a gethostbyaddr_r function, which shouldn't be all that though to implement. From the code that I looked at today, the problems lie inside of glibc. It declares globally a few static variables that are used by the gethost* functions. Obviously in a threaded environment, this is bad. A nice fix would be to get rid of those variables entirely. A quicker fix would be just to enclose those global variables in mutexes. Personally, I like the nicer fix better, which will (unfortunately) involve rewriting most of the frontends to the res_* functions. If no one has any objections, I'd like to start on this tomorrow. Thanks, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 18:19:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id 0CE8514FD0 for ; Mon, 9 Aug 1999 18:19:48 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp177-pm5.humboldt1.com [207.104.21.170]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id SAA02821; Mon, 9 Aug 1999 18:16:18 -0700 (PDT) Date: Mon, 9 Aug 1999 18:16:18 -0700 (PDT) Message-Id: <199908100116.SAA02821@home.humboldt1.com> From: Joe Groff To: dan@trinsec.com Cc: louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Reply-To: ognir@humboldt1.com Subject: Re: gethostbyaddr() and threads. In-Reply-To: <19990809212147.A47699@trinsec.com> X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Dan Moschuk said: > > | Well, I guess we might as well change the API, since everyone else does. > Unless > | someone comes up with a bettter idea, of course :) > | > | -Joe > > The API should not change. There is already enough descrepency between UNIXs > to warrant programs like autoconf, we should not introduce another. > We should introduce a gethostbyaddr_r function, which shouldn't be all that > though to implement. That's what I meant by an API change. Sorry for not being clearer. However, if you can roll in reentrancy without having to add the _r functions, that would save some sweat on the programmers' side. >>From the code that I looked at today, the problems lie inside of glibc. It > declares globally a few static variables that are used by the gethost* > functions. Obviously in a threaded environment, this is bad. > > A nice fix would be to get rid of those variables entirely. A quicker fix > would be just to enclose those global variables in mutexes. Personally, I > like the nicer fix better, which will (unfortunately) involve rewriting most > of the frontends to the res_* functions. > > If no one has any objections, I'd like to start on this tomorrow. > Go for it! Someone needs to. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 18:33:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D9DE152F2 for ; Mon, 9 Aug 1999 18:33:33 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp177-pm5.humboldt1.com [207.104.21.170]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id SAA05131 for freebsd-hackers@freebsd.org; Mon, 9 Aug 1999 18:30:51 -0700 (PDT) Date: Mon, 9 Aug 1999 18:30:51 -0700 (PDT) Message-Id: <199908100130.SAA05131@home.humboldt1.com> From: Joe Groff To: freebsd-hackers@freebsd.org Reply-To: ognir@humboldt1.com Subject: New kernel drivers X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (FreeBSD) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a device 'foo' which I'm working on. What files do I need to edit so that config recognizes foo as a controller/pseudo-device/device/disk/whatever? Thanks! -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 19:25: 6 1999 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 EC19915344 for ; Mon, 9 Aug 1999 19:24:59 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id WAA11443 for ; Mon, 9 Aug 1999 22:21:18 -0400 (EDT) Date: Mon, 9 Aug 1999 22:08:16 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Configuration mechanism of PCI bus 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 Even with "PCI System Architecture, 4th edition" at hand, I still have some problems understanding the code in isa/pcibus.c. Please point out any misunderstanding I may have in the following: (1) At first, you can not modify the address port at 0xcf8 without a FULL 32-bit write. The routine pci_cfgopen() seems to use this fact. (2) The constant CONF1_ENABLE_MSK includes 4 higher bus number bits, only 4 bits can be used as bus number, so we can have at most 16 PCI buses. (3) The variable "mode1res" seems to refer to any residual left by BIOS in the address port. If it is non-zero, we will try to find a device using configuration mechanism 1. (3) The magic constant 0xf870ff excludes many devices. How it is chosen? I guess those excluded devices are not important or supported by FreeBSD. It seems to me that if pci_cfgcheck() finds at least one device, then the configuration mechanism is regarded as correctly detected. Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit 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 Mon Aug 9 19:54:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 810F71532E for ; Mon, 9 Aug 1999 19:54:31 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA07363; Tue, 10 Aug 1999 10:48:12 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA28106; Tue, 10 Aug 1999 10:49:36 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (8.9.1b+Sun/SMI-SVR4) id KAA09518; Tue, 10 Aug 1999 10:49:33 +0800 (WST) Message-Id: <199908100249.KAA09518@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@freebsd.org Cc: shocking@ariadne.tensor.pgs.com, ognir@humboldt1.com Subject: Re: freebsd-hackers-digest V4 #576 In-reply-to: Your message of "Mon, 09 Aug 1999 13:34:57 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Aug 1999 10:49:33 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > = > I believe the joystick driver in FreeBSD could probably be redone, to s= upport > all the non-standard joysticks that many people (like me :) have. Havin= g > just recently converted to FreeBSD from Linux, though, I don't know the= best > way to go about it. Here are some ideas (sorry if my terminology is wro= ng): > = > (1) Redefine the core joystick code as a controller, and then have all = the > different joystick types ride on top of it, like: > = > controller joy0 at isa? port IO_GAME # Serves joystick port 0x2= 01 > #device jan0 at joy0 # Analog joystick > device jgpp0 at joy0 # Gravis GamePad Pro > etc... > This would also allow for modules to be used for all the different = joystick > types, I think. > = > (2) Have a monolithic joystick driver, with options to pick the proper = type: > = > device joy0 at isa? port IO_GAME # Just like it is now > options JOY_ANALOG > options JOY_GRAVIS > etc... > = > I also believe it should use the Linux joystick's device interface, so = that > folks that have already written their games to use the Linux joysticks = can work > in FreeBSD with minor effort. > = > Any help or comments are appreciated. > = I'm partway through porting Vojtech's Linux joystick code to FreeBSD, as = a = series of loadable modules. There is the main module (which is mostly = converted, although some of the Linuxisms are a bit hard to come up with = an = equivalent to, even with the Linux device drivers book) and a seperate mo= dule = for each of the different hardware devices. You'll kldload the main modul= e = first, then the device specific module, which'll call a joystick registra= tion = routine to make itself known. You've just spurred me into action and I ho= pe to = get the main module finished this weekend. The recent chatter about allowing kldload to give modules arguments is ve= ry = interesting, as it would allow one to specify port addresses and the like= =2E Stephen -- = The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could prod= uce the Complete Works of Shakespeare; now, thanks to the Internet, we k= now this is not true." Robert Wilensky, University of Califor= nia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22: 3:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id CB5E315371 for ; Mon, 9 Aug 1999 22:03:19 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp144-pm5.humboldt1.com [207.104.21.137]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id WAA08394; Mon, 9 Aug 1999 22:00:53 -0700 (PDT) Date: Mon, 9 Aug 1999 22:14:26 -0700 (PDT) From: Joe Groff X-Sender: joe@shovel.groff To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: hackers@FreeBSD.ORG, shocking@ariadne.tensor.pgs.com, ognir@humboldt1.com Subject: Re: freebsd-hackers-digest V4 #576 In-Reply-To: <199908100249.KAA09518@ariadne.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > > I believe the joystick driver in FreeBSD could probably be redone, to support > > all the non-standard joysticks that many people (like me :) have. Having > > just recently converted to FreeBSD from Linux, though, I don't know the best > > way to go about it. Here are some ideas (sorry if my terminology is wrong): > > > > (1) Redefine the core joystick code as a controller, and then have all the > > different joystick types ride on top of it, like: > > > > controller joy0 at isa? port IO_GAME # Serves joystick port 0x201 > > #device jan0 at joy0 # Analog joystick > > device jgpp0 at joy0 # Gravis GamePad Pro > > etc... > > This would also allow for modules to be used for all the different joystick > > types, I think. > > > > (2) Have a monolithic joystick driver, with options to pick the proper type: > > > > device joy0 at isa? port IO_GAME # Just like it is now > > options JOY_ANALOG > > options JOY_GRAVIS > > etc... > > > > I also believe it should use the Linux joystick's device interface, so that > > folks that have already written their games to use the Linux joysticks can work > > in FreeBSD with minor effort. > > > > Any help or comments are appreciated. > > > > I'm partway through porting Vojtech's Linux joystick code to FreeBSD, as a > series of loadable modules. There is the main module (which is mostly > converted, although some of the Linuxisms are a bit hard to come up with an > equivalent to, even with the Linux device drivers book) and a seperate module > for each of the different hardware devices. You'll kldload the main module > first, then the device specific module, which'll call a joystick registration > routine to make itself known. You've just spurred me into action and I hope to > get the main module finished this weekend. > > The recent chatter about allowing kldload to give modules arguments is very > interesting, as it would allow one to specify port addresses and the like. > > Stephen Well, I was going to try to roll my own for this, but it's always nice to know someone's already done it for me. :) I'm gone though for the next couple weeks though, so that'll be a nice thing to get back home to. Many thanks! Where will I be able to get it? -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:18: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 1CF9E14A12 for ; Mon, 9 Aug 1999 22:17:58 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id OAA09396; Tue, 10 Aug 1999 14:47:20 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199908100517.OAA09396@gizmo.internode.com.au> Subject: Re: freebsd-hackers-digest V4 #576 To: ognir@humboldt1.com (Joe Groff) Date: Tue, 10 Aug 1999 14:47:20 +0930 (CST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Joe Groff" at Aug 9, 99 10:14:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking wrote: > The recent chatter about allowing kldload to give modules arguments is very > interesting, as it would allow one to specify port addresses and the like. Would it be useful to be able to be able to do something like this: kldload -t kernel_config /sys/i386/conf/YOURKERNELNAME ... and have drivers consult the information they find in there for config hints? If newbus knew how to reconstruct config_devtab at runtime by parsing a "kernel_config" module's "device" and "controller" lines, we'd get dynamic runtime reconfiguration for free. It could even defer the initial construction of config_devtab until boot-time if you used "options INCLUDE_CONFIG_FILE" to provide default configuration data... - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:21:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 000F714D75 for ; Mon, 9 Aug 1999 22:21:46 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id NAA07709; Tue, 10 Aug 1999 13:17:24 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id NAA02198; Tue, 10 Aug 1999 13:18:49 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (8.9.1b+Sun/SMI-SVR4) id NAA09738; Tue, 10 Aug 1999 13:18:47 +0800 (WST) Message-Id: <199908100518.NAA09738@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joe Groff Cc: shocking@ariadne.tensor.pgs.com, hackers@freebsd.org Subject: Re: freebsd-hackers-digest V4 #576 In-reply-to: Your message of "Mon, 09 Aug 1999 22:14:26 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Aug 1999 13:18:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Stephen > Well, I was going to try to roll my own for this, but it's always nice to > know someone's already done it for me. :) I'm gone though for the next > couple weeks though, so that'll be a nice thing to get back home to. Many > thanks! > > Where will I be able to get it? > > -Joe > Well, it's not ready yet. I'll be putting it in as a PR once I've finished. Probably it'll be released to the multimedia group first as a test. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:36:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 99CF714D84 for ; Mon, 9 Aug 1999 22:36:17 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id WAA03299; Mon, 9 Aug 1999 22:31:18 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA19305; Mon, 9 Aug 1999 22:26:50 -0700 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA14998; Mon, 9 Aug 99 22:31:13 PDT Message-Id: <37AFB921.D3070875@softweyr.com> Date: Mon, 09 Aug 1999 23:31:13 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: ognir@humboldt1.com Cc: louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <199908092354.QAA18586@home.humboldt1.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Groff wrote: > > ---Louis A. Mamakos said: > >> You could malloc() a struct hostent for each call to > >> gethostby*(), each time registering the hostent in some list along with the > >> thread's PID. If the same thread calls gethostby*, use the same buffer, or > >> allocate a new one if another thread calls it. Have a static function be > > called > >> atexit to free all the mallocs. > > > > Yuk! > > > > If you're writing a multithreaded program, a slightly different API for > > gethostbyname() is likely to be the least of your worries. > > > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last > resort, though, since we don't want to introduce to many FreeBSDisms into the > already-fragmented-enough Unix world. > > Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps? Probably the way POSIX specifies, which would certainly be *our* target. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:44:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A1C7115371 for ; Mon, 9 Aug 1999 22:44:45 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id WAA03329; Mon, 9 Aug 1999 22:43:14 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA19417; Mon, 9 Aug 1999 22:38:46 -0700 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA15506; Mon, 9 Aug 99 22:43:09 PDT Message-Id: <37AFBBEC.7E078E26@softweyr.com> Date: Mon, 09 Aug 1999 23:43:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: ognir@humboldt1.com Cc: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <199908100116.SAA02821@home.humboldt1.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Groff wrote: > > ---Dan Moschuk said: > > > > | Well, I guess we might as well change the API, since everyone else does. > > Unless > > | someone comes up with a bettter idea, of course :) > > | > > | -Joe > > > > The API should not change. There is already enough descrepency between UNIXs > > to warrant programs like autoconf, we should not introduce another. > > We should introduce a gethostbyaddr_r function, which shouldn't be all that > > though to implement. > That's what I meant by an API change. Sorry for not being clearer. > However, if you can roll in reentrancy without having to add the _r > functions, that would save some sweat on the programmers' side. No, it wouldn't, because any existing programs that already handle name server queries within threads will already use the gethostby*_r APIs. > >>From the code that I looked at today, the problems lie inside of glibc. It > > declares globally a few static variables that are used by the gethost* > > functions. Obviously in a threaded environment, this is bad. > > > > A nice fix would be to get rid of those variables entirely. A quicker fix > > would be just to enclose those global variables in mutexes. Personally, I > > like the nicer fix better, which will (unfortunately) involve rewriting most > > of the frontends to the res_* functions. > > > > If no one has any objections, I'd like to start on this tomorrow. > > > Go for it! Someone needs to. :) Here are the prototypes. Hosts: #include #include #include #include #include struct hostent *gethostbyname_r(const char *name, struct hostent *result, char *buffer, int buflen, int *h_errnop); struct hostent *gethostbyaddr_r(const char *addr, int length, int type, struct hostent *result, char *buffer, int buflen, int *h_errnop); struct hostent *gethostent_r(struct hostent *result, char *buffer, int buflen, int *h_errnop); Nets: #include struct netent *getnetbyname_r(const char *name, struct netent *result, char *buffer, int buflen); struct netent *getnetbyaddr_r(long net, int type, struct netent *result, char *buffer, int buflen); struct netent *getnetent_r(struct netent *result, char *buffer, int buflen); Protocols: #include struct protoent *getprotobyname_r(const char *name, struct protoent *result, char *buffer, int buflen); struct protoent *getprotobynumber_r(int proto, struct protoent *result, char *buffer, int buflen); struct protoent *getprotoent_r(struct protoent *result, char *buffer, int buflen); Services: #include struct servent *getservbyname_r(const char *name, const char *proto, struct servent *result, char *buffer, int buflen); struct servent *getservbyport_r(int port, const char *proto, struct servent *result, char *buffer, int buflen); struct servent *getservent_r(struct servent *result, char *buffer, int buflen); RPC services: #include struct rpcent *getrpcbyname_r(const char * name, struct rpcent *result, char *buffer, int buflen); struct rpcent *getrpcbynumber_r(const int number, struct rpcent *result, char *buffer, int buflen); struct rpcent *getrpcent_r(struct rpcent *result, char *buffer, int buflen); Any questions? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:49:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.humboldt1.com (home.humboldt1.com [206.13.45.1]) by hub.freebsd.org (Postfix) with ESMTP id E496F15242 for ; Mon, 9 Aug 1999 22:49:16 -0700 (PDT) (envelope-from ognir@humboldt1.com) Received: from shovel.groff (ppp144-pm5.humboldt1.com [207.104.21.137]) by home.humboldt1.com (Pro-8.9.2/Pro-8.9.2) with SMTP id WAA14285; Mon, 9 Aug 1999 22:48:01 -0700 (PDT) Date: Mon, 9 Aug 1999 23:01:36 -0700 (PDT) From: Joe Groff X-Sender: joe@shovel.groff To: Wes Peters Cc: ognir@humboldt1.com, dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. In-Reply-To: <37AFBBEC.7E078E26@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Wes Peters wrote: > Here are the prototypes. Hosts: > > #include > #include > #include > #include > #include > > struct hostent *gethostbyname_r(const char *name, > struct hostent *result, char *buffer, int buflen, > int *h_errnop); > > struct hostent *gethostbyaddr_r(const char *addr, > int length, int type, struct hostent *result, > char *buffer, int buflen, int *h_errnop); > > struct hostent *gethostent_r(struct hostent *result, > char *buffer, int buflen, int *h_errnop); > > Nets: > > #include > > struct netent *getnetbyname_r(const char *name, > struct netent *result, char *buffer, int buflen); > > struct netent *getnetbyaddr_r(long net, int type, > struct netent *result, char *buffer, int buflen); > > struct netent *getnetent_r(struct netent *result, > char *buffer, int buflen); > > Protocols: > > #include > > struct protoent *getprotobyname_r(const char *name, > struct protoent *result, char *buffer, int buflen); > > struct protoent *getprotobynumber_r(int proto, > struct protoent *result, char *buffer, int buflen); > > struct protoent *getprotoent_r(struct protoent *result, > char *buffer, int buflen); > > Services: > > #include > > struct servent *getservbyname_r(const char *name, > const char *proto, struct servent *result, > char *buffer, int buflen); > > struct servent *getservbyport_r(int port, const char *proto, > struct servent *result, char *buffer, int buflen); > > struct servent *getservent_r(struct servent *result, > char *buffer, int buflen); > > RPC services: > > #include > > struct rpcent *getrpcbyname_r(const char * name, > struct rpcent *result, char *buffer, int buflen); > > struct rpcent *getrpcbynumber_r(const int number, > struct rpcent *result, char *buffer, int buflen); > > struct rpcent *getrpcent_r(struct rpcent *result, > char *buffer, int buflen); > > Any questions? Looks pretty close to the POSIX/GNU way. Good luck with it. -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 22:51: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 6BC49150FF for ; Mon, 9 Aug 1999 22:50:58 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id HAA03722; Tue, 10 Aug 1999 07:49:31 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa03715; Tue Aug 10 07:49:03 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id HAA11766; Tue, 10 Aug 1999 07:53:41 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id HAA00378; Tue, 10 Aug 1999 07:56:33 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <37AFBF11.B8F11E5F@post.com> Date: Tue, 10 Aug 1999 07:56:33 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ognir@humboldt1.com Cc: Hackers FreeBSD Subject: Re: New kernel drivers References: <199908100130.SAA05131@home.humboldt1.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Groff wrote: > I have a device 'foo' which I'm working on. What files do I need to edit so > that config recognizes foo as a controller/pseudo-device/device/disk/whatever? Take a look at /usr/src/sys/i386/files.i386. You device driver files need to have an entry in this file. Also make sure that you have your driver mentioned in your kernel config file. eT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 9 23:14: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 332DF14CBA for ; Mon, 9 Aug 1999 23:14:05 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id XAA03428; Mon, 9 Aug 1999 23:09:32 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id XAA19744; Mon, 9 Aug 1999 23:05:03 -0700 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16656; Mon, 9 Aug 99 23:09:30 PDT Message-Id: <37AFC219.6F7465A8@softweyr.com> Date: Tue, 10 Aug 1999 00:09:29 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Joe Groff Cc: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Groff wrote: > > On Mon, 9 Aug 1999, Wes Peters wrote: > > > > struct rpcent *getrpcent_r(struct rpcent *result, > > char *buffer, int buflen); > > > > Any questions? > > Looks pretty close to the POSIX/GNU way. Good luck with it. ;^) Straight from the Solaris man pages. Should be as POSIX as working code can be. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 0:42:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B10DF14C22 for ; Tue, 10 Aug 1999 00:42:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id AAA74195; Tue, 10 Aug 1999 00:31:42 -0700 (PDT) Date: Tue, 10 Aug 1999 00:32:07 -0700 (PDT) From: Julian Elischer To: eT Cc: ognir@humboldt1.com, Hackers FreeBSD Subject: Re: New kernel drivers In-Reply-To: <37AFBF11.B8F11E5F@post.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, eT wrote: > Joe Groff wrote: > > > I have a device 'foo' which I'm working on. What files do I need to edit so > > that config recognizes foo as a controller/pseudo-device/device/disk/whatever? > > Take a look at /usr/src/sys/i386/files.i386. You device driver files > need to have an entry in this file. Also make sure that you have your > driver mentioned in your kernel config file. Alternatively it might have an entry in files.MYCONFIG if you don't want to patch a distributed file. > > eT > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 2: 5:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D70A3153B9 for ; Tue, 10 Aug 1999 02:05:37 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id TAA05753 for hackers@FreeBSD.org; Tue, 10 Aug 1999 19:06:54 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199908100906.TAA05753@cimlogic.com.au> Subject: FreeBSD on VMEbus To: hackers@FreeBSD.org Date: Tue, 10 Aug 1999 19:06:53 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anyone using FreeBSD on a VMEbus PC? I have an application which should use VxWorks like the rest of the project, but since this part has been subcontracted, Wind River wants A$35,000 for an OEM licence for the right to link to their libraries. Blood suckers. They only charge A$5990 for the tools! I am being pressured to write a kernel driver for NT to run on the same machine that is doing some pretty heavy FFT calculations using LabView. I want to put a box in between, and if I can't have a realtime operating system, then I need something that I can embedded, like FreeBSD. The question is: out of all the VMEbus PCs available, which one is the best choice based on drivers working out-of-the box? Ethernet is particularly important. For those who are interested, here is a link to the main project: (JORN). Please save me from a fate worse than death. I got this contact on the basis that it _wasn't_ a Microsoft development, so either I need to jump off the nearest tall building, walk away, or find an alternative... -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 3:20:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C5346153C1 for ; Tue, 10 Aug 1999 03:20:35 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA20282 for ; Tue, 10 Aug 1999 19:50:34 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990810195034:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" Date: Tue, 10 Aug 1999 19:50:34 +0930 (CST) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Subject: STAILQ macros.. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990810195034:611=_ Content-Type: text/plain; charset=us-ascii Hi, I am looking at the STAILQ macros defined in and I am curious why it is necessary to declare stqh_last in the STAILQ_HEAD as a pointer to pointer, rather than just a pointer? (like the head pointer) Please don't laugh too hard.. my head hurts :) --- 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 --_=XFMail.1.3.p0.FreeBSD:990810195034:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN6/88lbYW/HEoF9pAQF3qwP8CKuwFM31epJqWMZ6OxXtGhz7hT5VakD4 m5ztpMtb9oNgtWEx7WdmN7CIs3aTKO2uKj854X4ostov0Z0HjB08Zv708Kja9uEB G3kubtfCxAZk7u43KNfUZ7MkajBswhhnMY+wLN4KGv3iYk+Ujr9r/wLGToFUSbnz RCen9ILTTQo= =1xEe -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990810195034:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 4:25:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id E46391524B for ; Tue, 10 Aug 1999 04:25:48 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA10329; Tue, 10 Aug 1999 07:22:35 -0400 (EDT) Date: Tue, 10 Aug 1999 07:22:35 -0400 (EDT) From: Daniel Eischen Message-Id: <199908101122.HAA10329@pcnet1.pcnet.com> To: hackers@FreeBSD.ORG, jb@cimlogic.com.au Subject: Re: FreeBSD on VMEbus Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > I have an application which should use VxWorks like the rest of the > project, but since this part has been subcontracted, Wind River wants > A$35,000 for an OEM licence for the right to link to > their libraries. Blood suckers. They only charge A$5990 for the tools! > > I am being pressured to write a kernel driver for NT to run on the same > machine that is doing some pretty heavy FFT calculations using LabView. > I want to put a box in between, and if I can't have a realtime operating > system, then I need something that I can embedded, like FreeBSD. > > The question is: out of all the VMEbus PCs available, which one is the > best choice based on drivers working out-of-the box? Ethernet is > particularly important. We've got a couple of General Micro Systems (www.gms4vme.com) SBC PCs, one single CPU and one dual CPU Pentium. They run Labview and NT fine :( I've booted FreeBSD on them a couple of years ago successfully. These SBCs (Mustang) were nice in that they had on-board aic7880 SCSI controller and DEC 21040 10/100 Ethernet. The newer models (see above web site) look rather nice also (dual Intel 10/100 Ethernet and 53C875 SCSI). A Tundra Universe II chip provides a PCI<->VMEbus interface. I've got the full documentation for the chip and it should be possible to make it work under FreeBSD, especially with newbus. You can download the documents for the chip at: http://www.tundra.com/index_prod.cfm?tree_id=100362 This isn't going to work out of the box, but if you only want to memory map VME devices, it shouldn't be that hard to teach FreeBSD that much. The bridge chip provides both master and slave addresses (A16/A24/A32) that look to be easy to configure. The chip also supports mapping of VMEbus interrupts to PCI bus interrupts. > For those who are interested, here is a link to the main project: > (JORN). > > Please save me from a fate worse than death. I got this contact on the > basis that it _wasn't_ a Microsoft development, so either I need to jump > off the nearest tall building, walk away, or find an alternative... Supporting VMEbus under FreeBSD is something that we'd like to see also (especially the Tundra chip). Believe it or not, we have had good luck running real-time simulations under Solaris on Force Computers SPARC SBCs with VMEbus. They provide the VMEbus (nexus) driver for Solaris, and you can easily write Solaris drivers for VMEbus devices. mmap is also supported for simply mapping memory to VMEbus devices. We've done both without any problems and have a fully populated 21-slot chassis. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 5:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id 4E406153DD for ; Tue, 10 Aug 1999 05:41:26 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11EBCB-000MD1-00; Tue, 10 Aug 1999 13:39:59 +0100 To: dan@trinsec.com From: Tony Finch Cc: hackers@freebsd.org Subject: Re: gethostbyaddr() and threads. In-Reply-To: <19990809212147.A47699@trinsec.com> References: <199908092322.TAA68246@whizzo.transsys.com> <199908100053.RAA28787@home.humboldt1.com> <199908100053.RAA28787@home.humboldt1.com> Message-Id: Date: Tue, 10 Aug 1999 13:39:59 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > >A quicker fix would be just to enclose those global variables in >mutexes. God, no. The resolver is already stupidly unparallelizable -- there's no need to make it thread-resistant too. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 6:12:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 50976153E4 for ; Tue, 10 Aug 1999 06:12:11 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA28488; Tue, 10 Aug 1999 06:11:26 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id GAA08074; Tue, 10 Aug 1999 06:11:25 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA07490; Tue, 10 Aug 1999 06:11:24 -0700 (PDT) From: Don Lewis Message-Id: <199908101311.GAA07490@salsa.gv.tsc.tdk.com> Date: Tue, 10 Aug 1999 06:11:24 -0700 In-Reply-To: Dan Moschuk "Re: gethostbyaddr() and threads." (Aug 9, 9:21pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Dan Moschuk , Joe Groff Subject: Re: gethostbyaddr() and threads. Cc: louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 9, 9:21pm, Dan Moschuk wrote: } Subject: Re: gethostbyaddr() and threads. } } | Well, I guess we might as well change the API, since everyone else does. Unless } | someone comes up with a bettter idea, of course :) } | } | -Joe } } The API should not change. There is already enough descrepency between UNIXs } to warrant programs like autoconf, we should not introduce another. } We should introduce a gethostbyaddr_r function, which shouldn't be all that } though to implement. } } >From the code that I looked at today, the problems lie inside of glibc. It } declares globally a few static variables that are used by the gethost* } functions. Obviously in a threaded environment, this is bad. } } A nice fix would be to get rid of those variables entirely. A quicker fix } would be just to enclose those global variables in mutexes. Personally, I } like the nicer fix better, which will (unfortunately) involve rewriting most } of the frontends to the res_* functions. } } If no one has any objections, I'd like to start on this tomorrow. You might want to grab the latest BIND release from ftp.isc.org. One of the comments in the CHANGES file from a while ago is: 384. [feature] there is now a nearly-thread-safe resolver API, with the old non-thread-safe API being a set of stubs on top of this. it is possible to program without _res. note: the documentation has not been updated. also note: IRS is a thread-ready API, get*by*() is not. (see ../contrib/manyhosts for an example application.) There's no sense re-inventing any more wheels than necessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 6:29:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id D3DD515444 for ; Tue, 10 Aug 1999 06:29:32 -0700 (PDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA22653; Tue, 10 Aug 1999 09:26:44 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.pa.dtd.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id JAA01963; Tue, 10 Aug 1999 09:26:44 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <199908101326.JAA01963@bmcgover-pc.cisco.com> To: ognir@humboldt1.com Cc: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. In-reply-to: Your message of "Mon, 09 Aug 1999 14:21:38 PDT." <199908092121.OAA21266@home.humboldt1.com> Date: Tue, 10 Aug 1999 09:26:44 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> gethostbyaddr... actually, most of the gethostby* functions... are not >> thread safe. They all use a static buffer in the library. >> >> Therefore, with threads, if you don't take precautions, I'd expect your >> results to be odd. >> -Brian >> >Couldn't this be easily fixed? I haven't looked at the source yet, but I >believe you could replaced the static buffers with a dynamically-allocated list >of buffers, with one for each thread using the gethost functions. Or perhaps >you could just eliminate all the static stuff altogether? -Joe You could, but thats not what was asked. Nor is the solution portable. Posix warns that these functions are not thread safe. Realistically, the portable solution would be to mutex lock (or equiv.) around the calls, so that only one thread can call the function(s) at a time, and be sure to copy the results out of the temporary buffers before releasing the locks. (see note on "if you don't take precautions") An even more interesting solution may be to write some wrappers that do the lock, call the function, and store the result in a thread-specific area, then unlock again. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 8:16:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 38F1115013 for ; Tue, 10 Aug 1999 08:16:41 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id LAA50942; Tue, 10 Aug 1999 11:28:36 -0400 (EDT) Date: Tue, 10 Aug 1999 11:28:36 -0400 From: Dan Moschuk To: Wes Peters Cc: ognir@humboldt1.com, louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. Message-ID: <19990810112836.B50820@trinsec.com> References: <199908092354.QAA18586@home.humboldt1.com> <37AFB921.D3070875@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37AFB921.D3070875@softweyr.com>; from Wes Peters on Mon, Aug 09, 1999 at 11:31:13PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last | > resort, though, since we don't want to introduce to many FreeBSDisms into the | > already-fragmented-enough Unix world. | > | > Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps? | | Probably the way POSIX specifies, which would certainly be *our* target. And does POSIX specify it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 8:22:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 9407915013 for ; Tue, 10 Aug 1999 08:22:45 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id LAA50991; Tue, 10 Aug 1999 11:34:32 -0400 (EDT) Date: Tue, 10 Aug 1999 11:34:32 -0400 From: Dan Moschuk To: Don Lewis Cc: Joe Groff , louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. Message-ID: <19990810113432.C50820@trinsec.com> References: <199908101311.GAA07490@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908101311.GAA07490@salsa.gv.tsc.tdk.com>; from Don Lewis on Tue, Aug 10, 1999 at 06:11:24AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | } If no one has any objections, I'd like to start on this tomorrow. | | You might want to grab the latest BIND release from ftp.isc.org. One | of the comments in the CHANGES file from a while ago is: | | 384. [feature] there is now a nearly-thread-safe resolver API, with | the old non-thread-safe API being a set of stubs on | top of this. it is possible to program without _res. | note: the documentation has not been updated. also | note: IRS is a thread-ready API, get*by*() is not. | (see ../contrib/manyhosts for an example application.) | | There's no sense re-inventing any more wheels than necessary. Great! This makes my job even easier! Does anyone have any issues with merging the new bind resolver API into libc? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 9: 6:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id DC47215150 for ; Tue, 10 Aug 1999 09:06:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #1) id 11EEPk-0004uR-00; Tue, 10 Aug 1999 10:06:13 -0600 Message-ID: <37B04DF4.136D3870@softweyr.com> Date: Tue, 10 Aug 1999 10:06:12 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Moschuk Cc: ognir@humboldt1.com, louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <199908092354.QAA18586@home.humboldt1.com> <37AFB921.D3070875@softweyr.com> <19990810112836.B50820@trinsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > > | > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last > | > resort, though, since we don't want to introduce to many FreeBSDisms into the > | > already-fragmented-enough Unix world. > | > > | > Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps? > | > | Probably the way POSIX specifies, which would certainly be *our* target. > > And does POSIX specify it? You didn't get the message with the function prototypes? I can send it again. This would be the *correct* way to implement thread-safe get*by* calls, since any existing threaded code (Solaris, Linux, etc.) will use these interfaces. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 9:20:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id F0FEB14CE0 for ; Tue, 10 Aug 1999 09:20:37 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA13027; Tue, 10 Aug 1999 09:19:02 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 10 Aug 1999 09:19:02 -0700 Date: Tue, 10 Aug 1999 09:19:01 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Wes Peters Cc: Dan Moschuk , ognir@humboldt1.com, louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. In-Reply-To: <37B04DF4.136D3870@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: wes@softweyr.com,dan@trinsec.com,ognir@humboldt1.com,louie@TransSys.COM,steve_tarkalson@hotmail.com,bmcgover@cisco.com,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Wes Peters wrote: > Dan Moschuk wrote: > > > > | > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last > > | > resort, though, since we don't want to introduce to many FreeBSDisms into the > > | > already-fragmented-enough Unix world. > > | > > > | > Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps? > > | > > | Probably the way POSIX specifies, which would certainly be *our* target. > > > > And does POSIX specify it? > > You didn't get the message with the function prototypes? I can send it again. > This would be the *correct* way to implement thread-safe get*by* calls, since > any existing threaded code (Solaris, Linux, etc.) will use these interfaces. Small detail, but having ported a multi-threaded library to Linux either Linux is not posix-compliant or everyone else (solaris and others) is not. It's _r API is quite different. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://softweyr.com/ wes@softweyr.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 9:39: 3 1999 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 7E88D14BF3 for ; Tue, 10 Aug 1999 09:38:58 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA24042; Wed, 11 Aug 1999 01:36:47 +0900 (JST) Message-ID: <37B05320.E6722A4B@newsguy.com> Date: Wed, 11 Aug 1999 01:28:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Dan Moschuk Cc: Don Lewis , Joe Groff , louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <199908101311.GAA07490@salsa.gv.tsc.tdk.com> <19990810113432.C50820@trinsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Moschuk wrote: > > Does anyone have any issues with merging the new bind resolver API into > libc? Well, Terry does, though I don't quite recall his reasoning. :-) Notice, he objects the way FreeBSD is today, with the bind resolver API inside libc. Of foremost importance, though, check the license. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 10:42: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 6F8F6153EA for ; Tue, 10 Aug 1999 10:40:29 -0700 (PDT) (envelope-from ccsanady@scl.ameslab.gov) Received: from scl.ameslab.gov (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id EFDD6C7; Tue, 10 Aug 1999 12:38:26 -0500 (CDT) Message-ID: <37B06392.1474E63A@scl.ameslab.gov> Date: Tue, 10 Aug 1999 12:38:26 -0500 From: Chris Csanady Reply-To: cc@137.org X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, ja, ru MIME-Version: 1.0 To: "Alton, Matthew" Cc: "'Hackers@FreeBSD.ORG'" Subject: Re: BSD XFS Port & BSD VFS Rewrite References: <0740CBD1D149D31193EB0008C7C56836EB8AFC@STLABCEXG012> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alton, Matthew" wrote: > > I am currently conducting a thorough study of the VFS subsystem > in preparation for an all-out effort to port SGI's XFS filesystem to > FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon > has written in hackers- that the VFS subsystem is presently not > well understood by any of the active kernel code contributers and > that it will be rewritten later this year. This is obviously of great > concern to me in this port. I greatly appreciate all assistance in > answering the following questions: > > 1) What are the perceived problems with the current VFS? > 2) What options are available to us as remedies? > 3) To what extent will existing FS code require revision in order > to be useful after the rewrite? > 4) Will Chapters 6,7,8 & 9 of "The Design and Implementation of > the 4.4BSD Operating System" still pertain after the rewrite? > 5) How important are questions 3 & 4 in the design of the new > VFS? > > I believe that the VFS is conceptually sound and that the existing > semantics should be strictly retained in the new code. Any new > functionality should be added in the form of entirely new kernel > routines and system calls, or possibly by such means as > converting the existing routines to the vararg format &etc. > > Does anyone know when SGI will release XFS? I don't know, but I came across this at SGI: http://oss.sgi.com/projects/xfs/ It looks as though they plan to release it under the GPL. :( Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 10:58:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 5BB8D14EE7 for ; Tue, 10 Aug 1999 10:58:47 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id NAA16837; Tue, 10 Aug 1999 13:57:09 -0400 (EDT) Date: Tue, 10 Aug 1999 13:57:09 -0400 (EDT) From: Ben Rosengart To: cc@137.org Cc: "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" Subject: Re: BSD XFS Port & BSD VFS Rewrite In-Reply-To: <37B06392.1474E63A@scl.ameslab.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Chris Csanady wrote: > I don't know, but I came across this at SGI: > > http://oss.sgi.com/projects/xfs/ > > It looks as though they plan to release it under the GPL. :( So? It can still be distributed with FreeBSD. How many people are going to want to modify this code anyway? -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 10:59:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (Postfix) with SMTP id CDA9714A13 for ; Tue, 10 Aug 1999 10:58:49 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id MAA28936; Tue, 10 Aug 1999 12:58:10 -0500 Received: from stlexggtw002-pozzoli.fw-users.busch.com(151.145.101.130) by gatewaya.anheuser-busch.com via smap (V5.0) id xma028785; Tue, 10 Aug 99 12:57:57 -0500 Received: from stlabcexg004.anheuser-busch.com ([151.145.101.160]) by 151.145.101.130 (Norton AntiVirus for Internet Email Gateways 1.0) ; Tue, 10 Aug 1999 17:55:53 0000 (GMT) Received: by stlabcexg004.anheuser-busch.com with Internet Mail Service (5.5.2448.0) id ; Tue, 10 Aug 1999 12:55:52 -0500 Message-ID: <0740CBD1D149D31193EB0008C7C56836EB8B00@STLABCEXG012> From: "Alton, Matthew" To: "'cc@137.org'" Cc: "'Hackers@FreeBSD.ORG'" Subject: RE: BSD XFS Port & BSD VFS Rewrite Date: Tue, 10 Aug 1999 12:55:43 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for this link. I assume that SGI will release the XFS code under some species of corporate community licensing scheme. The BSD/XFS will be implemented as an optional bolt-on set of kernel modules in a manner designed to avoid GPL-ifying the BSD kernel. I currently believe that this can be done so long as the modules constitute a discrete "product." I will have my lawyer confirm this when the details of the SGI license become public. > -----Original Message----- > From: Chris Csanady [SMTP:ccsanady@scl.ameslab.gov] > Sent: Tuesday, August 10, 1999 12:38 PM > To: Alton, Matthew > Cc: 'Hackers@FreeBSD.ORG' > Subject: Re: BSD XFS Port & BSD VFS Rewrite > > "Alton, Matthew" wrote: > > > > I am currently conducting a thorough study of the VFS subsystem > > in preparation for an all-out effort to port SGI's XFS filesystem to > > FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon > > has written in hackers- that the VFS subsystem is presently not > > well understood by any of the active kernel code contributers and > > that it will be rewritten later this year. This is obviously of great > > concern to me in this port. I greatly appreciate all assistance in > > answering the following questions: > > > > 1) What are the perceived problems with the current VFS? > > 2) What options are available to us as remedies? > > 3) To what extent will existing FS code require revision in order > > to be useful after the rewrite? > > 4) Will Chapters 6,7,8 & 9 of "The Design and Implementation of > > the 4.4BSD Operating System" still pertain after the rewrite? > > 5) How important are questions 3 & 4 in the design of the new > > VFS? > > > > I believe that the VFS is conceptually sound and that the existing > > semantics should be strictly retained in the new code. Any new > > functionality should be added in the form of entirely new kernel > > routines and system calls, or possibly by such means as > > converting the existing routines to the vararg format &etc. > > > > Does anyone know when SGI will release XFS? > > I don't know, but I came across this at SGI: > > http://oss.sgi.com/projects/xfs/ > > It looks as though they plan to release it under the GPL. :( > > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 11:14:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.141.33]) by hub.freebsd.org (Postfix) with ESMTP id 2984515105 for ; Tue, 10 Aug 1999 11:14:27 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.9.3/8.9.3) with ESMTP id NAA22868; Tue, 10 Aug 1999 13:27:16 -0400 X-Authentication-Warning: dragon.ham.muohio.edu: howardjp owned process doing -bs Date: Tue, 10 Aug 1999 13:27:16 -0400 (EDT) From: Jamie Howard X-Sender: howardjp@dragon.ham.muohio.edu To: cc@137.org Cc: "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" Subject: Re: BSD XFS Port & BSD VFS Rewrite In-Reply-To: <37B06392.1474E63A@scl.ameslab.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Aug 1999, Chris Csanady wrote: > I don't know, but I came across this at SGI: > > http://oss.sgi.com/projects/xfs/ > > It looks as though they plan to release it under the GPL. :( This is why people should start emailing asking for a dual-license that would support incorporation into FreeBSD. If I remember my history right[1], SGI based Irix on BSD extensively and became the first POSIX compatable BSD. See if you can play off some sense of loyalty. Explain to them that using a dual license would permit even further use of the product. Is there a stock "Please use a BSD license instead" letter that is kept around for these purposes? Jamie [1] This is always questionable. And when the history doesn't fit what I need it to say, I change it anyway:) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 11:16:10 1999 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 9BC571506F for ; Tue, 10 Aug 1999 11:16: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 MAA17279; Tue, 10 Aug 1999 12:15:55 -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 MAA13264; Tue, 10 Aug 1999 12:16:08 -0600 (MDT) Message-Id: <199908101816.MAA13264@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: gethostbyaddr() and threads. Cc: Dan Moschuk , Don Lewis , Joe Groff , louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 01:28:16 +0900." <37B05320.E6722A4B@newsguy.com> References: <37B05320.E6722A4B@newsguy.com> <199908101311.GAA07490@salsa.gv.tsc.tdk.com> <19990810113432.C50820@trinsec.com> Date: Tue, 10 Aug 1999 12:16:08 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37B05320.E6722A4B@newsguy.com> "Daniel C. Sobral" writes: : Well, Terry does, though I don't quite recall his reasoning. :-) : Notice, he objects the way FreeBSD is today, with the bind resolver : API inside libc. The size of _res has changed. Although it starts with an _, it is officially part of the API. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 12:45:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id D110B14EE5 for ; Tue, 10 Aug 1999 12:45:31 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id VAA00322; Tue, 10 Aug 1999 21:46:09 +0200 (CEST) To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. References: <199908101311.GAA07490@salsa.gv.tsc.tdk.com> <19990810113432.C50820@trinsec.com> <37B05320.E6722A4B@newsguy.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 10 Aug 1999 21:46:09 +0200 In-Reply-To: "Daniel C. Sobral"'s message of "Wed, 11 Aug 1999 01:28:16 +0900" Message-ID: <5lso5riflq.fsf@assaris.sics.se> Lines: 25 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > Of foremost importance, though, check the license. Are we still talking about irs? I don't find any particular strange licenses in src/lib/irs in recent bind distributions: /assar /* * Copyright (c) 1996,1999 by Internet Software Consortium. * * Permission to use, copy, modify, and distribute this software for any * purpose with or without fee is hereby granted, provided that the above * copyright notice and this permission notice appear in all copies. * * THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS * ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE * CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL * DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR * PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS * ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS * SOFTWARE. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 13: 5:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DBB3014EE5 for ; Tue, 10 Aug 1999 13:05:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EI8r-0006M0-00 for hackers@freebsd.org; Tue, 10 Aug 1999 22:05:01 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Using legacy sysinstall to upgrade live system Date: Tue, 10 Aug 1999 22:05:01 +0200 Message-ID: <24427.934315501@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've just gotten feedback from PR 12777, in which at least 2 people are complaining that sysinstall as installed by 3.1-RELEASE can not be used to upgrade a live machine to 3.2-RELEASE on the fly. I've told both parties that they need to use a boot floppy with the correct version of sysinstall, or build a 3.2-RELEASE sysinstall from source, and one of the chaps I'm speaking to thinks that this is unreasonable. Before I tell him that diffs are welcome, I thought I'd check that I'm not making a mistake here. I lost my confidence when it was pointed out that sysinstall can be given any arbitrary release name to use for Upgrade without issuing any warnings. So? Am I wrong? If you _are_ supposed to be able to upgrade to any arbitrary release using sysinstall as installed by any prior release, perhaps someone could suggest the cause of the problems reported on the PR? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 13:26: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from opera.kharkov.ua (opera.kharkov.ua [193.124.76.194]) by hub.freebsd.org (Postfix) with ESMTP id 2272D1546B for ; Tue, 10 Aug 1999 13:25:57 -0700 (PDT) (envelope-from Tosh@assa.vl.net.ua) Received: from [193.124.76.15] (helo=assa.vl.net.ua) by opera.kharkov.ua with esmtp (Exim 2.05 #6) id 11EISW-0000n4-00 for hackers@freebsd.org; Tue, 10 Aug 1999 23:25:20 +0300 Received: from ws7 ([192.168.1.16] helo=ws7.assa.vl.net.ua) by assa.vl.net.ua with esmtp (Exim 2.053 #1) id 11EIR4-0007ZG-00 for hackers@freebsd.org; Tue, 10 Aug 1999 23:23:50 +0300 Date: Tue, 10 Aug 1999 23:23:43 +0300 From: Anton X-Mailer: The Bat! (v1.34a) S/N EBAD242B Reply-To: Anton X-Priority: 3 (Normal) Message-ID: <1974.990810@assa.vl.net.ua> To: hackers@freebsd.org Subject: ppp header size 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 could you tell me, what size is ppp header on FreeBSD? anton. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 20: 1:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uumail.elektra.ru (uumail.elektra.ru [193.125.99.66]) by hub.freebsd.org (Postfix) with ESMTP id 59B0814EB9 for ; Tue, 10 Aug 1999 20:01:22 -0700 (PDT) (envelope-from kuzbe!experiment.kec.ke!kec.kuzbe.elektra.ru!sysadmin@oasis.osib.elektra.ru) Received: from kuzbe!experiment.kec.ke!kec.kuzbe.elektra.ru (uucp@localhost) by uumail.elektra.ru (8.9.3/8.9.2) with UUCP id HAA45708 for hackers@freebsd.org; Wed, 11 Aug 1999 07:01:55 +0400 (MSD) Received: from experiment.kec.ke (experiment.kec.ke [10.2.1.55]) by kec.kuzbe.elektra.ru with ESMTP id IAA13892 (8.8.5m/8.6.12 for ); Wed, 11 Aug 1999 08:09:58 +0800 (MSD) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 11 Aug 1999 08:13:47 +0800 (KRSS) From: Gutov Grigory To: hackers@freebsd.org Subject: Question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All. I have a question. I buy 6 MegaRAID Ultra PCI SCSI Disk Array Controller's and want to use they in FreeBSD, but not found driver. I wrote to support@ami.com and they siad that no driver for FreeBSD. I found driver for Linux and want use it in FreeBSD 3.1-3.2. How ? P.S. Sorry for my bad english. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 21: 8:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 982C014DFE for ; Tue, 10 Aug 1999 21:08:35 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA01686; Wed, 11 Aug 1999 13:38:38 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990811133838:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" Date: Wed, 11 Aug 1999 13:38:38 +0930 (CST) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Subject: Kernel malloc problem? Cc: bvandepe@gsoft.com.au Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990811133838:611=_ Content-Type: text/plain; charset=us-ascii We are experiencing what appears to be a memory corruption problem with a kernel device driver running under FreeBSD 2.2.8-STABLE with the CAM patches. The driver manages a series of memory buffers implemented using a singly-linked tail list. The number and size of buffers may be changed via an ioctl call which causes all of the currently-allocated buffers (one per tail list element) to be deallocated, and a new set - matching the required buffer size - to be malloc'ed. The tail queue holding the newly- allocated buffers is a local copy, and not subject to change in the event of an interrupt meant for the driver. Given certain choices for the size and number of buffers, we are observing corruption of the local copy of the tail queue during and after the memory allocation process. The corruption usually takes the form of a NULL pointer overwriting the linking member of a queue element somewhere in the list, thus rendering some protions of the allocated memory to be "lost", or non-free-able. The particular combination of buffer size and number of buffers which exhibits the problem is: buffer_size = 8k + 8 bytes (8k buffer + link pointer etc) num_buffers >= 22. If less than 22 buffers are allocated, the list appears to remain intact. I'm not sure if it's relavant, but I note that 22 * 8k is just over the 256 kb size, while 21 * 8k is less than this total. Here is the snipet of code which builds the list -> STAILQ_INIT(&buildlist); gsio_tossbuffers(sc); /* dump old buffers */ i = args->value; while(i--) { /* allocate required buffers */ gb = malloc(sizeof(struct gsio_buf) + args->which, M_DEVBUF, M_NOWAIT); debug(BUF2, "g_freelist +> %p", gb); if (gb == NULL) { /* allocate failed, toss all * buffers */ debug(BUF, "failed to allocate buffers, freeing"); while ((gb = STAILQ_FIRST(&buildlist)) != NULL) { STAILQ_REMOVE_HEAD(&buildlist, g_link); free(gb, M_DEVBUF); } error = ENOMEM; break; } else { STAILQ_INSERT_HEAD(&buildlist, gb, g_link); debug(BUF, "New buffer at %p length 0x%x, next is %p ,tail is %p", gb, sizeof(struct gsio_buf) + args->which, gb->g_link.stqe_next, buildlist.stqh_last); } } --- 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 --_=XFMail.1.3.p0.FreeBSD:990811133838:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN7D3RVbYW/HEoF9pAQFRtwP9HuRIBLhozHk/bzcLA/QR/ElUMvgxUB9I Ferhxxt6AwnxJuBqBSs2KytD2X5HWpNoB/Mw+PKj5HsTucL7XsJD2T7+Jd9+MHBD jsKrTB11lYeSumDXbCN6g9kysQ3bUM0DzLDJGS/6MPQu5+vsV+jglf3bm7HFVFfx T6OaL0vOans= =mbl5 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990811133838:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 21:34:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ACE0514DFE for ; Tue, 10 Aug 1999 21:34:25 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA72189; Tue, 10 Aug 1999 21:32:38 -0700 (PDT) (envelope-from dillon) Date: Tue, 10 Aug 1999 21:32:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199908110432.VAA72189@apollo.backplane.com> To: "Daniel O'Connor" Cc: freebsd-hackers@FreeBSD.ORG, bvandepe@gsoft.com.au Subject: Re: Kernel malloc problem? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :size - to be malloc'ed. The tail queue holding the newly- :allocated buffers is a local copy, and not subject to change :in the event of an interrupt meant for the driver. Given If the interrupt scans or in any way accesses the buffer list, you have to disable interrupts temporarily using the appropriate spl*() calls whenever your non-interrupt code (i.e. the ioctl code) makes modifications to the list. Otherwise the interrupt might occur while the list and/or buffers are in an invalid state. If that isn't the problem, look for situations where you might be corrupting memory within the driver. The two most common situations are where you accidently leave references to a buffer you just freed, or where you overrun a buffer. :--- :Daniel O'Connor software and network engineer -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 22:16:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id BCB39154B4 for ; Tue, 10 Aug 1999 22:15:09 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA02458; Wed, 11 Aug 1999 14:44:18 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990811144418:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <199908110432.VAA72189@apollo.backplane.com> Date: Wed, 11 Aug 1999 14:44:18 +0930 (CST) From: "Daniel O'Connor" To: Matthew Dillon Subject: Re: Kernel malloc problem? Cc: bvandepe@gsoft.com.au, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990811144418:611=_ Content-Type: text/plain; charset=us-ascii On 11-Aug-99 Matthew Dillon wrote: > If the interrupt scans or in any way accesses the buffer list, > you have to disable interrupts temporarily using the appropriate > spl*() calls whenever your non-interrupt code (i.e. the ioctl code) > makes modifications to the list. Otherwise the interrupt might > occur while the list and/or buffers are in an invalid state. Yes we have splhigh() around code which modifies any of the lists/pointers that the interrupt routine calls. > If that isn't the problem, look for situations where you might > be corrupting memory within the driver. The two most common > situations are where you accidently leave references to a buffer > you just freed, or where you overrun a buffer. Yes, well the we can reproduce the corruption. One place it happens is during the construction of the list (the code I showed you). The list in question is used by _nothing_ else (the list is built and then 'transfered' to the list the interrupt handler will used). The corruption seems to occur while the list is being built, but only with some specific buffer sizes :-/ --- 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 --_=XFMail.1.3.p0.FreeBSD:990811144418:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN7EGqlbYW/HEoF9pAQEFQgQAp7pE2/PfIGXTf1XUpAAuxA6EQTpryGU4 EH1xhFGrbD2l8Nc4e/6Ys1zGbGkW+2kpgIR/uGSPJimKq+t4G4Sefo0qQ6hYnA2K 1UpISmtUscHkSYqlZHUUDjNFvUUDAB0ml+/A5Gb0ZXPSUhnIyu8eaagXYtiHxO+M sqQDJQcMUNA= =Bkp1 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990811144418:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 10 22:55: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 393FB14F7C for ; Tue, 10 Aug 1999 22:54:45 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA92641 for ; Wed, 11 Aug 1999 12:51:52 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 11 Aug 1999 12:51:52 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: AccelePort C/X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! are there any device drivers for any *BSD for DigiBoard AccelePort C/X or should I start writing them myself? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 0: 8: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5697C14FCB for ; Wed, 11 Aug 1999 00:08:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA19703; Wed, 11 Aug 1999 00:07:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system In-reply-to: Your message of "Tue, 10 Aug 1999 22:05:01 +0200." <24427.934315501@axl.noc.iafrica.com> Date: Wed, 11 Aug 1999 00:07:41 -0700 Message-ID: <19699.934355261@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 3:16:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.pl (home.pl [195.205.230.32]) by hub.freebsd.org (Postfix) with SMTP id 7CE3114F00 for ; Wed, 11 Aug 1999 03:16:44 -0700 (PDT) (envelope-from steve@home.pl) Received: from haven.home.net.pl (HELO haven) (195.205.230.2) by home.pl with SMTP; 11 Aug 1999 10:16:23 -0000 Message-ID: <017f01bee3e2$86c62840$02e6cdc3@haven.home.net.pl> From: "Steven Jurczyk" To: Subject: how fast get real/absolute path of file Date: Wed, 11 Aug 1999 12:16:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How fast get real / absolute path of specified file. I try use readlink, = but this slow (for path /home/web/docs/index.htm must be done 4 or more = (if this path have symlinks) readlink's - for /home, /home/web, = /home/web/docs and /home/web/docs/index.htm). Is any faster/simpler = method for getting absolute path of file? Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 4:59:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DB73D154D2 for ; Wed, 11 Aug 1999 04:59:00 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EWzf-0007YC-00; Wed, 11 Aug 1999 13:56:31 +0200 From: Sheldon Hearn To: "Jordan K. Hubbard" Cc: hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system In-reply-to: Your message of "Wed, 11 Aug 1999 00:07:41 MST." <19699.934355261@localhost> Date: Wed, 11 Aug 1999 13:56:31 +0200 Message-ID: <29027.934372591@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999 00:07:41 MST, "Jordan K. Hubbard" wrote: > Nonetheless, for the expected installation experience one is > encouraged to boot the desired OS release's installation media and > select an upgrade instead of a new install. Gotcha. So you'd be interested in diffs that teach sysinstall to bleat if an Upgrade is requested for a release for which the instance of sysinstall was not designed? 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 Aug 11 6:38:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D252014D2E; Wed, 11 Aug 1999 06:38:23 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA12263; Wed, 11 Aug 1999 15:38:06 +0200 (CEST) (envelope-from des) To: Josef Karthauser Cc: hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. References: <19990808185112.A99557@pavilion.net> From: Dag-Erling Smorgrav Date: 11 Aug 1999 15:38:05 +0200 In-Reply-To: Josef Karthauser's message of "Sun, 8 Aug 1999 18:51:12 +0100" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > If so, what extra work is required to make it work with non UFS file > systems - is 'disklabel' used on non UFS fs's? Disklabel doesn't work at the fs level, it works at the slice level - dividing slices into partitions, in which you can create file systems. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 7: 6:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 2AE5015514 for ; Wed, 11 Aug 1999 07:06:51 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id QAA27835; Wed, 11 Aug 1999 16:03:46 +0200 (MET DST) Date: Wed, 11 Aug 1999 16:03:32 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions on new-bus source code 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 > (2) I guess that the probe process of all devices on the tree is triggered > by root_bus_configure() in subr_bus.c. It is done from top to bottom, > i.e. the probe process should be propagated down the device tree from > root_bus. Am I right? How does this tree structure achieve the dynamic > feature of device configuring (adding/removing devices on the fly)? When the loaded module registers itself as a driver in a devclass, all the non-attached devices are probed by calling the method BUS_DRIVER_ADDED (in devclass_add_driver). Devices that are already attached are not detached forcefully. There is still some discussion going on on whether a driver needs to give up a device when a better fitting driver is loaded (a stub versus a full blown driver for a device). See also the listed methods for busses (sys/kern/bus_if.m) and for devices (sys/kern/device_if.m). Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 7:22:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 4129615093 for ; Wed, 11 Aug 1999 07:22:52 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id QAA08256 for ; Wed, 11 Aug 1999 16:22:55 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa08249; Wed Aug 11 16:22:41 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id QAA02232 for ; Wed, 11 Aug 1999 16:27:14 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id QAA00766 for ; Wed, 11 Aug 1999 16:30:24 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <37B188FD.3BBF93F0@post.com> Date: Wed, 11 Aug 1999 16:30:22 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Hackers FreeBSD Subject: changing root device to ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD 2.2.6-RELEASE i have a scsi device and i want to change root to this device during startup. i added the following line in my kernel config file: config kernel root on sd0s1 but in the boot up, the message, "changing root device to wd0s1" keeps appearing and keeps failing. in my /etc/fstab i have the following entry: /dev/sd0s1a / ufs rw 1 1 does anyone have any ideas. the sd0 is probed and attached successfully during startup, but the change root fails because it keeps on trying to change root to a wd0 IDE. any ideas? eT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 8:24: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A7C2514CE9 for ; Wed, 11 Aug 1999 08:23:54 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA12678; Wed, 11 Aug 1999 17:23:34 +0200 (CEST) (envelope-from des) To: Archie Cobbs Cc: igusarov@chat.ru (Igor Gousarov), freebsd-hackers@FreeBSD.ORG Subject: Re: Unsafe code in libc in 3.0-RELEASE FreeBSD i386 References: <199902091620.IAA32532@bubba.whistle.com> From: Dag-Erling Smorgrav Date: 11 Aug 1999 17:23:33 +0200 In-Reply-To: Archie Cobbs's message of "Tue, 9 Feb 1999 08:20:27 -0800 (PST)" Message-ID: Lines: 57 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > Igor Gousarov writes: > > The source file for setlocale function (/usr/src/lib/libc/locale/setlocale.c) > > contains the line which might put libc into infinite loop: > > [...] > Please file a PR to make sure that this doesn't "slip through > the cracks"... It seems to have slipped through the cracks. Good thing I had a process mark on this message. What do you think of the attached patch (against -CURRENT)? I think there's still a possibility of new_categories being overrun, since there's no bounds checking on i in the do ... while (*locale) loop. I suggest that a careful audit by somebody who knows this code (or at least knows what it's supposed to do). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no Index: src/lib/libc/locale/setlocale.c =================================================================== RCS file: /home/ncvs/src/lib/libc/locale/setlocale.c,v retrieving revision 1.23 diff -u -r1.23 setlocale.c --- setlocale.c 1998/04/29 22:39:56 1.23 +++ setlocale.c 1999/08/11 15:21:05 @@ -156,9 +156,11 @@ new_categories[i][ENCODING_LEN] = '\0'; } } else { - for (i = 1; r[1] == '/'; ++r); + while (r[1] == '/') + ++r; if (!r[1]) return (NULL); /* Hmm, just slashes... */ + i = 1; do { len = r - locale > ENCODING_LEN ? ENCODING_LEN : r - locale; (void)strncpy(new_categories[i], locale, len); @@ -169,13 +171,13 @@ ++locale; while (*++r && *r != '/'); } while (*locale); - while (i < _LC_LAST) + for (; i < _LC_LAST; ++i) (void)strcpy(new_categories[i], new_categories[i-1]); } } - if (category) + if (category != LC_ALL) return (loadlocale(category)); for (i = 1; i < _LC_LAST; ++i) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 8:30:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id D1A2A15548 for ; Wed, 11 Aug 1999 08:30:08 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id LAA24256; Wed, 11 Aug 1999 11:30:46 -0400 (EDT) Date: Wed, 11 Aug 1999 11:30:46 -0400 (EDT) From: Ben Rosengart To: Gutov Grigory Cc: hackers@FreeBSD.ORG Subject: Re: Question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Gutov Grigory wrote: > I have a question. I buy 6 MegaRAID Ultra PCI SCSI Disk Array Controller's > and want to use they in FreeBSD, but not found driver. I wrote to > support@ami.com and they siad that no driver for FreeBSD. I found driver for > Linux and want use it in FreeBSD 3.1-3.2. How ? I'm afraid you can't, unless you port the driver to FreeBSD, or write a new driver, or get someone else to do so. FreeBSD runs Linux software, but not Linux device drivers. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9: 0:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id 8BD4514E97 for ; Wed, 11 Aug 1999 09:00:04 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id KAA24052; Wed, 11 Aug 1999 10:59:28 -0500 (CDT) Date: Wed, 11 Aug 1999 10:59:28 -0500 (CDT) From: Mark Tinguely Message-Id: <199908111559.KAA24052@plains.NoDak.edu> To: howardjp@wam.umd.edu Subject: Re: BSD XFS Port & BSD VFS Rewrite Cc: Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is why people should start emailing asking for a dual-license that > would support incorporation into FreeBSD. good luck, the SGI crowd are very Linux-oriented. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:16:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id AB48A14EE4; Wed, 11 Aug 1999 09:16:23 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id RAA13400; Wed, 11 Aug 1999 17:15:14 +0100 (BST) (envelope-from joe) Date: Wed, 11 Aug 1999 17:15:14 +0100 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. Message-ID: <19990811171514.X88035@pavilion.net> References: <19990808185112.A99557@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Aug 11, 1999 at 03:38:05PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999 at 03:38:05PM +0200, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > If so, what extra work is required to make it work with non UFS file > > systems - is 'disklabel' used on non UFS fs's? > > Disklabel doesn't work at the fs level, it works at the slice level - > dividing slices into partitions, in which you can create file systems. Ahha - of course. Ok, let me re-phrase the question then. By looking at the contents of the superblocks on a UFS file system it's possible to reconstruct a disklabel for a slice. Is this trick possible with other kinds of file systems too? (Does it even make sense to ask that question?). Should this recovery functionality be part of an already existing tool, like disklabel, or should it be a completely new tool? Opinions? Would it be possible to tag swap partitions with an equivalent of a superblock to make their recognition easier under failure conditions? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:23:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 206E515531; Wed, 11 Aug 1999 09:23:33 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA13015; Wed, 11 Aug 1999 18:23:25 +0200 (CEST) (envelope-from des) To: Josef Karthauser Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. References: <19990808185112.A99557@pavilion.net> <19990811171514.X88035@pavilion.net> From: Dag-Erling Smorgrav Date: 11 Aug 1999 18:23:24 +0200 In-Reply-To: Josef Karthauser's message of "Wed, 11 Aug 1999 17:15:14 +0100" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > Ahha - of course. Ok, let me re-phrase the question then. By looking > at the contents of the superblocks on a UFS file system it's possible to > reconstruct a disklabel for a slice. Well, it's possible to reconstruct the label information for *that particular UFS file system*, since if you know the location of the superblock (or one of its backup copies), you can determine the offset and size of the FS. It won't tell you anything about *other* partitions though. > Is this trick possible with other > kinds of file systems too? That's totally dependent on the particular file system. For instance, a swap partition contains no metadata (that I know of), so all you can do is deduce it's size and position from the sizes and positions of surrounding partitions, and of the slice they're in. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:35:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 0745815581; Wed, 11 Aug 1999 09:35:44 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id RAA16474; Wed, 11 Aug 1999 17:35:35 +0100 (BST) (envelope-from joe) Date: Wed, 11 Aug 1999 17:35:35 +0100 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. Message-ID: <19990811173535.Y88035@pavilion.net> References: <19990808185112.A99557@pavilion.net> <19990811171514.X88035@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Aug 11, 1999 at 06:23:24PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999 at 06:23:24PM +0200, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > Ahha - of course. Ok, let me re-phrase the question then. By looking > > at the contents of the superblocks on a UFS file system it's possible to > > reconstruct a disklabel for a slice. > > Well, it's possible to reconstruct the label information for *that > particular UFS file system*, since if you know the location of the > superblock (or one of its backup copies), you can determine the offset > and size of the FS. It won't tell you anything about *other* > partitions though. That's ok, because each slice has its _own_ label. If the bios partition table loses it's mind that's a little more work :). > > Is this trick possible with other kinds of file systems too? > > That's totally dependent on the particular file system. For instance, > a swap partition contains no metadata (that I know of), so all you can > do is deduce it's size and position from the sizes and positions of > surrounding partitions, and of the slice they're in. > What are the implications of adding a metadata structure to the swap structure. (It only needs a block :). [Although thinking out loud, it's complicated because there's no 'newfs' process that touches the partition, on the other hand the size of the partition is known at swap-mounting time, so the meta data could be written at that point.] Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:47:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0352014C59; Wed, 11 Aug 1999 09:47:17 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA13180; Wed, 11 Aug 1999 18:46:51 +0200 (CEST) (envelope-from des) To: Josef Karthauser Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. References: <19990808185112.A99557@pavilion.net> <19990811171514.X88035@pavilion.net> <19990811173535.Y88035@pavilion.net> From: Dag-Erling Smorgrav Date: 11 Aug 1999 18:46:51 +0200 In-Reply-To: Josef Karthauser's message of "Wed, 11 Aug 1999 17:35:35 +0100" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > On Wed, Aug 11, 1999 at 06:23:24PM +0200, Dag-Erling Smorgrav wrote: > > Josef Karthauser writes: > > > Ahha - of course. Ok, let me re-phrase the question then. By looking > > > at the contents of the superblocks on a UFS file system it's possible to > > > reconstruct a disklabel for a slice. > > Well, it's possible to reconstruct the label information for *that > > particular UFS file system*, since if you know the location of the > > superblock (or one of its backup copies), you can determine the offset > > and size of the FS. It won't tell you anything about *other* > > partitions though. > That's ok, because each slice has its _own_ label. If the bios partition > table loses it's mind that's a little more work :). You're confusing partitions and slices. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:49: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oleg.sani-c.vrn.ru (oleg.sani-c.vrn.ru [195.98.74.83]) by hub.freebsd.org (Postfix) with ESMTP id D166215540 for ; Wed, 11 Aug 1999 09:48:23 -0700 (PDT) (envelope-from oleg@oleg.sani-c.vrn.ru) Received: (from root@localhost) by oleg.sani-c.vrn.ru (8.9.2/8.9.2) id UAA01527 for freebsd-hackers@freebsd.org; Wed, 11 Aug 1999 20:48:08 +0400 (MSD) (envelope-from oleg) Date: Wed, 11 Aug 1999 20:48:08 +0400 (MSD) From: Oleg Derevenetz Message-Id: <199908111648.UAA01527@oleg.sani-c.vrn.ru> To: freebsd-hackers@freebsd.org Subject: mmap bug Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This small program, running as 'mmap', not 'mmap -u', can hang my machine. Is this a known bug in FreeBSD's kernel, or it is my fantasy ? Thank you for answer. #include #include #include #include #include #include #include main(int argc, char *argv[]) { int fd; int i; int len=1024*1024*10; /*ie 10Mbytes*/ caddr_t addr; char ttt[80]; int bunlink = 0; if ( argc > 1 && strcmp(argv[1], "-u") == 0 ) { bunlink = 1; } printf("unlink files? %s\n", bunlink ? "YES" : "NO"); for (i=0;;i++) { sprintf (ttt,"%d",i); printf("mmaping %ld byte region on file %s\n", len, ttt); fd=open(ttt,O_CREAT|O_RDWR,0666); if (fd<0) { printf("mmap error %ld",errno); exit(1); } memset(addr,'x',len); if ( munmap(addr, len) != 0 ) { fprintf(stderr, "munmap failed\n"); exit(EXIT_FAILURE); } close(fd); if ( bunlink ) unlink(ttt); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 9:52:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mission.mvnc.edu (mission.mvnc.edu [149.143.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 713CD15571 for ; Wed, 11 Aug 1999 09:51:53 -0700 (PDT) (envelope-from kdrobnac@mission.mvnc.edu) Received: from localhost (kdrobnac@localhost) by mission.mvnc.edu (8.9.0/8.9.0) with SMTP id MAA25028; Wed, 11 Aug 1999 12:49:27 -0400 (EDT) Date: Wed, 11 Aug 1999 12:49:27 -0400 (EDT) From: Kenny Drobnack To: Mark Tinguely Cc: howardjp@wam.umd.edu, Hackers@FreeBSD.ORG Subject: Re: BSD XFS Port & BSD VFS Rewrite In-Reply-To: <199908111559.KAA24052@plains.NoDak.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may be a stupid question, but what's to keep from putting xfs in FreeBSD? Is there something in the licenses that says you can't use GPL'ed software and software under the BSD License together? > > This is why people should start emailing asking for a dual-license that > > would support incorporation into FreeBSD. > > good luck, the SGI crowd are very Linux-oriented. > > > --mark. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > --------------------------------------*******************--------------------------------------- | | | Kenny Drobnack | | Student at Mount Vernon Nazarene College | | Major: Computer Science | | Minor: Math | | Working on: Computer Internship at the Public Library of Mount Vernon and Knox County | | | ------------------------------------*********************--------------------------------------- Linux Demo Day '99 One Step Closer to World Domination One Day, One World, One Cool Penguin. X X L IIIIIIIIII N N U U X X L I NN N U U X X L I N N N U U X X L I N N N U U X L I N N N U U X X L I N N N U U X X L I N N N U U X X LLLLL IIIIIIIIII N NN UUU X X --------------------------------------***************************------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10: 0:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id CF935155A5 for ; Wed, 11 Aug 1999 10:00:17 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Wed, 11 Aug 1999 18:04:31 +0100 Message-ID: <37B1A8C0.26BD96CA@baker.ie> Date: Wed, 11 Aug 1999 17:45:52 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: eT Cc: hackers@freebsd.org Subject: Re: changing root device to ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > but in the boot up, the message, "changing root device to wd0s1" keeps appearing and keeps > failing. in my /etc/fstab i have the following entry: > /dev/sd0s1a / ufs rw 1 1 > does anyone have any ideas. > the sd0 is probed and attached successfully during startup, but the change root fails > because it keeps on trying to change root to a wd0 IDE. would i be right in guessing that you used to have the FreeBSD system on IDE disk wd0 after which you transferred it over to SCSI disk sd0 ? is the system still booting off the IDE disk (if present) ? to boot your system off the SCSI disk you should be able to enter the following at the boot prompt : 0:sd(0,a)/kernel (or whatever the name of your kernel is) which should set the root device ok... Regards, - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10: 1:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id BC313155A1; Wed, 11 Aug 1999 10:01:01 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id SAA19912; Wed, 11 Aug 1999 18:00:48 +0100 (BST) (envelope-from joe) Date: Wed, 11 Aug 1999 18:00:48 +0100 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk label recovery - request for suggestions. Message-ID: <19990811180048.Z88035@pavilion.net> References: <19990808185112.A99557@pavilion.net> <19990811171514.X88035@pavilion.net> <19990811173535.Y88035@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Aug 11, 1999 at 06:46:51PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999 at 06:46:51PM +0200, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > On Wed, Aug 11, 1999 at 06:23:24PM +0200, Dag-Erling Smorgrav wrote: > > > Josef Karthauser writes: > > > > Ahha - of course. Ok, let me re-phrase the question then. By looking > > > > at the contents of the superblocks on a UFS file system it's possible to > > > > reconstruct a disklabel for a slice. > > > Well, it's possible to reconstruct the label information for *that > > > particular UFS file system*, since if you know the location of the > > > superblock (or one of its backup copies), you can determine the offset > > > and size of the FS. It won't tell you anything about *other* > > > partitions though. > > That's ok, because each slice has its _own_ label. If the bios partition > > table loses it's mind that's a little more work :). > > You're confusing partitions and slices. I don't think so - PC's have a partition table. Us FreeBSDers call these partitions 'slices', and subdivide these into FreeBSD partitions. Each slice (pc partition) has a disklabel which denotes where the FreeBSD partitions live on the slice. I see what you were saying now above now. I agree that the superblock for a UFS file system won't tell anything about other UFS partitions, but a block by block search of the whole slice will identify potential superblocks that will. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10: 7:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 3F85915571 for ; Wed, 11 Aug 1999 10:07:13 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id KAA26592; Wed, 11 Aug 1999 10:04:28 -0700 (PDT) Message-Id: <199908111704.KAA26592@lestat.nas.nasa.gov> To: Oleg Derevenetz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 11 Aug 1999 10:04:26 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999 20:48:08 +0400 (MSD) Oleg Derevenetz wrote: > This small program, running as 'mmap', not 'mmap -u', can hang my machine. > Is this a known bug in FreeBSD's kernel, or it is my fantasy ? > Thank you for answer. If it hangs your system, must be a bug in FreeBSD. Here is what happens on a NetBSD/alpha system: bishop:thorpej 26$ ./mmap-bug unlink files? NO mmaping 10485760 byte region on file 0 Memory fault (core dumped) bishop:thorpej 27$ ./mmap-bug -u unlink files? YES mmaping 10485760 byte region on file 0 Memory fault (core dumped) bishop:thorpej 28$ ...which is correct. There isn't any backing store for the region you've mapped. > > #include > #include > #include > #include > #include > #include > #include > > main(int argc, char *argv[]) > { > int fd; > int i; > int len=1024*1024*10; /*ie 10Mbytes*/ > caddr_t addr; > char ttt[80]; > int bunlink = 0; > > if ( argc > 1 && strcmp(argv[1], "-u") == 0 ) { > bunlink = 1; > } > printf("unlink files? %s\n", bunlink ? "YES" : "NO"); > > for (i=0;;i++) > { > sprintf (ttt,"%d",i); > printf("mmaping %ld byte region on file %s\n", len, ttt); > fd=open(ttt,O_CREAT|O_RDWR,0666); > if (fd<0) > { > printf("mmap error %ld",errno); > exit(1); > } > memset(addr,'x',len); > if ( munmap(addr, len) != 0 ) { > fprintf(stderr, "munmap failed\n"); > exit(EXIT_FAILURE); > } > close(fd); > if ( bunlink ) unlink(ttt); > } > } > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:24:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 3E5B614CBE for ; Wed, 11 Aug 1999 10:24:48 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id NAA26187; Wed, 11 Aug 1999 13:22:29 -0400 (EDT) Date: Wed, 11 Aug 1999 13:22:29 -0400 (EDT) From: Bosko Milekic To: Oleg Derevenetz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug In-Reply-To: <199908111648.UAA01527@oleg.sani-c.vrn.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 Are you running this as root? <----- - - . . Bosko Milekic http://www.dsuper.net/~bmilekic/ Network Operations - Delphi SuperNet, an Internet Direct company +1.514.281.7500 (vox) / +1.514.281.6599 (fax) / http://www.dsuper.net/ . . - - -----> On Wed, 11 Aug 1999, Oleg Derevenetz wrote: !> !>This small program, running as 'mmap', not 'mmap -u', can hang my machine. !>Is this a known bug in FreeBSD's kernel, or it is my fantasy ? !>Thank you for answer. !> [ code snipped ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:30:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns0.sports.gov.uk (dns0.sports.gov.uk [195.89.151.148]) by hub.freebsd.org (Postfix) with ESMTP id B3A1515571 for ; Wed, 11 Aug 1999 10:29:58 -0700 (PDT) (envelope-from ad@netbsd.org) Message-ID: <37B1B2C0.AB80D46D@netbsd.org> Date: Wed, 11 Aug 1999 18:28:32 +0100 From: Andy Doran X-Accept-Language: en-GB,en,en-* MIME-Version: 1.0 To: Oleg Derevenetz Cc: freebsd-hackers@freebsd.org Subject: Re: mmap bug References: <199908111648.UAA01527@oleg.sani-c.vrn.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Um, just where do you call mmap(2) in this code? - ad Oleg Derevenetz wrote: > This small program, running as 'mmap', not 'mmap -u', can hang my machine. > Is this a known bug in FreeBSD's kernel, or it is my fantasy ? > Thank you for answer. > > #include > #include > #include > #include > #include > #include > #include > > main(int argc, char *argv[]) > { > int fd; > int i; > int len=1024*1024*10; /*ie 10Mbytes*/ > caddr_t addr; > char ttt[80]; > int bunlink = 0; > > if ( argc > 1 && strcmp(argv[1], "-u") == 0 ) { > bunlink = 1; > } > printf("unlink files? %s\n", bunlink ? "YES" : "NO"); > > for (i=0;;i++) > { > sprintf (ttt,"%d",i); > printf("mmaping %ld byte region on file %s\n", len, ttt); > fd=open(ttt,O_CREAT|O_RDWR,0666); > if (fd<0) > { > printf("mmap error %ld",errno); > exit(1); > } > memset(addr,'x',len); > if ( munmap(addr, len) != 0 ) { > fprintf(stderr, "munmap failed\n"); > exit(EXIT_FAILURE); > } > close(fd); > if ( bunlink ) unlink(ttt); > } > } > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:33:39 1999 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 AEA5115776; Wed, 11 Aug 1999 10:33:19 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA20642; Wed, 11 Aug 1999 11:33: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 LAA18169; Wed, 11 Aug 1999 11:33:30 -0600 (MDT) Message-Id: <199908111733.LAA18169@harmony.village.org> To: Dag-Erling Smorgrav Subject: Re: Disk label recovery - request for suggestions. Cc: Josef Karthauser , hackers@FreeBSD.ORG, fs@FreeBSD.ORG In-reply-to: Your message of "11 Aug 1999 18:23:24 +0200." References: <19990808185112.A99557@pavilion.net> <19990811171514.X88035@pavilion.net> Date: Wed, 11 Aug 1999 11:33:30 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dag-Erling Smorgrav writes: : superblock (or one of its backup copies), you can determine the offset : and size of the FS. It won't tell you anything about *other* : partitions though. It will give a fairly strong hint, however. If you know what is taken up by this partition, you can remove it from the pool of available space and guess with a relatively high degree of accuracy that the next partition begins where this one ends. : > Is this trick possible with other : > kinds of file systems too? : : That's totally dependent on the particular file system. For instance, : a swap partition contains no metadata (that I know of), so all you can : do is deduce it's size and position from the sizes and positions of : surrounding partitions, and of the slice they're in. Yes. This is true.... That's one of the problems of my disklabel reconstruction program that tries to run fast... It slows way down when it hits the swap area... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:35:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id B3CA014CCF for ; Wed, 11 Aug 1999 10:35:19 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA26611; Wed, 11 Aug 1999 10:30:34 -0700 (PDT) Message-Id: <199908111730.KAA26611@implode.root.com> To: Oleg Derevenetz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug In-reply-to: Your message of "Wed, 11 Aug 1999 20:48:08 +0400." <199908111648.UAA01527@oleg.sani-c.vrn.ru> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 10:30:34 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This report seems to be severely lacking in details. First, I don't understand why it is called "mmap" since it doesn't do an mmap and the "addr" that is being frobbed with isn't even initialized. Second, I get a core dump when I run it on a -stable machine: [speedy:tmp9] mmap unlink files? NO mmaping 10485760 byte region on file 0 Segmentation fault (core dumped) ...which is exactly what I'd expect when dealing with a bogus pointer. You didn't specify what version of FreeBSD you saw a hang and didn't provide any details of the hang. Please provide more information so that we can help you. Thanks. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com >This small program, running as 'mmap', not 'mmap -u', can hang my machine. >Is this a known bug in FreeBSD's kernel, or it is my fantasy ? >Thank you for answer. > >#include >#include >#include >#include >#include >#include >#include > >main(int argc, char *argv[]) >{ > int fd; > int i; > int len=1024*1024*10; /*ie 10Mbytes*/ > caddr_t addr; > char ttt[80]; > int bunlink = 0; > > if ( argc > 1 && strcmp(argv[1], "-u") == 0 ) { > bunlink = 1; > } > printf("unlink files? %s\n", bunlink ? "YES" : "NO"); > > for (i=0;;i++) > { > sprintf (ttt,"%d",i); > printf("mmaping %ld byte region on file %s\n", len, ttt); > fd=open(ttt,O_CREAT|O_RDWR,0666); > if (fd<0) > { > printf("mmap error %ld",errno); > exit(1); > } > memset(addr,'x',len); > if ( munmap(addr, len) != 0 ) { > fprintf(stderr, "munmap failed\n"); > exit(EXIT_FAILURE); > } > close(fd); > if ( bunlink ) unlink(ttt); > } >} > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:37:56 1999 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 9964614D00 for ; Wed, 11 Aug 1999 10:37:52 -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 LAA20655; Wed, 11 Aug 1999 11:37:20 -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 LAA18192; Wed, 11 Aug 1999 11:37:43 -0600 (MDT) Message-Id: <199908111737.LAA18192@harmony.village.org> To: Kenny Drobnack Subject: Re: BSD XFS Port & BSD VFS Rewrite Cc: Mark Tinguely , howardjp@wam.umd.edu, Hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 12:49:27 EDT." References: Date: Wed, 11 Aug 1999 11:37:43 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenny Drobnack writes: : This may be a stupid question, but what's to keep from putting xfs in : FreeBSD? Is there something in the licenses that says you can't use : GPL'ed software and software under the BSD License together? The BSD license allows binary only applications, while the GPL doesn't. However, keep in mind that the GPL has never been tested in a court of law, so how a judge will react to it, and which provisions are legal and which ones constitute unfair or extreme consequences have not been determined. One could argue for years on end about what it says and what other cases have shown, but at the end of the day you still don't know with certainty how it will fair in court. That's why we have a GPL math emulator, but don't include it in the GENERIC kernel. There are many people that repackage FreeBSD for embedded applications who do not include the source code to their proprietary bits and strip out all or most of the GPL software from their deliverables to avoid this potential legal quagmire. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:49:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 6070715560 for ; Wed, 11 Aug 1999 10:49:09 -0700 (PDT) (envelope-from rminnich@acl.lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA145529 for ; Wed, 11 Aug 1999 11:48:45 -0600 (MDT) Date: Wed, 11 Aug 1999 11:48:45 -0600 From: "Ronald G. Minnich" To: hackers@freebsd.org Subject: Scaleable Coherent Interface drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm making them available on my web page, www.acl.lanl.gov/~rminnich Thanks to Dolphin for allowing this release. Questions to me. it's not the greatest driver on the planet. If you want to write a better one you can use mine as a model. I'm probably done with SCI for now, but I'll take bug fixes. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 10:57:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 6F86B14E17 for ; Wed, 11 Aug 1999 10:57:32 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 11:56:42 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC0303786B72@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@FreeBSD.ORG Cc: Oleg Derevenetz Subject: RE: mmap bug Date: Wed, 11 Aug 1999 11:56:39 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like Oleg made a mistake in posting the code. I saw an earlier version of this in freebsd-questions and followed up with him. I've appended the version I think he meant to include. He's reporting this behavior with 3.2R. Runs fine with 'mmap -u', appears to hang the machine on the second iteration (file "1") with 'mmap'. Runs fine on Solaris 2.6 and Digital Unix 4.0D -- with the exception of filling the disk without "-u" :^). He's trying to ask if this is a problem with the code in question or 3.2R's mmap. Charles --- mmap.c --- #include #include #include #include #include #include #include main(int argc, char *argv[]) { int fd; int i; int len=1024*1024*10; /*ie 10Mbytes*/ caddr_t addr; char ttt[80]; int bunlink = 0; if ( argc > 1 && strcmp(argv[1], "-u") == 0 ) { bunlink = 1; } printf("unlink files? %s\n", bunlink ? "YES" : "NO"); for (i=0;;i++) { sprintf (ttt,"%d",i); printf("mmaping %ld byte region on file %s\n", len, ttt); fd=open(ttt,O_CREAT|O_RDWR,0666); if (fd<0) { printf("open error %ld\n",errno); exit(1); } lseek(fd,len-1,SEEK_SET); write(fd,"",1); addr=mmap(0,len,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0); if (addr==MAP_FAILED) { printf("mmap error %ld",errno); exit(1); } memset(addr,'x',len); if ( munmap(addr, len) != 0 ) { fprintf(stderr, "munmap failed\n"); exit(EXIT_FAILURE); } close(fd); if ( bunlink ) unlink(ttt); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 11: 6:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E7AB515571 for ; Wed, 11 Aug 1999 11:06:01 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb35.imasy.or.jp [202.227.24.163]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id DAA14430; Thu, 12 Aug 1999 03:05:25 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908111805.DAA14430@tasogare.imasy.or.jp> To: shocking@prth.pgs.com, ognir@humboldt1.com Cc: hackers@FreeBSD.ORG, iwasaki@jp.freebsd.org Subject: Re: New Joystick driver? X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 12 Aug 1999 03:09:08 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > Well, I was going to try to roll my own for this, but it's always nice to > > know someone's already done it for me. :) I'm gone though for the next > > couple weeks though, so that'll be a nice thing to get back home to. Many > > thanks! > > > > Where will I be able to get it? > > > > -Joe > > > > Well, it's not ready yet. I'll be putting it in as a PR once I've finished. > Probably it'll be released to the multimedia group first as a test. I made quick hack on Linux js compatible joystick driver just last month. Please refer the following URL if you are interested in. http://home.jp.FreeBSD.ORG/cgi-bin/showmail/raw/tech-jp/2385 (Sorry, it is in Japanese. I'll explain for you if you need.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 11:23: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 6A80F14E17 for ; Wed, 11 Aug 1999 11:22:56 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA26998; Wed, 11 Aug 1999 11:19:06 -0700 (PDT) Message-Id: <199908111819.LAA26998@implode.root.com> To: Charles Randall Cc: freebsd-hackers@FreeBSD.ORG, Oleg Derevenetz Subject: Re: mmap bug In-reply-to: Your message of "Wed, 11 Aug 1999 11:56:39 MDT." <64003B21ECCAD11185C500805F31EC0303786B72@houston.matchlogic.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 11:19:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Looks like Oleg made a mistake in posting the code. I saw an earlier version >of this in freebsd-questions and followed up with him. > >I've appended the version I think he meant to include. > >He's reporting this behavior with 3.2R. Runs fine with 'mmap -u', appears to >hang the machine on the second iteration (file "1") with 'mmap'. > >Runs fine on Solaris 2.6 and Digital Unix 4.0D -- with the exception of >filling the disk without "-u" :^). > >He's trying to ask if this is a problem with the code in question or 3.2R's >mmap. That's better. It appears to be a classic resource related deadlock that is caused by the VFS code needing pages in order to page things out (and thus free up pages), but is unable to since no memory is available. Matt Dillon was working on deadlocks like this in -current awhile back and it would be interesting to know if the hang occurs there as well. I don't have a -current machine at the moment so I can't test it myself. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 11:39:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 3A4FE155B6 for ; Wed, 11 Aug 1999 11:39:16 -0700 (PDT) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id CCA861F57; Wed, 11 Aug 1999 11:39:38 -0700 (PDT) X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com Cc: Charles Randall , freebsd-hackers@FreeBSD.ORG, Oleg Derevenetz Subject: Re: mmap bug In-reply-to: Your message of "Wed, 11 Aug 1999 11:19:05 PDT." <199908111819.LAA26998@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Aug 1999 11:39:38 -0700 From: Jake Burkholder Message-Id: <19990811183938.CCA861F57@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >He's trying to ask if this is a problem with the code in question or 3.2R's > >mmap. > > That's better. It appears to be a classic resource related deadlock that > is caused by the VFS code needing pages in order to page things out (and thus > free up pages), but is unable to since no memory is available. > Matt Dillon was working on deadlocks like this in -current awhile back and > it would be interesting to know if the hang occurs there as well. I don't > have a -current machine at the moment so I can't test it myself. FreeBSD 4.0-CURRENT #14: Mon Aug 9 17:44:35 PDT 1999 It doesn't hang my machine here, I let it go to about 25. -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 11:39:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from charon.npc.net (charon.finall.com [199.15.61.3]) by hub.freebsd.org (Postfix) with ESMTP id 7A57E15624 for ; Wed, 11 Aug 1999 11:39:41 -0700 (PDT) (envelope-from mjung@npc.net) Received: from exchange.finall.com (exchange-gw.finall.com [10.0.158.37]) by charon.npc.net (8.9.1/8.8.8) with SMTP id OAA02618 for ; Wed, 11 Aug 1999 14:39:43 -0400 (EDT) (envelope-from mjung@npc.net) Received: by exchange.finall.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BEE407.E6065030@exchange.finall.com>; Wed, 11 Aug 1999 14:43:38 -0400 Message-ID: From: "Jung, Michael" To: "'freebsd-hackers@freebsd.org'" Subject: Recreating LKM Date: Wed, 11 Aug 1999 14:43:38 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok.... How does one recreate /dev/lkm for 4.0-Current? It is no longer in /dev/MAKEDEV. Thanks --mikej Michael Jung (502) 315-2457 Voice Senior Network Specialist (502) 315-2815 Facsimile National Processing Company, Inc. mjung@npc.net 1231 Durrett Lane MJ548 Louisville, KY 40285 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 12:47:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id 3DECE14C17 for ; Wed, 11 Aug 1999 12:47:01 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11EeKj-000NTD-00; Wed, 11 Aug 1999 20:46:45 +0100 To: kdrobnac@mission.mvnc.edu From: Tony Finch Cc: Hackers@FreeBSD.ORG Subject: Re: BSD XFS Port & BSD VFS Rewrite In-Reply-To: References: <199908111559.KAA24052@plains.NoDak.edu> Message-Id: Date: Wed, 11 Aug 1999 20:46:45 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenny Drobnack wrote: > >This may be a stupid question, but what's to keep from putting xfs in >FreeBSD? Is there something in the licenses that says you can't use >GPL'ed software and software under the BSD License together? Yes. The BSD licence requirement for acknowledging UCB in any advertising conflicts with the GPL requirement that further restrictions should not be added to those already in the GPL. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 14:17:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2645E1560F for ; Wed, 11 Aug 1999 14:17:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA77941; Wed, 11 Aug 1999 14:16:59 -0700 (PDT) (envelope-from dillon) Date: Wed, 11 Aug 1999 14:16:59 -0700 (PDT) From: Matthew Dillon Message-Id: <199908112116.OAA77941@apollo.backplane.com> To: David Greenman Cc: Charles Randall , freebsd-hackers@FreeBSD.ORG, Oleg Derevenetz Subject: Re: mmap bug References: <199908111819.LAA26998@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :>He's trying to ask if this is a problem with the code in question or 3.2R's :>mmap. : : That's better. It appears to be a classic resource related deadlock that :is caused by the VFS code needing pages in order to page things out (and thus :free up pages), but is unable to since no memory is available. : Matt Dillon was working on deadlocks like this in -current awhile back and :it would be interesting to know if the hang occurs there as well. I don't :have a -current machine at the moment so I can't test it myself. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org :Creator of high-performance Internet servers - http://www.terasolutions.com The problem can occur in both STABLE and CURRENT. I ran the test program on a CURRENT system artificially limited to 64MB of ram. It locked it up instantly. This is because we map clean R+W pages as R+W. Thus we do not take a fault when the process dirties a pages underlying a map, so we do not know that it has been dirtied until it is far too late. When we run out of pages, the system daemons lockup in the VFS subsystem when the filesystem tries to read or write metadata. One solution would be to map clean R+W pages RO and force a write fault to occur, allowing the system to recognize that there are too many dirty pages in vm_fault before it is too late and flush some of them. The downside of this is that, of course, we take unnecessary faults. Another solution might be to reorganize the emergency page reserve to operate based on a P_ flag in the process structure, so VFS routines that normally block when memory is low are allowed to proceed when called from system processes. I'll try persuing the second idea. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 14:31:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from qn-lpr2-98.quicknet.inet.fi (qn-lpr2-165.quicknet.inet.fi [194.251.102.165]) by hub.freebsd.org (Postfix) with ESMTP id 0EE24155A3 for ; Wed, 11 Aug 1999 14:31:51 -0700 (PDT) (envelope-from junki@qn-lpr2-165.quicknet.inet.fi) Received: from localhost (junki@localhost) by qn-lpr2-98.quicknet.inet.fi (8.9.3/8.9.1) with ESMTP id AAA00431 for ; Thu, 12 Aug 1999 00:31:06 +0300 (EEST) (envelope-from junki@qn-lpr2-165.quicknet.inet.fi) Date: Thu, 12 Aug 1999 00:31:06 +0300 (EEST) From: Juha Nurmela X-Sender: junki@pena.oh5nxo.ampr.org Reply-To: Juha.Nurmela@quicknet.inet.fi To: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the latter mmap.c is allowed to fill up filesystem, -current hangs in /kernel: pid 2 (pagedaemon), uid 0 on /: file system full /kernel: vnode_pager_putpages: I/O error 28 /kernel: vnode_pager_putpages: residual I/O 16384 at 880 ...repeating the last two lines, gradually increasing pindex, residual changing to 64kB. Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 14:41:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B7E414E55 for ; Wed, 11 Aug 1999 14:41:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA78172; Wed, 11 Aug 1999 14:39:32 -0700 (PDT) (envelope-from dillon) Date: Wed, 11 Aug 1999 14:39:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199908112139.OAA78172@apollo.backplane.com> To: Juha Nurmela Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If the latter mmap.c is allowed to fill up filesystem, -current hangs in : :/kernel: pid 2 (pagedaemon), uid 0 on /: file system full :/kernel: vnode_pager_putpages: I/O error 28 :/kernel: vnode_pager_putpages: residual I/O 16384 at 880 : :...repeating the last two lines, gradually increasing pindex, :residual changing to 64kB. : :Juha It should stop eventually when it runs out of pages in the map. This is what happens when you map a file, ftruncate() it to be a certain size (all zero-fill), and then touch the pages forcing the filesystem to allocate actual blocks for the data and the filesystem isn't big enough. The system doesn't know the filesystem isn't big enough until it actually tries to flush the pages. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 14:48:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (Postfix) with SMTP id 61BFE14E31; Wed, 11 Aug 1999 14:48:01 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id QAA24660; Wed, 11 Aug 1999 16:49:19 -0500 Received: from stlexggtw002-pozzoli.fw-users.busch.com(151.145.101.130) by gatewaya.anheuser-busch.com via smap (V5.0) id xma024583; Wed, 11 Aug 99 16:48:57 -0500 Received: from stlabcexg006.anheuser-busch.com ([151.145.101.161]) by 151.145.101.130 (Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 11 Aug 1999 21:46:50 0000 (GMT) Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 16:46:33 -0500 Message-ID: <0740CBD1D149D31193EB0008C7C56836EB8B05@STLABCEXG012> From: "Alton, Matthew" To: "'Hackers@FreeBSD.ORG'" , "'fs@FreeBSD.ORG'" Subject: BSD-XFS Update Date: Wed, 11 Aug 1999 16:46:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SGI has released a portion of the XFS source code under the GPL: http://oss.sgi.com/projects/xfs/download/ the source file is xfs_log.tar.gz. Of greater interest at this stage are the documents in: http://oss.sgi.com/projects/xfs/design_docs/ I am currently researching methods for implementing the 64-bit syscalls stat64(), fstat64(), lseek64() &etc. delineated in the SGI design doc _64 Bit File Access_ by Adam Sweeney. The BSD-XFS port will be made available as a patch to the RELEASE FreeBSD kernels. Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 15:36:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A844C14DEE; Wed, 11 Aug 1999 15:36:33 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA71891; Wed, 11 Aug 1999 15:34:57 -0700 (PDT) Date: Wed, 11 Aug 1999 15:35:31 -0700 (PDT) From: Julian Elischer To: "Alton, Matthew" Cc: "'Hackers@FreeBSD.ORG'" , "'fs@FreeBSD.ORG'" Subject: Re: BSD-XFS Update In-Reply-To: <0740CBD1D149D31193EB0008C7C56836EB8B05@STLABCEXG012> 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 stat, fstat, lseek are all already 64 bits in freebsd..... On Wed, 11 Aug 1999, Alton, Matthew wrote: > SGI has released a portion of the XFS source code under the GPL: > > http://oss.sgi.com/projects/xfs/download/ > > the source file is xfs_log.tar.gz. > > Of greater interest at this stage are the documents in: > > http://oss.sgi.com/projects/xfs/design_docs/ > > I am currently researching methods for implementing the 64-bit > syscalls stat64(), fstat64(), lseek64() &etc. delineated in the > SGI design doc _64 Bit File Access_ by Adam Sweeney. > > The BSD-XFS port will be made available as a patch to the RELEASE > FreeBSD kernels. > > > Matthew Alton > Computer Services - UNIX Systems Administration > (314)632-6644 matthew.alton@anheuser-busch.com > alton@plantnet.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 16: 2:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id 1534915636; Wed, 11 Aug 1999 16:02:48 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.106.150.250]) by vax1.baker.ie with ESMTP; Thu, 12 Aug 1999 0:08:10 +0100 Message-ID: <37B20EBE.76AC89DA@baker.ie> Date: Thu, 12 Aug 1999 01:01:02 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > when a network interface is put into promiscuous mode, a kernel > > > message is logged ie. "ep0: promiscuous mode enabled" are there plans > > > to log the reverse of this message ie. "ep0: promiscuous mode > > > disabled"..I think this was suggested before in the mailing-lists but > > > did anything come of it ? > > > > Not that I saw. Patches would accelerate the process, probably :-) > Patches certainly would.. :) here's a patch for /sys/net/if.c that works on 3.2-STABLE for the ep0 and lo0 interfaces (only ones I tested) all I did was add in 2 lines of code (whoopee doo..) my inserted lines start with "--->" However will this work with all interfaces ?? this was the only code I could find that calls log() to record a "promiscuous mode enabled" message so I guess in theory the following should work for all interfaces ? (correct me if I'm wrong..) -- snip -- if (pswitch) { /* * If the device is not configured up, we cannot put it in * promiscuous mode. */ if ((ifp->if_flags & IFF_UP) == 0) return (ENETDOWN); if (ifp->if_pcount++ != 0) return (0); ifp->if_flags |= IFF_PROMISC; log(LOG_INFO, "%s%d: promiscuous mode enabled\n", ifp->if_name, ifp->if_unit); } else { if (--ifp->if_pcount > 0) return (0); ifp->if_flags &= ~IFF_PROMISC; ---> log(LOG_INFO, "%s%d: promiscuous mode disabled\n", ---> ifp->if_name, ifp->if_unit); } -- snip -- - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 16: 4:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (Postfix) with SMTP id 65C5615636; Wed, 11 Aug 1999 16:04:06 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id SAA01734; Wed, 11 Aug 1999 18:05:51 -0500 Received: from stlexggtw002-pozzoli.fw-users.busch.com(151.145.101.130) by gatewaya.anheuser-busch.com via smap (V5.0) id xma001698; Wed, 11 Aug 99 18:05:44 -0500 Received: from stlabcexg006.anheuser-busch.com ([151.145.101.161]) by 151.145.101.130 (Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 11 Aug 1999 23:03:37 0000 (GMT) Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 18:03:20 -0500 Message-ID: <0740CBD1D149D31193EB0008C7C56836EB8B06@STLABCEXG012> From: "Alton, Matthew" To: "'Julian Elischer'" Cc: "'Hackers@FreeBSD.ORG'" , "'fs@FreeBSD.ORG'" Subject: RE: BSD-XFS Update Date: Wed, 11 Aug 1999 18:03:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quite so. Thank you. I initially only looked at things like: 19 COMPAT POSIX { long lseek(int fd, long offset, int whence); } from /usr/src/sys/kern/syscalls.master and assumed a 32-bit long int. The easy way to deal with this is to change the calls in the XFS code. The syscall part is mostly done. > -----Original Message----- > From: Julian Elischer [SMTP:julian@whistle.com] > Sent: Wednesday, August 11, 1999 5:36 PM > To: Alton, Matthew > Cc: 'Hackers@FreeBSD.ORG'; 'fs@FreeBSD.ORG' > Subject: Re: BSD-XFS Update > > stat, fstat, lseek are all already 64 bits in freebsd..... > > > On Wed, 11 Aug 1999, Alton, Matthew wrote: > > > SGI has released a portion of the XFS source code under the GPL: > > > > http://oss.sgi.com/projects/xfs/download/ > > > > the source file is xfs_log.tar.gz. > > > > Of greater interest at this stage are the documents in: > > > > http://oss.sgi.com/projects/xfs/design_docs/ > > > > I am currently researching methods for implementing the 64-bit > > syscalls stat64(), fstat64(), lseek64() &etc. delineated in the > > SGI design doc _64 Bit File Access_ by Adam Sweeney. > > > > The BSD-XFS port will be made available as a patch to the RELEASE > > FreeBSD kernels. > > > > > > Matthew Alton > > Computer Services - UNIX Systems Administration > > (314)632-6644 matthew.alton@anheuser-busch.com > > alton@plantnet.com > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 16: 9:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id B433D14DB3 for ; Wed, 11 Aug 1999 16:09:18 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA02748; Wed, 11 Aug 1999 16:08:14 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA20802; Wed, 11 Aug 1999 16:03:25 -0700 Received: from softweyr.com (dyn5.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA14538; Wed, 11 Aug 99 16:08:10 PDT Message-Id: <37B2025A.778CCA59@softweyr.com> Date: Wed, 11 Aug 1999 17:08:10 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Sheldon Hearn Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system References: <29027.934372591@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Wed, 11 Aug 1999 00:07:41 MST, "Jordan K. Hubbard" wrote: > > > Nonetheless, for the expected installation experience one is > > encouraged to boot the desired OS release's installation media and > > select an upgrade instead of a new install. > > Gotcha. > > So you'd be interested in diffs that teach sysinstall to bleat if an > Upgrade is requested for a release for which the instance of sysinstall > was not designed? Something like: +-- Doh! -----------------------------------------------+ | | | You are trying to upgrade to FreeBSD 3.2 using a | | FreeBSD 2.0.5 installation program. This is doomed | | to fail. Please download the FreeBSD 3.2 install | | disk set, create install floppies, and run the | | upgrade from the 3.2 installation program. | | | | +--------+ +--------------+ | | | Cancel | | I feel lucky | | | +--------+ +--------------+ | | | +-------------------------------------------------------+ would certainly be of value. It's OK to let the users shoot their feet off, but they may not know they're about to shoot their feet off. Giving them an alert would be polite. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 16:12:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A631114C39 for ; Wed, 11 Aug 1999 16:12:05 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EhW8-0008pw-00; Thu, 12 Aug 1999 01:10:44 +0200 From: Sheldon Hearn To: Wes Peters Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system In-reply-to: Your message of "Wed, 11 Aug 1999 17:08:10 CST." <37B2025A.778CCA59@softweyr.com> Date: Thu, 12 Aug 1999 01:10:44 +0200 Message-ID: <33971.934413044@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999 17:08:10 CST, Wes Peters wrote: > It's OK to let the users shoot their feet off, but they may not know > they're about to shoot their feet off. Giving them an alert would be > polite. I'll feel more comfortable about letting them shoot their feet off if you can point out _any_ way in which it might be beneficial for them to do so. :-) later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 17:34:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id 493D6155BE for ; Wed, 11 Aug 1999 17:34:38 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18351.on.bellglobal.com [206.172.130.31]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id UAA18993; Wed, 11 Aug 1999 20:36:34 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id UAA38491; Wed, 11 Aug 1999 20:34:59 -0400 (EDT) (envelope-from tim) Date: Wed, 11 Aug 1999 20:34:59 -0400 From: Tim Vanderhoek To: Sheldon Hearn Cc: Wes Peters , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system Message-ID: <19990811203459.B38401@mad> References: <37B2025A.778CCA59@softweyr.com> <33971.934413044@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <33971.934413044@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Aug 12, 1999 at 01:10:44AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 12, 1999 at 01:10:44AM +0200, Sheldon Hearn wrote: > > I'll feel more comfortable about letting them shoot their feet off if > you can point out _any_ way in which it might be beneficial for them to > do so. :-) I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. In my dictionary, "bleet" translates to "warn". Just make sysinstall bleet as you originally offered and everyone will be happy. :-) Hmm... "bleet"'s not in esr's hacker dictionary. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 17:38:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A3EDF15610 for ; Wed, 11 Aug 1999 17:38:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA79144; Wed, 11 Aug 1999 17:36:47 -0700 (PDT) (envelope-from dillon) Date: Wed, 11 Aug 1999 17:36:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199908120036.RAA79144@apollo.backplane.com> To: Juha Nurmela Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mmap bug References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If the latter mmap.c is allowed to fill up filesystem, -current hangs in : :/kernel: pid 2 (pagedaemon), uid 0 on /: file system full :/kernel: vnode_pager_putpages: I/O error 28 :/kernel: vnode_pager_putpages: residual I/O 16384 at 880 : :...repeating the last two lines, gradually increasing pindex, :residual changing to 64kB. : :Juha Ok, we have a fix for the mmap bug which should go in relatively soon. I reproduced the I/O error too. It does create an infinite loop... I'm not sure how to fix it yet. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 18:32:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 192EC14E4D for ; Wed, 11 Aug 1999 18:32:44 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11Ejhc-0009Pi-00; Thu, 12 Aug 1999 03:30:44 +0200 From: Sheldon Hearn To: Tim Vanderhoek Cc: Wes Peters , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: Using legacy sysinstall to upgrade live system In-reply-to: Your message of "Wed, 11 Aug 1999 20:34:59 -0400." <19990811203459.B38401@mad> Date: Thu, 12 Aug 1999 03:30:44 +0200 Message-ID: <36189.934421444@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999 20:34:59 -0400, Tim Vanderhoek wrote: > I suggest that it would be beneficial for you to let them shoot off > their feet... I have used legacy sysinstall to upgrade a live > multiuser system before and will probably do so again. Hair-raising. :-) Anyway, I've snuffled around in the code and I think I'd have to teach sysinstall what release it was built for before producing as comprehensive a warning as Wes was talking about. That'd be easy if I knew how VAR_RELNAME gets initialized. My take on the code made me think it's via kern.osrelease, but that doesn't seem to be the case. I've attached the diff I have on hand, but I'd obviously like to know how to do this properly. > Hmm... "bleet"'s not in esr's hacker dictionary. My original spelling was "bleat". Ciao, Sheldon. Index: options.c =================================================================== RCS file: /home/ncvs/src/release/sysinstall/options.c,v retrieving revision 1.62 diff -u -d -r1.62 options.c --- options.c 1999/08/05 19:50:26 1.62 +++ options.c 1999/08/12 01:04:16 @@ -95,7 +95,10 @@ #define TAPE_PROMPT "Please enter the tape block size in 512 byte blocks:" #define NEWFS_PROMPT "Please enter newfs(8) parameters:" -#define RELNAME_PROMPT "Please specify the release you wish to load or\n\"none\" for a generic release install:" +#define RELNAME_PROMPT "Please specify the release you wish to load or " \ + "\"none\" for a\ngeneric release install. Using an installed version " \ + "of sysinstall\nto install or upgrade to later releases is not " \ + "recommended." #define BPKG_PROMPT "Please specify the name of the HTML browser package:" #define BBIN_PROMPT "Please specify a full pathname to the HTML browser binary:" #define EDITOR_PROMPT "Please specify the name of the text editor you wish to use:" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 19:12:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 2E4071517C for ; Wed, 11 Aug 1999 19:12:12 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id TAA73493; Wed, 11 Aug 1999 19:10:37 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37B22D1E.56921DD@gorean.org> Date: Wed, 11 Aug 1999 19:10:38 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ignoretime in login.conf?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Doug writes: > > Also, the 'boolean' option is essentially undocumented in the > > login.conf man page. It's mentioned once, but there is no example of how > > it works or the fact that the @ sign is the symbol for it. The info is in > > login_cap(3), but it's hard to decipher for a non-programmer. I'll put > > this on my list if no one else wants to take it, and submit a PR. > > login.conf is a capability database like any other and therefore > follows the syntax described in the getcap(3) man page. Yes, which is basically restating my point, namely that if you don't already understand how it works the man page is of no use to you. :) I will produce diffs sometime soon. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 19:38:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 0686414CFE; Wed, 11 Aug 1999 19:38:20 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA00416; Wed, 11 Aug 1999 19:37:23 -0700 (PDT) Message-Id: <199908120237.TAA00416@lestat.nas.nasa.gov> To: "Alton, Matthew" Cc: "'Hackers@FreeBSD.ORG'" , "'fs@FreeBSD.ORG'" Subject: Re: BSD-XFS Update Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 11 Aug 1999 19:37:22 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999 16:46:46 -0500 "Alton, Matthew" wrote: > I am currently researching methods for implementing the 64-bit > syscalls stat64(), fstat64(), lseek64() &etc. delineated in the > SGI design doc _64 Bit File Access_ by Adam Sweeney. ...which, of course, is completely unnecessary, as systems derived from 4.4BSD have always had 64-bit file offsets. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 20:39:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AEF2B14CF3 for ; Wed, 11 Aug 1999 20:39:33 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id XAA81867 for ; Wed, 11 Aug 1999 23:39:46 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Wed, 11 Aug 1999 23:39:46 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: hackers@FreeBSD.org Subject: libcompat proposition Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What do you all think about growing a gnu subdirectory in src/lib/libcompat? Things like a getopt_long implementation (yes, if it will be accepted, I am volunteering to write it...) would go there, and all sorts of lame GNU libc cruft that we can try to be more compatible with. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Aug 11 20:47:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 04107156BE; Wed, 11 Aug 1999 20:47:29 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA18751; Thu, 12 Aug 1999 13:16:18 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990812131618:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Thu, 12 Aug 1999 13:16:18 +0930 (CST) From: "Daniel O'Connor" To: "Brian F. Feldman" Subject: RE: libcompat proposition Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990812131618:611=_ Content-Type: text/plain; charset=us-ascii On 12-Aug-99 Brian F. Feldman wrote: > What do you all think about growing a gnu subdirectory in src/lib/libcompat? > Things like a getopt_long implementation (yes, if it will be accepted, > I am volunteering to write it...) would go there, and all sorts of lame > GNU libc cruft that we can try to be more compatible with. Yay.. It would be quite handy.. No more digging through the source tree for a version of getopt.c and adding it by hand to the port.. --- 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 --_=XFMail.1.3.p0.FreeBSD:990812131618:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN7JDilbYW/HEoF9pAQFPxQP8ChzmFUIHfa4sT2Se0XWg4xz0hiLLMsNb o+apwZ4mw/lbYyDpxE4zoGBGP4kQ+gUmBN3SBRv9CX9SJuXD9Op8ArXuylGVMMbx 8/ApsCwtr55O09eQZyXSDcYB6iBaJDfzgZ5K9mTMRxb5EvzvC9ZPvPu71DUbZkVq 5FcZ9FoFTjc= =NE9p -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990812131618:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 20:50:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from swbell.net (mail-gw1.rcsntx.swbell.net [151.164.30.51]) by hub.freebsd.org (Postfix) with ESMTP id 4174B1575C; Wed, 11 Aug 1999 20:50:11 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (adsl-216-62-154-215.dsl.hstntx.swbell.net [216.62.154.215]) by swbell.net (8.9.3/8.9.3) with ESMTP id WAA02414; Wed, 11 Aug 1999 22:50:17 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA24100; Wed, 11 Aug 1999 22:52:10 -0500 (CDT) (envelope-from chris) Date: Wed, 11 Aug 1999 22:52:10 -0500 From: Chris Costello To: "Brian F. Feldman" Cc: hackers@FreeBSD.ORG Subject: Re: libcompat proposition Message-ID: <19990811225210.E772@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Brian F. Feldman on Wed, Aug 11, 1999 at 11:39:46PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 11, 1999, Brian F. Feldman wrote: > What do you all think about growing a gnu subdirectory in src/lib/libcompat? > Things like a getopt_long implementation (yes, if it will be accepted, > I am volunteering to write it...) would go there, and all sorts of lame > GNU libc cruft that we can try to be more compatible with. I'm in favor of a libgnucompat rather than gnu functions in libcompat. -- |Chris Costello |DYNAMIC LINKING ERROR: Your mistake is now everywhere. `------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 22:11:59 1999 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 13F0714C1C; Wed, 11 Aug 1999 22:11:46 -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 XAA22356; Wed, 11 Aug 1999 23:11:53 -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 XAA02041; Wed, 11 Aug 1999 23:11:38 -0600 (MDT) Message-Id: <199908120511.XAA02041@harmony.village.org> To: "Brian F. Feldman" Subject: Re: libcompat proposition Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Aug 1999 23:39:46 EDT." References: Date: Wed, 11 Aug 1999 23:11:38 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Brian F. Feldman" writes: : What do you all think about growing a gnu subdirectory in src/lib/libcompat? : Things like a getopt_long implementation (yes, if it will be accepted, : I am volunteering to write it...) would go there, and all sorts of lame : GNU libc cruft that we can try to be more compatible with. src/gnu/lib/libgnucompat might be better if is was GPL code. We've been trying to keep GPL'd code walled off from other code in the system. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 11 22:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 8284414D81 for ; Wed, 11 Aug 1999 22:41:29 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id HAA11874; Thu, 12 Aug 1999 07:41:34 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa11872; Thu Aug 12 07:41:33 1999 Received: from fwd.kryptokom.de ([192.168.6.40]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id HAA07363; Thu, 12 Aug 1999 07:45:59 +0200 Received: from post.com (localhost [127.0.0.1]) by fwd.kryptokom.de (8.9.2/8.9.2) with ESMTP id HAA01588; Thu, 12 Aug 1999 07:49:12 +0200 (CEST) (envelope-from eT@post.com) Message-ID: <37B26058.9B6A396F@post.com> Date: Thu, 12 Aug 1999 07:49:12 +0200 From: eT X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Cillian Sharkey , Hackers FreeBSD Subject: Re: changing root device to ... References: <37B1A8C0.26BD96CA@baker.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cillian Sharkey wrote: > > but in the boot up, the message, "changing root device to wd0s1" keeps appearing and keeps > > failing. in my /etc/fstab i have the following entry: > > > /dev/sd0s1a / ufs rw 1 1 > > > does anyone have any ideas. > > > the sd0 is probed and attached successfully during startup, but the change root fails > > because it keeps on trying to change root to a wd0 IDE. > > would i be right in guessing that you used to have the FreeBSD > system on IDE disk wd0 after which you transferred it over to > SCSI disk sd0 ? Hi Cillian! Thanks for the reply. You are absolutely correct. This is exactely the case. > is the system still booting off the IDE disk (if present) ? Yes. But not from the SCSI > to boot your system off the SCSI disk you should be able > to enter the following at the boot prompt : > 0:sd(0,a)/kernel > (or whatever the name of your kernel is) which should set > the root device ok... This works .. but how do I inflict a permanent change so that I don't have to use that method any longer? With fdisk I set the partition as bootable on the SCSI disk and it seems to boot it now but it can't mount the root partition as I can't figure out what device name to use as my root device in the /etc/fstab. I tried all the /dev/sd0* permutations I could find. eT -- Etienne de Bruin; eT@post.com "Visit http://Welcome.to/Shophar". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 0:14:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id ADC8B14D43 for ; Thu, 12 Aug 1999 00:14:42 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id QAA07865 for ; Thu, 12 Aug 1999 16:14:27 +0900 (JST) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id QAA03745 for ; Thu, 12 Aug 1999 16:14:27 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id QAA04064; Thu, 12 Aug 1999 16:14:26 +0900 (JST) Message-Id: <199908120714.QAA04064@lavender.yy.cs.keio.ac.jp> To: hackers@FreeBSD.org Subject: Is there any plan to newbuslize for 3-stable? X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 12 Aug 1999 16:14:26 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I have a question about new-bus code. Currently device style of FreeBSD-4-current is changing to newbus. But is there any plan to newbuslize for 3-stable? If my patch for pcm/ESS sound chip apply to FreeBSD, may I send-pr with old-config style? Yes, current pcm sound driver is old-config, but "Cameron Grant" is working to newbuslize. MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 0:26: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oleg.sani-c.vrn.ru (oleg.sani-c.vrn.ru [195.98.74.83]) by hub.freebsd.org (Postfix) with ESMTP id D5F3014D43 for ; Thu, 12 Aug 1999 00:25:37 -0700 (PDT) (envelope-from oleg@oleg.sani-c.vrn.ru) Received: from localhost (oleg@localhost) by oleg.sani-c.vrn.ru (8.9.2/8.9.2) with ESMTP id LAA00355 for ; Thu, 12 Aug 1999 11:25:38 +0400 (MSD) (envelope-from oleg@oleg.sani-c.vrn.ru) Date: Thu, 12 Aug 1999 11:25:37 +0400 (MSD) From: Oleg Derevenetz To: freebsd-hackers@freebsd.org Subject: mmap bug 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 Oh, I'm sorry, I made a mistake when posting code. I posted incorrectly patched version... This version correct : #include #include #include #include #include #include #include main(int argc, char *argv[]) { int fd; int i; int len=1024*1024*10; /*ie 10Mbytes*/ caddr_t addr; char ttt[80]; int bunlink=0; if (argc>1 && strcmp (argv[1], "-u")==0) bunlink=1; for (i=0;;i++) { sprintf (ttt,"%d",i); printf ("mmapping %ld byte region on file %s\n", len, ttt); fd=open(ttt,O_CREAT|O_RDWR,0666); if (fd<0) { printf("open error %ld\n",errno); exit(1); } lseek(fd,len-1,SEEK_SET); write(fd,"",1); addr=mmap(0,len,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0); if (addr==MAP_FAILED) { printf("mmap error %ld",errno); exit(1); } memset(addr,'x',len); if ( munmap(addr, len) != 0 ) { fprintf(stderr, "munmap failed\n"); exit(EXIT_FAILURE); } close(fd); if ( bunlink ) unlink (ttt); } } Thank you for answers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 1:41:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id F3EED14E44 for ; Thu, 12 Aug 1999 01:41:40 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Thu, 12 Aug 1999 9:43:54 +0100 Message-ID: <37B284E5.AAC0DFD1@baker.ie> Date: Thu, 12 Aug 1999 09:25:09 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: eT Cc: Hackers FreeBSD Subject: Re: changing root device to ... References: <37B1A8C0.26BD96CA@baker.ie> <37B26058.9B6A396F@post.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > is the system still booting off the IDE disk (if present) ? > > Yes. But not from the SCSI You can try setting the BIOS to boot from the SCSI disk which should do the trick..unless you have a crappy BIOS that doesn't let you do that.. :( > With fdisk I set the partition as bootable on the SCSI disk and it seems to boot it now but it > can't mount the root partition as I can't figure out what device name to use as my root device > in the /etc/fstab. > > I tried all the /dev/sd0* permutations I could find. /dev/sd0a should point to your root partition on the SCSI disk Regards, - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 1:49:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 41EA514F6E for ; Thu, 12 Aug 1999 01:49:19 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA59983; Thu, 12 Aug 1999 11:49:14 +0300 (EEST) (envelope-from will) To: Matthew.Alton@anheuser-busch.com (Alton, Matthew) Cc: hackers@freebsd.org Subject: Re: BSD-XFS Update References: <0740CBD1D149D31193EB0008C7C56836EB8B05@STLABCEXG012> From: Ville-Pertti Keinonen Date: 12 Aug 1999 11:49:13 +0300 In-Reply-To: Matthew.Alton@anheuser-busch.com's message of "12 Aug 1999 00:49:21 +0300" Message-ID: <86btcdmliu.fsf@not.demophon.com> Lines: 15 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew.Alton@anheuser-busch.com (Alton, Matthew) writes: > I am currently researching methods for implementing the 64-bit > syscalls stat64(), fstat64(), lseek64() &etc. delineated in the > SGI design doc _64 Bit File Access_ by Adam Sweeney. Do the design docs indicate how inode numbers should interact with userland APIs? IIRC, inode numbers are 64-bit numbers in XFS. Since ino_t, st_ino of struct stat and d_fileno of struct dirent are only 32 bits, inode numbers may be truncated and not appear unique to userland. This would break the assumptions of some code (e.g. getcwd(3), when not using the kernel extension). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 1:54:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 36B2B14FAD for ; Thu, 12 Aug 1999 01:54:10 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA59992; Thu, 12 Aug 1999 11:52:38 +0300 (EEST) (envelope-from will) To: chris@calldei.com Cc: hackers@freebsd.org Subject: Re: libcompat proposition References: <19990811225210.E772@holly.dyndns.org> From: Ville-Pertti Keinonen Date: 12 Aug 1999 11:52:37 +0300 In-Reply-To: chris@calldei.com's message of "12 Aug 1999 06:52:20 +0300" Message-ID: <86aerxmld6.fsf@not.demophon.com> Lines: 9 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG chris@calldei.com (Chris Costello) writes: > I'm in favor of a libgnucompat rather than gnu functions in > libcompat. And how would a libgnucompat be different from libiberty? Except of course that it would be maintained by the FreeBSD folks... Or that it would be maintained at all. ;--) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2: 1:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1389214FAD for ; Thu, 12 Aug 1999 02:01:06 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA17105; Thu, 12 Aug 1999 11:01:07 +0200 (CEST) (envelope-from des) To: Tony Finch Cc: kdrobnac@mission.mvnc.edu, Hackers@FreeBSD.ORG Subject: Re: BSD XFS Port & BSD VFS Rewrite References: <199908111559.KAA24052@plains.NoDak.edu> From: Dag-Erling Smorgrav Date: 12 Aug 1999 11:01:06 +0200 In-Reply-To: Tony Finch's message of "Wed, 11 Aug 1999 20:46:45 +0100" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch writes: > Kenny Drobnack wrote: > > This may be a stupid question, but what's to keep from putting xfs in > > FreeBSD? Is there something in the licenses that says you can't use > > GPL'ed software and software under the BSD License together? > Yes. The BSD licence requirement for acknowledging UCB in any > advertising conflicts with the GPL requirement that further > restrictions should not be added to those already in the GPL. This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2:19:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 6F06914D18 for ; Thu, 12 Aug 1999 02:19:11 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.9.3/8.9.3) id LAA02565 for ; Thu, 12 Aug 1999 11:18:04 +0200 (SAST) Received: by citadel via recvmail id 2563; Thu Aug 12 11:17:43 1999 Message-ID: <37B2917A.6CBBC950@cdsec.com> Date: Thu, 12 Aug 1999 11:18:50 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: New tests for test(1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2:24:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D2C214E2C for ; Thu, 12 Aug 1999 02:24:06 -0700 (PDT) (envelope-from nadav@cs.technion.ac.il) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with ESMTP id MAA07904; Thu, 12 Aug 1999 12:25:09 +0300 (IDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id MAA28180; Thu, 12 Aug 1999 12:25:07 +0300 (IDT) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Thu, 12 Aug 1999 12:25:07 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Graham Wheeler Cc: hackers@freebsd.org Subject: Re: New tests for test(1) In-Reply-To: <37B2917A.6CBBC950@cdsec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Graham Wheeler wrote: > Hi all > > I was writing a script yesterday, and I wanted to have a test to compare > the modification time of two files. test(1) doesn't have the ability to > do this. In the end I worked around this by using make(1), but it set me > thinking - wouldn't it be a good idea to add some new tests to test(1), > to compare files based on criteria like size or modification date? A suggestion for another way to implement such a test: ls -1t file1 file2 | head -1 will give you the newest of the two... That's what I use when I need to do such tests. I guess it's easier and faster than make. > > Anyone else think this is a good idea? > > -- > Dr Graham Wheeler E-mail: gram@cequrux.com > Cequrux Technologies Phone: +27(21)423-6065/6/7 > Firewalls/Virtual Private Networks Fax: +27(21)24-3656 > Data/Network Security Specialists WWW: http://www.cequrux.com/ > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2:36:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.indigo.ie (relay02.indigo.ie [194.125.133.226]) by hub.freebsd.org (Postfix) with SMTP id B156F14EC2 for ; Thu, 12 Aug 1999 02:36:31 -0700 (PDT) (envelope-from niall@pobox.com) Received: (qmail 19052 messnum 46178 invoked from network[194.125.134.55/ts01-055.dublin.indigo.ie]); 12 Aug 1999 09:33:34 -0000 Received: from ts01-055.dublin.indigo.ie (HELO pobox.com) (194.125.134.55) by relay02.indigo.ie (qp 19052) with SMTP; 12 Aug 1999 09:33:34 -0000 Message-ID: <37B2B02B.90751E96@pobox.com> Date: Thu, 12 Aug 1999 11:29:47 +0000 From: Niall Smart X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Cillian Sharkey Cc: Doug White , questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions References: <37B20EBE.76AC89DA@baker.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -- snip -- > if (pswitch) { > /* > * If the device is not configured up, we cannot put it > in > * promiscuous mode. > */ > if ((ifp->if_flags & IFF_UP) == 0) > return (ENETDOWN); > if (ifp->if_pcount++ != 0) > return (0); > ifp->if_flags |= IFF_PROMISC; > log(LOG_INFO, "%s%d: promiscuous mode enabled\n", > ifp->if_name, ifp->if_unit); > } else { > if (--ifp->if_pcount > 0) > return (0); > ifp->if_flags &= ~IFF_PROMISC; > ---> log(LOG_INFO, "%s%d: promiscuous mode disabled\n", > ---> ifp->if_name, ifp->if_unit); Shouldn't this be: if (ipf->if_flags & IFF_PROMISC) { ipf->if_flags &= ~IFF_PROMISC; log(LOG_INFO, "%s%d: promiscuous mode disabled\n", ifp->if_name, ifp->if_unit); } Or is the test for IFF_PROMISC made earlier in the code? You should only print a disabled message when it has previously been enabled so that log file watchers can always match up the up/down pairs. Regards, Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2:43:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B8A4614E9F for ; Thu, 12 Aug 1999 02:43:28 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA17254; Thu, 12 Aug 1999 11:42:43 +0200 (CEST) (envelope-from des) To: Graham Wheeler Cc: hackers@FreeBSD.ORG Subject: Re: New tests for test(1) References: <37B2917A.6CBBC950@cdsec.com> From: Dag-Erling Smorgrav Date: 12 Aug 1999 11:42:42 +0200 In-Reply-To: Graham Wheeler's message of "Thu, 12 Aug 1999 11:18:50 +0200" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler writes: > I was writing a script yesterday, and I wanted to have a test to compare > the modification time of two files. test(1) doesn't have the ability to > do this. In the end I worked around this by using make(1), but it set me > thinking - wouldn't it be a good idea to add some new tests to test(1), > to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 2:49:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B0DB514EEA; Thu, 12 Aug 1999 02:49:28 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11ErSd-0000Ss-00; Thu, 12 Aug 1999 11:47:47 +0200 From: Sheldon Hearn To: Niall Smart Cc: Cillian Sharkey , Doug White , questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions In-reply-to: Your message of "Thu, 12 Aug 1999 11:29:47 GMT." <37B2B02B.90751E96@pobox.com> Date: Thu, 12 Aug 1999 11:47:47 +0200 Message-ID: <1789.934451267@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: > Or is the test for IFF_PROMISC made earlier in the code? You > should only print a disabled message when it has previously > been enabled so that log file watchers can always match up > the up/down pairs. I've been using if.c modified exactly as suggested for a few months now and have experienced the intended results without apparent problems. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3: 8:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id AA14514D46; Thu, 12 Aug 1999 03:08:52 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Thu, 12 Aug 1999 11:14:12 +0100 Message-ID: <37B29A10.2DD73A0A@baker.ie> Date: Thu, 12 Aug 1999 10:55:28 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Niall Smart Cc: hackers@freebsd.org, questions@freebsd.org Subject: Re: Various Questions References: <37B20EBE.76AC89DA@baker.ie> <37B2B02B.90751E96@pobox.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > if (--ifp->if_pcount > 0) > > return (0); > > ifp->if_flags &= ~IFF_PROMISC; > > ---> log(LOG_INFO, "%s%d: promiscuous mode disabled\n", > > ---> ifp->if_name, ifp->if_unit); > > Shouldn't this be: > > if (ipf->if_flags & IFF_PROMISC) { > ipf->if_flags &= ~IFF_PROMISC; > log(LOG_INFO, "%s%d: promiscuous mode disabled\n", ifp->if_name, > ifp->if_unit); > } > > Or is the test for IFF_PROMISC made earlier in the code? You > should only print a disabled message when it has previously > been enabled so that log file watchers can always match up > the up/down pairs. yes that I think that would be a better idea to check to see if it is actually in promiscuous mode first before printing out our disabled message so all pairs match..however doesn't the following code from above seem to gaurd against this situation : ? if (--ifp->if_pcount > 0) return (0); from what I can see, it only turns off promiscuous mode if if_pcount reaches zero, ie. all requests for promiscuous mode to be off account for all the previous requests for promiscuous mode to be on..? ..then again I'm no expert kernel hacker (yet!) and I certainly don't pretend to be one either, so I'll leave this to the experts :-D - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3:23:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3B64614D46 for ; Thu, 12 Aug 1999 03:23:00 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11Es0P-0000YH-00; Thu, 12 Aug 1999 12:22:41 +0200 From: Sheldon Hearn To: Dag-Erling Smorgrav Cc: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: New tests for test(1) In-reply-to: Your message of "12 Aug 1999 11:42:42 +0200." Date: Thu, 12 Aug 1999 12:22:39 +0200 Message-ID: <2124.934453359@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Aug 1999 11:42:42 +0200, Dag-Erling Smorgrav wrote: > NetBSD's test(1) utility has this (-nt and -ot). We should probably > merge in their changes. Their code isn't useful in this case, since they've merged in a pdksh-derived version of test. How about we do the same? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3:24:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay04.indigo.ie (relay04.indigo.ie [194.125.133.228]) by hub.freebsd.org (Postfix) with SMTP id C4C28156FD for ; Thu, 12 Aug 1999 03:24:20 -0700 (PDT) (envelope-from niall@pobox.com) Received: (qmail 26143 messnum 46410 invoked from network[194.125.220.174/ts06-047.dublin.indigo.ie]); 12 Aug 1999 10:24:22 -0000 Received: from ts06-047.dublin.indigo.ie (HELO pobox.com) (194.125.220.174) by relay04.indigo.ie (qp 26143) with SMTP; 12 Aug 1999 10:24:22 -0000 Message-ID: <37B2BC13.ECA642D0@pobox.com> Date: Thu, 12 Aug 1999 12:20:35 +0000 From: Niall Smart X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Cillian Sharkey , Doug White , questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions References: <1789.934451267@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: > > > Or is the test for IFF_PROMISC made earlier in the code? You > > should only print a disabled message when it has previously > > been enabled so that log file watchers can always match up > > the up/down pairs. > > I've been using if.c modified exactly as suggested for a few months now > and have experienced the intended results without apparent problems. But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Time to start reading some code methinks Niall + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3:27:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 7F11F15705 for ; Thu, 12 Aug 1999 03:27:21 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id DAA06011; Thu, 12 Aug 1999 03:25:00 -0700 (PDT) Message-Id: <199908121025.DAA06011@lestat.nas.nasa.gov> To: Dag-Erling Smorgrav Cc: Tony Finch , kdrobnac@mission.mvnc.edu, Hackers@FreeBSD.ORG Subject: Re: BSD XFS Port & BSD VFS Rewrite Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 12 Aug 1999 03:25:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav wrote: > This prevents you from relicensing BSD software under the GPL. It does > not prevent you from selling an OS that has both BSD and GPL bits, as > long as the GPL bits come with full source. If you have an executable object which includes GPL'd code, you must supply FULL SOURCE for the *entire* object, not just the GPL'd bits. This is the real crux of the problem; the GPL has a virus-like nature. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3:29: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A988B15705 for ; Thu, 12 Aug 1999 03:29:04 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA17420; Thu, 12 Aug 1999 12:27:35 +0200 (CEST) (envelope-from des) To: Jason Thorpe Cc: Dag-Erling Smorgrav , Tony Finch , kdrobnac@mission.mvnc.edu, Hackers@FreeBSD.ORG Subject: Re: BSD XFS Port & BSD VFS Rewrite References: <199908121025.DAA06011@lestat.nas.nasa.gov> From: Dag-Erling Smorgrav Date: 12 Aug 1999 12:27:35 +0200 In-Reply-To: Jason Thorpe's message of "Thu, 12 Aug 1999 03:25:00 -0700" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe writes: > On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav wrote: > > This prevents you from relicensing BSD software under the GPL. It does > > not prevent you from selling an OS that has both BSD and GPL bits, as > > long as the GPL bits come with full source. > If you have an executable object which includes GPL'd code, you must > supply FULL SOURCE for the *entire* object, not just the GPL'd bits. We're talking separate binaries here. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 3:35:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 36B0C14FAD; Thu, 12 Aug 1999 03:35:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11Es7N-0000Zu-00; Thu, 12 Aug 1999 12:29:53 +0200 From: Sheldon Hearn To: Niall Smart Cc: Cillian Sharkey , Doug White , questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions In-reply-to: Your message of "Thu, 12 Aug 1999 12:20:35 GMT." <37B2BC13.ECA642D0@pobox.com> Date: Thu, 12 Aug 1999 12:29:53 +0200 Message-ID: <2225.934453793@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999 12:20:35 GMT, Niall Smart wrote: > But what happens if you write a program which does whatever ioctl is > required to unpromiscify an interface and run it on an unpromiscuous > interface, does it print a message to syslog even though promiscuous > mode was never enabled in the first place? Like I said, I seem to get the intended behaviour. vty1 -> start trafshow Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled vty2 -> start trafshow vty1 -> kill trafshow vty2 -> kill trafshow Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4: 1:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cube.gelatinous.com (cube.gelatinous.com [207.82.194.150]) by hub.freebsd.org (Postfix) with SMTP id ABCE11577E for ; Thu, 12 Aug 1999 04:01:40 -0700 (PDT) (envelope-from aaron@gelatinous.com) Received: (qmail 13572 invoked by uid 1000); 12 Aug 1999 11:01:48 -0000 Date: Thu, 12 Aug 1999 04:01:48 -0700 From: Aaron Smith To: freebsd-hackers@freebsd.org Subject: Re: New tests for test(1) Message-ID: <19990812040148.A13484@gelatinous.com> References: <37B2917A.6CBBC950@cdsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37B2917A.6CBBC950@cdsec.com>; from Graham Wheeler on Thu, Aug 12, 1999 at 11:18:50AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. -- Aaron Smith aaron@mutex.org On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: > thinking - wouldn't it be a good idea to add some new tests to test(1), > to compare files based on criteria like size or modification date? > > Anyone else think this is a good idea? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4: 2:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id 17E9615726 for ; Thu, 12 Aug 1999 04:02:43 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11Escl-000Nxv-00; Thu, 12 Aug 1999 12:02:19 +0100 To: dillon@apollo.backplane.com From: Tony Finch Cc: freebsd-hackers@freebsd.org Subject: Re: mmap bug In-Reply-To: <199908112116.OAA77941@apollo.backplane.com> References: <199908111819.LAA26998@implode.root.com> Message-Id: Date: Thu, 12 Aug 1999 12:02:19 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > One solution would be to map clean R+W pages RO and force a write fault > to occur, allowing the system to recognize that there are too many dirty > pages in vm_fault before it is too late and flush some of them. The > downside of this is that, of course, we take unnecessary faults. Surely they aren't unnecessary faults if they are required for correctness? Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4:18:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 6E0CF155DA for ; Thu, 12 Aug 1999 04:18:05 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.9.3/8.9.3) id NAA10290; Thu, 12 Aug 1999 13:15:30 +0200 (SAST) Received: by citadel via recvmail id 10220; Thu Aug 12 13:14:44 1999 Message-ID: <37B2ACE8.D263C8E7@cdsec.com> Date: Thu, 12 Aug 1999 13:15:52 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Aaron Smith Cc: freebsd-hackers@freebsd.org Subject: Re: New tests for test(1) References: <37B2917A.6CBBC950@cdsec.com> <19990812040148.A13484@gelatinous.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aaron Smith wrote: > > this seems undesirable to me, since using it immediately makes your shell > scripts nonportable. i liked the ls -t suggestion though. Portability is a Good Thing, but I write a lot of one-off scripts in which portability isn't an issue. Also, just because one uses standard shell commands is no guarantee of portability, as a shell script can invoke arbitrary programs, which may or may not be present or compatible across different hosts. -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4:37:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 99BB314E5B for ; Thu, 12 Aug 1999 04:37:34 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id MAA16954; Thu, 12 Aug 1999 12:35:33 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 12 Aug 1999 12:26:43 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990812040148.A13484@gelatinous.com> References: <37B2917A.6CBBC950@cdsec.com>; from Graham Wheeler on Thu, Aug 12, 1999 at 11:18:50AM +0200 <37B2917A.6CBBC950@cdsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 12 Aug 1999 12:26:41 +0000 To: Aaron Smith From: Bob Bishop Subject: Re: New tests for test(1) Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 4:01 am -0700 12/8/99, Aaron Smith wrote: >this seems undesirable to me, since using it immediately makes your shell >scripts nonportable. i liked the ls -t suggestion though. Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... > >On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: >> thinking - wouldn't it be a good idea to add some new tests to test(1), >> to compare files based on criteria like size or modification date? >> >> Anyone else think this is a good idea? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4:52:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4B3CB14E5B for ; Thu, 12 Aug 1999 04:52:37 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EtLI-00012a-00; Thu, 12 Aug 1999 13:48:20 +0200 From: Sheldon Hearn To: Bob Bishop Cc: Aaron Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: New tests for test(1) In-reply-to: Your message of "Thu, 12 Aug 1999 12:26:41 GMT." Date: Thu, 12 Aug 1999 13:48:20 +0200 Message-ID: <4003.934458500@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999 12:26:41 GMT, Bob Bishop wrote: > Further, isn't test a builtin for most (all?) shells? Sounds like a can of > worms to me... If your only motivation for saying it's a can of worms is that test is usually a builtin, don't sweat it. Lots of scripts insist on using /bin/test . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 4:53:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4AA4415040 for ; Thu, 12 Aug 1999 04:53:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EtPk-00013S-00; Thu, 12 Aug 1999 13:52:56 +0200 From: Sheldon Hearn To: Graham Wheeler Cc: Aaron Smith , freebsd-hackers@freebsd.org Subject: Re: New tests for test(1) In-reply-to: Your message of "Thu, 12 Aug 1999 13:15:52 +0200." <37B2ACE8.D263C8E7@cdsec.com> Date: Thu, 12 Aug 1999 13:52:56 +0200 Message-ID: <4057.934458776@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999 13:15:52 +0200, Graham Wheeler wrote: > Portability is a Good Thing, but I write a lot of one-off scripts > in which portability isn't an issue. Not to mention that following NetBSD's lead on issues relating to portability probably is seldom a bad idea. :-) Give PR 13091 a bash. Or a sh. Whatever works for you. :-) >Number: 13091 >Synopsis: [PATCH] pdksh-derived replacement for test(1) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 5:26:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DB7EA15727 for ; Thu, 12 Aug 1999 05:25:58 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11EttU-00019K-00; Thu, 12 Aug 1999 14:23:40 +0200 From: Sheldon Hearn To: Dag-Erling Smorgrav , Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: New tests for test(1) In-reply-to: Your message of "Thu, 12 Aug 1999 12:22:39 +0200." <2124.934453359@axl.noc.iafrica.com> Date: Thu, 12 Aug 1999 14:23:40 +0200 Message-ID: <4421.934460620@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999 12:22:39 +0200, Sheldon Hearn wrote: > Their code isn't useful in this case, since they've merged in a > pdksh-derived version of test. How about we do the same? :-) By the way, OpenBSD have _also_ incorporated NetBSD's test. *evil.grin* Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 6:17:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from grisu.bik-gmbh.de (grisu.bik-gmbh.de [194.233.237.82]) by hub.freebsd.org (Postfix) with ESMTP id D391A14D18 for ; Thu, 12 Aug 1999 06:17:16 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by grisu.bik-gmbh.de (8.8.8/8.6.9) with ESMTP id PAA11699; Thu, 12 Aug 1999 15:16:43 +0200 (MEST) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id PAA18923; Thu, 12 Aug 1999 15:16:40 +0200 (MET DST) Date: Thu, 12 Aug 1999 15:16:39 +0200 From: Martin Cracauer To: Bob Bishop Cc: Aaron Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: New tests for test(1) Message-ID: <19990812151639.A17479@cons.org> References: <37B2917A.6CBBC950@cdsec.com>; <37B2917A.6CBBC950@cdsec.com> <19990812040148.A13484@gelatinous.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Bob Bishop on Thu, Aug 12, 1999 at 12:26:41PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> thinking - wouldn't it be a good idea to add some new tests to test(1), > >> to compare files based on criteria like size or modification date? So far it has been policy for FreeBSD not to add options to commandline utilities that are replaceable by simple shell script constructs. Especially if that other construct is POSIX-compliant. Examples: - An option to date(1), which would print the machine's idea of the time, no matter what $TZ is set it. Easily replaceable by (unset TZ; date) - An option to a tool that puts out a single line of text to stdout. The option would make it print its line without the final newline. Easily replaceable by backquotes echo `thistool` Clearly, the functionality discussed falls into this category. ls -t and head are specified in POSIX, thus it isn't affected by the usualy shell script unportability like another poster implied. > >this seems undesirable to me, since using it immediately makes your shell > >scripts nonportable. i liked the ls -t suggestion though. > > Further, isn't test a builtin for most (all?) shells? Sounds like a can of > worms to me... FreeBSD's /bin/sh uses the external /bin/test. Most other shells in common use have it built in. You are right that this would confuse people no end since most couldn't use the same test(1) arguments in theirs scripts and interactivly. In a word, I'm against it. Whatever you want this for, it's the far better solution to have your own test(1)-like utility in your personal search path. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 7: 4:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 868DD15774 for ; Thu, 12 Aug 1999 07:04:48 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id QAA01522; Thu, 12 Aug 1999 16:03:28 +0200 (CEST) To: "Steven Jurczyk" Cc: Subject: Re: how fast get real/absolute path of file References: <017f01bee3e2$86c62840$02e6cdc3@haven.home.net.pl> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 12 Aug 1999 16:03:27 +0200 In-Reply-To: "Steven Jurczyk"'s message of "Wed, 11 Aug 1999 12:16:07 +0200" Message-ID: <5lpv0tt7tc.fsf@assaris.sics.se> Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven Jurczyk" writes: > How fast get real / absolute path of specified file. I try use > readlink, but this slow (for path /home/web/docs/index.htm must be > done 4 or more (if this path have symlinks) readlink's - for /home, > /home/web, /home/web/docs and /home/web/docs/index.htm). Is any > faster/simpler method for getting absolute path of file? I would use realpath(3). What's your application where that's not fast enough? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 7:54: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id A6633157A1 for ; Thu, 12 Aug 1999 07:54:05 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id QAA01614; Thu, 12 Aug 1999 16:55:11 +0200 (CEST) To: "Jung, Michael" Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Recreating LKM References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 12 Aug 1999 16:55:10 +0200 In-Reply-To: "Jung, Michael"'s message of "Wed, 11 Aug 1999 14:43:38 -0400" Message-ID: <5loggdt5f5.fsf@assaris.sics.se> Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jung, Michael" writes: > Ok.... How does one recreate /dev/lkm for 4.0-Current? It is no longer > in /dev/MAKEDEV. There's no LKM support in -current any longer. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 8:17:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.epita.fr (hermes.epita.fr [194.98.116.10]) by hub.freebsd.org (Postfix) with ESMTP id 5EC73157C2; Thu, 12 Aug 1999 08:17:01 -0700 (PDT) (envelope-from freebsd@epita.fr) Received: from guiscar (guiscar.epita.fr [10.42.1.49]) by hermes.epita.fr id QAA13470 Thu, 12 Aug 1999 16:45:12 GMT From: free bsd Message-Id: <199908121645.QAA13470@hermes.epita.fr> Subject: need some tools To: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Thu, 12 Aug 1999 17:16:07 +0000 (GMT) Organization: Epita (French Computer Science school) Operating-System: definitely UNIX Postal-Address: 14 rue voltaire, 94270 kremlin bicêtre Function: Computer Science Student X-Mailer: ELM [version 2.5 PL0pre8] 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 hello, I would like to know, if there a way (a tools) to make a partition "fat16". thanks. -- flav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 8:23:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 97105157CA for ; Thu, 12 Aug 1999 08:23:29 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA91462; Thu, 12 Aug 1999 11:22:53 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 11:22:53 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Warner Losh Cc: hackers@FreeBSD.org Subject: Re: libcompat proposition In-Reply-To: <199908120511.XAA02041@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Warner Losh wrote: > In message "Brian F. Feldman" writes: > : What do you all think about growing a gnu subdirectory in src/lib/libcompat? > : Things like a getopt_long implementation (yes, if it will be accepted, > : I am volunteering to write it...) would go there, and all sorts of lame > : GNU libc cruft that we can try to be more compatible with. > > src/gnu/lib/libgnucompat > > might be better if is was GPL code. We've been trying to keep GPL'd > code walled off from other code in the system. I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I wouldn't be taking encumbered code to put in a standard library that would normally be free... > > Warner > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 8:31:33 1999 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 1FA0D157CE; Thu, 12 Aug 1999 08:31:28 -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 JAA23838; Thu, 12 Aug 1999 09:29:00 -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 JAA04195; Thu, 12 Aug 1999 09:28:50 -0600 (MDT) Message-Id: <199908121528.JAA04195@harmony.village.org> To: free bsd Subject: Re: need some tools Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 12 Aug 1999 17:16:07 -0000." <199908121645.QAA13470@hermes.epita.fr> References: <199908121645.QAA13470@hermes.epita.fr> Date: Thu, 12 Aug 1999 09:28:50 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908121645.QAA13470@hermes.epita.fr> free bsd writes: : I would like to know, if there a way (a tools) to make a partition "fat16". fdisk to mark the partion as fat16, newfs_msdos to splat a file system onto it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 8:31:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id 46DF3157F0; Thu, 12 Aug 1999 08:31:34 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Thu, 12 Aug 1999 16:34:03 +0100 Message-ID: <37B2E503.B6A3C229@baker.ie> Date: Thu, 12 Aug 1999 16:15:15 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Niall Smart , Doug White , questions@freebsd.org, hackers@freebsd.org Subject: Re: Various Questions References: <2225.934453793@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But what happens if you write a program which does whatever ioctl is > > required to unpromiscify an interface and run it on an unpromiscuous > > interface, does it print a message to syslog even though promiscuous > > mode was never enabled in the first place? > > Like I said, I seem to get the intended behaviour. > > vty1 -> start trafshow > Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled > vty2 -> start trafshow > vty1 -> kill trafshow > vty2 -> kill trafshow > Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled > > :-) If everything works ok , howabout one of the developers commits this modification to /sys/net/if.c ? - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 8:44:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E9DB7157E5 for ; Thu, 12 Aug 1999 08:44:29 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA91725; Thu, 12 Aug 1999 11:41:31 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 11:41:31 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Graham Wheeler , hackers@FreeBSD.org Subject: Re: New tests for test(1) 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 12 Aug 1999, Dag-Erling Smorgrav wrote: > Graham Wheeler writes: > > I was writing a script yesterday, and I wanted to have a test to compare > > the modification time of two files. test(1) doesn't have the ability to > > do this. In the end I worked around this by using make(1), but it set me > > thinking - wouldn't it be a good idea to add some new tests to test(1), > > to compare files based on criteria like size or modification date? > > NetBSD's test(1) utility has this (-nt and -ot). We should probably > merge in their changes. Hmm... this is in pdksh too... > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 8:45:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.Bohemia.Net (relay.Bohemia.Net [194.24.224.37]) by hub.freebsd.org (Postfix) with ESMTP id B1F2E15840; Thu, 12 Aug 1999 08:45:49 -0700 (PDT) (envelope-from lizner@komix.cz) Received: from komix.bohemia.net (komix.bohemia.net [194.24.227.232]) by relay.Bohemia.Net (8.9.3/8.9.3) with ESMTP id RAA19516; Thu, 12 Aug 1999 17:45:50 +0200 Received: from ganymed.komix.com (lizner@ganymed [207.207.207.207]) by komix.bohemia.net (8.8.5/SCO5) with ESMTP id RAA07912; Thu, 12 Aug 1999 17:39:37 +0200 (CETDST) Date: Thu, 12 Aug 1999 17:48:22 +0200 (CEST) From: Martin Lizner X-Sender: lizner@ganymed.komix.com To: freebsd-net@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: freebsd4.0 (a little bit offtopic) In-Reply-To: <199908121528.JAA04195@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gentlemen, i am writing a short article on differences between 4.0 vs 3.2 versions for our corporate magazine - it's focused especially on networking/hacking. Is there a list of new features/approach ? Or what is your experience ? (i am testing myself, but more people == more interesting opinions). Thank you. Martin Lizner +420-2-7911637 Konstantinova 1472 Praha 4 CR Xerox does it again and again To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 8:51:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A7D62157E5 for ; Thu, 12 Aug 1999 08:51:48 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA91870; Thu, 12 Aug 1999 11:50:03 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 11:50:03 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Graham Wheeler , hackers@FreeBSD.org Subject: Re: New tests for test(1) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Brian F. Feldman wrote: > On 12 Aug 1999, Dag-Erling Smorgrav wrote: > > > Graham Wheeler writes: > > > I was writing a script yesterday, and I wanted to have a test to compare > > > the modification time of two files. test(1) doesn't have the ability to > > > do this. In the end I worked around this by using make(1), but it set me > > > thinking - wouldn't it be a good idea to add some new tests to test(1), > > > to compare files based on criteria like size or modification date? > > > > NetBSD's test(1) utility has this (-nt and -ot). We should probably > > merge in their changes. > > Hmm... this is in pdksh too... In other words, I think we've come upon more reasons to switch. > > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ > green@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 > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 8:58:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E9C5F157E5; Thu, 12 Aug 1999 08:58:10 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA91943; Thu, 12 Aug 1999 11:57:36 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 11:57:36 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Warner Losh Cc: free bsd , freebsd-net@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: need some tools In-Reply-To: <199908121528.JAA04195@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Warner Losh wrote: > In message <199908121645.QAA13470@hermes.epita.fr> free bsd writes: > : I would like to know, if there a way (a tools) to make a partition "fat16". > > fdisk to mark the partion as fat16, newfs_msdos to splat a file system > onto it. > > Warner > This should have gone to freebsd-questions, not either -net, -hackers, or BOTH. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 9:28:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id A46A015040; Thu, 12 Aug 1999 09:28:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA26032; Thu, 12 Aug 1999 09:32:13 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199908121632.JAA26032@troutmask.apl.washington.edu> Subject: Re: libcompat proposition In-Reply-To: from "Brian F. Feldman" at "Aug 12, 1999 11:22:53 am" To: green@FreeBSD.ORG (Brian F. Feldman) Date: Thu, 12 Aug 1999 09:32:13 -0700 (PDT) Cc: imp@village.org (Warner Losh), hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman wrote: > On Wed, 11 Aug 1999, Warner Losh wrote: > > > In message "Brian F. Feldman" writes: > > : What do you all think about growing a gnu subdirectory in src/lib/libcompat? > > : Things like a getopt_long implementation (yes, if it will be accepted, > > : I am volunteering to write it...) would go there, and all sorts of lame > > : GNU libc cruft that we can try to be more compatible with. > > > > src/gnu/lib/libgnucompat > > > > might be better if is was GPL code. We've been trying to keep GPL'd > > code walled off from other code in the system. > > I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I > wouldn't be taking encumbered code to put in a standard library that would > normally be free... > If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 9:40: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6325D14E2F for ; Thu, 12 Aug 1999 09:40:05 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id MAA92610; Thu, 12 Aug 1999 12:39:59 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 12:39:59 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Steve Kargl Cc: Warner Losh , hackers@FreeBSD.org Subject: Re: libcompat proposition In-Reply-To: <199908121632.JAA26032@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Steve Kargl wrote: > > If you're writing unencumbered code, placing it under > libcompat/gnu may lead to confusion because all other > directory paths containing gnu contain GPL'd code. > Just stick it into libcompat. That doesn't fit with the current organization. Choose: a. fsf b. gnu c. glibc If this were to be approved of, of course. > > -- > Steve > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 9:43:57 1999 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 D1EDE14D00; Thu, 12 Aug 1999 09:43: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 KAA24015; Thu, 12 Aug 1999 10:43:27 -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 KAA04759; Thu, 12 Aug 1999 10:43:18 -0600 (MDT) Message-Id: <199908121643.KAA04759@harmony.village.org> To: Steve Kargl Subject: Re: libcompat proposition Cc: green@FreeBSD.ORG (Brian F. Feldman), hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 12 Aug 1999 09:32:13 PDT." <199908121632.JAA26032@troutmask.apl.washington.edu> References: <199908121632.JAA26032@troutmask.apl.washington.edu> Date: Thu, 12 Aug 1999 10:43:18 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908121632.JAA26032@troutmask.apl.washington.edu> Steve Kargl writes: : If you're writing unencumbered code, placing it under : libcompat/gnu may lead to confusion because all other : directory paths containing gnu contain GPL'd code. : Just stick it into libcompat. Or libiberty :-) That way we can have a GPL-free libiberty, which would be something that many people would want. It would also force the FSF to move more of their code from GPL to LGPL since it is stallman's policy to release things under the LGPL when there are alternative interfaces available. Although the recent hacks by tchrist@perl.com to generically wrap any library in rcp calls so that the progrma using the library doesn't have any GPL tainted code compiled into its address space might change that.... I hate the GPL. It has too many different interpretations. Look at the currentsituation with Linux: Linus says loadable drivers in Linux aren't covered by the GPL, while Stallman insists that they are. Its interpretation is open to too many variables :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 9:53: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id E38D415856; Thu, 12 Aug 1999 09:52:54 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 4C18D1C09; Thu, 12 Aug 1999 11:54:48 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 4794B381F; Thu, 12 Aug 1999 11:54:48 -0400 (EDT) Date: Thu, 12 Aug 1999 11:54:48 -0400 (EDT) From: Bill Fumerola To: Warner Losh Cc: Steve Kargl , "Brian F. Feldman" , hackers@FreeBSD.ORG Subject: Re: libcompat proposition In-Reply-To: <199908121643.KAA04759@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Warner Losh wrote: > I hate the GPL. It has too many different interpretations. Look at > the currentsituation with Linux: Linus says loadable drivers in Linux > aren't covered by the GPL, while Stallman insists that they are. Its > interpretation is open to too many variables :-(. None of which by anyone with a law degree. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 9:57: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id D245314D00; Thu, 12 Aug 1999 09:57:01 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA26170; Thu, 12 Aug 1999 09:59:18 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199908121659.JAA26170@troutmask.apl.washington.edu> Subject: Re: libcompat proposition In-Reply-To: from "Brian F. Feldman" at "Aug 12, 1999 12:39:59 pm" To: green@FreeBSD.org (Brian F. Feldman) Date: Thu, 12 Aug 1999 09:59:18 -0700 (PDT) Cc: imp@village.org (Warner Losh), hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian F. Feldman wrote: > On Thu, 12 Aug 1999, Steve Kargl wrote: > > > > > If you're writing unencumbered code, placing it under > > libcompat/gnu may lead to confusion because all other > > directory paths containing gnu contain GPL'd code. > > Just stick it into libcompat. > > That doesn't fit with the current organization. > > Choose: > a. fsf > b. gnu > c. glibc d. other src/lib/libcompat/{fsf,gnu,glibc} connotes GPL code. src/lib/libcompat/other allows SysV, Solaris, Linux, etc. compatibility functions. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 11:22:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AEDFB1577D for ; Thu, 12 Aug 1999 11:22:17 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id OAA94347; Thu, 12 Aug 1999 14:21:11 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 12 Aug 1999 14:21:11 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Steve Kargl Cc: Warner Losh , hackers@FreeBSD.org Subject: Re: libcompat proposition In-Reply-To: <199908121659.JAA26170@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Steve Kargl wrote: > > > > That doesn't fit with the current organization. > > > > Choose: > > a. fsf > > b. gnu > > c. glibc > d. other > > src/lib/libcompat/{fsf,gnu,glibc} connotes GPL code. > > src/lib/libcompat/other allows SysV, Solaris, Linux, etc. > compatibility functions. I disagree with this. other is too generic. I don't care if most of the directories called "gnu" in the current tree contain GPLd code. How about contrib, which contains GPLd code too, but no gnu dir? It will be plainly obvious from the copyright I'd put at the beginning of any files in src/lib/libccompat/gnu that they're not under the GPL. There is simply no reason to assume that anything under a gnu directory is GPLd, or that anything GPLd is going to be under a gnu directory (which it's not.) > > -- > Steve > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Thu Aug 12 11:30:23 1999 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 9DF0715830; Thu, 12 Aug 1999 11:30:18 -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 MAA24248; Thu, 12 Aug 1999 12:30: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 MAA05156; Thu, 12 Aug 1999 12:30:20 -0600 (MDT) Message-Id: <199908121830.MAA05156@harmony.village.org> To: "Brian F. Feldman" Subject: Re: libcompat proposition Cc: Steve Kargl , hackers@FreeBSD.org In-reply-to: Your message of "Thu, 12 Aug 1999 14:21:11 EDT." References: Date: Thu, 12 Aug 1999 12:30:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Brian F. Feldman" writes: : There : is simply no reason to assume that anything under a gnu directory is GPLd, : or that anything GPLd is going to be under a gnu directory (which it's not.) I'm afraid there is. It has been stated many times in the past that all GPL'd software resides under gnu. This is true in the big (/usr/src/gnu) and in the small (src/sys/gnu). The gnu directory name is magic in the minds of many people, and has been for a long time in the FreeBSD project. While much of the actual software lives in /usr/contrib, those parts that are under GPL are still built in gnu/.... It is confusing, despite your assertions to the contrary. That's just how FreeBSD has operated for as long as I can recall, certainly back to the 1.0 time frame. glibc or fsf do not carry these long term connocations. To some they might connote gpl'd code, but they are better choices for naming in the libcompat tree since it doesn't have the traditionally overloaded "gnu" term plus tell what the code is compatible with (which is how the directories in libcompat work. Contrib doesn't have a separate gnu dir, but that is irrelevant. Nothing is built in the contrib tree. It is all built in usr.bin or usr.sbin or gnu/usr.bin, etc. All the GPL'd parts of the contrib tree are built under gnu/... (it is a bug if they are not). Using it to support a gnu directory would likely have negative impact on the strength of your argument. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 11:31:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D30F15830 for ; Thu, 12 Aug 1999 11:31:18 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [170.1.70.5]) by quack.kfu.com (8.9.2/8.8.5) with ESMTP id LAA35314 for ; Thu, 12 Aug 1999 11:31:28 -0700 (PDT) Received: (from nsayer@localhost) by medusa.kfu.com (8.9.2/8.8.8) id LAA55284; Thu, 12 Aug 1999 11:31:27 -0700 (PDT) (envelope-from nsayer) Date: Thu, 12 Aug 1999 11:31:27 -0700 (PDT) Message-Id: <199908121831.LAA55284@medusa.kfu.com> To: freebsd-hackers@freebsd.org From: Nick Sayer Subject: Whither makefiles for src/crypto/telnet/* ? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A long time ago I got some kinky modifications to telnet from a place in Germany the purpose of which was to encrypt telnet sessions. It did a Diffie-Hellman up front and used the common secret as a DES key sort of the way Kerberos does. It was called SRA telnet. It was vulnerable to monkey-in-the-middle, but it was better than nothing and unlike other encrypted session systems it had NO administrative overhead. I also added IDEA as an alternative encryption method just to sort of up the ante a bit. At one point I seem to remember that the cryto telnet sources sort of got combined inexorably with Kerberos, which made the idea of adding SRA in order to get a standalone encrypted telnet to be standard-issue sort of die. But today, just out of curiosity, I decided to see if it would be possible to resurrect the idea. In the scrypto section, I see that the telnet stuff is set aside nicely in its own spot. I was able to add my patches just fine, but it appears that the Makefiles are somewhere else. Maybe in with the kerberos stuff or something? Does anyone know how telnet actually gets built when you want a telnet/telnetd that uses encryption? I would once again like to add SRA to telnet/telnetd. There is something to be said for having something reasonably secure in the default (at least for the domestic audience) distribution. Yes, we can all go add the ssh port, but having an encrypted telnet work right out of the box is a good thing. So I can pretty easily turn this into something that can be added right into src/crypto/telnet, but I need to find out about the Makefile issue. Can anyone help? Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 11:36: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 47F3D15770; Thu, 12 Aug 1999 11:35:59 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA18257; Thu, 12 Aug 1999 12:33:28 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA05897; Thu, 12 Aug 1999 12:33:25 -0600 Date: Thu, 12 Aug 1999 12:33:25 -0600 Message-Id: <199908121833.MAA05897@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: "Brian F. Feldman" , Steve Kargl , hackers@FreeBSD.ORG Subject: Re: libcompat proposition In-Reply-To: <199908121830.MAA05156@harmony.village.org> References: <199908121830.MAA05156@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : There > : is simply no reason to assume that anything under a gnu directory is GPLd, > : or that anything GPLd is going to be under a gnu directory (which it's not.) > > I'm afraid there is. It has been stated many times in the past that > all GPL'd software resides under gnu. This is true in the big > (/usr/src/gnu) and in the small (src/sys/gnu). The gnu directory name > is magic in the minds of many people, and has been for a long time in > the FreeBSD project. While much of the actual software lives in > /usr/contrib, those parts that are under GPL are still built in > gnu/.... It is confusing, despite your assertions to the contrary. > That's just how FreeBSD has operated for as long as I can recall, > certainly back to the 1.0 time frame. This decision was made before *any* releases were made, and should continue. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 11:37:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8854D14DB9 for ; Thu, 12 Aug 1999 11:37:20 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA71681 for ; Thu, 12 Aug 1999 14:37:30 -0400 (EDT) Message-Id: <199908121837.OAA71681@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working] Date: Thu, 12 Aug 1999 14:37:30 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The problem I am having is that the keyboard works all the way up to sysinstall. I can use the keyboard in the visual kernel config/etc. I searched and found under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't documented to do anything uner 3/4 but I tried anyway, nothing. I also noticed that flags 0x04 and 0x02 may be some use (on atkbc). I tried 0x4, 0x2, and 0x6 to no avail. help? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 12:56: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 7E27D15859; Thu, 12 Aug 1999 12:55:50 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id OAA33714; Thu, 12 Aug 1999 14:33:34 -0400 (EDT) Date: Thu, 12 Aug 1999 14:33:34 -0400 (EDT) From: Ben Rosengart To: Steve Kargl Cc: "Brian F. Feldman" , Warner Losh , hackers@FreeBSD.ORG Subject: Re: libcompat proposition In-Reply-To: <199908121632.JAA26032@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Steve Kargl wrote: > Brian F. Feldman wrote: > > If you're writing unencumbered code, placing it under > libcompat/gnu may lead to confusion because all other > directory paths containing gnu contain GPL'd code. > Just stick it into libcompat. How about libcompat/gnuish? (Funny, it doesn't look gnuish.) -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 13:22:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D6FAD14C83 for ; Thu, 12 Aug 1999 13:22:18 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA73483; Thu, 12 Aug 1999 16:21:49 -0400 (EDT) Message-Id: <199908122021.QAA73483@cs.rpi.edu> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working] In-Reply-To: Message from "David E. Cross" of "Thu, 12 Aug 1999 14:37:30 EDT." <199908121837.OAA71681@cs.rpi.edu> Date: Thu, 12 Aug 1999 16:18:04 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The > problem I am having is that the keyboard works all the way up to sysinstall. > I can use the keyboard in the visual kernel config/etc. I searched and found > under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't documented > to do anything uner 3/4 but I tried anyway, nothing. I also noticed that > flags 0x04 and 0x02 may be some use (on atkbc). I tried 0x4, 0x2, and 0x6 to > no avail. help? Here are some additional details... I tried the 2.2.8-RELEASE install with the flags of '0x10' on sc0. That worked OK. I dug through the CVS repo and I have discovered that those are the XT keyboard options (flags 0x04 on atkbd). so I went into the CLI config on the 3.2-STABLE bootdisk at turned those flags on BOTH atkdb0 at atkbdc0 (just in case), still no luck. I have looked at the source for 2.2 syscons and 3.2 atkbd and I can not see what the difference is in the codeset initialization and keyboard translation for the 2 types. I would like to try 3.0-RELEASE, but I cannot find anything that old ;) Suggestions? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14: 1:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from officemail.starmedia.com (officemail.starmedia.net [208.133.204.60]) by hub.freebsd.org (Postfix) with ESMTP id 9E2AB14CAB; Thu, 12 Aug 1999 14:01:42 -0700 (PDT) (envelope-from mannsber@starmedia.net) Received: from starmedia.net ([209.185.179.134]) by officemail.starmedia.com (8.8.8/8.8.8) with ESMTP id PAA04598; Thu, 12 Aug 1999 15:08:52 -0400 (EDT) (envelope-from mannsber@starmedia.net) Message-ID: <37B31C67.FF7ACC92@starmedia.net> Date: Thu, 12 Aug 1999 15:11:35 -0400 From: Michael Mannsberger X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: hey Content-Type: multipart/alternative; boundary="------------E5E15A77EF5094F3D1C4D886" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------E5E15A77EF5094F3D1C4D886 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit a problem somebody had >>>>>> ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? FreeBSD doesn't like "_" in a URL!!!!!!!! bash-2.02$ ping www.atayatirim.com.tr ping: cannot resolve www.atayatirim.com.tr: Unknown server error bash-2.02$ nslookup www.atayatirim.com.tr Server: ns3.starmedia.com Address: 209.67.42.5 Non-authoritative answer: Name: ata_www_prm.atayatirim.com.tr <<<<<<<<<<<<<<<<<<<<<<<< Address: 195.174.236.9 Aliases: www.atayatirim.com.tr -mike --------------E5E15A77EF5094F3D1C4D886 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit a problem somebody had >>>>>>

ping  www.atayatirim.com.tr works under Sun but not in FreeBSD - why?
FreeBSD doesn't like "_" in a URL!!!!!!!!
 

bash-2.02$ ping www.atayatirim.com.tr
ping: cannot resolve www.atayatirim.com.tr: Unknown server error
 

bash-2.02$ nslookup www.atayatirim.com.tr
Server:  ns3.starmedia.com
Address:  209.67.42.5

Non-authoritative answer:
Name:    ata_www_prm.atayatirim.com.tr                          <<<<<<<<<<<<<<<<<<<<<<<<
Address:  195.174.236.9
Aliases:  www.atayatirim.com.tr

-mike --------------E5E15A77EF5094F3D1C4D886-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14: 8:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from swbell.net (mail-gw2.rcsntx.swbell.net [151.164.30.52]) by hub.freebsd.org (Postfix) with ESMTP id 023611589B; Thu, 12 Aug 1999 14:08:43 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (adsl-216-62-154-215.dsl.hstntx.swbell.net [216.62.154.215]) by swbell.net (8.9.3/8.9.3) with ESMTP id QAA21667; Thu, 12 Aug 1999 16:08:25 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA26568; Thu, 12 Aug 1999 16:10:14 -0500 (CDT) (envelope-from chris) Date: Thu, 12 Aug 1999 16:10:14 -0500 From: Chris Costello To: Michael Mannsberger Cc: freebsd-questions@FreeBSD.ORG Subject: Re: hey Message-ID: <19990812161014.B24489@holly.dyndns.org> Reply-To: chris@calldei.com References: <37B31C67.FF7ACC92@starmedia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <37B31C67.FF7ACC92@starmedia.net>; from Michael Mannsberger on Thu, Aug 12, 1999 at 03:11:35PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [followups set to -questions only] On Thu, Aug 12, 1999, Michael Mannsberger wrote: > a problem somebody had >>>>>> > > ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? > FreeBSD doesn't like "_" in a URL!!!!!!!! a. www.atayatirim.com.tr is not a URL, it's a hostname. b. According to your nslookup response, www.atayatirim.com is an alias for ata_www_prm.atayatirim.com.tr -- `_' is not a valid DNS character. Please contact the site's DNS administrator and ask that he or she fix the error. -- |Chris Costello |Base 8 is just like base 10, if you are missing two fingers. - Tom Lehrer `-------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14:10:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 03597158DD; Thu, 12 Aug 1999 14:09:58 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.2/8.9.2) with ESMTP id RAA06064; Thu, 12 Aug 1999 17:16:43 -0400 (EDT) Date: Thu, 12 Aug 1999 17:16:43 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Michael Mannsberger Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: hey In-Reply-To: <37B31C67.FF7ACC92@starmedia.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 That's because the resolver on the Sun box is archaic, whereas FreeBSD has an up-to-date (and legal) resolver. Can't remember which RFC defined the '_' as being illegal off-hand...but all modern resolvers will react the same. That site admin must be running an old implementation of BIND (or possibly NT!). -marc ---------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Thu, 12 Aug 1999, Michael Mannsberger wrote: > a problem somebody had >>>>>> > > ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? > FreeBSD doesn't like "_" in a URL!!!!!!!! > > > bash-2.02$ ping www.atayatirim.com.tr > ping: cannot resolve www.atayatirim.com.tr: Unknown server error > > > bash-2.02$ nslookup www.atayatirim.com.tr > Server: ns3.starmedia.com > Address: 209.67.42.5 > > Non-authoritative answer: > Name: ata_www_prm.atayatirim.com.tr > <<<<<<<<<<<<<<<<<<<<<<<< > Address: 195.174.236.9 > Aliases: www.atayatirim.com.tr > > -mike > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14:14:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 9A18F1589B; Thu, 12 Aug 1999 14:14:09 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A18F51C09; Thu, 12 Aug 1999 16:15:51 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 9E5363820; Thu, 12 Aug 1999 16:15:51 -0400 (EDT) Date: Thu, 12 Aug 1999 16:15:51 -0400 (EDT) From: Bill Fumerola To: Michael Mannsberger Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: hey In-Reply-To: <37B31C67.FF7ACC92@starmedia.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, 12 Aug 1999, Michael Mannsberger wrote: > ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? > FreeBSD doesn't like "_" in a URL!!!!!!!! Uhm, that's a hostname, but yes, FreeBSD doesn't like it. Windows is okay with it, however. http://www.crynwr.com/crynwr/rfc1035/rfc1035.html#2.3.1. However explains why this hostname is not allowed. FreeBSD is not violating RFC. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - hawk% ping wam_notes.internal.chc-chimes.com ping: cannot resolve wam_notes.internal.chc-chimes.com: Unknown server error hawk% dig wam_notes.internal.chc-chimes.com |grep notes ; <<>> DiG 8.1 <<>> wam_notes.internal.chc-chimes.com ;; wam_notes.internal.chc-chimes.com, type = A, class = IN wam_notes.internal.chc-chimes.com. 1D IN CNAME notes.internal.chc-chimes.com. notes.internal.chc-chimes.com. 1D IN A 172.16.81.245 It should be noted that the dns server that my workstation queried is running FreeBSD and has no trouble _serving_ hostnames with an underscore. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14:26:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from balsam.methow.com (balsam.methow.com [206.107.156.5]) by hub.freebsd.org (Postfix) with SMTP id 041C714D6D for ; Thu, 12 Aug 1999 14:26:28 -0700 (PDT) (envelope-from tcole@balsam.methow.com) Received: (qmail 4199 invoked by uid 535); 12 Aug 1999 21:26:31 -0000 Message-ID: <19990812142630.A4093@wcug.wwu.edu> Date: Thu, 12 Aug 1999 14:26:30 -0700 From: Travis Cole To: Nick Sayer , freebsd-hackers@freebsd.org Subject: Re: Whither makefiles for src/crypto/telnet/* ? References: <199908121831.LAA55284@medusa.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199908121831.LAA55284@medusa.kfu.com>; from Nick Sayer on Thu, Aug 12, 1999 at 11:31:27AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 12, 1999 at 11:31:27AM -0700, Nick Sayer wrote: > > In the scrypto section, I see that the telnet stuff is set aside > nicely in its own spot. I was able to add my patches just fine, > but it appears that the Makefiles are somewhere else. Maybe in > with the kerberos stuff or something? Does anyone know how telnet > actually gets built when you want a telnet/telnetd that uses > encryption? Just a me too. I would really like to know how this is doen also. -- --Travis When it comes to violence, morality and the young, we're the Idiot Nation, the laughingstock not only of the civilized world but of the highly-wired generation of kids we're supposedly trying to protect. Jon Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 14:27: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 3576D14C97 for ; Thu, 12 Aug 1999 14:26:49 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox.bogus.net (ell74.acadia.net [205.217.218.58]) by p2.acadia.net (8.9.1/8.9.1) with ESMTP id RAA23246 for ; Thu, 12 Aug 1999 17:26:41 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox.bogus.net (8.9.3/8.9.3) id RAA02152; Thu, 12 Aug 1999 17:25:05 -0400 (EDT) (envelope-from tbuswell) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 12 Aug 1999 17:25:05 -0400 (EDT) To: hackers@freebsd.org Subject: interacting with ISA PnP devices. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14259.14514.212606.703642@localhost.bogus.net> From: tbuswell@acadia.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What is the path of least resistance for getting an unsupported ISA PnP device to the point where you can do I/O to it (inb,outb)? Do I need a driver, or is there some general purpose way for getting the device "up" to the point that you can use /dev/io and a user space application? (on -current) If I need to write a driver, would a device driver that just maps the device be considered useful (feasible to implement?)? This specific device is a "winmodem" which I believe I have enough hardware documentation to fiddle with, once I get past the ISA PnP interface. Thanks, -Ted (ISA PnP newbie) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 12 15: 0:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ds9.sci.fi (ds9.sci.fi [195.74.0.54]) by hub.freebsd.org (Postfix) with ESMTP id 8609214D17 for ; Thu, 12 Aug 1999 15:00:31 -0700 (PDT) (envelope-from yurtesen@ispro.net.tr) Received: from ispro.net.tr (dyn-3-166.tku.netti.fi [195.16.220.167]) by ds9.sci.fi (8.9.1/8.9.1) with ESMTP id AAA27056; Fri, 13 Aug 1999 00:59:32 +0300 (EET DST) Message-ID: <37B343A8.A94CD343@ispro.net.tr> Date: Fri, 13 Aug 1999 00:59:04 +0300 From: Evren Yurtesen X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: Michael Mannsberger , freebsd-hackers@FreeBSD.ORG Subject: Re:(2) hey References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I am the person who has this problem. The RFCs does not explicitly say that we should not use underscore character as far as I understood. But it suggests which characters we should use. Also in RFC1033 it says (well the status of this one is UNKNOWN though) ----------------------------------------------------------------------------- The domain system allows a label to contain any 8-bit character. Although the domain system has no restrictions, other protocols such as SMTP do have name restrictions. Because of other protocol restrictions, only the following characters are recommended for use in a host name (besides the dot separator): "A-Z", "a-z", "0-9", dash and underscore ----------------------------------------------------------------------------- So Solaris does the right thing by understanding underscore I guess. Since it is not forbidden to use it in hostnames. http://www.crynwr.com/crynwr/rfc1035/rfc1035.html#2.3.1. ----------------------------------------------------------------------------- For example, when naming a mail domain, the user should satisfy both the rules of this memo and those in RFC-822. When creating a new host name, the old rules for HOSTS.TXT should be followed. This avoids problems when old software is converted to use domain names. The following syntax will result in fewer problems with many applications that use domain names (e.g., mail, TELNET). ::= | " " ::=