From owner-freebsd-hackers Sun Mar 19 2:24:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id B3B6437B6F2 for ; Sun, 19 Mar 2000 02:24:39 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 67F192DC07; Sun, 19 Mar 2000 11:29:00 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 7F8E17811; Sun, 19 Mar 2000 11:22:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 7A7C510E17; Sun, 19 Mar 2000 11:22:44 +0100 (CET) Date: Sun, 19 Mar 2000 11:22:44 +0100 (CET) From: Andrzej Bialecki To: Alfred Perlstein Cc: "Matthew N. Dodd" , "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG Subject: Re: How to read a file from a device driver? In-Reply-To: <20000317212751.F14789@fw.wintelcom.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 Fri, 17 Mar 2000, Alfred Perlstein wrote: > * Matthew N. Dodd [000317 21:22] wrote: > > On Fri, 17 Mar 2000, Gary T. Corcoran wrote: > > > I'm trying to initialize a network device, and I'm trying to download > > > code *into* my device from some binary system files. There is no > > > "user space" or user process, for that matter, to deal with at this > > > point. I just want to (at this step) open a file(s) directly from my > > > device driver, read the file(s), and download the relevant parts to my > > > device. > > > > There isn't really any clean way of doing this so most drivers that need > > to load firmware usually compile them in. :/ > > Now that I think about it, with FreeBSD's ability to dynamically load > and unload modules it would seem like using anything else would be > pretty annoying unless there's something else we don't understand here. I think if you combine the ability to load arbitrary chunks of data (from within bootloader) as modules, with similar auto-loading as in the vfs case, you'll have a good solution. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 19 4:57:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nscache2.x-treme.gr (mail1.x-treme.gr [212.120.196.23]) by hub.freebsd.org (Postfix) with ESMTP id A3B3D37B5C0 for ; Sun, 19 Mar 2000 04:57:04 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (pat16.x-treme.gr [212.120.197.208]) by nscache2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with ESMTP id OAA22120; Sun, 19 Mar 2000 14:56:55 +0200 Received: (from charon@localhost) by hades.hell.gr (8.9.3/8.9.3) id LAA59269; Sun, 19 Mar 2000 11:24:39 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 Mar 2000 11:24:38 +0200 From: Giorgos Keramidas To: Micke Cc: hackers@FreeBSD.ORG Subject: Re: swap Message-ID: <20000319112438.A55921@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <000701bf9136$252e0e20$0201a0c0@micke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000701bf9136$252e0e20$0201a0c0@micke>; from micke@swebase.com on Sun, Mar 19, 2000 at 01:00:31AM +0100 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 19, 2000 at 01:00:31AM +0100, Micke wrote: > How do i check the status of my new swap it isn't showing in top or in > pstat -s > > I have done the following > > cd /dev sh ./MAKEDEV vn0 > > create a swapfile (/usr/swap0) > > dd if=/dev/zero of=/usr/swap0 bs=1024k count=64 > > set proper permissions on (/usr/swap0) > > chmod 0600 /usr/swap0 > > enable the swap file in /etc/rc.conf > > swapfile="/usr/swap0" # Set to name of swapfile ... Uhm, you should have vnodes enabled into your kernel, because the commands executed by the /etc/rc script, when swapfile is set to something not null, are: vnconfig /dev/vn0b ${swapfile} && swapon /dev/vn0b I'll have a look at the Handbook and see if it mentions vnconfig at the proper section, and let the -doc guys know about it if it's necessary. - Giorgos Keramidas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 19 15:56:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 13B0037B810 for ; Sun, 19 Mar 2000 15:56:47 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id AAA00638; Mon, 20 Mar 2000 00:56:44 +0100 (CET) (envelope-from assar) To: Robert Watson Cc: Mourad Lakhdar <992C396651@stud.alakhawayn.ma>, freebsd-hackers@FreeBSD.ORG Subject: Re: need help References: From: Assar Westerlund Date: 20 Mar 2000 00:56:44 +0100 In-Reply-To: Robert Watson's message of "Sat, 18 Mar 2000 22:23:56 -0500 (EST)" Message-ID: <5ld7oqldj7.fsf@assaris.sics.se> Lines: 9 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson writes: > with the advent of IPv6, I'm not sure what the approved mechanism > is. int inet_pton(int af, const char *src, void *dst); See rfc2553. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 8: 6:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3778437B819 for ; Mon, 20 Mar 2000 08:06:07 -0800 (PST) (envelope-from anderson@cs.duke.edu) Received: from cold.cs.duke.edu (cold.cs.duke.edu [152.3.140.78]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA22873; Mon, 20 Mar 2000 11:06:05 -0500 (EST) From: Darrell Anderson Received: (anderson@localhost) by cold.cs.duke.edu (8.8.5/8.6.9) id LAA12793; Mon, 20 Mar 2000 11:06:05 -0500 (EST) Message-Id: <200003201606.LAA12793@cold.cs.duke.edu> Subject: Re: How to read a file from a device driver? To: garycor@home.com Date: Mon, 20 Mar 2000 11:06:05 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Mar 2000, Gary T. Corcoran wrote: > > I'm trying to initialize a network device, and I'm trying to download > code *into* my device from some binary system files. There is no "user > space" or user process, for that matter, to deal with at this point. I > just want to (at this step) open a file(s) directly from my device > driver, read the file(s), and download the relevant parts to my device. sysctl might also do the trick. to answer your question, here's some code: struct vnode * vp_open(char *fname) { struct vnode *vp; struct nameidata nd; int error; NDINIT(&nd, LOOKUP, FOLLOW, UIO_SYSSPACE, fname, curproc); if ((error = vn_open(&nd, FREAD|FWRITE|O_CREAT, S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH)) != 0) { printf("vp_open: failed for %s with error %d\n", fname, error); return NULL; } vp = nd.ni_vp; NDFREE(&nd, NDF_ONLY_PNBUF); VOP_UNLOCK(vp, 0, curproc); if (vp->v_type != VREG) { printf("vp_open: %s not a regular file\n", fname); vn_close(vp, FREAD|FWRITE, curproc->p_ucred, curproc); return NULL; } return vp; } int vp_close(struct vnode *vp) { int error; if (vp == NULL) { printf("vp_close: caller supplied NULL vp\n"); return ENOENT; } if ((error = vn_close(vp, FREAD|FWRITE, curproc->p_ucred, curproc)) { printf("vp_close: vn_close error %d\n", error); } return error; } int vp_read(struct vnode *vp, off_t offset, int len, caddr_t data) { struct iovec iov; struct uio uio; int error; iov.iov_base = data; iov.iov_len = len; uio.uio_iov = &iov; uio.uio_iovcnt = 1; uio.uio_offset = offset; uio.uio_resid = iov.iov_len; uio.uio_segflg = UIO_SYSSPACE; uio.uio_rw = UIO_READ; uio.uio_procp = NULL; if ((error = vn_lock(vp, LK_SHARED|LK_RETRY, curproc)) == 0) { error = VOP_READ(vp, &uio, IO_SYNC, curproc->p_ucred); VOP_UNLOCK(vp, 0, curproc); if (uio.uio_resid) { bzero(data + (len - uio.uio_resid), uio.uio_resid); } } return error; } -Darrell -- Department of Computer Science, Duke University, Durham, NC 27708-0129 Darrell Anderson, anderson@cs.duke.edu, http://www.cs.duke.edu/~anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 9: 1:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C40E537B92E for ; Mon, 20 Mar 2000 09:01:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA19537; Mon, 20 Mar 2000 18:01:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: splFoo() question In-reply-to: Your message of "Sat, 18 Mar 2000 13:31:28 MST." <200003182031.NAA97975@harmony.village.org> Date: Mon, 20 Mar 2000 18:01:23 +0100 Message-ID: <19535.953571683@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003182031.NAA97975@harmony.village.org>, Warner Losh writes: >I'd like to be able to do some simple spl locking in a driver that I'm >writing. While I could go the splhigh() route, I'm concerned that >spending lots of time at splhigh could cause problems, and some of my >critical sections look to be very expensive. They only need >protection against the card itself, not against the entire system. It >just seems to be an overly large hammer. I miss this too. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 10:53:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 492F437B92C; Mon, 20 Mar 2000 10:49:48 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com ([216.88.157.130]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id FAA12887; Tue, 21 Mar 2000 05:16:43 +1030 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id LAA01974; Fri, 17 Mar 2000 11:53:53 -0800 (PST) (envelope-from grog) Date: Fri, 17 Mar 2000 11:53:53 -0800 From: Greg Lehey To: Rafael Gomez Cc: FreeBSD Questions Subject: Re: kERNEL Message-ID: <20000317115353.E1773@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from rgomez@c-com.net.ve on Fri, Mar 17, 2000 at 09:09:41AM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to FreeBSD-questions -- *again* ] On Friday, 17 March 2000 at 9:09:41 -0400, Rafael Gomez wrote: > Can any of you send me a copy of a text kernel file? This is the second time you've sent a message which we can't understand to FreeBSD-hackers. The first time I told you to post to FreeBSD-questions, not FreeBSD-hackers, and asked some questions which you didn't answer. If you want help, please do your part. Otherwise you'll find that people ignore you. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 11: 5:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 7855637C2B4 for ; Mon, 20 Mar 2000 11:05:50 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B4B051E00A; Mon, 20 Mar 2000 14:05:38 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA00178; Mon, 20 Mar 2000 14:05:38 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id LAA01936; Mon, 20 Mar 2000 11:04:55 -0800 (PST) Message-Id: <200003201904.LAA01936@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: newton@internode.com.au Subject: Re: WaveLAN/IEEE Turbo (Silver) Cc: freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 11:04:54 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I know the WaveLAN stuff is crap Actually, I've had terrific luck with WaveLAN IEEE stuff on laptops for the last year or so. I'm not sure what's so bad about it?... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 11:47: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3101.mail.yahoo.com (web3101.mail.yahoo.com [204.71.202.186]) by hub.freebsd.org (Postfix) with SMTP id 7029A37B96F for ; Mon, 20 Mar 2000 11:47:03 -0800 (PST) (envelope-from mike_bsdlists@yahoo.com) Message-ID: <20000320194702.11223.qmail@web3101.mail.yahoo.com> Received: from [206.85.234.111] by web3101.mail.yahoo.com; Mon, 20 Mar 2000 11:47:02 PST Date: Mon, 20 Mar 2000 11:47:02 -0800 (PST) From: MikeM Subject: Unicode on FreeBSD To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone thought of Unicode support on FreeBSD? I think that it is inevitable that eventually FreeBSD will *need* to support unicode if it wants to continue as a viable operating system in the future. This means that it probably will need to be modified from the ground up. I am not well versed in the specifics of what's needed, but if someone could explain it to me I'd be gratefull. Is it possible, or is it totally out of the question? What would it require? Is there any way of implementing partial support, working in stages, untill it is fully supported? Thanks, Mike. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 12: 0:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 177DF37B8B8 for ; Mon, 20 Mar 2000 12:00:11 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id CE284A85A; Mon, 20 Mar 2000 21:00:08 +0100 (CET) Date: Mon, 20 Mar 2000 21:00:08 +0100 From: Guido van Rooij To: Warner Losh Cc: hackers@freebsd.org Subject: Re: splFoo() question Message-ID: <20000320210008.A59405@gvr.gvr.org> References: <200003182031.NAA97975@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200003182031.NAA97975@harmony.village.org>; from Warner Losh on Sat, Mar 18, 2000 at 01:31:28PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 18, 2000 at 01:31:28PM -0700, Warner Losh wrote: > > I'd like to be able to do some simple spl locking in a driver that I'm > writing. While I could go the splhigh() route, I'm concerned that > spending lots of time at splhigh could cause problems, and some of my > critical sections look to be very expensive. They only need > protection against the card itself, not against the entire system. It > just seems to be an overly large hammer. > perhaps we need some mutex mechanism? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 12: 1:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id B9C6737BA21 for ; Mon, 20 Mar 2000 12:00:51 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA25217; Mon, 20 Mar 2000 13:00:32 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA27867; Mon, 20 Mar 2000 13:00:31 -0700 (MST) (envelope-from nate) Date: Mon, 20 Mar 2000 13:00:31 -0700 (MST) Message-Id: <200003202000.NAA27867@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bill Fenner Cc: newton@internode.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: WaveLAN/IEEE Turbo (Silver) In-Reply-To: <200003201904.LAA01936@windsor.research.att.com> References: <200003201904.LAA01936@windsor.research.att.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I know the WaveLAN stuff is crap > > Actually, I've had terrific luck with WaveLAN IEEE stuff on laptops > for the last year or so. I'm not sure what's so bad about it?... Agreed. WaveLAN hardware is good stuff. We deployed 200+ users in a network, and aside from the normal problems associated with wireless communications, it worked quite well. Highly recommended... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 12:46:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id CAE3837CC26; Mon, 20 Mar 2000 12:22:04 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id KAA10576; Mon, 20 Mar 2000 10:43:58 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003202043.KAA10576@mauibuilt.com> Subject: 4.0 using dd and cdroms To: freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 10:43:57 -1000 (HST) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have tried using dd on serveral 4.0 systems in order to capture an image off a cdrom. I tried dd if=/dev/acd0a of=file.img as well as on a scsi system (/dev/cd0a) and eovery other cd device (/dev/acd0c /cdv/racd0c /dev/cd0c ect) and I get dd: /dev/acd0a Bad address 0+0 records in 0+0 records out 0 bytes transferd yada yada yada I have tried to remake the devices to to no avail. Another strange thing is that on one of the systems with an atapi cdrom when doing the dd it started the drive spinning and the drive never stoped unil I pressed the eject button. I am not sure if this is a problem with dd or what.. Just thought I'd put this out there.. Thanks for any reply RP puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 13:20:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5F6C237C44F for ; Mon, 20 Mar 2000 12:57:18 -0800 (PST) (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 NAA19482; Mon, 20 Mar 2000 13:57:13 -0700 (MST) (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 NAA17486; Mon, 20 Mar 2000 13:57:03 -0700 (MST) Message-Id: <200003202057.NAA17486@harmony.village.org> To: Guido van Rooij Subject: Re: splFoo() question Cc: hackers@freebsd.org In-reply-to: Your message of "Mon, 20 Mar 2000 21:00:08 +0100." <20000320210008.A59405@gvr.gvr.org> References: <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> Date: Mon, 20 Mar 2000 13:57:03 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000320210008.A59405@gvr.gvr.org> Guido van Rooij writes: : perhaps we need some mutex mechanism? Yes. Right now the mutex mechanism that we have is blocking of interrupts when the bit is set in the cpl. I guess I'm a little too close to the mechanism and need to step back. You are right that I'm asking for a call that is approximately "block my interrupt handler from running until I say it is ok." A more generalized mutex/locking scheme is needed so that I can just grab a mutex in my code and in my ISR and the right thing will just happen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 13:44:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 84E6A37B952; Mon, 20 Mar 2000 13:44:51 -0800 (PST) (envelope-from dave@elvis.mu.org) Received: (from dave@localhost) by elvis.mu.org (8.9.1/8.9.1) id PAA63798; Mon, 20 Mar 2000 15:46:14 -0600 (CST) (envelope-from dave) Date: Mon, 20 Mar 2000 15:46:14 -0600 From: Dave McKay To: freebsd-security@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: ports security advisories.. Message-ID: <20000320154614.A63670@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Is it really necessary to post the ports security advisories? The exploitable programs are not part of the FreeBSD OS, they are third party software. I think the proper place for these is the Bugtraq mailing list on securityfocus.com. Also to add to the arguments, most of the advisories are not FreeBSD specific. --=20 Dave McKay Network Engineer - Google Inc. dave@mu.org - dave@google.com I'm feeling lucky... --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBONacJXY8vP7IQ1TlAQEjwgQAlTj79musTFaLJOmfDAGRot4nvUqB70vz rjHSEEIFKBQNOajTLgWgDC59vLTnTJuOnliOVeRH8e2iHLN8MdqTldvq5GeGI6k5 7sY9iOmb2u9/mfl9Yf0o5zFdZrBfzSvoozB+bQygQohMRmFgeVXsBi+27vW39IXc Fm7z3dPNLAc= =vMIo -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 13:53: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 1Cust60.tnt4.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A96B37BF66; Mon, 20 Mar 2000 13:52:52 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 20 Mar 2000 16:52:47 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: FreeBSD MAIL Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: 4.0 using dd and cdroms In-Reply-To: <200003202043.KAA10576@mauibuilt.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 Don't post to multiple lists; it's rude. I'll reply to both so others on -hackers won't think noone replied and reply, too. On Mon, 20 Mar 2000, FreeBSD MAIL wrote: > I have tried using dd on serveral 4.0 systems in order to capture an image off a cdrom. > > I tried dd if=/dev/acd0a of=file.img as well as on a scsi system (/dev/cd0a) and > eovery other cd device (/dev/acd0c /cdv/racd0c /dev/cd0c ect) and I get > > dd: /dev/acd0a Bad address > 0+0 records in > 0+0 records out Mode 1 CD-ROM DATA is 2352 bytes of data and ECC per block. The actual data returned from the drive is 2048 bytes, so each block is effectively 2048 bytes. Use ibs=2k or a multiple thereof. I've made a utility that does a nice job for CD duplication needs (the reading half), which you can find at: http://people.FreeBSD.org/~green/read_cd.tar.gz MD5 (read_cd.tar.gz) = 7881ea5ef1428ced7533b1cb2a3afbb1 > Thanks for any reply HTH > RP > puga@mauibuilt.com -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Mar 20 13:57:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tandem.milestonerdl.com (tandem.milestonerdl.com [204.107.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 8905537BA14; Mon, 20 Mar 2000 13:56:52 -0800 (PST) (envelope-from marc@milestonerdl.com) Received: from tandem.milestonerdl.com (tandem.milestonerdl.com [204.107.138.1]) by tandem.milestonerdl.com (8.10.0/8.10.0) with ESMTP id e2KLtDQ03532; Mon, 20 Mar 2000 15:55:13 -0600 (CST) Date: Mon, 20 Mar 2000 15:55:12 -0600 (CST) From: Marc Rassbach To: Dave McKay Cc: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ports security advisories.. In-Reply-To: <20000320154614.A63670@elvis.mu.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 Is it necessary to post ports security advisories? YES. Should they be on this list? You think not. And until a list exists for security on FreeBSD not related to core OS/packages, this is the best forum for it, as it relates to FreeBSD Security. On Mon, 20 Mar 2000, Dave McKay wrote: > Is it really necessary to post the ports security advisories? > The exploitable programs are not part of the FreeBSD OS, they > are third party software. I think the proper place for these > is the Bugtraq mailing list on securityfocus.com. Also to add > to the arguments, most of the advisories are not FreeBSD > specific. > > -- > Dave McKay > Network Engineer - Google Inc. > dave@mu.org - dave@google.com > I'm feeling lucky... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 14:21:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brain.proaxis.com (brain.proaxis.com [206.163.142.1]) by hub.freebsd.org (Postfix) with ESMTP id 4FB2F37B8B8; Mon, 20 Mar 2000 14:21:06 -0800 (PST) (envelope-from cdinsmore@vatyx.com) Received: from proxyserver (pd02-56.inet-x.net [206.163.153.120]) by brain.proaxis.com (8.9.3/8.9.3) with SMTP id OAA06343; Mon, 20 Mar 2000 14:20:54 -0800 (PST) Received: by proxyserver (VPOP3) with SMTP; Mon, 20 Mar 2000 14:25:20 -0800 Received: by SERVER with Internet Mail Service (5.0.1457.3)id ; Mon, 20 Mar 2000 14:24:51 -0800 Message-ID: From: Casey Dinsmore To: Dave McKay , freebsd-security@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: ports security advisories.. Date: Mon, 20 Mar 2000 14:24:48 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain X-Server: VPOP3 V1.2.0d - Registered to: Vatyx, Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that it is a necessary thing to do, since these programs are offered in the ports collection, and this is -security after all. It was nice and convienant to have the advisories posted because I just happened to have completed installing lynx-ssl from the ports collection mere hours before they were posted on wednesday. Casey Dinsmore Webmaster / Network Administrator Vatyx, Inc. cdinsmore@vatyx.com http://www.vatyx.com Phone: 541.929.6496 Fax: 541.929.2251 > -----Original Message----- > From: Dave McKay [SMTP:dave@mu.org] > Sent: Monday, March 20, 2000 1:46 PM > To: freebsd-security@FreeBSD.ORG > Cc: freebsd-hackers@FreeBSD.ORG > Subject: ports security advisories.. > > Is it really necessary to post the ports security advisories? > The exploitable programs are not part of the FreeBSD OS, they > are third party software. I think the proper place for these > is the Bugtraq mailing list on securityfocus.com. Also to add > to the arguments, most of the advisories are not FreeBSD > specific. > > -- > Dave McKay > Network Engineer - Google Inc. > dave@mu.org - dave@google.com > I'm feeling lucky... << File: ATT00142.ATT >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 14:34:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from stud.alakhawayn.ma (stud.alakhawayn.ma [193.194.63.94]) by hub.freebsd.org (Postfix) with ESMTP id 6715737BA44 for ; Mon, 20 Mar 2000 14:34:18 -0800 (PST) (envelope-from 992C396651@stud.alakhawayn.ma) Received: from localhost (992C396651@localhost) by stud.alakhawayn.ma (8.9.0/8.9.0) with SMTP id WAA03988 for ; Mon, 20 Mar 2000 22:33:28 GMT Date: Mon, 20 Mar 2000 22:33:28 +0000 (GMT) From: Mourad Lakhdar <992C396651@stud.alakhawayn.ma> To: freebsd-hackers@FreeBSD.org Subject: need help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi every body: when i change in the kernel , i config it , made : make depend while doing >make i got the error : /var : write failed , file system is full cpp: /var/tmp/ccT1684.i:No space left on device error code 1 stop so what should i do best regards, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 15:15:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 0CCC937BB5A; Mon, 20 Mar 2000 15:15:31 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B5AB41CC9; Mon, 20 Mar 2000 23:15:28 -0800 (PST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dave McKay Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: ports security advisories.. In-Reply-To: Message from Dave McKay of "Mon, 20 Mar 2000 15:46:14 CST." <20000320154614.A63670@elvis.mu.org> Date: Mon, 20 Mar 2000 23:15:28 -0800 From: Peter Wemm Message-Id: <20000321071528.B5AB41CC9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave McKay wrote: > Is it really necessary to post the ports security advisories? > The exploitable programs are not part of the FreeBSD OS, they > are third party software. I think the proper place for these > is the Bugtraq mailing list on securityfocus.com. Also to add > to the arguments, most of the advisories are not FreeBSD > specific. Sadly yes, it seems it is. If we get in first, we get to remind people that it's not a standard part of FreeBSD etc. Otherwise people post on bugtraq "security hole in FreeBSD, no public response after a week" style things which do not look good at all. Doing it this way is a bit irritiating but is the least evil of the alternatives. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 15:24:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id A64E337BBDC for ; Mon, 20 Mar 2000 15:24:14 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id QAA04450; Mon, 20 Mar 2000 16:23:56 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D6B353.FA58BB15@softweyr.com> Date: Mon, 20 Mar 2000 16:25:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: splFoo() question References: <19535.953571683@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200003182031.NAA97975@harmony.village.org>, Warner Losh writes: > > >I'd like to be able to do some simple spl locking in a driver that I'm > >writing. While I could go the splhigh() route, I'm concerned that > >spending lots of time at splhigh could cause problems, and some of my > >critical sections look to be very expensive. They only need > >protection against the card itself, not against the entire system. It > >just seems to be an overly large hammer. > > I miss this too. Semaphores? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 15:24:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 54F0537BD60; Mon, 20 Mar 2000 15:24:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2KNlSC07286; Mon, 20 Mar 2000 15:47:28 -0800 (PST) Date: Mon, 20 Mar 2000 15:47:28 -0800 From: Alfred Perlstein To: Dave McKay Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: ports security advisories.. Message-ID: <20000320154728.G14789@fw.wintelcom.net> References: <20000320154614.A63670@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000320154614.A63670@elvis.mu.org>; from dave@mu.org on Mon, Mar 20, 2000 at 03:46:14PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dave McKay [000320 14:18] wrote: > Is it really necessary to post the ports security advisories? > The exploitable programs are not part of the FreeBSD OS, they > are third party software. I think the proper place for these > is the Bugtraq mailing list on securityfocus.com. Also to add > to the arguments, most of the advisories are not FreeBSD > specific. I don't agree, I monitor FreeBSD boxes almost exclusively and find that the recent additional advisories take less time to go through and since they are freebsd specific they help the average FreeBSD-joe upgrade with FreeBSD specific instructions. Also, considering the recent bugtraq postings about problems with FreeBSD ports when it was a 3rd party application... I think that it's a wise PR move. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 20 16:27:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 1912637B6D3 for ; Mon, 20 Mar 2000 16:24:26 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id QAA17917 for freebsd-hackers@FreeBSD.ORG; Mon, 20 Mar 2000 16:31:37 -0600 (CST) (envelope-from obonilla) Date: Mon, 20 Mar 2000 16:31:37 -0600 From: Oscar Bonilla To: freebsd-hackers@FreeBSD.ORG Subject: NSS for FreeBSD Message-ID: <20000320163137.A17849@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ long email --- there's a specific question at the end ] I've started work a couple of weeks ago to port the NSS implementation from NetBSD to FreeBSD. This is needed for things like authenticating with an LDAP server, etc. If you search for LDAP in Hackers you'll find a thread that discusses why it's needed in more detail. I've put up a web page showing the status of the NSS port. It's at http://www.fisicc-ufm.edu/~obonilla/nss/ In brief: nsdispatch() has been incorporated to the FreeBSD libc code. getpwent(), getpwnam(), and getpwuid() all call nsdispatch() and work for both files and nis. I wish I could say that work in this file is completed, but I still haven't got to the compat implementation. See below. There are a bunch of other files that need to be modified to make use of the new nsdispatch function. There's a list at the URL given above. I need help with the NIS code. In particular I wish someone could explain to me exactly what the unwind() function in getpwent() does. In detail: The nsdispatch() function is *exactly* the same as in NetBSD. Thus, the NSS mechanism currently works on FreeBSD exactly as it workd in NetBSD. NetBSD's way: Basically you have a file named /etc/nsswitch.conf which tells the C library where to get the info from. So if you have a line saying: hosts files nis it means that /etc/hosts is checked first and the yp maps are checked next. The man page explains this in more detail and is available in the URL given above for those who don't have NetBSD. NetBSD provides also a compatibility mode for two of the system's databases (passwd and group). For example: passwd compat means that the system will behave as it did before the nsdispatch function was added. e.d. lookup files first and if it finds a line +:::::: then it will lookup nis. NetBSD provides an extra parameter, namely: passwd_compat nis which tells the system which database to use *after* files and when it finds the +::::: token. This makes sense since NetBSD supports two different databases besides files out of the box: NIS, and Hesiod (extra DNS records). I personally don't see this as a big benefit, since if I wanted to have the system lookup stuff first in files and then in, say, hesiod. I would just get rid of the +:::: token in /etc/passwd and change the /etc/nsswitch.conf to be: passwd files dns instead of relaying on the compat stuff. I'm sure there's a good reason they did it like this, I just can't seem to find it. FreeBSD's proposed way: Given that FreeBSD doesn't support Hesiod, I think it would make sense to have nsswitch behave the following way: *exactly* like NetBSD for all databases minus compat. *only* for compat: get rid of the foo_compat blah to select blah as the source for database foo and simply make compat mode behave exactly as it behaves now (pre nss); which is, lookup files and if it finds the +::::: token, lookup NIS. Specific Question: For the FreeBSD implementation of NSS: is it worth to have a way to tell the compat database which source to use for the +::::: token in /etc/passwd or should it just default to NIS? Help: If someone is interested in helping with this I would appreciate it. Thanks and Regards, -Oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 16:37:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mw3.texas.net (mw3.texas.net [206.127.30.13]) by hub.freebsd.org (Postfix) with ESMTP id 70E1537BAB4 for ; Mon, 20 Mar 2000 16:37:33 -0800 (PST) (envelope-from luser@texas.net) Received: from 206.127.8.28 (www2.texas.net [207.207.0.42]) by mw3.texas.net (2.4/2.4) with SMTP id SAA25755 for ; Mon, 20 Mar 2000 18:37:31 -0600 (CST) Message-Id: <200003210037.SAA25755@mw3.texas.net> To: freebsd-hackers@freebsd.org From: luser@texas.net Subject: subscribe Date: Mon, 20 Mar 2000 18:37:31 US/Central X-Mailer: Texas.Net Webmail (Endymion MailMan Standard Edition v3.0.12) X-User: luser Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 16:43:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id C13B537B8A5 for ; Mon, 20 Mar 2000 16:43:39 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id RAA04699; Mon, 20 Mar 2000 17:43:19 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D6C5EB.E96A6514@softweyr.com> Date: Mon, 20 Mar 2000 17:44:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Guido van Rooij , hackers@FreeBSD.ORG Subject: Re: splFoo() question References: <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> <200003202057.NAA17486@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <20000320210008.A59405@gvr.gvr.org> Guido van Rooij writes: > : perhaps we need some mutex mechanism? > > Yes. Right now the mutex mechanism that we have is blocking of > interrupts when the bit is set in the cpl. I guess I'm a little too > close to the mechanism and need to step back. > > You are right that I'm asking for a call that is approximately "block > my interrupt handler from running until I say it is ok." A more > generalized mutex/locking scheme is needed so that I can just grab a > mutex in my code and in my ISR and the right thing will just happen. A per-driver mutex, perhaps? This would save us from potential deadly embraces within a single driver, at least. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 16:49:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from clockwork.csudsu.com (clockwork.csudsu.com [209.249.57.100]) by hub.freebsd.org (Postfix) with ESMTP id 6A65737BA86 for ; Mon, 20 Mar 2000 16:49:21 -0800 (PST) (envelope-from stefan@csudsu.com) Received: by clockwork.csudsu.com (Postfix, from userid 1001) id C15FE1AECA; Mon, 20 Mar 2000 16:49:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clockwork.csudsu.com (Postfix) with ESMTP id A6AA21AEC6; Mon, 20 Mar 2000 16:49:12 -0800 (PST) Date: Mon, 20 Mar 2000 16:49:12 -0800 (PST) From: Stefan Molnar To: Bill Fenner Cc: newton@internode.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: WaveLAN/IEEE Turbo (Silver) In-Reply-To: <200003201904.LAA01936@windsor.research.att.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 With Encryption? From last I saw it is not an option. Stefan On Mon, 20 Mar 2000, Bill Fenner wrote: > > >I know the WaveLAN stuff is crap > > Actually, I've had terrific luck with WaveLAN IEEE stuff on laptops > for the last year or so. I'm not sure what's so bad about it?... > > Bill > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 16:56: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0893837B9D9 for ; Mon, 20 Mar 2000 16:56:02 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id TAA00427; Mon, 20 Mar 2000 19:56:53 -0500 (EST) Message-Id: <200003210056.TAA00427@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 20 Mar 2000 19:51:57 -0500 To: Wes Peters From: Dennis Subject: Re: if_fxp driver Cc: hackers@FreeBSD.ORG In-Reply-To: <38D3CFAD.BBAB3C6D@softweyr.com> References: <200003181706.MAA23691@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well its gone from cdrom.com which is where i usually get it.... ftp://ftp.freesoftware.com/pub/FreeBSD/releases/i386/3.4-STABLE/ is just a packages directory. cdrom.com redirects you to freesoftware.com...just FYI. Dennis At 11:49 AM 3/18/00 -0700, Wes Peters wrote: >Dennis wrote: >> >> Is there a version of the fxp driver that works with intels latest boards >> without giving the "unsupported PHY" message? All the boards we get lately >> have this problem, and it seems that the 3.4 stuff is been virtually wiped >> from the ftp site. > >Yeah, right: > >ftp> pwd >257 "/.0/FreeBSD/releases/i386/3.4-RELEASE" is current directory. >ftp> dir >200 PORT command successful. >150 Opening ASCII mode data connection for 'file list'. >total 144 >-rw-r--r-- 1 root 207 9818 Dec 19 23:57 ABOUT.TXT >-rw-r--r-- 1 root 207 2490 Jan 25 20:38 ERRATA.TXT >-rw-r--r-- 1 root 207 26513 Dec 19 23:57 HARDWARE.TXT >-rw-r--r-- 1 root 207 24538 Dec 19 23:57 INSTALL.TXT >-rw-r--r-- 1 root 207 4736 Dec 19 23:57 LAYOUT.TXT >-rw-r--r-- 1 root 207 3713 Dec 19 23:57 README.TXT >-rw-r--r-- 1 root 207 22209 Dec 19 23:57 RELNOTES.TXT >-rw-r--r-- 1 root 207 16811 Dec 19 23:57 TROUBLE.TXT >-rw-r--r-- 1 root 207 8367 Dec 19 23:57 UPGRADE.TXT >drwxr-xr-x 4 2035 207 1024 Sep 10 1999 XF86335 >drwxr-xr-x 2 2035 207 2048 Dec 20 11:39 bin >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 catpages >-rw-r--r-- 1 root 207 25 Dec 19 23:57 cdrom.inf >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 compat1x >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 compat20 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 compat21 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 compat22 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 des >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 dict >drwxr-xr-x 2 2035 207 1024 Dec 23 05:57 doc >drwxr-xr-x 4 2035 207 512 Dec 22 02:21 floppies >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 games >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 info >drwxr-xr-x 2 2035 207 1024 Dec 20 11:39 manpages >lrwxrwxrwx 1 root 207 40 Feb 27 00:35 packages -> ../../../ports/i386/packages-3.4-release >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 ports >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 proflibs >drwxr-xr-x 2 2035 207 4608 Dec 23 02:47 src >226 Transfer complete. > >Nope, no 3.4 stuff there on ftp.freebsd.org, not at all. > >-- > "Where am I, and what am I doing in this handbasket?" > >Wes Peters Softweyr LLC >wes@softweyr.com http://softweyr.com/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 16:57: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id EBD9F37BD3F for ; Mon, 20 Mar 2000 16:56:54 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id TAA00436; Mon, 20 Mar 2000 19:57:55 -0500 (EST) Message-Id: <200003210057.TAA00436@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 20 Mar 2000 19:52:59 -0500 To: Wes Peters From: Dennis Subject: Re: if_fxp driver Cc: hackers@FreeBSD.ORG In-Reply-To: <38D3CFAD.BBAB3C6D@softweyr.com> References: <200003181706.MAA23691@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope your happy, but do you know the answer to my question? Has the driver been updated recently? DB At 11:49 AM 3/18/00 -0700, Wes Peters wrote: >Dennis wrote: >> >> Is there a version of the fxp driver that works with intels latest boards >> without giving the "unsupported PHY" message? All the boards we get lately >> have this problem, and it seems that the 3.4 stuff is been virtually wiped >> from the ftp site. > >Yeah, right: > >ftp> pwd >257 "/.0/FreeBSD/releases/i386/3.4-RELEASE" is current directory. >ftp> dir >200 PORT command successful. >150 Opening ASCII mode data connection for 'file list'. >total 144 >-rw-r--r-- 1 root 207 9818 Dec 19 23:57 ABOUT.TXT >-rw-r--r-- 1 root 207 2490 Jan 25 20:38 ERRATA.TXT >-rw-r--r-- 1 root 207 26513 Dec 19 23:57 HARDWARE.TXT >-rw-r--r-- 1 root 207 24538 Dec 19 23:57 INSTALL.TXT >-rw-r--r-- 1 root 207 4736 Dec 19 23:57 LAYOUT.TXT >-rw-r--r-- 1 root 207 3713 Dec 19 23:57 README.TXT >-rw-r--r-- 1 root 207 22209 Dec 19 23:57 RELNOTES.TXT >-rw-r--r-- 1 root 207 16811 Dec 19 23:57 TROUBLE.TXT >-rw-r--r-- 1 root 207 8367 Dec 19 23:57 UPGRADE.TXT >drwxr-xr-x 4 2035 207 1024 Sep 10 1999 XF86335 >drwxr-xr-x 2 2035 207 2048 Dec 20 11:39 bin >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 catpages >-rw-r--r-- 1 root 207 25 Dec 19 23:57 cdrom.inf >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 compat1x >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 compat20 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 compat21 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 compat22 >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 des >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 dict >drwxr-xr-x 2 2035 207 1024 Dec 23 05:57 doc >drwxr-xr-x 4 2035 207 512 Dec 22 02:21 floppies >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 games >drwxr-xr-x 2 2035 207 512 Dec 20 11:39 info >drwxr-xr-x 2 2035 207 1024 Dec 20 11:39 manpages >lrwxrwxrwx 1 root 207 40 Feb 27 00:35 packages -> ../../../ports/i386/packages-3.4-release >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 ports >drwxr-xr-x 2 2035 207 512 Dec 20 11:38 proflibs >drwxr-xr-x 2 2035 207 4608 Dec 23 02:47 src >226 Transfer complete. > >Nope, no 3.4 stuff there on ftp.freebsd.org, not at all. > >-- > "Where am I, and what am I doing in this handbasket?" > >Wes Peters Softweyr LLC >wes@softweyr.com http://softweyr.com/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 17:10:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.targetnet.com (mail.targetnet.com [207.245.246.3]) by hub.freebsd.org (Postfix) with ESMTP id 9976D37B919 for ; Mon, 20 Mar 2000 17:10:04 -0800 (PST) (envelope-from james@targetnet.com) Received: from james by mail.targetnet.com with local (Exim 3.02 #1) id 12Vy1L-000CvV-00; Fri, 17 Mar 2000 09:46:35 -0500 Date: Fri, 17 Mar 2000 09:46:35 -0500 From: James FitzGibbon To: David Malone Cc: hackers@freebsd.org Subject: Re: T/TCP friendly inetd change? Message-ID: <20000317094635.B41950@targetnet.com> References: <200003162131.aa50415@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <200003162131.aa50415@salmon.maths.tcd.ie> Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Malone (dwmalone@maths.tcd.ie) [000316 16:51]: > I've tried this over my slip link and it does seem to reduce the > number of packets sent by 2 for telnetting to the daytime port. I > also had a look at fetch (the only thing in the tree which uses > MSG_EOF at the moment), which has an option for turning off the > MSG_EOF stuff 'cos some buggy http servers don't like half closed > connections. I don't think this applies in this case 'cos we're > on the server side - not the client side, and the client expects > an EOF anyway. > > Would this be an acceptable patch to inetd? It would be nice to > encourage the use of T/TCP within FreeBSD, as we seem to be the > only people who have it ;-) A couple of points of feedback: - by default, T/TCP is off in the kernel (see src/sys/netinet/tcp_subr.c; around line 85 in my 3.x box). It's also off by default in /etc/defaults/rc.conf - all the "internal" services that inetd provides (including daytime) are turned off by default in /etc/inetd.conf - security conscious people who have read through LINT may turn on the "TCP_DROP_SYNFIN" kernel opt, which breaks T/TCP. I think that this option should be made a sysctl knob just like support for T/TCP before a change like this goes through. That way, any program that wants to support T/TCP can query the value of the knob before deciding if it will support the extensions or not. I like T/TCP (I use it on some of my networked apps for the same reasons you describe), but I don't think that it should be added to a program like inetd which has two default settings that would need to be changed before the T/TCP extensions would ever provide any benefit. More education on T/TCP for both client and server authors is the key here I think; if major web browsers alone would support the extensions, then the massive overhead of HTTP (and the issues that arise from getting around it with HTTP/1.1 KeepAlive and such) would be significantly reduced. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 17:21:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual.valuelinx.net (virtual.valuelinx.net [208.189.209.17]) by hub.freebsd.org (Postfix) with ESMTP id 6D00A37BDC8 for ; Mon, 20 Mar 2000 17:20:54 -0800 (PST) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp124440.sympatico.ca [216.209.187.131]) by virtual.valuelinx.net (8.9.1/8.9.1) with SMTP id UAA28831 for ; Mon, 20 Mar 2000 20:23:32 GMT Message-ID: <38D6CDC5.5ADC5325@penix.org> Date: Mon, 20 Mar 2000 20:17:57 -0500 From: "[ -dp- ]" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Odd problem.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi- dissent.p200.box kernel log messages: > wd1s1f: wdstart: timeout waiting to give command writing fsbn 262208 of 262208-262223 (wd1s1 bn 7430208; cn 462 tn 129 sn 51) (status d0 error 0) > wd1s1f: wdstart: timeout waiting to give command writing fsbn 262208 of 262208-262223 (wd1s1 bn 7430208; cn 462 tn 129 sn 51) (status d0 error 1) > wd1s1f: wdstart: timeout waiting to give command writing fsbn 262208 of 262208-262223 (wd1s1 bn 7430208; cn 462 tn 129 sn 51) (status d0 error 1) Normally this wouldn't bother me, however the problem occurs on two different hd's. Any idea's? -- [ - deadpoint - ] ======================================================================= Don't underestimate the power of stupid people in large groups. Email: dp@penix.org BIO: http://bling.dny.dhs.org GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3E8B9 Public Key's available here: http://bling.dyn.dhs.org/texts/public.html ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 17:46:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 5950037C0DD for ; Mon, 20 Mar 2000 17:46:17 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id SAA28421; Mon, 20 Mar 2000 18:46:02 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id SAA17825; Mon, 20 Mar 2000 18:46:01 -0700 (MST) (envelope-from nate) Date: Mon, 20 Mar 2000 18:46:01 -0700 (MST) Message-Id: <200003210146.SAA17825@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Wes Peters Cc: Warner Losh , Guido van Rooij , hackers@FreeBSD.ORG Subject: Re: splFoo() question In-Reply-To: <38D6C5EB.E96A6514@softweyr.com> References: <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> <200003202057.NAA17486@harmony.village.org> <38D6C5EB.E96A6514@softweyr.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : perhaps we need some mutex mechanism? > > > > Yes. Right now the mutex mechanism that we have is blocking of > > interrupts when the bit is set in the cpl. I guess I'm a little too > > close to the mechanism and need to step back. > > > > You are right that I'm asking for a call that is approximately "block > > my interrupt handler from running until I say it is ok." A more > > generalized mutex/locking scheme is needed so that I can just grab a > > mutex in my code and in my ISR and the right thing will just happen. > > A per-driver mutex, perhaps? This would save us from potential > deadly embraces within a single driver, at least. The only concern I can see is that currently it requires you to get too cozy with the machine independant code. Basically, the 'resource' that you want to lock on is the IRQ, and the raw IRQ code is quite machine dependant. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 17:56:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E73F137B9F3 for ; Mon, 20 Mar 2000 17:56:40 -0800 (PST) (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 SAA20701; Mon, 20 Mar 2000 18:56:29 -0700 (MST) (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 SAA19697; Mon, 20 Mar 2000 18:56:19 -0700 (MST) Message-Id: <200003210156.SAA19697@harmony.village.org> To: Wes Peters Subject: Re: splFoo() question Cc: Guido van Rooij , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Mar 2000 17:44:27 MST." <38D6C5EB.E96A6514@softweyr.com> References: <38D6C5EB.E96A6514@softweyr.com> <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> <200003202057.NAA17486@harmony.village.org> Date: Mon, 20 Mar 2000 18:56:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D6C5EB.E96A6514@softweyr.com> Wes Peters writes: : > In message <20000320210008.A59405@gvr.gvr.org> Guido van Rooij writes: : > : perhaps we need some mutex mechanism? : > : > Yes. Right now the mutex mechanism that we have is blocking of : > interrupts when the bit is set in the cpl. I guess I'm a little too : > close to the mechanism and need to step back. : > : > You are right that I'm asking for a call that is approximately "block : > my interrupt handler from running until I say it is ok." A more : > generalized mutex/locking scheme is needed so that I can just grab a : > mutex in my code and in my ISR and the right thing will just happen. : : A per-driver mutex, perhaps? This would save us from potential : deadly embraces within a single driver, at least. We kinda sorta have this right now with the interrupt routine being blocked when the cpl is too high. I'd like to see this more generalized than it is today. However, jumping in and mucking with this code makes me nervous. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:11:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2C0D137C123; Mon, 20 Mar 2000 18:11:34 -0800 (PST) (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 TAA20760; Mon, 20 Mar 2000 19:11:32 -0700 (MST) (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 TAA19792; Mon, 20 Mar 2000 19:11:21 -0700 (MST) Message-Id: <200003210211.TAA19792@harmony.village.org> To: Dave McKay Subject: Re: ports security advisories.. Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Mar 2000 15:46:14 CST." <20000320154614.A63670@elvis.mu.org> References: <20000320154614.A63670@elvis.mu.org> Date: Mon, 20 Mar 2000 19:11:21 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- In message <20000320154614.A63670@elvis.mu.org> Dave McKay writes: : Is it really necessary to post the ports security advisories? Yes. : The exploitable programs are not part of the FreeBSD OS, they : are third party software. I think the proper place for these : is the Bugtraq mailing list on securityfocus.com. Also to add : to the arguments, most of the advisories are not FreeBSD : specific. But they are part of FreeBSD in the public mind. In order to show FreeBSD's commitment to Security, we must inform the public about all parts of the system that we offer under our name. The FreeBSD ports collection is very much part of FreeBSD, and is very FreeBSD specific[*]. Since we have packaged the sources for people, they have the reasonable expectation that this packaging was done in a safe and secure way. It is passing the buck to say "well, it really wasn't our fault that popper had a bug in it, so we didn't think we needed to tell anybody." It is code we've made available. It is no different than holes in the base OS that we inherited from the 4.4-lite distribution. We could say "well, all BSD derived OSes have this problem, so we'll not tell anybody that we fixed it." They are the same thing, especially in the mind of the users of the system. We want to elevate the security of the entire system to a higher level, and to do that we have to disiminate security information about the system more fully that we've done in the past. I'm sorry that you feel that this step to improve the security of FreeBSD is inappropriate and annoys you. So far I've had only one or two negative comment from the increased level of posting about these problems. Kris has done an excellent job of running down these issues and keeping on top of them. I think he's done the greater community an excellent service by reading bugtraq and other sources of security information and identifying those problems which will negatively impact FreeBSD users and issuing advisories. Keeping up with bugtraq can take a lot of time and effort and Kris' advisories makes this easy. Warner Losh FreeBSD Security Officer -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAwUBONbaSNxynu/2qPVhAQHC8AQAgDR9qaksAgvfSUG12hRqHJDD+QmBuCtN g7pg3aw/A4Vz3ezu4ythW7zLj04XEnC+5UzCMu6uAmyO+pUWM2CJ3KQQYttm5XAG z+AV0hxpbOe0b003C8f2dFjvDReRBOqiQAZnH264dxVXpllQgQjiRzYkcXNB4r2r pUqxUwYwslA= =xKkJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:33:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 2629F37B9D2 for ; Mon, 20 Mar 2000 18:33:37 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id D8F4F4CE05; Mon, 20 Mar 2000 21:33:32 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id VAA01567; Mon, 20 Mar 2000 21:33:32 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id SAA05069; Mon, 20 Mar 2000 18:32:49 -0800 (PST) Message-Id: <200003210232.SAA05069@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: stefan@csudsu.com Subject: Re: WaveLAN/IEEE Turbo (Silver) Cc: newton@internode.com.au, freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 18:32:49 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The FreeBSD driver doesn't currently support encryption, correct. The Linux driver does, so perhaps it would be fairly easy to port the functionality, and the Linux driver is dual-licensed under GPL and BSD licenses so there's no worry of GPL contamination. ftp://sourceforge.org/pcmcia/contrib/wavelan2_cs-6.00.tar.gz I'm going to have to figure this out soon, since we're going to turn encryption on soon. I'd be ecstatic if someone else figured it out first =) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:39:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 885FD37BA38 for ; Mon, 20 Mar 2000 18:39:57 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id SAA28507; Mon, 20 Mar 2000 18:39:38 -0800 (PST) Date: Mon, 20 Mar 2000 18:39:38 -0800 From: Brooks Davis To: Bill Fenner Cc: stefan@csudsu.com, newton@internode.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: WaveLAN/IEEE Turbo (Silver) Message-ID: <20000320183938.A27414@orion.ac.hmc.edu> References: <200003210232.SAA05069@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200003210232.SAA05069@windsor.research.att.com>; from fenner@research.att.com on Mon, Mar 20, 2000 at 06:32:49PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 06:32:49PM -0800, Bill Fenner wrote: > > The FreeBSD driver doesn't currently support encryption, correct. > The Linux driver does, so perhaps it would be fairly easy to port the > functionality, and the Linux driver is dual-licensed under GPL and BSD > licenses so there's no worry of GPL contamination. > ftp://sourceforge.org/pcmcia/contrib/wavelan2_cs-6.00.tar.gz > > I'm going to have to figure this out soon, since we're going to turn > encryption on soon. I'd be ecstatic if someone else figured it out > first =) You're in luck. Bill Paul commited support at Linux World. There appear to be some weird things like a comment about the API using a 14byte field to pass 128bits of data, but it's supposed to work. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:40:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 5A03437BA40 for ; Mon, 20 Mar 2000 18:40:36 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 5F3869B19; Mon, 20 Mar 2000 21:40:33 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 5674DBA1D; Mon, 20 Mar 2000 21:40:33 -0500 (EST) Date: Mon, 20 Mar 2000 21:40:33 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net Reply-To: freebsd-questions@FreeBSD.org To: Mourad Lakhdar <992C396651@stud.alakhawayn.ma> Cc: freebsd-hackers@FreeBSD.org Subject: Re: need help In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ...redirecting to -questions On Mon, 20 Mar 2000, Mourad Lakhdar wrote: > > hi every body: > > > when i change in the kernel , i config it , made : make depend > > while doing >make > > i got the error : > > /var : write failed , file system is full > cpp: /var/tmp/ccT1684.i:No space left on device > > error code 1 > stop > > so what should i do > Remove some files from your /var partition? ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:45:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 0190437BB16 for ; Mon, 20 Mar 2000 18:45:10 -0800 (PST) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ivea1j.dialup.mindspring.com [165.247.40.51]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA10408; Mon, 20 Mar 2000 21:44:55 -0500 (EST) Message-ID: <38D6E14E.90257842@confusion.net> Date: Mon, 20 Mar 2000 21:41:18 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Mourad Lakhdar <992C396651@stud.alakhawayn.ma> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: need help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Put more descriptive subjects, it'll help people with less time locate the questions they can and/or want to answer. 2. Try one of these: -get a new /var with more space -use vinum so you can add more hds to add space -make one of the larger directories on /var a symlink to somewhere that has free space -delete some stuff in /var (old logs you no longer need etc.) There are of course other ways to fix this, but these come to mind off the top of my head. Hope I could help, Laurence Mourad Lakhdar wrote: > > hi every body: > > when i change in the kernel , i config it , made : make depend > > while doing >make > > i got the error : > > /var : write failed , file system is full > cpp: /var/tmp/ccT1684.i:No space left on device > > error code 1 > stop > > so what should i do > > best regards, > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:48:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 8C1DC37B717 for ; Mon, 20 Mar 2000 18:48:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA41919; Mon, 20 Mar 2000 18:50:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003210250.SAA41919@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fenner Cc: newton@internode.com.au, freebsd-hackers@freebsd.org Subject: Re: WaveLAN/IEEE Turbo (Silver) In-reply-to: Your message of "Mon, 20 Mar 2000 18:32:49 PST." <200003210232.SAA05069@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 18:50:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The FreeBSD driver doesn't currently support encryption, correct. Incorrect. > I'm going to have to figure this out soon, since we're going to turn > encryption on soon. I'd be ecstatic if someone else figured it out > first =) As I posted just a little while ago, we were using WEP at Linuxworld; Bill Paul did the support there. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:58:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id F0DDC37BACA; Mon, 20 Mar 2000 18:58:35 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id ACE431E01C; Mon, 20 Mar 2000 21:58:25 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id VAA03126; Mon, 20 Mar 2000 21:58:25 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id SAA05123; Mon, 20 Mar 2000 18:57:42 -0800 (PST) Message-Id: <200003210257.SAA05123@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: msmith@freebsd.org Subject: Re: WaveLAN/IEEE Turbo (Silver) Cc: newton@internode.com.au, freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 18:57:42 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Er, I meant the 3.x driver =) How embarassing. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 18:59:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 8F2A237BBB0 for ; Mon, 20 Mar 2000 18:59:45 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 00EAA1CC9; Tue, 21 Mar 2000 02:59:44 -0800 (PST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: Wes Peters , hackers@FreeBSD.ORG Subject: Re: if_fxp driver In-Reply-To: Message from Dennis of "Mon, 20 Mar 2000 19:51:57 EST." <200003210056.TAA00427@etinc.com> Date: Tue, 21 Mar 2000 02:59:43 -0800 From: Peter Wemm Message-Id: <20000321105944.00EAA1CC9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > Well its gone from cdrom.com which is where i usually get it.... cdrom.com has not been the correct location for a *long* time (like 4+ years!). The proper hostname is ftp.freebsd.org - that hasn't changed and the paths there are still perfectly valid. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19: 2:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from clockwork.csudsu.com (clockwork.csudsu.com [209.249.57.100]) by hub.freebsd.org (Postfix) with ESMTP id 4A3F637B717; Mon, 20 Mar 2000 19:01:51 -0800 (PST) (envelope-from stefan@csudsu.com) Received: by clockwork.csudsu.com (Postfix, from userid 1001) id CAE6B1AECA; Mon, 20 Mar 2000 19:01:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clockwork.csudsu.com (Postfix) with ESMTP id B10491AEC6; Mon, 20 Mar 2000 19:01:45 -0800 (PST) Date: Mon, 20 Mar 2000 19:01:45 -0800 (PST) From: Stefan Molnar To: Mike Smith Cc: Bill Fenner , newton@internode.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: WaveLAN/IEEE Turbo (Silver) In-Reply-To: <200003210250.SAA41919@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well shuck my corn and call me Sally. I will try it out. Esp after I figure out to make this AirConnect work with the Apple AirPort. Stefan On Mon, 20 Mar 2000, Mike Smith wrote: > > > > The FreeBSD driver doesn't currently support encryption, correct. > > Incorrect. > > > I'm going to have to figure this out soon, since we're going to turn > > encryption on soon. I'd be ecstatic if someone else figured it out > > first =) > > As I posted just a little while ago, we were using WEP at Linuxworld; Bill > Paul did the support there. > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19: 5:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id A448337BF97 for ; Mon, 20 Mar 2000 19:05:39 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 4CF841E01C; Mon, 20 Mar 2000 22:05:33 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id WAA03689; Mon, 20 Mar 2000 22:05:32 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id TAA05140; Mon, 20 Mar 2000 19:04:50 -0800 (PST) Message-Id: <200003210304.TAA05140@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: stefan@csudsu.com Subject: Re: WaveLAN/IEEE Turbo (Silver) Cc: freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 19:04:49 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an Airport configuration utility almost usable, if you're interested in trying it. (It doesn't support configuring keys yet, although I think I know where they're stored so if you want to experiment...) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19: 6:50 2000 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 7343137B9DD for ; Mon, 20 Mar 2000 19:06:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA29682; Mon, 20 Mar 2000 19:05:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: Dennis , Wes Peters , hackers@FreeBSD.ORG Subject: Re: if_fxp driver In-reply-to: Your message of "Tue, 21 Mar 2000 02:59:43 PST." <20000321105944.00EAA1CC9@overcee.netplex.com.au> Date: Mon, 20 Mar 2000 19:05:35 -0800 Message-ID: <29679.953607935@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's also the case that there's never been anything in the release/3.x-STABLE or release/4.x-STABLE directories except a package link since those directories are there only for sysinstall, they're not for humans to go to and browse. Humans looking for actual source code for these branches should refer to the Handbook and then cvsup, CTM, etc. - Jordan > Dennis wrote: > > Well its gone from cdrom.com which is where i usually get it.... > > cdrom.com has not been the correct location for a *long* time (like 4+ > years!). The proper hostname is ftp.freebsd.org - that hasn't changed > and the paths there are still perfectly valid. > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id E6B2337B7E1; Mon, 20 Mar 2000 19:11:11 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id RAA00995; Mon, 20 Mar 2000 17:11:58 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003210311.RAA00995@mauibuilt.com> Subject: Davicam dc0 driver To: freebsd-hackers@freebsd.org Date: Mon, 20 Mar 2000 17:11:56 -1000 (HST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a BookPC with a built in Davi Comm 10/100 ethernet card. I am always getting /kernel: dc0: watchdog timeout every few minutes.. Can thease errors be stopped? Thank you for any reply RP puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19:20: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from stud.alakhawayn.ma (stud.alakhawayn.ma [193.194.63.94]) by hub.freebsd.org (Postfix) with ESMTP id DE02C37B551 for ; Mon, 20 Mar 2000 19:19:57 -0800 (PST) (envelope-from 992C396651@stud.alakhawayn.ma) Received: from localhost (992C396651@localhost) by stud.alakhawayn.ma (8.9.0/8.9.0) with SMTP id DAA05724 for ; Tue, 21 Mar 2000 03:19:34 GMT Date: Tue, 21 Mar 2000 03:19:28 +0000 (GMT) From: Mourad Lakhdar <992C396651@stud.alakhawayn.ma> To: freebsd-hackers@freebsd.org Subject: need help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have always problems when trying to work with the inet_addr(), inet_network() ,inet_ntoa() functions ,when changin in the ip_input file: i got error like(when making): ip_input.o(.text+0xce9):undefined reference to '__inet_addr' may you help? best regards, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 19:34:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (Postfix) with ESMTP id 8941037B82C for ; Mon, 20 Mar 2000 19:33:56 -0800 (PST) (envelope-from garycor@home.com) Received: from home.com ([24.3.185.85]) by mail.rdc1.nj.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000321033355.ZSYC20681.mail.rdc1.nj.home.com@home.com>; Mon, 20 Mar 2000 19:33:55 -0800 Message-ID: <38D6EDD1.990EAF13@home.com> Date: Mon, 20 Mar 2000 22:34:41 -0500 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Darrell Anderson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to read a file from a device driver? References: <200003201606.LAA12793@cold.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darrell, > > I'm trying to initialize a network device, and I'm trying to download > > code *into* my device from some binary system files. There is no "user > > space" or user process, for that matter, to deal with at this point. I > > just want to (at this step) open a file(s) directly from my device > > driver, read the file(s), and download the relevant parts to my device. > > sysctl might also do the trick. to answer your question, here's some code: > > struct vnode * > vp_open(char *fname) > { > struct vnode *vp; > struct nameidata nd; > int error; > > NDINIT(&nd, LOOKUP, FOLLOW, UIO_SYSSPACE, fname, curproc); < rest of good code sample snipped - see previous message> This is great - thanks! One question though (since I'm new to FreeBSD drivers): Is "curproc" a global variable that will be set to the "right thing" while my device driver is executing? Presuming that it is, it looks like I can just take your sample code and run with it... :) Thanks, Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 20:51:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 93EC837BDD8 for ; Mon, 20 Mar 2000 20:51:35 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id UAA25057; Mon, 20 Mar 2000 20:45:09 -0800 (PST) Message-Id: <200003210445.UAA25057@implode.root.com> To: Dennis Cc: Wes Peters , hackers@FreeBSD.ORG Subject: Re: if_fxp driver In-reply-to: Your message of "Mon, 20 Mar 2000 19:52:59 EST." <200003210057.TAA00436@etinc.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 20 Mar 2000 20:45:09 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I hope your happy, but do you know the answer to my question? Has the >driver been updated recently? Not to fix the problem that you are reporting. The solution might be as simple as adding another PHY identifier to the list of supported ones. I need to find some time to sit down with one of the not-working cards and fiddle with it. I was going to do that this past weekend, but then got sick with a virus. It's on my list. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 22:21:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id C15C937BCDC for ; Mon, 20 Mar 2000 22:21:18 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA05554; Mon, 20 Mar 2000 23:21:08 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D7151E.EBC079DC@softweyr.com> Date: Mon, 20 Mar 2000 23:22:22 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp driver References: <200003181706.MAA23691@etinc.com> <200003210057.TAA00436@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > I hope your happy, I'll be happier when you stop FUD'ing two separate FreeBSD development lists with your bleating about this driver. > but do you know the answer to my question? Has the > driver been updated recently? Define "updated" and "recently". On which code branch? It's been updated a LOT on -CURRENT, and twice on RELENG_3: revision 1.59.2.6 date: 2000/01/18 14:12:52; author: luigi; state: Exp; lines: +5 -4 fix bridging support for potential null dereference ---------------------------- revision 1.59.2.5 date: 1999/12/06 20:11:52; author: peter; state: Exp; lines: +4 -1 MFC: new PCI device ID for the InBusiness 10/100 card. (an 82559 with a different PCI device ID in it's eprom - 0x1030 instead of 0x1229) Reviewed by: jkh, dg I suspect the change in 1.59.2.5 is what you're looking for. Would it have been so difficult for you to check yourself? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 22:31:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id F39E037BB05 for ; Mon, 20 Mar 2000 22:31:24 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA05578; Mon, 20 Mar 2000 23:31:14 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D7177C.C7DD9BF1@softweyr.com> Date: Mon, 20 Mar 2000 23:32:28 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Guido van Rooij , hackers@FreeBSD.ORG Subject: Re: splFoo() question References: <38D6C5EB.E96A6514@softweyr.com> <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> <200003202057.NAA17486@harmony.village.org> <200003210156.SAA19697@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <38D6C5EB.E96A6514@softweyr.com> Wes Peters writes: > : > In message <20000320210008.A59405@gvr.gvr.org> Guido van Rooij writes: > : > : perhaps we need some mutex mechanism? > : > > : > Yes. Right now the mutex mechanism that we have is blocking of > : > interrupts when the bit is set in the cpl. I guess I'm a little too > : > close to the mechanism and need to step back. > : > > : > You are right that I'm asking for a call that is approximately "block > : > my interrupt handler from running until I say it is ok." A more > : > generalized mutex/locking scheme is needed so that I can just grab a > : > mutex in my code and in my ISR and the right thing will just happen. > : > : A per-driver mutex, perhaps? This would save us from potential > : deadly embraces within a single driver, at least. > > We kinda sorta have this right now with the interrupt routine being > blocked when the cpl is too high. I'd like to see this more > generalized than it is today. > > However, jumping in and mucking with this code makes me nervous. I'm much more familiar with VxWorks style device drivers, which typically just give a "go" semaphore to an appropriate task that will then perform the actual I/O in a task (think thread) context. It's a different kind of beast from a typical UNIX driver model, but it goes a long way towards avoiding interrupt livelock, since you can balance the priorities of the threads doing the actual I/O. This seems like a good place to point out how much kernel threads would help. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 22:47:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 25F5537BB16 for ; Mon, 20 Mar 2000 22:47:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA23425; Tue, 21 Mar 2000 07:46:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Wes Peters Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: splFoo() question In-reply-to: Your message of "Mon, 20 Mar 2000 16:25:07 MST." <38D6B353.FA58BB15@softweyr.com> Date: Tue, 21 Mar 2000 07:46:57 +0100 Message-ID: <23423.953621217@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D6B353.FA58BB15@softweyr.com>, Wes Peters writes: >Poul-Henning Kamp wrote: >> >> In message <200003182031.NAA97975@harmony.village.org>, Warner Losh writes: >> >> >I'd like to be able to do some simple spl locking in a driver that I'm >> >writing. While I could go the splhigh() route, I'm concerned that >> >spending lots of time at splhigh could cause problems, and some of my >> >critical sections look to be very expensive. They only need >> >protection against the card itself, not against the entire system. It >> >just seems to be an overly large hammer. >> >> I miss this too. > >Semaphores? spl*() are semaphores. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 23:41:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 1D38E37BB4C for ; Mon, 20 Mar 2000 23:41:11 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (1554 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 21 Mar 2000 02:41:05 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Tue, 21 Mar 2000 02:41:05 -0500 From: Jim Mercer To: hackers@freebsd.org Subject: spontaneous reboots FreeBSD 3.x and 4.0-stable Message-ID: <20000321024104.S15100@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've got two systems, one a pentium 233 with adaptec 2940, scsi, using vinum running a big postgresql database, and a new one, dual pentium 550, dual adaptec 29160, not using vinum, and another big postgresql database. the first system runs 3.4-stable and gets spontaneous reboots infrequently, and there are no messages (dmesg, console or syslog) indicating why it rebooted. initially, i though it might be the vinum. the new system runs 4.0-stable, doesn't have vinum, and is spontaneously rebooting (several times in 48 hrs). again no messages indicting the problem. postgres runs as a non-root user. on the second system, it has rebooted during heavy database processing, but mysterously, has rebooted again within 30-40 minutes, even though the database processing doesn't automatically restart (ie. the second reboot was not caused by heavy processing, as there was no processing happening). has anybody had similar issues? solutions? suggestions? -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 20 23:52:35 2000 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 E1D8E37BCEC for ; Mon, 20 Mar 2000 23:52:24 -0800 (PST) (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 JAA25812; Tue, 21 Mar 2000 09:52:19 +0200 (IST) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id JAA19189; Tue, 21 Mar 2000 09:52:17 +0200 (IST) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Tue, 21 Mar 2000 09:52:17 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: Jim Mercer Cc: hackers@freebsd.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable In-Reply-To: <20000321024104.S15100@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Mar 2000, Jim Mercer wrote: > > i've got two systems, one a pentium 233 with adaptec 2940, scsi, using vinum > running a big postgresql database, and a new one, dual pentium 550, dual adaptec > 29160, not using vinum, and another big postgresql database. > > the first system runs 3.4-stable and gets spontaneous reboots infrequently, > and there are no messages (dmesg, console or syslog) indicating why it rebooted. > > initially, i though it might be the vinum. > > the new system runs 4.0-stable, doesn't have vinum, and is spontaneously > rebooting (several times in 48 hrs). again no messages indicting the problem. > > postgres runs as a non-root user. > > on the second system, it has rebooted during heavy database processing, but > mysterously, has rebooted again within 30-40 minutes, even though the > database processing doesn't automatically restart (ie. the second reboot > was not caused by heavy processing, as there was no processing happening). > > has anybody had similar issues? solutions? suggestions? I have (had?) some similar reboots, but I'm not sure it's the same. Still, it's another data point: I have a 133MHz Pentium with two IDE disks, running Postgresql over vinum. The machine is underpowered (only 32MB RAM, so it swaps heavily when more than 2-3 clients are concurrently active), and under heavy loads it rebooted several times. Naturaly, it all stoppoed once I added dumping to the config to debug it ;-) It also used to give bad file descriptor errors for files both on the vinum volumes and on other volumes in the nightly cron runs. What's even weirder is that some of these bad file descriptor errors disappeared (files were back to normal when I came to check in the morning). I thought this was all related to one of the disks being flaky (it has a large area with bad sectors that I just partitioned around), but your description kinda rings a bell. Anyway, I haven't seen any of these reboots for about 3 weeks now, but would sure like to get to the bottom of this, if I can. > > -- > [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] > [ Reptilian Research -- Longer Life through Colder Blood ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 0: 7:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 20E2D37BBC6 for ; Tue, 21 Mar 2000 00:07:44 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (2472 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 21 Mar 2000 03:07:39 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Tue, 21 Mar 2000 03:07:39 -0500 From: Jim Mercer To: Nadav Eiron Cc: hackers@freebsd.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable Message-ID: <20000321030738.T15100@reptiles.org> References: <20000321024104.S15100@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from nadav@cs.Technion.AC.IL on Tue, Mar 21, 2000 at 09:52:17AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 09:52:17AM +0200, Nadav Eiron wrote: > I have (had?) some similar reboots, but I'm not sure it's the same. Still, > it's another data point: I have a 133MHz Pentium with two IDE disks, > running Postgresql over vinum. The machine is underpowered (only 32MB RAM, > so it swaps heavily when more than 2-3 clients are concurrently active), > and under heavy loads it rebooted several times. both my machines have more than adequate RAM (384 Meg and 512 Meg). one runs vinum, the other doesn't. (in fact the one running vinum reboots less frequently than the one without vinum). > Naturaly, it all stoppoed > once I added dumping to the config to debug it ;-) i considered adding this, but even with the reboots, i need the systems in production, and i suspect that adding the debug stuff would cause the system to wait for manual intervention. > It also used to give > bad file descriptor errors for files both on the vinum volumes and on > other volumes in the nightly cron runs. What's even weirder is that some > of these bad file descriptor errors disappeared (files were back to normal > when I came to check in the morning). I thought this was all related to > one of the disks being flaky (it has a large area with bad sectors that I > just partitioned around), but your description kinda rings a bell. i haven't seen the bad file descriptor problem. > Anyway, > I haven't seen any of these reboots for about 3 weeks now, but would sure > like to get to the bottom of this, if I can. so, adding debug to the kernel "fixed" it? -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 0:14:45 2000 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 1449037BC0A for ; Tue, 21 Mar 2000 00:14:39 -0800 (PST) (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 KAA26253; Tue, 21 Mar 2000 10:14:48 +0200 (IST) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id KAA16250; Tue, 21 Mar 2000 10:14:47 +0200 (IST) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Tue, 21 Mar 2000 10:14:47 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: Jim Mercer Cc: hackers@freebsd.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable In-Reply-To: <20000321030738.T15100@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Mar 2000, Jim Mercer wrote: > both my machines have more than adequate RAM (384 Meg and 512 Meg). > > one runs vinum, theother doesn't. (in fact the one running vinum reboots > less frequently than the one without vinum). > > > Naturaly, it all stoppoed > > once I added dumping to the config to debug it ;-) > > i considered adding this, but even with the reboots, i need the systems in > production, and i suspect that adding the debug stuff would cause the system > to wait for manual intervention. I didn't add kernel debugger, just kernel dumps. All the time it takes on a reboot is the time your disks take to copy RAM to swapspace. Even with your RAM size it should be less than a minute. [snip] > > > Anyway, > > I haven't seen any of these reboots for about 3 weeks now, but would sure > > like to get to the bottom of this, if I can. > > so, adding debug to the kernel "fixed" it? The kernel is unchanged, so there's nothing that could really fix the problem. It did go away though (at least for now) :-) > > -- > [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] > [ Reptilian Research -- Longer Life through Colder Blood ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 0:30: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 904D037B720 for ; Tue, 21 Mar 2000 00:30:00 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (1832 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 21 Mar 2000 03:29:56 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Tue, 21 Mar 2000 03:29:55 -0500 From: Jim Mercer To: Nadav Eiron Cc: hackers@freebsd.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable Message-ID: <20000321032955.U15100@reptiles.org> References: <20000321030738.T15100@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from nadav@cs.Technion.AC.IL on Tue, Mar 21, 2000 at 10:14:47AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 10:14:47AM +0200, Nadav Eiron wrote: > > i considered adding this, but even with the reboots, i need the systems in > > production, and i suspect that adding the debug stuff would cause the system > > to wait for manual intervention. > > I didn't add kernel debugger, just kernel dumps. All the time it takes on > a reboot is the time your disks take to copy RAM to swapspace. Even with > your RAM size it should be less than a minute. so, how does one do this? /etc/rc.conf: dumpdev="/dev/da0s2b" # this is the swap partition yes? > > > I haven't seen any of these reboots for about 3 weeks now, but would sure > > > like to get to the bottom of this, if I can. > > > > so, adding debug to the kernel "fixed" it? > > The kernel is unchanged, so there's nothing that could really fix the > problem. It did go away though (at least for now) :-) well, fingers crossed, i'll give it a whirl. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 0:35:46 2000 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 EA8B537B774 for ; Tue, 21 Mar 2000 00:33:51 -0800 (PST) (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 KAA26659; Tue, 21 Mar 2000 10:33:58 +0200 (IST) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id KAA25154; Tue, 21 Mar 2000 10:33:57 +0200 (IST) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Tue, 21 Mar 2000 10:33:57 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: Jim Mercer Cc: hackers@freebsd.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable In-Reply-To: <20000321032955.U15100@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Mar 2000, Jim Mercer wrote: > On Tue, Mar 21, 2000 at 10:14:47AM +0200, Nadav Eiron wrote: > > I didn't add kernel debugger, just kernel dumps. All the time it takes on > > a reboot is the time your disks take to copy RAM to swapspace. Even with > > your RAM size it should be less than a minute. > > so, how does one do this? > > /etc/rc.conf: > dumpdev="/dev/da0s2b" # this is the swap partition > > yes? Yes. You should also have your kernel compiled with debugging information (and then installed stripped), so that you can make sense out of the dump if you get one. See: http://www.freebsd.org/handbook/kerneldebug.html > > > The kernel is unchanged, so there's nothing that could really fix the > > problem. It did go away though (at least for now) :-) > > well, fingers crossed, i'll give it a whirl. Good luck (though I doubt it'll change anything). > > -- > [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] > [ Reptilian Research -- Longer Life through Colder Blood ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 2: 2:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 738F637B5B8 for ; Tue, 21 Mar 2000 02:02:44 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA08002 for ; Tue, 21 Mar 2000 11:01:22 +0100 (CET) Message-Id: <200003211001.LAA08002@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-hackers@freebsd.org Subject: Re: need help Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 21 Mar 2000 03:19:28 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Mar 2000 11:01:22 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mourad Lakhdar writes: > > > > i have always problems when trying to work with the > inet_addr(), inet_network() ,inet_ntoa() functions ,when changin >in the ip_input file: > i got error like(when making): > ip_input.o(.text+0xce9):undefined reference to >'__inet_addr' > > >may you help? > WTF are you trying to do ? You can't use these routines in the kernel, they're part of a userland library. I get the impression that you're way over your head here. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 3: 8:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 7EE0037B762; Tue, 21 Mar 2000 03:08:07 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 4.0.1) with ESMTP id ; Tue, 21 Mar 2000 11:07:41 +0000 Received: from ADMIN ([10.100.1.20]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id G3Y8SZM6; Tue, 21 Mar 2000 11:06:04 -0000 Received: from [10.100.35.12] (helo=voodoo.pandhm.co.uk) by admin with esmtp (Exim 1.92 #1) id 12XMVz-0007Yi-00; Tue, 21 Mar 2000 11:07:59 +0000 Received: by voodoo.pandhm.co.uk (Postfix, from userid 104) id 1CC8E236; Tue, 21 Mar 2000 11:07:58 +0000 (GMT) Date: Tue, 21 Mar 2000 11:07:58 +0000 To: Dave McKay Cc: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ports security advisories.. Message-ID: <20000321110758.B913@voodoo.pandhm.co.uk> References: <20000320154614.A63670@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000320154614.A63670@elvis.mu.org>; from dave@mu.org on Mon, Mar 20, 2000 at 09:46:14PM -0000 X-Warning: Go away or I will replace you with a very small shell script. X-OS: FreeBSD 3.4-STABLE i386 X-Uptime: 5:01PM up 1:18, 8 users, load averages: 0.06, 0.11, 0.19 From: Dom.Mitchell@palmerharvey.co.uk (Dominic Mitchell) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 09:46:14PM -0000, Dave McKay wrote: > Is it really necessary to post the ports security advisories? > The exploitable programs are not part of the FreeBSD OS, they > are third party software. I think the proper place for these > is the Bugtraq mailing list on securityfocus.com. Also to add > to the arguments, most of the advisories are not FreeBSD > specific. Just to add a point here, some of the problems noted in these advisories *have* been FreeBSD specific, due to the way that a port has modified the default install, or suchlike. So it's definitely up to us to point this out. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Putting the doh! into dot-com.'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 3:44:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id CA84B37B87F for ; Tue, 21 Mar 2000 03:44:37 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (2181 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 21 Mar 2000 06:44:29 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Tue, 21 Mar 2000 06:44:28 -0500 From: Jim Mercer To: =?iso-8859-1?Q?Pawe=B3_Dubin?= Cc: hackers@freebsd.org, pgsql-general@postgresql.org Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable Message-ID: <20000321064428.W15100@reptiles.org> References: <00032112150500.00666@paweld> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <00032112150500.00666@paweld>; from paweld@suimed.tpnet.pl on Tue, Mar 21, 2000 at 12:06:05PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 12:06:05PM +0100, Pawe³ Dubin wrote: > > the first system runs 3.4-stable and gets spontaneous reboots infrequently, > > and there are no messages (dmesg, console or syslog) indicating why it rebooted. > > the new system runs 4.0-stable, doesn't have vinum, and is spontaneously > > rebooting (several times in 48 hrs). again no messages indicting the problem. > > We have similar problem (the same configuration but RH 5.1) (I dont know what > is vinum). It is probably from scsi board when we have 4 devices it reboots > every 3 days. now with 2 devices every 2 weeks. > > It is probably caused by intel -> driver -> scsi cooperation, because on K6 > system works ok. Maybe newer kernel with recognized pentium bugs. i wonder, it might actually be heat. in the first system, it was originally housed in an IBM PC 325 cabinet and rebooted quite frequently, then it was moved to a 48VDC rackmount chassis, with somewhat better airflow, and it rebooted less frequently. the new server is a rackmount case, but it doesn't have much in the way of extra fans. is it possible the reboots we are seeing are due to some component overheating? > Sorry for my english your english is fine. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 4:10:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 3A64537B63D for ; Tue, 21 Mar 2000 04:10:39 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id OAA62335; Tue, 21 Mar 2000 14:10:26 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Tue, 21 Mar 2000 14:10:25 +0200 (EET) From: Narvi To: MikeM Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unicode on FreeBSD In-Reply-To: <20000320194702.11223.qmail@web3101.mail.yahoo.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, 20 Mar 2000, MikeM wrote: > Has anyone thought of Unicode support on FreeBSD? > Depends on what you mean by 'Unicode support'. If you use a suitable encoding (UTF-8?) everything should work, only it might look strange, as userland doesn't support it. It is largely a 'application space' problem as I understand it - you need to modify each and every utility to know that file names should be treated as strings of wide characters. Toolkits providing a 'select file' std dialog need to be dealt with. > I think that it is inevitable that eventually FreeBSD > will *need* to support unicode if it wants to continue > as a viable operating system in the future. This means > that it probably will need to be modified from the > ground up. I am not well versed in the specifics of > what's needed, but if someone could explain it to me > I'd be gratefull. > See above for a subset. > Is it possible, or is it totally out of the question? > > What would it require? > > Is there any way of implementing partial support, > working in stages, untill it is fully supported? > > > Thanks, > Mike. > > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.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 Mar 21 6:55:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id D245337B9C2 for ; Tue, 21 Mar 2000 06:54:57 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id PAA05480 for ; Tue, 21 Mar 2000 15:54:55 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id PAA28098 for ; Tue, 21 Mar 2000 15:55:50 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id PAA27547 for hackers@freebsd.org; Tue, 21 Mar 2000 15:55:00 +0100 (CET) Date: Tue, 21 Mar 2000 15:55:00 +0100 (CET) From: Christoph Kukulies Message-Id: <200003211455.PAA27547@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: 100Bit Fast Ethernet EISA card - anyone? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there one at all? And if so, does anyone have one for sale/giving away? FreeBSD friend Aled Morris (aledm) was so kind to send me an FDDI DEFEA (Eisa) card for zero. Although I found a free EISA Motherboard now, I'm lacking a 100MBit Fast Ethernet card now to build the complete router. In the first place I thought I could use the DEFEA on an ISA slot as well so that I could use a PCI MB and put a cheapo 100MBit card into a PCI slot. But it turned out that the DEFEA is an EISA only board. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 7:30:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C3BBB37B944 for ; Tue, 21 Mar 2000 07:30:23 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA02547; Tue, 21 Mar 2000 10:31:17 -0500 (EST) Message-Id: <200003211531.KAA02547@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 21 Mar 2000 10:26:15 -0500 To: dg@root.com From: Dennis Subject: Re: if_fxp driver Cc: Wes Peters , hackers@FreeBSD.ORG In-Reply-To: <200003210445.UAA25057@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:45 PM 3/20/00 -0800, David Greenman wrote: >>I hope your happy, but do you know the answer to my question? Has the >>driver been updated recently? > > Not to fix the problem that you are reporting. The solution might be as >simple as adding another PHY identifier to the list of supported ones. I need >to find some time to sit down with one of the not-working cards and fiddle >with it. I was going to do that this past weekend, but then got sick with a >virus. It's on my list. Ok. Thanks. Mr. Peters thinks that I should spend a half day searching for, installing and testing the "latest driver" (of course latest depends on where you happen to download it from), when it seems to me that asking the developers if a particuar issue has been corrected is a more reasonable approach. Shoot me for using an available resource. Dennis Emerging Technologies, Inc. ---------------------------------------------------------------------------- --------- http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 8:26: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id 8208837B8D3 for ; Tue, 21 Mar 2000 08:25:57 -0800 (PST) (envelope-from adam@whizkidtech.net) Received: from WhizKid (r27.bfm.org [216.127.220.123]) by mail.bfm.org (Post.Office MTA v3.5.3 release 223 ID# 0-52399U2500L250S0V35) with SMTP id org; Tue, 21 Mar 2000 10:26:14 -0600 Message-Id: <3.0.6.32.20000321101838.00a4d6e0@mail85.pair.com> X-Sender: whizkid@mail85.pair.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 21 Mar 2000 10:18:38 -0600 To: MikeM , freebsd-hackers@FreeBSD.ORG From: "G. Adam Stanislav" Subject: Re: Unicode on FreeBSD In-Reply-To: <20000320194702.11223.qmail@web3101.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:47 20-03-2000 -0800, MikeM wrote: >Has anyone thought of Unicode support on FreeBSD? Certainly. >Is it possible, or is it totally out of the question? > >What would it require? > >Is there any way of implementing partial support, >working in stages, untill it is fully supported? I worked on Unicode support last year, but had to discontinue my work due to serious health problems (almost died). I am better now, but am not likely to resume this particular work in the near future. Anyway, I did partial support, with a UTF-8 package that is in the ports (I think it is called utrans). It allows you to convert between various Unicode encodings. As for console support, I do not see how full Unicode set of characters could be displayed on the standard console due to its hardware design which allows for a theoretical maximum of 256 characters, with a practical maximum even less. X Window certainly does not have that limitation, but that is not directly a matter of FreeBSD. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 9:16:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 3564D37B707 for ; Tue, 21 Mar 2000 09:16:49 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA26301; Tue, 21 Mar 2000 09:18:46 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003211718.JAA26301@troutmask.apl.washington.edu> Subject: Re: if_fxp driver In-Reply-To: <200003211531.KAA02547@etinc.com> from Dennis at "Mar 21, 2000 10:26:15 am" To: Dennis Date: Tue, 21 Mar 2000 09:18:45 -0800 (PST) Cc: dg@root.com, Wes Peters , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > Ok. Thanks. Mr. Peters thinks that I should spend a half day searching for, > installing and testing the "latest driver" (of course latest depends on > where you happen to download it from), when it seems to me that asking the > developers if a particuar issue has been corrected is a more reasonable > approach. > "A half day searching"? It took me 2 minutes. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_fxp.c http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_fxpreg.h http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_fxpvar.h -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 9:37: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E38C37B95F; Tue, 21 Mar 2000 09:37:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA81344; Tue, 21 Mar 2000 09:36:38 -0800 (PST) (envelope-from dillon) Date: Tue, 21 Mar 2000 09:36:38 -0800 (PST) From: Matthew Dillon Message-Id: <200003211736.JAA81344@apollo.backplane.com> To: FreeBSD MAIL Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Davicam dc0 driver References: <200003210311.RAA00995@mauibuilt.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a BookPC with a built in Davi Comm 10/100 ethernet card. : :I am always getting : :/kernel: dc0: watchdog timeout : :every few minutes.. : :Can thease errors be stopped? : : :Thank you for any reply : :RP :puga@mauibuilt.com If you've got a kernel build environment setup, try the following patch to if_dc (suggested to me by Bill Paul a few months ago). I would be interested in knowing if it reduces the number of wdog timeouts you get. It seems to help mine. -Matt Matthew Dillon Index: if_dc.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_dc.c,v retrieving revision 1.7 diff -u -r1.7 if_dc.c --- if_dc.c 2000/01/24 17:19:37 1.7 +++ if_dc.c 2000/01/26 23:27:20 @@ -1548,7 +1548,7 @@ break; case DC_DEVICEID_82C115: sc->dc_type = DC_TYPE_PNICII; - sc->dc_flags |= DC_TX_POLL|DC_TX_USE_TX_INTR; + sc->dc_flags |= DC_TX_POLL|DC_TX_INTR_ALWAYS; break; case DC_DEVICEID_82C168: sc->dc_type = DC_TYPE_PNIC; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 9:54:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ultra.levelogic.com (ultra.levelogic.com [209.75.61.10]) by hub.freebsd.org (Postfix) with ESMTP id 75EB237BA07 for ; Tue, 21 Mar 2000 09:54:19 -0800 (PST) (envelope-from arthur@levelogic.com) Message-ID: <38D7B6F9.55CA61DD@levelogic.com> Date: Tue, 21 Mar 2000 09:52:57 -0800 From: "Arthur M. Kang" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jim Mercer Cc: =?iso-8859-1?Q?Pawe=B3?= Dubin , hackers@freebsd.org, pgsql-general@postgresql.org Subject: Re: [GENERAL] Re: spontaneous reboots FreeBSD 3.x and 4.0-stable References: <00032112150500.00666@paweld> <20000321064428.W15100@reptiles.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Had this rebooting problem before for a while and it drove me NUTZ! Inst= alled RedHat and FreeBSD and both rebooted periodically. Don't know if my solution wi= ll help or not, but what was causing my reboots was the system BIOS. The options for Pow= er Management in the system BIOS should have some settings for the monitor as well as t= he hard drive. I was finding that the spinning down of the hard drive caused the machine= to reboot. No traces in any error logs or anything... Hope that helps somebody...somewhere... :) Arthur Jim Mercer wrote: > On Tue, Mar 21, 2000 at 12:06:05PM +0100, Pawe=B3 Dubin wrote: > > > the first system runs 3.4-stable and gets spontaneous reboots infre= quently, > > > and there are no messages (dmesg, console or syslog) indicating why= it rebooted. > > > the new system runs 4.0-stable, doesn't have vinum, and is spontane= ously > > > rebooting (several times in 48 hrs). again no messages indicting t= he problem. > > > > We have similar problem (the same configuration but RH 5.1) (I dont k= now what > > is vinum). It is probably from scsi board when we have 4 devices it r= eboots > > every 3 days. now with 2 devices every 2 weeks. > > > > It is probably caused by intel -> driver -> scsi cooperation, because= on K6 > > system works ok. Maybe newer kernel with recognized pentium bugs. > > i wonder, it might actually be heat. > > in the first system, it was originally housed in an IBM PC 325 cabinet = and > rebooted quite frequently, then it was moved to a 48VDC rackmount chass= is, > with somewhat better airflow, and it rebooted less frequently. > > the new server is a rackmount case, but it doesn't have much in the way= of > extra fans. > > is it possible the reboots we are seeing are due to some component over= heating? > > > Sorry for my english > > your english is fine. > > -- > [ Jim Mercer jim@reptiles.org +1 416 506-0= 654 ] > [ Reptilian Research -- Longer Life through Colder Blood = ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Cod= e. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 11:14:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from getafix.cs.rpi.edu (getafix.cs.rpi.edu [128.213.8.214]) by hub.freebsd.org (Postfix) with ESMTP id C087337BBE7 for ; Tue, 21 Mar 2000 11:14:42 -0800 (PST) (envelope-from chris@getafix.cs.rpi.edu) Received: (from chris@localhost) by getafix.cs.rpi.edu (8.9.3/8.9.3) id OAA00331 for hackers@FreeBSD.ORG; Tue, 21 Mar 2000 14:14:39 -0500 (EST) (envelope-from chris) Date: Tue, 21 Mar 2000 14:14:39 -0500 From: Chris Parker To: hackers@FreeBSD.ORG Subject: Re: spontaneous reboots FreeBSD 3.x and 4.0-stable Message-ID: <20000321141439.A300@getafix.cs.rpi.edu> References: <20000321024104.S15100@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000321024104.S15100@reptiles.org>; from jim@reptiles.org on Tue, Mar 21, 2000 at 02:41:05AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I don't have quite the same setup but I do seem to suffer from the spontaneous reboot problem - with a twist. It only happens when I'm in X. Happens every couple of days. Mine is an Abit BP6 motherboard with dual Celeron 400s, 256MB RAM. I'm not using vinum, I'm not using anything spiffy other than a USB keyboard. Everything locks for a second and then *boom* reboot. And then I get this after kernel.config q's out: avail memory = 256589824 (250576K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 10 IOAPIC #0 intpin 18 -> irq 11 IOAPIC #0 intpin 19 -> irq 5 AP #1 (PHY# 1) failed! panic y/n? [y] panic: bye-bye mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 Uptime: 0s "neat." It didn't do this under 3.4. Any ideas? .chris On Tue, Mar 21, 2000 at 02:41:05AM -0500, Jim Mercer wrote: > > i've got two systems, one a pentium 233 with adaptec 2940, scsi, using vinum > running a big postgresql database, and a new one, dual pentium 550, dual adaptec > 29160, not using vinum, and another big postgresql database. > > the first system runs 3.4-stable and gets spontaneous reboots infrequently, > and there are no messages (dmesg, console or syslog) indicating why it rebooted. > > initially, i though it might be the vinum. > > the new system runs 4.0-stable, doesn't have vinum, and is spontaneously > rebooting (several times in 48 hrs). again no messages indicting the problem. > > postgres runs as a non-root user. > > on the second system, it has rebooted during heavy database processing, but > mysterously, has rebooted again within 30-40 minutes, even though the > database processing doesn't automatically restart (ie. the second reboot > was not caused by heavy processing, as there was no processing happening). > > has anybody had similar issues? solutions? suggestions? -- Chris Parker Department of Computer Science Graduate Student, Labstaff http://www.cs.rpi.edu/~parkerc/ Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 11:38:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 59D2537B960 for ; Tue, 21 Mar 2000 11:38:49 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA05059; Tue, 21 Mar 2000 20:25:44 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01376; Tue, 21 Mar 2000 20:07:16 +0100 (CET) (envelope-from wilko) Date: Tue, 21 Mar 2000 20:07:16 +0100 From: Wilko Bulte To: Christoph Kukulies Cc: hackers@freebsd.org Subject: Re: 100Bit Fast Ethernet EISA card - anyone? Message-ID: <20000321200716.H966@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <200003211455.PAA27547@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003211455.PAA27547@gil.physik.rwth-aachen.de>; from kuku@gilberto.physik.RWTH-Aachen.DE on Tue, Mar 21, 2000 at 03:55:00PM +0100 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 03:55:00PM +0100, Christoph Kukulies wrote: > Is there one at all? And if so, does anyone have one for sale/giving away? They seem to exist (rumor has it etc..) > In the first place I thought I could use the DEFEA on an ISA slot > as well so that I could use a PCI MB and put a cheapo 100MBit card > into a PCI slot. > > But it turned out that the DEFEA is an EISA only board. ISA fits in EISA slots. Not the other way around. An FDDI ISA card would not be much fun (performance wise) -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 11:39:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B9DDB37BF0A for ; Tue, 21 Mar 2000 11:39:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA05064; Tue, 21 Mar 2000 20:25:50 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA01129; Tue, 21 Mar 2000 19:49:39 +0100 (CET) (envelope-from wilko) Date: Tue, 21 Mar 2000 19:49:39 +0100 From: Wilko Bulte To: Bill Fenner Cc: stefan@csudsu.com, newton@internode.com.au, freebsd-hackers@freebsd.org Subject: Re: WaveLAN/IEEE Turbo (Silver) Message-ID: <20000321194939.C966@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <200003210232.SAA05069@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003210232.SAA05069@windsor.research.att.com>; from fenner@research.att.com on Mon, Mar 20, 2000 at 06:32:49PM -0800 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 06:32:49PM -0800, Bill Fenner wrote: > The FreeBSD driver doesn't currently support encryption, correct. > The Linux driver does, so perhaps it would be fairly easy to port the > functionality, and the Linux driver is dual-licensed under GPL and BSD > licenses so there's no worry of GPL contamination. > ftp://sourceforge.org/pcmcia/contrib/wavelan2_cs-6.00.tar.gz > > I'm going to have to figure this out soon, since we're going to turn > encryption on soon. I'd be ecstatic if someone else figured it out > first =) > Guido van Rooij was working on encryption when I last spoke to him. Try guido@gvr.org for a status poll. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 11:51:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8B86137BD90 for ; Tue, 21 Mar 2000 11:51:04 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id MAA07221; Tue, 21 Mar 2000 12:50:35 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D7D2D2.64349BD5@softweyr.com> Date: Tue, 21 Mar 2000 12:51:46 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: dg@root.com, hackers@FreeBSD.ORG Subject: Re: if_fxp driver References: <200003211531.KAA02547@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > At 08:45 PM 3/20/00 -0800, David Greenman wrote: > >>I hope your happy, but do you know the answer to my question? Has the > >>driver been updated recently? > > > > Not to fix the problem that you are reporting. The solution might be as > >simple as adding another PHY identifier to the list of supported ones. I need > >to find some time to sit down with one of the not-working cards and fiddle > >with it. I was going to do that this past weekend, but then got sick with a > >virus. It's on my list. > > Ok. Thanks. Mr. Peters thinks that I should spend a half day searching for, > installing and testing the "latest driver" (of course latest depends on > where you happen to download it from), when it seems to me that asking the > developers if a particuar issue has been corrected is a more reasonable > approach. > > Shoot me for using an available resource. Shoot you for wasting a resource that could better spend their time developing FreeBSD instead of answering questions for people to lazy or stupid to look for themselves. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 11:55:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id B76DD37BBAA; Tue, 21 Mar 2000 11:55:31 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id UAA18036; Tue, 21 Mar 2000 20:55:27 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id UAA02015; Tue, 21 Mar 2000 20:56:21 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id UAA29653; Tue, 21 Mar 2000 20:55:34 +0100 (CET) Date: Tue, 21 Mar 2000 20:55:34 +0100 From: Christoph Kukulies To: wilko@freebsd.org Cc: Christoph Kukulies , hackers@freebsd.org Subject: Re: 100Bit Fast Ethernet EISA card - anyone? Message-ID: <20000321205534.A29602@gil.physik.rwth-aachen.de> References: <200003211455.PAA27547@gil.physik.rwth-aachen.de> <20000321200716.H966@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000321200716.H966@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Tue, Mar 21, 2000 at 08:07:16PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 08:07:16PM +0100, Wilko Bulte wrote: > On Tue, Mar 21, 2000 at 03:55:00PM +0100, Christoph Kukulies wrote: > > > Is there one at all? And if so, does anyone have one for sale/giving away? > > They seem to exist (rumor has it etc..) ... > > ISA fits in EISA slots. Not the other way around. Yeah, you're right. I never really dealt with EISA Hardware through the years. Forgive my ignorance. > > An FDDI ISA card would not be much fun (performance wise) Also true. > > -- > Wilko Bulte Arnhem, The Netherlands > http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 15:42:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 4F42E37C201 for ; Tue, 21 Mar 2000 15:42:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id PAA33698; Tue, 21 Mar 2000 15:41:59 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Mar 2000 15:41:58 -0800 (PST) From: Doug White To: Kasper Kristiansson Cc: hackers@FreeBSD.ORG Subject: Re: Loginproblem In-Reply-To: <200003182324.AA2333933860@swebase.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 This belongs on freebsd-questions@freebsd.org. On Sat, 18 Mar 2000, Kasper Kristiansson wrote: > When i login this message comes, > > ** Who are you? (Unable to look up login name)** > > and when i do a whoami it answers whit my uid, why has my server lost the loginnames??? Log in as root and 'vipw', then fix your password file. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 17:52:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1F1AE37BF7D for ; Tue, 21 Mar 2000 17:52:12 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p14-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.15]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA14143; Wed, 22 Mar 2000 10:51:51 +0900 (JST) Message-ID: <38D80B15.C54C61F5@newsguy.com> Date: Wed, 22 Mar 2000 08:51:49 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wes Peters Cc: Warner Losh , Guido van Rooij , hackers@FreeBSD.ORG Subject: Re: splFoo() question References: <20000320210008.A59405@gvr.gvr.org> <200003182031.NAA97975@harmony.village.org> <200003202057.NAA17486@harmony.village.org> <38D6C5EB.E96A6514@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > A per-driver mutex, perhaps? This would save us from potential > deadly embraces within a single driver, at least. I'm surprised no one mentioned the following yet. splFoo() is one of FreeBSD curses. While what we have is much better than the older splFoo() stuff, it's still pretty much the giant kernel lock thingy. We need to get away from that of many reasons. Well, one of the reasons is better SMP. Alas, BSD/OS allegedly have a kick-ass SMP, which means they have replaced the splFoo() ickyness. It would be useful to know if we'll be, indeed, using an alternative they have developed, or if we are going to roll our own. Now, there are TONS of research in OS concerning this. As a matter of fact, we could even copy what _Linux_ is using to solve the problem. This is not the place for NIH attacks. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org dcs@zurichgnomes.bsdonspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 19:19:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 07C3A37C0DF for ; Tue, 21 Mar 2000 19:19:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id WAA49869; Tue, 21 Mar 2000 22:19:35 -0500 (EST) Date: Tue, 21 Mar 2000 22:19:35 -0500 (EST) From: "Matthew N. Dodd" To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: 100Bit Fast Ethernet EISA card - anyone? In-Reply-To: <200003211455.PAA27547@gil.physik.rwth-aachen.de> 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, 21 Mar 2000, Christoph Kukulies wrote: > Is there one at all? And if so, does anyone have one for sale/giving away? Well, you can try some of the 3c597 boards but they aren't gonna be able to fill the pipe, or keep up very well. I've got a NetFlex 3/E with a 100 meg module, but have not been able to get it working reliablly. Your best bet is to pick up an EISA/PCI motherboard. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 19:20:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C6D4837BD4C; Tue, 21 Mar 2000 19:20:15 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id WAA49900; Tue, 21 Mar 2000 22:20:14 -0500 (EST) Date: Tue, 21 Mar 2000 22:20:14 -0500 (EST) From: "Matthew N. Dodd" To: wilko@FreeBSD.ORG Cc: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: 100Bit Fast Ethernet EISA card - anyone? In-Reply-To: <20000321200716.H966@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Mar 2000, Wilko Bulte wrote: > An FDDI ISA card would not be much fun (performance wise) But they exist, as do ISA 100baseTX cards. :) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 21:39:34 2000 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 C953D37C0C3 for ; Tue, 21 Mar 2000 21:39:19 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id GAA03990; Wed, 22 Mar 2000 06:39:13 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: hackers@freebsd.org Subject: IBM Netfinity 5600 From: Dag-Erling Smorgrav Date: 22 Mar 2000 06:39:12 +0100 Message-ID: Lines: 56 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following patch adds support for the host to pci bridge on IBM's new Netfinity 5600. It's based on the 3.4-RELEASE code, I don't know if it'll apply to 4.0 or 5.0. It's also quite a hack; I guess what you'd really want to do is either use NBUS instead of 2, or extract some kind of "correct" value from the chipset. Also, I have no idea what the chipset's real name is. Without the patch, the second (64-bit) PCI bus will not work, which is kind of a bummer since the first (32-bit) PCI bus only has two slots. For the curious, this was hacked up and tested on Netfinity 5600 assembly no. 52, which we have on loan from IBM to replace two downed servers (the disk enclosure died on us - never buy Trimm again!). It's a lovely little thang, I'd absolutely *love* to have a truckload of them in my server room... Kudos to Zippy for pointing us in the right direction. Index: pcisupport.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v retrieving revision 1.86.2.13 diff -u -r1.86.2.13 pcisupport.c --- pcisupport.c 1999/11/01 22:48:34 1.86.2.13 +++ pcisupport.c 2000/03/22 05:30:07 @@ -233,8 +233,14 @@ } #endif } - +/* Hackety-hack-hack */ +static void +fixbushigh_nf5600(pcici_t tag) +{ + tag->secondarybus = tag->subordinatebus = 2; +} + static const char* chipset_probe (pcici_t tag, pcidi_t type) { @@ -242,6 +248,10 @@ char *descr; switch (type) { + /* IBM Netfinity 5600 */ + case 0x00091166: + fixbushigh_nf5600(tag); + return ("IBM Netfinity 5600 host to PCI bridge"); /* Intel -- vendor 0x8086 */ case 0x00088086: /* Silently ignore this one! What is it, anyway ??? */ DES (half past six aye emm, still at work...) -- 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 Tue Mar 21 21:55:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 10EEA37BD89 for ; Tue, 21 Mar 2000 21:55:48 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id VAA07257 for ; Tue, 21 Mar 2000 21:55:40 -0800 (PST) (envelope-from nsayer@yoda.sftw.com) Received: (from nsayer@localhost) by yoda.sftw.com (8.9.3/8.9.3) id VAA56886 for freebsd-hackers@freebsd.org; Tue, 21 Mar 2000 21:55:39 -0800 (PST) (envelope-from nsayer) Date: Tue, 21 Mar 2000 21:55:39 -0800 (PST) From: Nick Sayer Message-Id: <200003220555.VAA56886@yoda.sftw.com> To: freebsd-hackers@freebsd.org Subject: md_image compression? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sort of thinking in my head about adding the ability for the md driver to handle gziped images. md's drvinit() looks like the perfect place to do this. if strcmp(type,"md_image_gzip") then gunzip the image and so on. Obviously this trades RAM for disk space. The target implementation is the i-opener -> X terminal transmogrification. I think I can cram the whole thing into the 16M flash card, and with compression of that image, I can cram a lot more. To implement it, I have some questions: 1. Is there a way to de-allocate or otherwise reuse the original compressed image after the unzip is finished? 2. What is the best strategy for allocating the output image? malloc(9)? 3. This would effectively add libz to the kernel. Does anyone object, given the proviso that this whole mess would hide inside of an option (MD_PRELOAD_GZIP springs to mind)? Perhaps instead the md unzipper could be loaded as a module. The module could be thrown away using the same mechanism as #1 once the decompression is finished. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 22:17:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 105F937C0D4 for ; Tue, 21 Mar 2000 22:17:36 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA32494; Wed, 22 Mar 2000 07:15:31 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003220615.HAA32494@info.iet.unipi.it> Subject: IOpener ? In-Reply-To: <200003220555.VAA56886@yoda.sftw.com> from Nick Sayer at "Mar 21, 2000 09:55:39 pm" To: Nick Sayer Date: Wed, 22 Mar 2000 07:15:31 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i think i missed something interesting... does someone have more info on what is the IOpener (more specifically on hw features, which i seem unable to find on the netpliance web site). thanks luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 22:23:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.scizzors.net (24.66.198.155.ab.wave.home.com [24.66.198.155]) by hub.freebsd.org (Postfix) with ESMTP id 2ED3037C106 for ; Tue, 21 Mar 2000 22:23:37 -0800 (PST) (envelope-from adam@scizzors.net) Received: from fatman.scizzors.net (adam@fatman.scizzors.net [10.0.100.5]) by gw.scizzors.net (8.9.3/8.9.3) with ESMTP id XAA06450; Tue, 21 Mar 2000 23:24:09 -0700 (MST) (envelope-from adam@scizzors.net) Date: Tue, 21 Mar 2000 23:23:21 -0700 (MST) From: Adam Serediuk To: luigi@info.iet.unipi.it Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IOpener ? (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You might want to try my website, http://www.i-opener-linux.net ;) -------- Adam Serediuk adam@scizzors.net http://www.scizzors.net On Wed, 22 Mar 2000, Adam wrote: > ---------- Forwarded message ---------- > Date: Wed, 22 Mar 2000 07:15:31 +0100 (CET) > From: Luigi Rizzo > To: Nick Sayer > Cc: freebsd-hackers@FreeBSD.ORG > Subject: IOpener ? > > Hi, > i think i missed something interesting... does someone have > more info on what is the IOpener (more specifically on hw features, > which i seem unable to find on the netpliance web site). > > thanks > luigi > -----------------------------------+------------------------------------- > Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione > http://www.iet.unipi.it/~luigi/ . Universita` di Pisa > TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) > Mobile +39-347-0373137 > -----------------------------------+------------------------------------- > > > 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 Mar 21 22:32:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7374637C0D4 for ; Tue, 21 Mar 2000 22:32:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA29641; Wed, 22 Mar 2000 07:32:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nick Sayer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: md_image compression? In-reply-to: Your message of "Tue, 21 Mar 2000 21:55:39 PST." <200003220555.VAA56886@yoda.sftw.com> Date: Wed, 22 Mar 2000 07:32:04 +0100 Message-ID: <29639.953706724@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003220555.VAA56886@yoda.sftw.com>, Nick Sayer writes: > >I'm sort of thinking in my head about adding the ability for the >md driver to handle gziped images. md's drvinit() looks like >the perfect place to do this. if strcmp(type,"md_image_gzip") then >gunzip the image and so on. > >Obviously this trades RAM for disk space. The target implementation >is the i-opener -> X terminal transmogrification. I think I can cram >the whole thing into the 16M flash card, and with compression of that >image, I can cram a lot more. To implement it, I have some questions: > >1. Is there a way to de-allocate or otherwise reuse the original >compressed image after the unzip is finished? currently not. >2. What is the best strategy for allocating the output image? >malloc(9)? Use the code already in MD which recognizes empty sectors, that will give you a little bit of compression. >3. This would effectively add libz to the kernel. We actually already have a unzip'er available in the kernel, the one which was used for unzip'ing a.out executables. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 22:42:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B3BA437BC00 for ; Tue, 21 Mar 2000 22:42:17 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA08496; Tue, 21 Mar 2000 23:42:05 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D86B8C.51CF88EF@softweyr.com> Date: Tue, 21 Mar 2000 23:43:24 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Adam Serediuk Cc: luigi@info.iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: IOpener ? (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adam Serediuk wrote: > > > From: Luigi Rizzo > > > > Hi, > > i think i missed something interesting... does someone have > > more info on what is the IOpener (more specifically on hw features, > > which i seem unable to find on the netpliance web site). > > You might want to try my website, http://www.i-opener-linux.net ;) Or, more close to home, http://www.netbsd.org/Changes/#iopener_booted_with_netbsd -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 21 22:56:59 2000 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 189C837C086 for ; Tue, 21 Mar 2000 22:56:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA20067; Tue, 21 Mar 2000 22:57:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Nick Sayer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: md_image compression? In-reply-to: Your message of "Tue, 21 Mar 2000 21:55:39 PST." <200003220555.VAA56886@yoda.sftw.com> Date: Tue, 21 Mar 2000 22:57:15 -0800 Message-ID: <20064.953708235@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sort of thinking in my head about adding the ability for the > md driver to handle gziped images. md's drvinit() looks like And you can't load the kernel and the gzipped images from the boot loader, letting the boot loader decompress the stuff and just using the existing MD_ROOT option hook to load it? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 6:11:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0BB1037C092 for ; Wed, 22 Mar 2000 06:11:28 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12Xlqz-000BTg-00 for freebsd-hackers@FreeBSD.org; Wed, 22 Mar 2000 16:11:21 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.org Subject: Re: openssh + krb5 (followup) In-reply-to: Your message of "Sat, 18 Mar 2000 13:01:09 +0200." <1834.953377269@axl.ops.uunet.co.za> Date: Wed, 22 Mar 2000 16:11:21 +0200 Message-ID: <44123.953734281@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Mar 2000 13:01:09 +0200, Sheldon Hearn wrote: > $ ssh -v -l root axl.ops > [...] > debug: Trying Kerberos V5 authentication. > ssh in free(): warning: chunk is already free. > [...] This was caused by a stale krb5.keytab on my box. It would have been nice if a more useful error message had been created, but the point is that kerberized ssh works. Interoperability with MIT krb5 still seems to be an issue. 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 Mar 22 6:12:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 175E137C068; Wed, 22 Mar 2000 06:12:41 -0800 (PST) (envelope-from danhil@cwnt.com) Received: from unspecified.host (ras3-p82.hfa.netvision.net.il [62.0.147.82]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id QAA16403; Wed, 22 Mar 2000 16:12:35 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Wed, 22 Mar 2000 16:02:02 +0200 Message-ID: <031701bf9407$5d000eb0$2e00a8c0@cwnt.co.il> From: "Daniel Hilevich" To: Cc: Subject: Loopback device and 127.0.0.1address Date: Wed, 22 Mar 2000 16:03:13 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anyone have an idea why after creating 128 loopack devices and configuring lo127 to 127.0.0.1 (instead of the default lo0) I am experiencing many problems in interprocess communication using sockets? Are lo0 and 127.0.0.1 (INADDR_LOOPBACK) tightly coupled? Thanks, --- Daniel Hilevich mailto:danhil@cwnt.com Tel: +972-4-9592203 ext. 214 Charlotte's Web Networks LTD. http://www.cwnt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 6:52:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9E56237BF64; Wed, 22 Mar 2000 06:51:57 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12XmU1-000BeB-00; Wed, 22 Mar 2000 16:51:41 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.org Cc: markm@FreeBSD.org Subject: Re: openssh + krb5 (followup) In-reply-to: Your message of "Wed, 22 Mar 2000 16:11:21 +0200." <44123.953734281@axl.ops.uunet.co.za> Date: Wed, 22 Mar 2000 16:51:41 +0200 Message-ID: <44774.953736701@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000 16:11:21 +0200, Sheldon Hearn wrote: > Interoperability with MIT krb5 still seems to be an issue. Bleh, more FUD. The problem is in operability with non-FreeBSD openssh! We use supported_authentication values for KRB5 that neither Datafellows SSH nor OpenBSD SSH use. :-( 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 Mar 22 7:11:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1-12.onmedia.com (mx1-12.onmedia.com [209.133.35.17]) by hub.freebsd.org (Postfix) with ESMTP id 68E1937BC22 for ; Wed, 22 Mar 2000 07:11:46 -0800 (PST) (envelope-from p_a_r@goplay.com) Received: from GP1 (root@localhost) by mx1-12.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id HAA22818 for hackers@freebsd.org; Wed, 22 Mar 2000 07:07:36 -0800 (PST) Received: from OnMedia Mail (GPX1) by mx1-12.onmedia.com ($Revision: 2.3 $) with OICP id 80880264; Wed, 22 Mar 2000 07:07:36 -0800 Subject: STABLE Date: Wed, 22 Mar 2000 07:07:13 -0800 Message-Id: <80880264.2.1636@mx1-12.onmedia.com> Reply-To: "p_a_r" From: "p_a_r" To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello were can i dównload freebsd3.4-stable as an iso image ?? +--------------------------------------------------------------------------+ | The coolest site for free home pages, email, chat, e-cards, movie info.. | | http://www.goplay.com - it's time to Go Play! | +--------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 7:17:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fischbach.saarnet.de (fischbach.saarnet.de [212.89.130.209]) by hub.freebsd.org (Postfix) with ESMTP id 206C537BE0F for ; Wed, 22 Mar 2000 07:17:20 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (IDENT:root@igate.aubi.de [212.89.130.136]) by fischbach.saarnet.de (8.9.3/8.9.3) with ESMTP id QAA01882; Wed, 22 Mar 2000 16:17:04 +0100 Received: from cisco.aubi.de (soraya.aubi.de [170.56.121.252]) by igate.aubi.de (8.9.1a/8.9.1) with ESMTP id QAA25339; Wed, 22 Mar 2000 16:17:01 +0100 Received: from exchange.aubi.de (exchange.aubi.de [170.56.121.4]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id QAA27730; Wed, 22 Mar 2000 16:58:53 +0100 (CET) Received: by exchange.aubi.de with Internet Mail Service (5.5.2650.21) id ; Wed, 22 Mar 2000 16:22:05 +0100 Message-ID: <506F47B83476D311975D00805FCC45E2017B5F@exchange.aubi.de> From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'p_a_r'" , hackers@FreeBSD.ORG Subject: RE: STABLE Date: Wed, 22 Mar 2000 16:22:04 +0100 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello were can i d=F3wnload freebsd3.4-stable as an iso image ?? do a "freebsd*.iso" search on http://ftpsearch.lycos.com --=20 Markus Doehr Tel: +49 6503 917 152 IT Admin Fax: +49 6503 917 190 SAP R/3 Basis e-Mail: doehrm@aubi.de AUBI Baubeschl=E4ge GmbH http://www.aubi.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 7:20:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1-13.onmedia.com (mx1-13.onmedia.com [209.133.35.11]) by hub.freebsd.org (Postfix) with ESMTP id 5729C37C144 for ; Wed, 22 Mar 2000 07:20:35 -0800 (PST) (envelope-from p_a_r@goplay.com) Received: from GP1 (root@localhost) by mx1-13.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id HAA12318 for freebsd-hackers@freebsd.org; Wed, 22 Mar 2000 07:17:35 -0800 (PST) Received: from OnMedia Mail (GPX1) by mx1-13.onmedia.com ($Revision: 2.3 $) with OICP id 80881121; Wed, 22 Mar 2000 07:17:35 -0800 Subject: ISO Date: Wed, 22 Mar 2000 07:17:12 -0800 Message-Id: <80881121.3.313@mx1-13.onmedia.com> Reply-To: "p_a_r" From: "p_a_r" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where can i download the 3-4-stable as an iso image?? +--------------------------------------------------------------------------+ | The coolest site for free home pages, email, chat, e-cards, movie info.. | | http://www.goplay.com - it's time to Go Play! | +--------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 7:20:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id D2E0137C144 for ; Wed, 22 Mar 2000 07:20:39 -0800 (PST) (envelope-from lloyd@brunel.uk1.vbc.net) Received: from localhost (lloyd@localhost) by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id PAA11322; Wed, 22 Mar 2000 15:20:33 GMT Date: Wed, 22 Mar 2000 15:20:33 +0000 (GMT) From: Lloyd Rennie To: p_a_r Cc: hackers@FreeBSD.ORG Subject: Re: STABLE In-Reply-To: <80880264.2.1636@mx1-12.onmedia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, p_a_r wrote: > Hello were can i d=F3wnload freebsd3.4-stable as an iso image ?? This should be on FreeBSD-questions. ftp://ftp.freebsd.org/.0/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso Or one of the MANY mirrors, as specified on www.freebsd.org -- Lloyd Rennie VBCnet GB Ltd=09 lloyd@vbc.net tel +44 (0) 117 929 1316 http://www.vbc.net fax +44 (0) 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 7:50:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law2-f159.hotmail.com [216.32.181.159]) by hub.freebsd.org (Postfix) with SMTP id 7DFED37BDD4 for ; Wed, 22 Mar 2000 07:50:49 -0800 (PST) (envelope-from karnanfans@hotmail.com) Received: (qmail 7492 invoked by uid 0); 22 Mar 2000 15:50:46 -0000 Message-ID: <20000322155046.7491.qmail@hotmail.com> Received: from 212.75.75.43 by www.hotmail.com with HTTP; Wed, 22 Mar 2000 07:50:46 PST X-Originating-IP: [212.75.75.43] From: "sdf dsg" To: freebsd-hackers@freebsd.org Subject: 3,4 Date: Wed, 22 Mar 2000 15:50:46 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When are the 3.4 release comming, and i dont want some beta things? Mike Hammer Helsingborg, Bårslöv ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 8: 7:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from swebase.com (mail.swebase.com [212.75.75.45]) by hub.freebsd.org (Postfix) with ESMTP id 942D337B9F8 for ; Wed, 22 Mar 2000 08:07:15 -0800 (PST) (envelope-from kasper@swebase.com) Date: Wed, 22 Mar 2000 17:10:20 +0100 Message-Id: <200003221710.AA7471348@swebase.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: "Kasper Kristiansson" Reply-To: To: Subject: IP X-Mailer: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder how i can add more than one ip number on the same network card. ./Kasper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 8:14:34 2000 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 9316D37C12C for ; Wed, 22 Mar 2000 08:14:29 -0800 (PST) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id LAA00560; Wed, 22 Mar 2000 11:13:09 -0500 (EST) Date: Wed, 22 Mar 2000 11:13:09 -0500 (EST) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Kasper Kristiansson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IP In-Reply-To: <200003221710.AA7471348@swebase.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 Use the "alias" descriptor in ifconfig. You may wish to attach alias addresses to a loopback interface rather than a physical interface, too. -marc On Wed, 22 Mar 2000, Kasper Kristiansson wrote: > I wonder how i can add more than one ip number on the same network card. > > ./Kasper > > > 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 Mar 22 8:26:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 85B2137B5C6 for ; Wed, 22 Mar 2000 08:26:24 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA06365 for ; Wed, 22 Mar 2000 11:27:46 -0500 (EST) Message-Id: <200003221627.LAA06365@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 22 Mar 2000 11:22:33 -0500 To: hackers@freebsd.org From: Dennis Subject: Re: if_fxp driver In-Reply-To: <38D7D2D2.64349BD5@softweyr.com> References: <200003211531.KAA02547@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:51 PM 3/21/00 -0700, you wrote: >Dennis wrote: >> >> At 08:45 PM 3/20/00 -0800, David Greenman wrote: >> >>I hope your happy, but do you know the answer to my question? Has the >> >>driver been updated recently? >> > >> > Not to fix the problem that you are reporting. The solution might be as >> >simple as adding another PHY identifier to the list of supported ones. I need >> >to find some time to sit down with one of the not-working cards and fiddle >> >with it. I was going to do that this past weekend, but then got sick with a >> >virus. It's on my list. >> >> Ok. Thanks. Mr. Peters thinks that I should spend a half day searching for, >> installing and testing the "latest driver" (of course latest depends on >> where you happen to download it from), when it seems to me that asking the >> developers if a particuar issue has been corrected is a more reasonable >> approach. >> >> Shoot me for using an available resource. > >Shoot you for wasting a resource that could better spend their time >developing FreeBSD instead of answering questions for people to lazy >or stupid to look for themselves. Its very sad what's happened to this team. If asking a yes/no question is a "waste of a resource" then there is no resource at all. Whatever, the linux driver works. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 9:27:53 2000 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 778C637BF13 for ; Wed, 22 Mar 2000 09:27:49 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA658020 for ; Wed, 22 Mar 2000 10:27:39 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id KAA01379 for ; Wed, 22 Mar 2000 10:27:39 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 22 Mar 2000 10:27:39 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@freebsd.org Subject: How a normal user can crash any linux system (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 anybody want to try this on -current? ron ---------- Forwarded message ---------- Date: Wed, 22 Mar 2000 16:02:40 +0100 From: Michael Lampe To: linux-kernel@vger.rutgers.edu Subject: How a normal user can crash any linux system I found the following by accident playing with PVM. If you start the 'gexample' from the examples directory with dimension=10000 and no of tasks=32 on one machine, it becomes almost immediately completely un- usable and begins with heavy swapping. Considering how much memory would be necessary for this computation before starting it would have avoided the trouble. So the processes go on allocating memory until physical memory and swap is exhausted. At this point processes are killed and now things are really becoming interesting: One would expect that the misbehaving gexample processes are killed or maybe other processes started by the same user. Actually random processes are killed: I've seen klogd, syslogd, cron, gpm and inetd disappear. In some cases the machine was unaccessible locally as well as remotely, but the kernel seemed to be still running -- ping showed the machine still up. Apart from the specific system processes that are killed, the problem can be reproduced under many different configurations. I have tried SuSE 6.0 with kernel 2.2.12, SuSE 6.2 with kernel 2.2.14, LinuxPPC R4/R5 (Red Hat 5.x based) with some recent 2.2.x kernels and finally the SuSE pre-release for PPC. PVM was 3.4.x. Any comments ???? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 9:29:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 715CC37BF1A for ; Wed, 22 Mar 2000 09:29:20 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id UAA27888; Wed, 22 Mar 2000 20:33:57 +0300 (MSK) Message-Id: <200003221733.UAA27888@aaz.links.ru> Subject: Re: ISO In-Reply-To: <80881121.3.313@mx1-13.onmedia.com> from "p_a_r" at "Mar 22, 0 07:17:12 am" To: p_a_r@goplay.com Date: Wed, 22 Mar 2000 20:33:57 +0300 (MSK) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 p_a_r writes: > Where can i download the 3-4-stable as an iso image?? ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 10: 0:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B824537C184 for ; Wed, 22 Mar 2000 10:00:49 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2MIO8e06969; Wed, 22 Mar 2000 10:24:08 -0800 (PST) Date: Wed, 22 Mar 2000 10:24:08 -0800 From: Alfred Perlstein To: "Ronald G. Minnich" Cc: hackers@FreeBSD.ORG, linux-kernel@vger.rutgers.edu, Michael Lampe Subject: Re: How a normal user can crash any linux system (fwd) Message-ID: <20000322102407.K7305@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from rminnich@lanl.gov on Wed, Mar 22, 2000 at 10:27:39AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is cross-posted to both linux-kernel and freebsd-hackers, please set your replies properly. > ---------- Forwarded message ---------- > Date: Wed, 22 Mar 2000 16:02:40 +0100 > From: Michael Lampe > To: linux-kernel@vger.rutgers.edu > Subject: How a normal user can crash any linux system > > I found the following by accident playing with PVM. If you start the > 'gexample' from the examples directory with dimension=10000 and no of > tasks=32 on one machine, it becomes almost immediately completely un- > usable and begins with heavy swapping. Considering how much memory > would be necessary for this computation before starting it would have > avoided the trouble. > > So the processes go on allocating memory until physical memory and swap > is exhausted. At this point processes are killed and now things are > really > becoming interesting: One would expect that the misbehaving gexample > processes are killed or maybe other processes started by the same user. > > Actually random processes are killed: I've seen klogd, syslogd, cron, > gpm > and inetd disappear. In some cases the machine was unaccessible locally > as > well as remotely, but the kernel seemed to be still running -- ping > showed > the machine still up. > > Apart from the specific system processes that are killed, the problem > can be > reproduced under many different configurations. I have tried SuSE 6.0 > with > kernel 2.2.12, SuSE 6.2 with kernel 2.2.14, LinuxPPC R4/R5 (Red Hat 5.x > based) > with some recent 2.2.x kernels and finally the SuSE pre-release for PPC. > PVM > was 3.4.x. > > Any comments ???? > * Ronald G. Minnich [000322 09:57] wrote: > anybody want to try this on -current? No, a normal user shouldn't be able to crash any unix box with proper limits in place, this local DoS only works if there are no limitations. Please people, this is a 20 year old trick that I'm really tired of hearing come up every other month. It's called a forkbomb with a twist, it's old, boring and doesn't affect people with properly configured systems. Please consult your Operating System's documentation on how to setup limits. If you want to know why random processes are sometimes killed then you need to buy and read an OS book. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 22 11:27:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 0F3A837C1B3; Wed, 22 Mar 2000 11:27:34 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id LAA80535; Wed, 22 Mar 2000 11:27:16 -0800 (PST) (envelope-from Doug@gorean.org) Date: Wed, 22 Mar 2000 11:27:16 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Daniel Hilevich Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Loopback device and 127.0.0.1address In-Reply-To: <031701bf9407$5d000eb0$2e00a8c0@cwnt.co.il> 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 Never cross-post to both -questions and -hackers, thanks. On Wed, 22 Mar 2000, Daniel Hilevich wrote: > Hi, > Does anyone have an idea why after creating 128 loopack devices and > configuring lo127 to 127.0.0.1 (instead of the default lo0) I am > experiencing many problems in interprocess communication using sockets? > Are lo0 and 127.0.0.1 (INADDR_LOOPBACK) tightly coupled? Errr... Haven't you just answered your own question? While we all wish it were otherwise I think you've already shown that there are places in the code that depend on lo0 == 127.0.0.1. Good luck, Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 11:55:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 21E7037C25B; Wed, 22 Mar 2000 11:55:50 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA59452; Wed, 22 Mar 2000 11:55:50 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 22 Mar 2000 11:55:49 -0800 (PST) From: Kris Kennaway To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.org, markm@FreeBSD.org Subject: Re: openssh + krb5 (followup) In-Reply-To: <44774.953736701@axl.ops.uunet.co.za> 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, 22 Mar 2000, Sheldon Hearn wrote: > > Interoperability with MIT krb5 still seems to be an issue. > > Bleh, more FUD. The problem is in operability with non-FreeBSD openssh! > We use supported_authentication values for KRB5 that neither Datafellows > SSH nor OpenBSD SSH use. :-( Hmm..I thought OpenBSD's OpenSSH didn't support krb5, only krb4. Regardless, we should fix this to bring ourselves in line (preferably with both). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 12:34:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-217.ricochet.net [204.179.134.217]) by hub.freebsd.org (Postfix) with ESMTP id 6907E37B636 for ; Wed, 22 Mar 2000 12:34:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00615; Wed, 22 Mar 2000 12:36:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003222036.MAA00615@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: freebsd-hackers@freebsd.org Subject: Re: md_image compression? In-reply-to: Your message of "Tue, 21 Mar 2000 21:55:39 PST." <200003220555.VAA56886@yoda.sftw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 12:36:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're using the loader, don't bother. It'll do this for you as it loads the image. See eg. how the install floppies work. > I'm sort of thinking in my head about adding the ability for the > md driver to handle gziped images. md's drvinit() looks like > the perfect place to do this. if strcmp(type,"md_image_gzip") then > gunzip the image and so on. > > Obviously this trades RAM for disk space. The target implementation > is the i-opener -> X terminal transmogrification. I think I can cram > the whole thing into the 16M flash card, and with compression of that > image, I can cram a lot more. To implement it, I have some questions: > > 1. Is there a way to de-allocate or otherwise reuse the original > compressed image after the unzip is finished? > > 2. What is the best strategy for allocating the output image? > malloc(9)? > > 3. This would effectively add libz to the kernel. Does anyone > object, given the proviso that this whole mess would hide inside > of an option (MD_PRELOAD_GZIP springs to mind)? Perhaps instead > the md unzipper could be loaded as a module. The module could > be thrown away using the same mechanism as #1 once the > decompression is finished. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 12:37: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id E5E1837BC4C for ; Wed, 22 Mar 2000 12:36:01 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id PAA00943 for hackers@freebsd.org; Wed, 22 Mar 2000 15:29:17 -0500 (EST) Date: Wed, 22 Mar 2000 15:29:17 -0500 From: Dan Moschuk To: hackers@freebsd.org Subject: Odd TCP problem Message-ID: <20000322152917.A919@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I've encounted somewhat of an odd problem that seemed to appear out of nowhere after my last -current upgrade a week or two ago. I rebuild last night and the problem is still around. Basically, near the end of the TCP transaction, consistant retransmission leads to the connection timing out. In the first example, my -current laptop is talking to a postgres database server running solaris7 on an ultra sparc. The program runs, and in the exact same spot each time (updating the last record) it stops. Here's a tcpdump: 14:20:01.894645 spirit.1100 > eclipse.5432: P 1176338:1176373(35) ack 136575 win 17520 (DF) 14:20:01.897467 eclipse.5432 > spirit.1100: P 136575:136624(49) ack 1176373 win 8760 (DF) 14:20:01.897951 spirit.1100 > eclipse.5432: P 1176373:1176756(383) ack 136624 win 17520 (DF) 14:20:01.908113 eclipse.5432 > spirit.1100: P 136624:136649(25) ack 1176756 win 8760 (DF) 14:20:01.910717 spirit.1100 > eclipse.5432: . 1176756:1178216(1460) ack 136649 win 17520 (DF) 14:20:01.911188 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:20:01.978311 eclipse.5432 > spirit.1100: . ack 1178216 win 8760 (DF) 14:20:02.977968 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:20:04.977986 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:20:08.978058 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:20:16.978187 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:20:32.978432 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) 14:21:04.978917 spirit.1100 > eclipse.5432: P 1178216:1178807(591) ack 136649 win 17520 (DF) This continues until spirit gives up and resets the connection. As you can see, its like eclipse vanished. Now, running a tcpdump on eclipse shows that these packets are in fact reaching the machine, its just not responding to them. It's not a problem with postgres itself, as the same problem can also be observed sending mail. Everything goes fine until after the DATA stage, where we become stuck in the above retransmission loop. Ideas? -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 12:54:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 796B837C292 for ; Wed, 22 Mar 2000 12:53:54 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com ([216.88.157.130]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id HAA00931; Thu, 23 Mar 2000 07:23:35 +1030 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA02709; Wed, 22 Mar 2000 12:53:07 -0800 (PST) (envelope-from grog) Date: Wed, 22 Mar 2000 12:53:07 -0800 From: Greg Lehey To: Poul-Henning Kamp Cc: Wes Peters , Warner Losh , hackers@FreeBSD.ORG Subject: Re: splFoo() question Message-ID: <20000322125307.B2183@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <38D6B353.FA58BB15@softweyr.com> <23423.953621217@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <23423.953621217@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Mar 21, 2000 at 07:46:57AM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 21 March 2000 at 7:46:57 +0100, Poul-Henning Kamp wrote: > In message <38D6B353.FA58BB15@softweyr.com>, Wes Peters writes: >> Poul-Henning Kamp wrote: >>> >>> In message <200003182031.NAA97975@harmony.village.org>, Warner Losh writes: >>> >>>> I'd like to be able to do some simple spl locking in a driver that I'm >>>> writing. While I could go the splhigh() route, I'm concerned that >>>> spending lots of time at splhigh could cause problems, and some of my >>>> critical sections look to be very expensive. They only need >>>> protection against the card itself, not against the entire system. It >>>> just seems to be an overly large hammer. >>> >>> I miss this too. >> >> Semaphores? > > spl*() are semaphores. spl*() are interrupt lockouts. The difference is very evident in an SMP environment. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 13:49: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 3EDBE37BF2E for ; Wed, 22 Mar 2000 13:48:56 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id OAA10216; Wed, 22 Mar 2000 14:48:36 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38D93F7E.7C5081@softweyr.com> Date: Wed, 22 Mar 2000 14:47:42 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp driver References: <200003211531.KAA02547@etinc.com> <200003221627.LAA06365@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > At 12:51 PM 3/21/00 -0700, you wrote: > >Dennis wrote: > >> > >> Shoot me for using an available resource. > > > >Shoot you for wasting a resource that could better spend their time > >developing FreeBSD instead of answering questions for people to lazy > >or stupid to look for themselves. > > Its very sad what's happened to this team. If asking a yes/no question is a > "waste of a resource" then there is no resource at all. Whatever, the linux > driver works. If you go back and read the list charter, something you seem to either be unaware of or completely ignore, this list is for discussing developing software on or for FreeBSD. Not for clueless newbie questions like "does FreeBSD work on my hardware?", that's what the -questions list is for. You seem to think the purpose of this list is for you to denigrate the work of the people who make FreeBSD, broadcast your own lovely little brand of FUD, and point out how much better Linux is for your customers. That's just fine, but this is NOT the appropriate channel for your opinions. If you want to present code that you think will fix the problem, fine. If you want to present diagnostics that think will fix the problem, fine. If you want user support questions, ask in -questions. If you want to opine that Linux is superior and FreeBSD a waste of time, as you have done so often lately, go do it somewhere else. This is not the appropriate venue. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 13:56: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 3899737C282 for ; Wed, 22 Mar 2000 13:55:58 -0800 (PST) (envelope-from jbryant@ppp-207-193-186-239.kscymo.swbell.net) Received: from ppp-207-193-186-239.kscymo.swbell.net ([207.193.186.239]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FRU00CB2FKNM6@mta1.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Wed, 22 Mar 2000 15:55:40 -0600 (CST) Received: (from jbryant@localhost) by ppp-207-193-186-239.kscymo.swbell.net (8.9.3/8.8.5) id PAA35282; Wed, 22 Mar 2000 15:55:31 -0600 (CST) Date: Wed, 22 Mar 2000 15:55:17 -0600 (CST) From: Jim Bryant Subject: Re: How a normal user can crash any linux system (fwd) In-reply-to: <20000322102407.K7305@fw.wintelcom.net> To: bright@wintelcom.net (Alfred Perlstein) Cc: rminnich@lanl.gov, hackers@FreeBSD.ORG, linux-kernel@vger.rutgers.edu, Michael.Lampe@iwr.uni-heidelberg.de Reply-To: kc5vdj@swbell.net Message-id: <200003222155.PAA35282@ppp-207-193-186-239.kscymo.swbell.net> MIME-version: 1.0 X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #8: Sat Oct 30 00:56:56 CDT 1999 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > This is cross-posted to both linux-kernel and freebsd-hackers, please > set your replies properly. > > > I found the following by accident playing with PVM. If you start the > > 'gexample' from the examples directory with dimension=10000 and no of > > tasks=32 on one machine, it becomes almost immediately completely un- > > usable and begins with heavy swapping. Considering how much memory > > would be necessary for this computation before starting it would have > > avoided the trouble. well, there are other ways to make a system slow to a crawl.... a good preventative measure is to never give shell accounts unless everyone is accountable. #!/bin/csh /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& /usr/games/primes 1 4294967295 >&/dev/null& # etc, ... # # [get the idea?] jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ kc5vdj@swbell.net KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81A KPC3+ & PK-232MBX Grid: EM28px ------------------------------------------------------------------------------ ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 14: 3: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D7CE937C29B for ; Wed, 22 Mar 2000 14:03:02 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2MMQNq13691; Wed, 22 Mar 2000 14:26:23 -0800 (PST) Date: Wed, 22 Mar 2000 14:26:23 -0800 From: Alfred Perlstein To: kc5vdj@swbell.net Cc: rminnich@lanl.gov, hackers@FreeBSD.ORG, linux-kernel@vger.rutgers.edu, Michael.Lampe@iwr.uni-heidelberg.de Subject: Re: How a normal user can crash any linux system (fwd) Message-ID: <20000322142623.R7305@fw.wintelcom.net> References: <20000322102407.K7305@fw.wintelcom.net> <200003222155.PAA35282@ppp-207-193-186-239.kscymo.swbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003222155.PAA35282@ppp-207-193-186-239.kscymo.swbell.net>; from jbryant@ppp-207-193-186-239.kscymo.swbell.net on Wed, Mar 22, 2000 at 03:55:17PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jim Bryant [000322 14:19] wrote: > In reply: > > This is cross-posted to both linux-kernel and freebsd-hackers, please > > set your replies properly. > > > > > I found the following by accident playing with PVM. If you start the > > > 'gexample' from the examples directory with dimension=10000 and no of > > > tasks=32 on one machine, it becomes almost immediately completely un- > > > usable and begins with heavy swapping. Considering how much memory > > > would be necessary for this computation before starting it would have > > > avoided the trouble. > > well, there are other ways to make a system slow to a crawl.... > > a good preventative measure is to never give shell accounts unless > everyone is accountable. True. > > #!/bin/csh > /usr/games/primes 1 4294967295 >&/dev/null& .... > /usr/games/primes 1 4294967295 >&/dev/null& > # etc, ... > # > # [get the idea?] why are you 'scripting' in csh? eww. No i don't get the idea, login.conf in FreeBSD is able to limit a user to a maximum amount of processes, I think even cputime limitations work but I haven't tried them. Yes, and one shouldn't give accounts out to irresponcible/thoughtless people. 'rmuser' is your friend. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 22 15: 0:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3C53037C352; Wed, 22 Mar 2000 15:00:17 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA16998; Wed, 22 Mar 2000 23:48:53 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA04118; Wed, 22 Mar 2000 23:30:55 +0100 (CET) (envelope-from wilko) Date: Wed, 22 Mar 2000 23:30:55 +0100 From: Wilko Bulte To: "Matthew N. Dodd" Cc: wilko@freebsd.org, Christoph Kukulies , hackers@freebsd.org Subject: Re: 100Bit Fast Ethernet EISA card - anyone? Message-ID: <20000322233055.I1709@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000321200716.H966@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from winter@jurai.net on Tue, Mar 21, 2000 at 10:20:14PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 10:20:14PM -0500, Matthew N. Dodd wrote: > On Tue, 21 Mar 2000, Wilko Bulte wrote: > > An FDDI ISA card would not be much fun (performance wise) > > But they exist, as do ISA 100baseTX cards. :) Duh.. Considering the premium price FDDI always had that is a surprise to me to be honest. Like a V8 in a VW Beetle ;-) -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: 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 Mar 22 15:58:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail3.aracnet.com (mail3.aracnet.com [216.99.193.38]) by hub.freebsd.org (Postfix) with ESMTP id 49CB737C406; Wed, 22 Mar 2000 15:58:26 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail3.aracnet.com (8.9.3/8.9.3) with ESMTP id PAA14067; Wed, 22 Mar 2000 15:56:43 -0800 Received: by shell1.aracnet.com (8.9.3) id PAA10800; Wed, 22 Mar 2000 15:57:45 -0800 Date: Wed, 22 Mar 2000 15:57:45 -0800 (PST) From: Brian Beattie To: wilko@FreeBSD.ORG Cc: "Matthew N. Dodd" , Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: 100Bit Fast Ethernet EISA card - anyone? In-Reply-To: <20000322233055.I1709@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Wilko Bulte wrote: > On Tue, Mar 21, 2000 at 10:20:14PM -0500, Matthew N. Dodd wrote: > > On Tue, 21 Mar 2000, Wilko Bulte wrote: > > > An FDDI ISA card would not be much fun (performance wise) > > > > But they exist, as do ISA 100baseTX cards. :) > > Duh.. Considering the premium price FDDI always had that is a surprise to > me to be honest. Like a V8 in a VW Beetle ;-) > Maybe, but that has been done too! :) > -- > Wilko Bulte Arnhem, The Netherlands > http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Brian Beattie | This email was produced using professional quality, beattie@aracnet.com | standards based software. Users of Microsoft beattie@aracnet.com | products or other substandard software should www.aracnet.com/~beattie | contact the author about receiving a Free upgrade to | FreeBSD or Linux. "FreeBSD: The power to serve" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 16: 9:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 08C4337C225 for ; Wed, 22 Mar 2000 16:09:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA94325; Wed, 22 Mar 2000 16:08:53 -0800 (PST) (envelope-from dillon) Date: Wed, 22 Mar 2000 16:08:53 -0800 (PST) From: Matthew Dillon Message-Id: <200003230008.QAA94325@apollo.backplane.com> To: Jim Bryant Cc: bright@wintelcom.net (Alfred Perlstein), rminnich@lanl.gov, hackers@FreeBSD.ORG, linux-kernel@vger.rutgers.edu, Michael.Lampe@iwr.uni-heidelberg.de Subject: Re: How a normal user can crash any linux system (fwd) References: <200003222155.PAA35282@ppp-207-193-186-239.kscymo.swbell.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In reply: :> This is cross-posted to both linux-kernel and freebsd-hackers, please :> set your replies properly. :> :> > I found the following by accident playing with PVM. If you start the :> > 'gexample' from the examples directory with dimension=10000 and no of :> > tasks=32 on one machine, it becomes almost immediately completely un- :> > usable and begins with heavy swapping. Considering how much memory :> > would be necessary for this computation before starting it would have :> > avoided the trouble. : :well, there are other ways to make a system slow to a crawl.... : :a good preventative measure is to never give shell accounts unless :everyone is accountable. : :#!/bin/csh :/usr/games/primes 1 4294967295 >&/dev/null& :/usr/games/primes 1 4294967295 >&/dev/null& :/usr/games/primes 1 4294967295 >&/dev/null& :... Generally speaking if a user wants to crash a machine, he can crash a machine. We've probably 'fixed' a dozen crashability holes in the last year but the count comes from a virtually unlimited supply. Short of being ridiculously draconian there will always be a way to twist the resource limits you are given to take a machine down or DOS it into unusability. And resource limits do not cover every conceivable facet. For example, just before the 4.0 release it was found that one can easily run the kernel out of vm_map_entry resources by mmap()ing hundreds of thousands of tiny files. We added a vm.max_proc_mmap sysctl to control that. And it still quite easy to bypass the datasize resource limit through the use of MAP_ANON mmap's. What resource limits are good at doing is preventing 'stupid user' mistakes. For example, at BEST we capped the CGI exec time at 10 cpu seconds (else our web servers would build up hundreds of broken CGI processes), but we set it as a soft limit so users who know what they are doing can unlimit it. I imposed a 40 process and 64 descriptor limit as being reasonable, but that's still 2560 descriptors to a user trying to mess things up on purpose. Quotas are useful for preventing a user from accidently filling up a disk partition. For example, I had a 100MB quota on /tmp, but quotas can be bypassed in a number of ways - for example, excessive syslogging (log files are owned by root). Resource limits are useful for protecting against a purposeful DOS attack insofar as it is generally the script kiddies who don't know their asses from their fingers who are trying to crash the machines. There is no way to protect against someone who knows what they are doing. So, in conclusion, resource limits are absolutely necessary in keeping a multi-user machine running smoothly, but the necessity has virtually nothing to do with preventing purposeful attacks. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 16:20:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D3D3D37BE06; Wed, 22 Mar 2000 16:20:46 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA88327; Wed, 22 Mar 2000 16:20:47 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 22 Mar 2000 16:20:47 -0800 (PST) From: Kris Kennaway To: sdf dsg Cc: freebsd-hackers@freebsd.org Subject: Re: 3,4 In-Reply-To: <20000322155046.7491.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, sdf dsg wrote: > When are the 3.4 release comming, and i dont want some beta things? 3.4 has been out for 4 months now. Please don't post this kind of thing to FreeBSD-hackers - it's not on-topic. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 16:34:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anime.net (anime.net [205.139.105.150]) by hub.freebsd.org (Postfix) with ESMTP id F2F5737B7CB for ; Wed, 22 Mar 2000 16:34:30 -0800 (PST) (envelope-from goemon@sasami.anime.net) Received: from localhost (goemon@localhost) by anime.net (8.9.3/8.9.3) with ESMTP id QAA25985; Wed, 22 Mar 2000 16:34:08 -0800 Date: Wed, 22 Mar 2000 16:34:07 -0800 (PST) From: Dan Hollis X-Sender: goemon@anime.net To: kc5vdj@swbell.net Cc: Alfred Perlstein , rminnich@lanl.gov, hackers@FreeBSD.ORG, linux-kernel@vger.rutgers.edu, Michael.Lampe@iwr.uni-heidelberg.de Subject: Re: How a normal user can crash any linux system (fwd) In-Reply-To: <200003222155.PAA35282@ppp-207-193-186-239.kscymo.swbell.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Jim Bryant wrote: > well, there are other ways to make a system slow to a crawl.... > #!/bin/csh > /usr/games/primes 1 4294967295 >&/dev/null& > [...] /etc/security/limits.conf get the idea? :) -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 18:27:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DD50237B51D for ; Wed, 22 Mar 2000 18:27:21 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA45152 for ; Wed, 22 Mar 2000 21:26:05 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 22 Mar 2000 21:26:01 -0500 (EST) From: Chuck Robey To: FreeBSD Hackers List Subject: nm output 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 looking through a nm listing for a static (unstripped) binary, and I keep seeing these things with the name ".Ltext0". Anyone ever see these things, or have any idea what they are? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 18:58:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 9638437B8DC for ; Wed, 22 Mar 2000 18:58:49 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id SAA98299 for hackers@FreeBSD.org; Wed, 22 Mar 2000 18:58:37 -0800 (PST) (envelope-from ulf) Date: Wed, 22 Mar 2000 18:58:37 -0800 From: Ulf Zimmermann To: hackers@FreeBSD.org Subject: Question about PCI vendor 0x127a Message-ID: <20000322185837.D95709@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have this Sony Notebook Z505R, running 4.0-RC3 and works great. But I noticed there is still one unknown card: pci0: (vendor=0x127a, dev=0x2005) at 11.0 irq 9 Checking out www.pcisig.com, this vendor id is not listed. Anyone have an idea what part of the notebook it could be ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 19:16: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 997A737BA23 for ; Wed, 22 Mar 2000 19:15:56 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id WAA26011; Wed, 22 Mar 2000 22:15:43 -0500 (EST) From: "Allen Pulsifer" To: Cc: Subject: RE: Question about PCI vendor 0x127a Date: Wed, 22 Mar 2000 22:15:43 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20000322185837.D95709@PacHell.TelcoSucks.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From http://www.yourvote.com/pci/ Rockwell Semiconductor Systems 714-221-4600 Vendor ID: 0x127A Short Name: Rockwell Semi Contact: richard.ward@nb.rockwell.com Web Site: http://www.rockwell.com Device ID: 0x1002 Chip Number: RC56HCFPCI Description: Modem enumerator Device ID: 0x1025 Description: PCI modem Device ID: 0x2005 Chip Number: RS56/SP-PCI11P1 Description: Single chip 56K V90 modem/spkrphone Device ID: 0x2014 Description: PCI modem > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Ulf Zimmermann > Sent: Wednesday, March 22, 2000 9:59 PM > To: hackers@FreeBSD.ORG > Subject: Question about PCI vendor 0x127a > > > I have this Sony Notebook Z505R, running 4.0-RC3 and works great. But I > noticed there is still one unknown card: > > pci0: (vendor=0x127a, dev=0x2005) at 11.0 irq 9 > > Checking out www.pcisig.com, this vendor id is not listed. Anyone have > an idea what part of the notebook it could be ? > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 19:27:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id D524C37B51F for ; Wed, 22 Mar 2000 19:27:42 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id TAA98485; Wed, 22 Mar 2000 19:27:32 -0800 (PST) (envelope-from ulf) Date: Wed, 22 Mar 2000 19:27:32 -0800 From: Ulf Zimmermann To: Allen Pulsifer Cc: ulf@Alameda.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Question about PCI vendor 0x127a Message-ID: <20000322192732.E95709@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000322185837.D95709@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from pulsifer@mediaone.net on Wed, Mar 22, 2000 at 10:15:43PM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 10:15:43PM -0500, Allen Pulsifer wrote: > >From http://www.yourvote.com/pci/ > > Rockwell Semiconductor Systems > 714-221-4600 > Vendor ID: 0x127A > Short Name: Rockwell Semi > Contact: richard.ward@nb.rockwell.com > Web Site: http://www.rockwell.com > > > Device ID: > 0x1002 > Chip Number: RC56HCFPCI > Description: Modem enumerator > > Device ID: > 0x1025 > Description: PCI modem > > Device ID: > 0x2005 > Chip Number: RS56/SP-PCI11P1 > Description: Single chip 56K V90 modem/spkrphone > > Device ID: > 0x2014 > Description: PCI modem Ahh, right, the modem, I forgot about it. Still funny that www.pcisig.com doesn't list 0x127a in their list sorted by hex. > > > > -----Original Message----- > > From: owner-freebsd-hackers@FreeBSD.ORG > > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Ulf Zimmermann > > Sent: Wednesday, March 22, 2000 9:59 PM > > To: hackers@FreeBSD.ORG > > Subject: Question about PCI vendor 0x127a > > > > > > I have this Sony Notebook Z505R, running 4.0-RC3 and works great. But I > > noticed there is still one unknown card: > > > > pci0: (vendor=0x127a, dev=0x2005) at 11.0 irq 9 > > > > Checking out www.pcisig.com, this vendor id is not listed. Anyone have > > an idea what part of the notebook it could be ? > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 19:52:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 8448437C320 for ; Wed, 22 Mar 2000 19:52:43 -0800 (PST) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 2749ADBB4; Wed, 22 Mar 2000 22:50:47 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 13B06DBB3 for ; Wed, 22 Mar 2000 22:50:47 -0500 (EST) Date: Wed, 22 Mar 2000 22:50:47 -0500 (EST) From: David Miller To: freebsd-hackers@freebsd.org Subject: NCR/FXP and coredumps 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 Two item: 1) I managed to crash an intel N440BX mobo with an fxp card and the onboard ncr drivers. Lots of network traffic (ping floods) and disk IO (rawio in parallel on two disks) took it down in something like two hours. I know this is a known bug, I'm just offering core dumps and testing services in fixing it if anyone wants to take a stab at it. 2) I have a production 3.2R system running on the same kind of hardware. I've done everything I did on the crashed system to try and pin down the problem but the core dumps are useless:( To review, I added 'makeoptions DEBUG="-g"' to the file, relinked the kernel, cp kernel to kernel.debug and ran "strip -g kernel". Booted on the new kernel. Added da0b to the rc.conf as the dumpdev, and added savecore -N /sys/compile/STAGING-1/kernel.debug /var/crash to /etc/ec. I get the coredumps fine: Mar 19 04:24:45 staging-1 savecore: reboot after panic: m_copym Mar 19 04:24:45 staging-1 savecore: writing core to /var/crash/vmcore.3 Mar 19 04:25:49 staging-1 savecore: writing kernel to /var/crash/kernel.3 But they don't seem to work:( staging-1:STAGING-1# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.3 (kgdb) core-file /var/crash/vmcore.3 IdlePTD 2985984 kernel symbol `gd_curpcb' not found. (kgdb) where No stack. (kgdb) Any ideas? This is about the most important box I have, and it's crashing once or twice per week. The core dump I could examine for 1) was from a 3.4-stable system. The dirty details: FreeBSD 3.2R, as shipped on CD kernel config file pretty standard - single CPU, most unnecessary drivers commented out, available to anyone who wants to see it Hardware: TruSolutions 2U rack server with Intel N440BX mobo, onboard FXP and NCR, second Intel Pro 10/100B, two ibm fast wide scsi drives. Thanks, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 19:55:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id B561A37C286 for ; Wed, 22 Mar 2000 19:55:13 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id WAA13321; Wed, 22 Mar 2000 22:54:59 -0500 (EST) From: "Allen Pulsifer" To: Cc: Subject: RE: Question about PCI vendor 0x127a Date: Wed, 22 Mar 2000 22:54:59 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20000322192732.E95709@PacHell.TelcoSucks.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Still funny that www.pcisig.com doesn't list 0x127a ... It costs $2500 per year to be a member of the PCI-SIG. If you stop paying, they delete you from their vendor list. A lot of companies join just to get assigned a vendor id, then they stop paying after the first year. So if you want to know the vendor id of a company that's no longer paying dues, you have to look at the unofficial list maintained by Jim Boemler at http://www.yourvote.com/pci/. Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 19:56:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id F0A4C37B96E for ; Wed, 22 Mar 2000 19:56:41 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (10092 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Wed, 22 Mar 2000 22:56:39 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Wed, 22 Mar 2000 22:56:39 -0500 From: Jim Mercer To: hackers@freebsd.org Subject: possible bug in kernel/if_ether.c Message-ID: <20000322225639.T983@reptiles.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2oS5YaxWCcQjTEyO" X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii i have a new system, dual pentium 550's, 512meg ram, dual adaptec 29160, realtek ethernet. (dmesg.boot enclosed) it has been having intermittent reboots, with no syslog output. i thought maybe we were having heat issues, or power issues, but maybe it is a kernel bug. i enabled dumpdev and now i have dumps. (arg, and it just crashed while i was snarfing the attached info) both crashes occur in the same place in the kernel. i think maybe that indicates a potential kernel/driver bug. please find attached: dmesg.boot gdb -k info - crash 0 gdb -k info - crash 1 last second info: nuffy# ifconfig rl0 rl0: flags=8843 mtu 1500 inet 209.167.108.145 netmask 0xffffff80 broadcast 209.167.108.255 inet 209.167.108.146 netmask 0xffffffff broadcast 209.167.108.146 ether 00:00:21:ef:1d:a4 media: autoselect (none) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX is it possible that the bug is being triggered because the driver has not selected a media type? i did notice that the ethernet performance sucked, but i wasn't sure if that was because the machine i was ftp'ing to sucked, or because this interface was not specifically set to a media. i elected not to set the media, because the machine is remote from me, and didn't want to have it lose the connection. i will physically visit the machine tomorrow. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Description: kgdb crash0 Content-Disposition: attachment; filename=snuffy1 ... SMP 2 cpus IdlePTD 3100672 initial pcb at 281960 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01997c8 stack pointer = 0x10:0xff806fa4 frame pointer = 0x10:0xff806fac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks... 11 11 ... #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc01549fc in poweroff_wait (junk=0xc0259c2f, howto=0) at ../../kern/kern_shutdown.c:554 #2 0xc022983b in trap_fatal (frame=0xff806f64, eva=8) at ../../i386/i386/trap.c:924 #3 0xc02294d1 in trap_pfault (frame=0xff806f64, usermode=0, eva=8) at ../../i386/i386/trap.c:817 #4 0xc02290a3 in trap (frame={tf_fs = 1107296280, tf_es = 16, tf_ds = -1056178160, tf_edi = -1, tf_esi = 0, tf_ebp = -8360020, tf_isp = -8360048, tf_ebx = 0, tf_edx = -1071016096, tf_ecx = 1, tf_eax = -1056143360, tf_trapno = 12, tf_err = 0, tf_eip = -1072064568, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:423 #5 0xc01997c8 in arpintr () at ../../netinet/if_ether.c:447 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Description: kgdb crash1 Content-Disposition: attachment; filename=snuffy2 SMP 2 cpus IdlePTD 3100672 initial pcb at 281960 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01997c8 stack pointer = 0x10:0xff80dfa4 frame pointer = 0x10:0xff80dfac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 syncing disks... 48 47 21 .... #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc01549fc in poweroff_wait (junk=0xc0259c2f, howto=0) at ../../kern/kern_shutdown.c:554 #2 0xc022983b in trap_fatal (frame=0xff80df64, eva=8) at ../../i386/i386/trap.c:924 #3 0xc02294d1 in trap_pfault (frame=0xff80df64, usermode=0, eva=8) at ../../i386/i386/trap.c:817 #4 0xc02290a3 in trap (frame={tf_fs = 1107296280, tf_es = 16, tf_ds = -1056178160, tf_edi = -1, tf_esi = 1, tf_ebp = -8331348, tf_isp = -8331376, tf_ebx = 0, tf_edx = -1071016096, tf_ecx = 16777217, tf_eax = -1056133376, tf_trapno = 12, tf_err = 0, tf_eip = -1072064568, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 1}) at ../../i386/i386/trap.c:423 #5 0xc01997c8 in arpintr () at ../../netinet/if_ether.c:447 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Description: dmesg.boot Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #2: Tue Mar 21 03:48:14 EST 2000 toor@snuffy.nag.ca:/usr/src/sys/compile/NAG-ORANGE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536870912 (524288K bytes) avail memory = 517988352 (505848K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02e3000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pci0: at 7.2 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x440-0x44f at device 7.3 on pci0 ahc0: port 0xe800-0xe8ff mem 0xffaff000-0xffafffff irq 16 at device 16.0 on pci0 ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xe400-0xe4ff mem 0xffafe000-0xffafefff irq 17 at device 17.0 on pci0 ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs rl0: port 0xe000-0xe0ff mem 0xffafdf00-0xffafdfff irq 18 at device 18.0 on pci0 rl0: Ethernet address: 00:00:21:ef:1d:a4 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default DUMMYNET initialized (000106) Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 8704MB (17827698 512 byte sectors: 255H 63S/T 1109C) da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 34746MB (71161520 512 byte sectors: 255H 63S/T 4429C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 34746MB (71161520 512 byte sectors: 255H 63S/T 4429C) Mounting root from ufs:/dev/da0s2a WARNING: / was not properly dismounted --2oS5YaxWCcQjTEyO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 21:15:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E21737B653 for ; Wed, 22 Mar 2000 21:15:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA96507; Wed, 22 Mar 2000 21:15:27 -0800 (PST) (envelope-from dillon) Date: Wed, 22 Mar 2000 21:15:27 -0800 (PST) From: Matthew Dillon Message-Id: <200003230515.VAA96507@apollo.backplane.com> To: Jim Mercer Cc: hackers@FreeBSD.ORG Subject: Re: possible bug in kernel/if_ether.c References: <20000322225639.T983@reptiles.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :SMP 2 cpus :IdlePTD 3100672 :initial pcb at 281960 :panicstr: page fault :panic messages: :--- :Fatal trap 12: page fault while in kernel mode :mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 :fault virtual address = 0x8 :fault code = supervisor read, page not present :instruction pointer = 0x8:0xc01997c8 :stack pointer = 0x10:0xff806fa4 :frame pointer = 0x10:0xff806fac :code segment = base 0x0, limit 0xfffff, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 :processor eflags = interrupt enabled, resume, IOPL = 0 :current process = Idle :interrupt mask = <- SMP: XXX :trap number = 12 :panic: page fault :mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 :boot() called on cpu#0 : :syncing disks... 11 11 :... :#0 boot (howto=256) at ../../kern/kern_shutdown.c:304 :304 dumppcb.pcb_cr3 = rcr3(); :(kgdb) bt :#0 boot (howto=256) at ../../kern/kern_shutdown.c:304 :#1 0xc01549fc in poweroff_wait (junk=0xc0259c2f, howto=0) : at ../../kern/kern_shutdown.c:554 :#2 0xc022983b in trap_fatal (frame=0xff806f64, eva=8) : at ../../i386/i386/trap.c:924 :#3 0xc02294d1 in trap_pfault (frame=0xff806f64, usermode=0, eva=8) : at ../../i386/i386/trap.c:817 :#4 0xc02290a3 in trap (frame={tf_fs = 1107296280, tf_es = 16, : tf_ds = -1056178160, tf_edi = -1, tf_esi = 0, tf_ebp = -8360020, : tf_isp = -8360048, tf_ebx = 0, tf_edx = -1071016096, tf_ecx = 1, : tf_eax = -1056143360, tf_trapno = 12, tf_err = 0, tf_eip = -1072064568, : tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) : at ../../i386/i386/trap.c:423 :#5 0xc01997c8 in arpintr () at ../../netinet/if_ether.c:447 : : :--2oS5YaxWCcQjTEyO :Content-Type: text/plain; charset=us-ascii :Content-Description: kgdb crash1 :Content-Disposition: attachment; filename=snuffy2 : : :SMP 2 cpus Very, very weird. Can you disassemble the 'arpintr' function from your kernel binary? gdb -k /kernel (or kernel.debug if you have it) disassemble arpintr :Fatal trap 12: page fault while in kernel mode :mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 :fault virtual address = 0x8 :fault code = supervisor read, page not present :instruction pointer = 0x8:0xc01997c8 :stack pointer = 0x10:0xff80dfa4 I can't pinpoint the fault point since my kernel is compiled up differently, but I suspect it's at the line I've indicated below. Unfortunately, it makes no sense whatsoever because %ebx would have to be NULL and that case already checked. I suspect the actual fault address is somewhere else if you do the dissassembly it should help. splx(s); if (m == 0 || (m->m_flags & M_PKTHDR) == 0) panic("arpintr"); if (m->m_len < sizeof(struct arphdr) && (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { log(LOG_ERR, "arp: runt packet -- m_pullup failed."); continue; 0xc01aa6b5 : testl %ebx,%ebx ---Type to continue, or q to quit--- 0xc01aa6b7 : je 0xc01aa6bf 0xc01aa6b9 : testb $0x2,0x12(%ebx) 0xc01aa6bd : jne 0xc01aa6cc 0xc01aa6bf : pushl $0xc0281c0e 0xc01aa6c4 : call 0xc015f700 0xc01aa6c9 : leal 0x0(%esi),%esi 0xc01aa6cc : cmpl $0x7,0xc(%ebx) 0xc01aa6d0 : jbe 0xc01aa71c 0xc01aa6d2 : movl 0x8(%ebx),%ecx <---- 0xc01aa6d5 : testl %ecx,%ecx ???? 0xc01aa6d7 : je 0xc01aa71c 0xc01aa6d9 : movzwl (%ecx),%eax -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 21:16:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 7478337BA17 for ; Wed, 22 Mar 2000 21:16:22 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id VAA19172; Wed, 22 Mar 2000 21:16:07 -0800 (PST) Date: Wed, 22 Mar 2000 21:16:07 -0800 From: Brooks Davis To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NCR/FXP and coredumps Message-ID: <20000322211607.A7582@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from dmiller@search.sparks.net on Wed, Mar 22, 2000 at 10:50:47PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 10:50:47PM -0500, David Miller wrote: > Two item: > > 1) I managed to crash an intel N440BX mobo with an fxp card and the > onboard ncr drivers. Lots of network traffic (ping floods) and disk IO > (rawio in parallel on two disks) took it down in something like two > hours. I know this is a known bug, I'm just offering core dumps and > testing services in fixing it if anyone wants to take a stab at it. DG has looked at this extensively and the current feeling is that this is a hardware bug. Using the sym driver instead of the ncr driver apparently helps somewhat, but the problem still happens. The generally recommended option is to buy an Adaptec SCSI controller and use that instead of the on-board SCSI. That works flawlessly. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 21:59:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 9980837BA06 for ; Wed, 22 Mar 2000 21:59:05 -0800 (PST) (envelope-from matt@thebiz.net) Received: (qmail 16274 invoked from network); 23 Mar 2000 00:58:57 -0500 Received: from mail2.thebiz.net (172.16.0.129) by mx1.thebiz.net with SMTP; 23 Mar 2000 00:58:57 -0500 Received: (qmail 9848 invoked by uid 0); 23 Mar 2000 00:58:57 -0500 Received: from unknown (HELO matthome) (24.161.33.83) by mail.thebiz.net with SMTP; 23 Mar 2000 00:58:57 -0500 Message-ID: <006501bf948c$e11bc8d0$5321a118@matthome> From: "Matthew Zahorik" To: Subject: Is this a bug? Date: Thu, 23 Mar 2000 00:58:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While making a slew of diskless machines I've tracked down a kernel panic. FreeBSD 4.0-RELEASE, kernel with BOOTP* enabled. Each machine has a private and public network attached. It netboots from the private network. Because of that, I didn't set a gw address in bootptab. The public network interface is brought up by the rc scripts. After booting, since there was no gateway, the BOOTP code makes an assumption and sets itself as the gateway and therefore starts proxy-arp. The relevant bit of code in ./nfs/bootp_subr.c: if (!gotgw) { /* Use proxyarp */ gw.sin_addr.s_addr = myaddr.sin_addr.s_addr; } While the network table is in this state, if you ping anything outside of the local network it causes a kernel panic (unaligned access fault) the kernel in ip_input:310 ie. From the console after boot, ping locally and it's fine. Ping anything off the local subnet and the kernel panics. Definately don't start sendmail with a non-local resolver. Also don't telnet into the box, causing a request to a non-local resolver. This was on an Alpha box. It may not reproduce on Intel, since it's more tolerant of off-alignment memory access. What I really need to know is, is this a bug or a is the proxy-arp gateway assumption a desired behavior? While the routing table is in this state, you're an errant IP packet away from a panic (: Since setting a gateway which was unreachable until the public interface came up didn't seem like a great idea to me, my solution was to program out the offending assumptions. If gw isn't received in the bootp reply, no default route is set. Diffs against ./nfs/boop_subr.c are available if the default behavior is wrong or considered obsolete. - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 23:54:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 132E137BE44 for ; Wed, 22 Mar 2000 23:54:56 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA87708 for ; Wed, 22 Mar 2000 23:54:55 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D9CDCF.D52555F0@gorean.org> Date: Wed, 22 Mar 2000 23:54:55 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Tiny GENERIC patch Content-Type: multipart/mixed; boundary="------------3622A431323E0EE4E1387B6A" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3622A431323E0EE4E1387B6A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I was doing some kernel debugging tonight and decided that I needed a backup plan. Since I already had built my test kernel I thought the attached would be a good idea. It has the added benefit of moving the existing kernel.GENERIC to kernel.GENERIC.old in the 'make install' step. Wording in the comment could probably be better... FWIW, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." --------------3622A431323E0EE4E1387B6A Content-Type: text/plain; charset=us-ascii; name="GENERIC.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="GENERIC.diff" Index: GENERIC =================================================================== RCS file: /usr/ncvs/src/sys/i386/conf/GENERIC,v retrieving revision 1.249 diff -u -r1.249 GENERIC --- GENERIC 2000/03/21 17:00:58 1.249 +++ GENERIC 2000/03/23 07:47:11 @@ -26,6 +26,7 @@ maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols +makeoptions KERNEL=kernel.GENERIC #Remove for building a custom kernel options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking --------------3622A431323E0EE4E1387B6A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 22 23:58:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 93B2F37B956 for ; Wed, 22 Mar 2000 23:58:31 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 36765 invoked by uid 1001); 23 Mar 2000 07:58:28 +0000 (GMT) To: brooks@one-eyed-alien.net Cc: dmiller@search.sparks.net, freebsd-hackers@FreeBSD.ORG Subject: Re: NCR/FXP and coredumps From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 22 Mar 2000 21:16:07 -0800" References: <20000322211607.A7582@orion.ac.hmc.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 23 Mar 2000 08:58:28 +0100 Message-ID: <36763.953798308@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1) I managed to crash an intel N440BX mobo with an fxp card and the > > onboard ncr drivers. Lots of network traffic (ping floods) and disk IO > > (rawio in parallel on two disks) took it down in something like two > > hours. I know this is a known bug, I'm just offering core dumps and > > testing services in fixing it if anyone wants to take a stab at it. > > DG has looked at this extensively and the current feeling is that this is > a hardware bug. Using the sym driver instead of the ncr driver > apparently helps somewhat, but the problem still happens. The generally > recommended option is to buy an Adaptec SCSI controller and use that > instead of the on-board SCSI. That works flawlessly. I can confirm that the sym driver has cured all such problems for us. Not a single crash after switching to the sym driver. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0: 4:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 7F2BE37BDE4 for ; Thu, 23 Mar 2000 00:04:12 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA48080; Thu, 23 Mar 2000 03:04:04 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Thu, 23 Mar 2000 03:04:46 -0500 To: hackers@FreeBSD.org From: Garance A Drosihn Subject: Re: Handling maximum values in C (was: MAX_UID) Cc: Bruce Evans , Peter Dufault , Ed Hall Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently on the freebsd-current mailing list, the topic came up of setting the maximum value of a given type (uid_t, as the specific example, but the conversation turned to having a generic way to find the maximum value of any given type). Some excerpts from that thread: > > > To get the all-1`s number, maybe it`s better to use ((uid_t)~0), > > > but that is a rather controversial topic anyway. > > > > That works, but on machines like the Alpha where longs are bigger > > than ints it only works by virtue of sign extension. Our existing > > headers seem to prefer ((uid_t)0-1). That`s what is used in the > > i386`s . > All 3 of these are broken in general. > ((uquad_t)0-1) in works because it is known that > uquad_t is no smaller than int. If foo_t is smaller than int, then > (foo_t)0 in an expression gets promoted to plain 0, which is rarely > what you want. > > ((uid_t)~(uid_t)0) is probably best. The first cast gives a sufficient > number of 0 bits and the second cast discards unwanted 1 bits. > > -1 is sometimes used instead of ~0 because there is a good rule > for converting -1 to an unsigned type. I can never quite remember > this rule, so I prefer to use ~something. Part of the rule is that > (unsigned int)-1 has all bits 1 even if -1 doesn`t have all bits 1. I've got some code I'm compiling on a number of different platforms with a number of different compilers, and was running into a problem depending on how 'char' (just plain 'char') was treated by default (ie, signed vs unsigned). Remembering the above, I thought "hey, I'll just check the maximum value for type 'char'. Once I found the messages, it took me another 30 seconds to realize the above is only for UNSIGNED types. For signed types, all of the above just result in a "max value" of -1... (so imagine the fun if some arbitrary type is changed from 'signed short' to 'unsigned int'...) For those interested in using the above when they do know they have an unsigned type, the: ((some_utype)~(some_utype)0) version does seem to be the one which compiles without warnings on the four compilers I tried (at least for unsigned char...). The above was good enough to find out if plain 'char' is signed or unsigned, but I'm wondering if there is any way to find the max value of some_generic_integer_type, without assuming anything about sizeof or signed/unsigned. Some portable trick where the value would be determined at compile-time, I mean... Just wondering. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0: 4:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grimreaper.grondar.za (dhcp65.iafrica.com [196.31.1.65]) by hub.freebsd.org (Postfix) with ESMTP id EC7EB37BE5B; Thu, 23 Mar 2000 00:04:16 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA02712; Thu, 23 Mar 2000 10:04:30 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200003230804.KAA02712@grimreaper.grondar.za> To: Kris Kennaway Cc: Sheldon Hearn , freebsd-hackers@FreeBSD.org, markm@FreeBSD.org Subject: Re: openssh + krb5 (followup) References: In-Reply-To: ; from Kris Kennaway "Wed, 22 Mar 2000 11:55:49 PST." Date: Thu, 23 Mar 2000 10:04:30 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 22 Mar 2000, Sheldon Hearn wrote: > > > > Interoperability with MIT krb5 still seems to be an issue. > > > > Bleh, more FUD. The problem is in operability with non-FreeBSD openssh! > > We use supported_authentication values for KRB5 that neither Datafellows > > SSH nor OpenBSD SSH use. :-( > > Hmm..I thought OpenBSD's OpenSSH didn't support krb5, only > krb4. Regardless, we should fix this to bring ourselves in line > (preferably with both). As far as I can work out, OpenBSD uses OpenSSH+Kerberos to mean KerberosIV, whereas Datafellows meand Kerberos5. This would be a mistake made by OpenBSD, and one that is easy to fix. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0:21:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 1E7A237BDF0 for ; Thu, 23 Mar 2000 00:21:54 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id JAA27093; Thu, 23 Mar 2000 09:21:50 +0100 (CET) (envelope-from k@numeri.campus.luth.se) Message-Id: <200003230821.JAA27093@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Wed, 22 Mar 2000 23:54:55 PST." <38D9CDCF.D52555F0@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 09:21:50 +0100 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 22 Mar 2000 23:54:55 PST, Doug Barton wrote: >This is a multi-part message in MIME format. >--------------3622A431323E0EE4E1387B6A >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > > I was doing some kernel debugging tonight and decided that I needed a >backup plan. Since I already had built my test kernel I thought the >attached would be a good idea. It has the added benefit of moving the >existing kernel.GENERIC to kernel.GENERIC.old in the 'make install' >step. Wording in the comment could probably be better... > >FWIW, > >Doug Before this is commited please have a look at the PR kern/17536 which addresses a similar thing. /Johan K >Index: GENERIC >=================================================================== >RCS file: /usr/ncvs/src/sys/i386/conf/GENERIC,v >retrieving revision 1.249 diff -u -r1.249 GENERIC >--- GENERIC 2000/03/21 17:00:58 1.249 >+++ GENERIC 2000/03/23 07:47:11 >@@ -26,6 +26,7 @@ > maxusers 32 > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols >+makeoptions KERNEL=kernel.GENERIC #Remove for building a custom kernel > > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0:33: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by hub.freebsd.org (Postfix) with ESMTP id 00B4337C3E7 for ; Thu, 23 Mar 2000 00:30:52 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12Y308-0007T3-00 for hackers@freebsd.org; Thu, 23 Mar 2000 09:29:56 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12Y307-00011V-00 for ; Thu, 23 Mar 2000 09:29:55 +0100 Date: Thu, 23 Mar 2000 09:29:55 +0100 (CET) From: Egervary Gergely To: hackers@freebsd.org Subject: Re: How a normal user can crash any linux system (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /etc/security/limits.conf mmm... this is for pam_limits.so in linux has anyone ported it to BSD? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0:51:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9E36137C3F4 for ; Thu, 23 Mar 2000 00:51:26 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Mar 2000 08:51:25 +0000 (GMT) Date: Thu, 23 Mar 2000 08:51:25 +0000 From: David Malone To: Egervary Gergely Cc: hackers@freebsd.org Subject: Re: How a normal user can crash any linux system (fwd) Message-ID: <20000323085125.A39526@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mauzi@faber.poli.hu on Thu, Mar 23, 2000 at 09:29:55AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 09:29:55AM +0100, Egervary Gergely wrote: > > /etc/security/limits.conf > > mmm... this is for pam_limits.so in linux > > has anyone ported it to BSD? /etc/login.conf can set limits for you, in a possibly more flexable way. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 0:57:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.com2com.ru (post.com2com.ru [195.98.160.26]) by hub.freebsd.org (Postfix) with ESMTP id BDCD337BB7F for ; Thu, 23 Mar 2000 00:57:20 -0800 (PST) (envelope-from vigov@com2com.ru) Received: from VIGOV (ws80.com2com.ru [195.98.160.80]) by post.com2com.ru (8.8.8/8.8.8) with ESMTP id LAA09031 for ; Thu, 23 Mar 2000 11:57:19 +0300 (MSK) (envelope-from vigov@com2com.ru) Date: Thu, 23 Mar 2000 12:03:59 +0300 From: vigov X-Mailer: The Bat! (v1.39) Educational Reply-To: vigov Organization: 2Com X-Priority: 3 (Normal) Message-ID: <12502.000323@com2com.ru> To: hackers@FreeBSD.ORG 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 unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 1: 3:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by hub.freebsd.org (Postfix) with ESMTP id 5113337BA5B for ; Thu, 23 Mar 2000 01:03:24 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12Y3Up-0007VN-00; Thu, 23 Mar 2000 10:01:39 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12Y3Uj-00019s-00; Thu, 23 Mar 2000 10:01:33 +0100 Date: Thu, 23 Mar 2000 10:01:33 +0100 (CET) From: Egervary Gergely To: David Malone Cc: hackers@freebsd.org Subject: Re: How a normal user can crash any linux system (fwd) In-Reply-To: <20000323085125.A39526@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > has anyone ported it to BSD? > > /etc/login.conf can set limits for you, in a possibly more flexable way. but login does not support session accounting that pam_limits.so does. (it should support, but it's not implemented) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 1:11:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3786837B60A for ; Thu, 23 Mar 2000 01:11:07 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Date: Thu, 23 Mar 2000 09:11:06 +0000 From: David Malone To: Egervary Gergely Cc: hackers@freebsd.org Subject: Re: How a normal user can crash any linux system (fwd) Message-ID: <20000323091106.A76435@salmon.maths.tcd.ie> References: <20000323085125.A39526@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mauzi@faber.poli.hu on Thu, Mar 23, 2000 at 10:01:33AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 10:01:33AM +0100, Egervary Gergely wrote: > > > has anyone ported it to BSD? > > > > /etc/login.conf can set limits for you, in a possibly more flexable way. > > but login does not support session accounting that pam_limits.so does. I don't see anything about session accouning in the pam_limits section of the html docs distributed with Redhat (this doesn't mean they're not present though ;-) What exactly does it do? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 1:23:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by hub.freebsd.org (Postfix) with ESMTP id DA30837B903 for ; Thu, 23 Mar 2000 01:23:17 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12Y3pL-0007X5-00 for hackers@freebsd.org; Thu, 23 Mar 2000 10:22:51 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12Y3pK-0001CT-00 for ; Thu, 23 Mar 2000 10:22:50 +0100 Date: Thu, 23 Mar 2000 10:22:50 +0100 (CET) From: Egervary Gergely To: hackers@freebsd.org Subject: Re: How a normal user can crash any linux system (fwd) In-Reply-To: <20000323091106.A76435@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't see anything about session accouning in the pam_limits section > of the html docs distributed with Redhat (this doesn't mean they're not > present though ;-) What exactly does it do? for example, this is very important on a ppp dial-up server: $ grep maxlogins /etc/security/limits.conf @dialup hard maxlogins 1 -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 1:45:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id B753737C3C5 for ; Thu, 23 Mar 2000 01:45:49 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id EAA399264; Thu, 23 Mar 2000 04:45:46 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 23 Mar 2000 04:46:27 -0500 To: hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Handling maximum values in C (was: MAX_UID) Cc: Bruce Evans , Peter Dufault , Ed Hall Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:04 AM -0500 3/23/00, I (Garance A Drosihn) wrote: >Once I found the messages, >it took me another 30 seconds to realize the above is only for >UNSIGNED types. For signed types, all of the above just result in a >"max value" of -1... (so imagine the fun if some arbitrary type is >changed from 'signed short' to 'unsigned int'...) That last part was SUPPOSED to be "imagine the fun if some arbitrary type is changed from 'unsigned short' (were these tricks work) to 'signed int' (where the tricks would result in a "max" value of -1). time for me to get some sleep, I guess... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 2:47:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id F293837B6BA for ; Thu, 23 Mar 2000 02:47:41 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (11743 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 23 Mar 2000 05:47:32 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 23 Mar 2000 05:47:32 -0500 From: Jim Mercer To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: possible bug in kernel/if_ether.c Message-ID: <20000323054731.W983@reptiles.org> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="LpQ9ahxlCli8rRTG" X-Mailer: Mutt 1.0i In-Reply-To: <200003230515.VAA96507@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Mar 22, 2000 at 09:15:27PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii On Wed, Mar 22, 2000 at 09:15:27PM -0800, Matthew Dillon wrote: > :#5 0xc01997c8 in arpintr () at ../../netinet/if_ether.c:447 > > Very, very weird. Can you disassemble the 'arpintr' function from your > kernel binary? > > gdb -k /kernel (or kernel.debug if you have it) > disassemble arpintr no problem (although much of this appears well over my head). thanx for having a look. > I can't pinpoint the fault point since my kernel is compiled up > differently, but I suspect it's at the line I've indicated below. > > Unfortunately, it makes no sense whatsoever because %ebx would have to > be NULL and that case already checked. I suspect the actual fault > address is somewhere else if you do the dissassembly it should help. just to clarify, i'm running 4.0-RELEASE, with a cvsup 4.x-stable-supfile as at approx Mar 21 02:00 i've attached my kernel config file as well. FreeBSD snuffy.nag.ca 4.0-STABLE FreeBSD 4.0-STABLE #2: Tue Mar 21 03:48:14 EST 2000 toor@snuffy.nag.ca:/usr/src/sys/compile/NAG-ORANGE i386 also, as at 23:00 last night (currently 05:30) i ifconfig'd the rl0 to 10mbps and rebooted, and i haven't had a reboot yet. mind you, it hasn't been rebooting with any regular frequency, nor do the reboots appear to be related to system load. (ie, i had some heavy database processing happening and a "make world" at the same time, without a reboot, then got a reboot later during an idle period). from kernel.debug: (kgdb) disassemble arpintr Dump of assembler code for function arpintr: 0xc019972c : pushl %ebp 0xc019972d : movl %esp,%ebp 0xc019972f : pushl %esi 0xc0199730 : pushl %ebx 0xc0199731 : cmpl $0x0,0xc0270084 0xc0199738 : je 0xc019986c 0xc019973e : call 0xc0232224 0xc0199743 : movl %eax,%edx 0xc0199745 : movl 0xc0270084,%ebx 0xc019974b : testl %ebx,%ebx 0xc019974d : je 0xc0199775 0xc019974f : movl 0x4(%ebx),%eax 0xc0199752 : movl %eax,0xc0270084 0xc0199757 : testl %eax,%eax 0xc0199759 : jne 0xc0199768 0xc019975b : movl $0x0,0xc0270088 0xc0199765 : leal 0x0(%esi),%esi 0xc0199768 : movl $0x0,0x4(%ebx) 0xc019976f : decl 0xc027008c 0xc0199775 : pushl %edx 0xc0199776 : call 0xc02320f4 0xc019977b : addl $0x4,%esp 0xc019977e : testl %ebx,%ebx 0xc0199780 : je 0xc0199788 0xc0199782 : testb $0x2,0x12(%ebx) 0xc0199786 : jne 0xc0199794 0xc0199788 : pushl $0xc024bace 0xc019978d : call 0xc0154968 0xc0199792 : movl %esi,%esi 0xc0199794 : cmpl $0x7,0xc(%ebx) 0xc0199798 : ja 0xc01997c8 0xc019979a : pushl $0x8 0xc019979c : pushl %ebx 0xc019979d : call 0xc016e4b8 0xc01997a2 : addl $0x8,%esp 0xc01997a5 : testl %eax,%eax 0xc01997a7 : sete %al 0xc01997aa : movzbl %al,%ebx 0xc01997ad : testl %ebx,%ebx 0xc01997af : je 0xc01997c8 0xc01997b1 : pushl $0xc024bae0 0xc01997b6 : pushl $0x3 0xc01997b8 : call 0xc015f524 0xc01997bd : addl $0x8,%esp 0xc01997c0 : jmp 0xc0199731 0xc01997c5 : leal 0x0(%esi),%esi 0xc01997c8 : movl 0x8(%ebx),%ecx 0xc01997cb : movzwl (%ecx),%eax 0xc01997ce : xchgb %ah,%al 0xc01997d0 : cmpw $0x1,%ax 0xc01997d4 : je 0xc0199804 0xc01997d6 : movzwl (%ecx),%eax 0xc01997d9 : xchgb %ah,%al 0xc01997db : cmpw $0x6,%ax 0xc01997df : je 0xc0199804 0xc01997e1 : pushl $0xc024ba8e 0xc01997e6 : pushl %ecx 0xc01997e7 : pushl $0xc024bb20 0xc01997ec : pushl $0x3 0xc01997ee : call 0xc015f524 0xc01997f3 : pushl %ebx 0xc01997f4 : call 0xc016d99c 0xc01997f9 : addl $0x14,%esp 0xc01997fc : jmp 0xc0199731 0xc0199801 : leal 0x0(%esi),%esi 0xc0199804 : movl %ebx,%eax 0xc0199806 : xorl %esi,%esi 0xc0199808 : testl %ebx,%ebx 0xc019980a : je 0xc0199815 0xc019980c : addl 0xc(%eax),%esi 0xc019980f : movl (%eax),%eax 0xc0199811 : testl %eax,%eax 0xc0199813 : jne 0xc019980c 0xc0199815 : movzbl 0x4(%ecx),%edx 0xc0199819 : movzbl 0x5(%ecx),%eax 0xc019981d : leal 0x8(,%eax,2),%eax 0xc0199824 : leal (%eax,%edx,2),%edx 0xc0199827 : cmpl %edx,%esi 0xc0199829 : jae 0xc0199848 0xc019982b : pushl $0xc024bb4b 0xc0199830 : pushl $0x3 0xc0199832 : call 0xc015f524 0xc0199837 : pushl %ebx 0xc0199838 : call 0xc016d99c 0xc019983d : addl $0xc,%esp 0xc0199840 : jmp 0xc0199731 0xc0199845 : leal 0x0(%esi),%esi 0xc0199848 : movzwl 0x2(%ecx),%eax 0xc019984c : xchgb %ah,%al 0xc019984e : cmpw $0x800,%ax 0xc0199852 : jne 0xc019985c 0xc0199854 : pushl %ebx 0xc0199855 : call 0xc0199874 0xc019985a : jmp 0xc0199862 0xc019985c : pushl %ebx 0xc019985d : call 0xc016d99c 0xc0199862 : addl $0x4,%esp 0xc0199865 : jmp 0xc0199731 0xc019986a : movl %esi,%esi 0xc019986c : leal 0xfffffff8(%ebp),%esp 0xc019986f : popl %ebx 0xc0199870 : popl %esi 0xc0199871 : leave 0xc0199872 : ret End of assembler dump. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Description: kernel config Content-Disposition: attachment; filename=NAG-ORANGE # machine i386 cpu I586_CPU cpu I686_CPU ident "NAG-ORANGE" maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options INCLUDE_CONFIG_FILE # Include this file in kernel options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST options DUMMYNET options MD5 # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support device rl # RealTek 8129/8139 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device bpf #Berkeley packet filter --LpQ9ahxlCli8rRTG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 5:52:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from irmgard.exp-math.uni-essen.de (irmgard.exp-math.uni-essen.de [132.252.150.18]) by hub.freebsd.org (Postfix) with ESMTP id C0A4B37B651 for ; Thu, 23 Mar 2000 05:52:36 -0800 (PST) (envelope-from eowmob@exp-math.uni-essen.de) Received: from werner.exp-math.uni-essen.de (werner.exp-math.uni-essen.de [132.252.150.17]) by irmgard.exp-math.uni-essen.de (8.9.3/8.9.3) with SMTP id OAA18002; Thu, 23 Mar 2000 14:52:28 +0100 Received: from localhost by werner.exp-math.uni-essen.de (AIX 4.1/UCB 5.64/4.03) id AA53248; Thu, 23 Mar 2000 14:54:01 +0100 Date: Thu, 23 Mar 2000 14:54:01 +0100 (MEZ) From: "Dr. Michael Weller" To: linux-kernel@vger.rutgers.edu, hackers@FreeBSD.ORG Subject: Re: How a normal user can crash any linux system In-Reply-To: <200003230008.QAA94325@apollo.backplane.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 OK, I know I should not answer to this thread, but I do it anyway, sorry for that. On Wed, 22 Mar 2000, Matthew Dillon wrote: > Generally speaking if a user wants to crash a machine, he can crash > a machine. We've probably 'fixed' a dozen crashability holes in the [...] > For example, just before the 4.0 release it was found that one can > easily run the kernel out of vm_map_entry resources by mmap()ing > hundreds of thousands of tiny files. We added a vm.max_proc_mmap > sysctl to control that. And it still quite easy to bypass the datasize > resource limit through the use of MAP_ANON mmap's. [...] The point is IMHO (all I say here is IMHO, of course), Unix (Ok, Linux Is Not UniX) Unix is intended as an OS to enable a capable user & programmer to use the computer as a very powerful tool. You see this everywhere in the design of Unix. The scripts and possibility of filters everywhere in the system setup and daemons show that and allow the capable person to manipulate and do everything. Of course this is not simple, the OS is designed to be used by a capable user, not for the click a button and hope it does the right thing person. In addition, each single user should be able to get the maximum usage of the machine.. Unfortunately there are some obvious unsolvable conceptional problems if each user can get the maximum usage of the machine for him. Another design issue of Unix is that most of the system is readable by anyone. Normally any user can see which processes everyone else runs, for example. All this is ok in the situation where you have a workgroup of people using a machine to get the maximum use of it. Unix is not designed to have logged in a community of hostile users. And you cannot really make Unix behave like that. Unix does not want to be like that actually: That level of hostility of the os to users would hinder users in a normal context to make good use of the machine. The point here is like always: there does not exist the solution to everything: C (or C++) is a nice language, I like it myself very much.. for example. However, it cannot do everything.. There are cases where Lisp, Fortran maybe Java.. a shell script, whatever... is better suited.. Does that mean you would pervert C to have all the features of these languages? No, you don't. Actually you cannot do that. Some features are actually contrary to each other. So a sensible programmer uses the language most fit to the problem he wants to solve. Now, if you have a bunch of hostile users, you don't let them login into your unix. You don't use unix actually.. You could run one of these old mainframe OS's.. maybe the old IBM VM/CMS.. every user gets actually a small virtual PC with a single threaded CPU and some fixed amount of memory.. Well... you lock up your login session... you can't just login another time.. (no other process possible for you).. you dial up the operator and tell him zillions of excuses and how stupid you are and he will kill your old session.. Oh.. a bug in the OS.. your session is unkillable... don't worry.. at the scheduled maintenance next week the machine is rebooted.. So what does that mean? Unix is just not the right OS for what you want to do and cannot be it and does not want to be it. Is that a problem? Not really.. just choose another OS. Actually, you could achieve what you want under unix by not giving people a full login account but give them a special application as login shell which only allows very limited operations. Loading or coding an own application and run it should by far not be one of their options. Maybe some very restrictive scripting language which is interpreted in a sandbox (a dialect of Java, maybe?) The same holds for the undieable overcommitment thread. Many new linux users come from a single threaded DOS or home computer OS scenario. They just don't understand unix memory semantics. I had the same problem when I first came into contact with unix (not linux those days).. However, I was first surprised only, then informed myself and realized why it was made this way and realized it is indeed useful for me. Actually, in those old days, we used to have some machine with a non-overcommitting unix.. It was a pain.. I tell you.. we could simply not use all the memory the machine actually had.. just because the fork() and general process semantics of Unix does not work w/o overcommitting. That machine always had megs of never used swapspace around (which was pretty expensive those days). It is a simple decision: you overcommit memory or you don't use the unix API. This does not mean that one should not discuss other ways to deal with OOM.. you may have some quotas or whatever.. I really like the sending of SIGDANGER in case some low watermark is hit and each process can decide to to catch it, notice with some syscall that memory is low and react accordingly.. still it is impossible to completely get rid of overcommitment.. IF you want to have the powers of a unix OS! So, please.. this list is about creation of a unix style os.. if that is not what you need.. go away.. BTW, I must admit I strongly dislike the 'linux world domination' attitude of some people. There is no OS for everything. Not linux, not anything else. This attitude makes people only think linux must be the solution for them when it is not. I don't want a linux OS in my dishwasher as much as I don't want a Windows in there. Best wishes and peace to everyone, Michael. -- Michael Weller: eowmob@exp-math.uni-essen.de, eowmob@ms.exp-math.uni-essen.de, or even mat42b@spi.power.uni-essen.de. If you encounter an eowmob account on any machine in the net, it's very likely it's me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 5:56:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jander.fl.net.au (jander.fl.net.au [202.181.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 2C9EE37B651 for ; Thu, 23 Mar 2000 05:56:29 -0800 (PST) (envelope-from acs@jander.fl.net.au) Received: from localhost (acs@localhost) by jander.fl.net.au (8.9.2/8.8.8) with ESMTP id AAA39762 for ; Fri, 24 Mar 2000 00:56:23 +1100 (EST) (envelope-from acs@jander.fl.net.au) Date: Fri, 24 Mar 2000 00:56:23 +1100 (EST) From: Andrew To: hackers@freebsd.org Subject: Getting data from an inode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a corrupt disk that I cant mount. fsck complains a bit: ** /dev/rwd1s1e CANNOT READ: BLK 16 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 31, LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CLEAN FLAG NOT SET IN SUPERBLOCK FIX? [yn] y 709 files, 7807 used, 12008 free (904 frags, 1388 blocks, 4.6% fragmentation) UPDATE STANDARD SUPERBLOCK? [yn] y CANNOT WRITE: BLK 16 CONTINUE? [yn] y THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 31, ***** FILE SYSTEM WAS MODIFIED ***** mount dies with an I/O error. fsdb allows me to look at the disk and I can see all the inodes of files I'm trying to recover but I'm not sure how to extract the data. A search of the archives reveals imp@village.org wrote a program (icat) to do it but I cant track it down. It was suggested at the time that the functionality be merged into fsdb. Was it? Any ideas? Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 6:10:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jander.fl.net.au (jander.fl.net.au [202.181.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 1AFDD37B6E9 for ; Thu, 23 Mar 2000 06:10:24 -0800 (PST) (envelope-from acs@jander.fl.net.au) Received: from localhost (acs@localhost) by jander.fl.net.au (8.9.2/8.8.8) with ESMTP id BAA39793 for ; Fri, 24 Mar 2000 01:10:22 +1100 (EST) (envelope-from acs@jander.fl.net.au) Date: Fri, 24 Mar 2000 01:10:22 +1100 (EST) From: Andrew To: hackers@freebsd.org Subject: Re: Getting data from an inode In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should have said that I have tried ffsrecov but it segfaults. inumtoptr returns an invalid address, it is passed: Breakpoint 1, inumtoptr (pi={fs = 0x8007000, map = 0x8005000, st = { st_dev = 0, st_ino = 8197, st_mode = 8608, st_nlink = 1, st_uid = 0, st_gid = 5, st_rdev = 131852, st_atimespec = {tv_sec = 953819670, tv_nsec = 0}, st_mtimespec = {tv_sec = 953819670, tv_nsec = 0}, st_ctimespec = {tv_sec = 953819670, tv_nsec = 0}, st_size = 0x0000000000000000, st_blocks = 0x0000000000000000, st_blksize = 65536, st_flags = 0, st_gen = 854941684, st_lspare = 0, st_qspare = {0xf0696c00f02261b8, 0x0000000000000000}}}, inum=2) at main.c:412 Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 7:22:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jander.fl.net.au (jander.fl.net.au [202.181.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 58CB337C2F7 for ; Thu, 23 Mar 2000 07:22:19 -0800 (PST) (envelope-from acs@jander.fl.net.au) Received: from localhost (acs@localhost) by jander.fl.net.au (8.9.2/8.8.8) with ESMTP id CAA40056 for ; Fri, 24 Mar 2000 02:22:15 +1100 (EST) (envelope-from acs@jander.fl.net.au) Date: Fri, 24 Mar 2000 02:22:15 +1100 (EST) From: Andrew To: hackers@freebsd.org Subject: Getting Data From Inodes (SOLVED) 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 Everyone, I've solved my problem, and here is the problem & solution for the archives. Problem ======= I had a disk crash. Of course backups were out of the question (but I have learnt my lesson this time for sure :-). fsck fixed 2 out of 3 partitions with a few files in lost+found. I mounted those partitions ro and copied off files. The last partition (/var or /dev/wd1s1e) had problems...running fsck: --example-- # fsck /dev/wd1s1e ** /dev/rwd1s1e CANNOT READ: BLK 16 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 31, LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CLEAN FLAG NOT SET IN SUPERBLOCK FIX? [yn] y 709 files, 7807 used, 12008 free (904 frags, 1388 blocks, 4.6% fragmentation) UPDATE STANDARD SUPERBLOCK? [yn] y CANNOT WRITE: BLK 16 CONTINUE? [yn] y THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 31, ***** FILE SYSTEM WAS MODIFIED ***** --eoe-- it seems my superblock was damaged. My backup copy was Ok as fsck could use it. fsck tried to restore the master superblock from the backup but got a disk error (this disk is sick). I couldnt mount /var as mount died with an I/O error...presumably trying to read the super block. I used fsdb to look at the disk and all/most of the data was still there. I could get the inode numbers of the files I wanted but had no idea how to get the data, even though I felt sure it was possible. SOLUTION ======== 1) use dd to make the partition a file: dd conv=noerror,sync if=/dev/wd1s1e of=var.file 2) use ffsrecov (from ports) to scan that file for backup superblocks (my primary super block was corrupt so ffsrecov would crash if I tried to recover anything) ffsrecov -s var.file You will get something like: superblock: 16384(byte), 32(block) superblock: 1312912(byte), 2564(block) remeber the byte address of one of the superblocks. 3) edit main.c (from ffsrecov) and find the line: pi.fs = pi.map + SBOFF; replace SBOFF with whatever address you found in part 2 so the line now reads: pi.fs = pi.map + 16384; 4) recompile ffsrecov cd ffsrecov make 5) recover as per normal ffsrecov -c 2 -n var var.file NOTE: If you dont know the inode your after: a) indoe 2 is always the root of the filesystem so if your lucky specifiying this gets you everything b) you can use fsdb to find the inode. Its the number in the ino column. --example-- # fsdb /dev/rwd1s1e ** /dev/rwd1s1e CANNOT READ: BLK 16 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 31, LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 Editing file system `/dev/rwd1s1e' Last Mounted on current inode: directory I=2 MODE=40755 SIZE=512 MTIME=Jul 4 08:14:18 1999 [0 nsec] CTIME=Jul 4 08:14:18 1999 [0 nsec] ATIME=Mar 18 03:36:26 2000 [0 nsec] OWNER=root GRP=wheel LINKCNT=18 FLAGS=0 BLKCNT=2 GEN=5022f135 fsdb (inum: 2)> ls slot 0 ino 2 reclen 12: directory, `.' slot 1 ino 2 reclen 12: directory, `..' slot 2 ino 3 reclen 16: directory, `account' slot 3 ino 4 reclen 12: directory, `at' slot 4 ino 7 reclen 16: directory, `backups' slot 5 ino 8 reclen 16: directory, `crash' slot 6 ino 10 reclen 16: directory, `cron' --eoe-- Thanks to everyone for the great tools, especially John-Mark Gurney for ffsrecov (and for his help last time I had a disk die). I have a few questions though (perhaps showing my lack of knowledge)... 1) why isnt there an option to mount (like -b to fsck) to tell it to look at a different copy of the superblock? This may imply -o ro. Corrupt file systems may panic the machine but that may be the lesser of 2 evils. 2) why dosn't ffsrecov have an option to use the discovered superblocks rather than having to patch the code? I'm guessing someone will say its because I haven't sent in the patches yet :-) 3) why dosn't fsdb have the ability to save the data of an inode to a different fs? This was mentioned as a possible new feature a few years ago according to the archives. Was it decided that this was a bad idea or did it just never get done? 4) why didn't I buy a tpe drive last time I had a disk fail... Thankyou again, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 7:49:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 23A8437B701 for ; Thu, 23 Mar 2000 07:44:44 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id QAA17917 for freebsd-hackers@FreeBSD.ORG; Mon, 20 Mar 2000 16:31:37 -0600 (CST) (envelope-from obonilla) Date: Mon, 20 Mar 2000 16:31:37 -0600 From: Oscar Bonilla To: freebsd-hackers@FreeBSD.ORG Subject: NSS for FreeBSD Message-ID: <20000320163137.A17849@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ long email --- there's a specific question at the end ] I've started work a couple of weeks ago to port the NSS implementation from NetBSD to FreeBSD. This is needed for things like authenticating with an LDAP server, etc. If you search for LDAP in Hackers you'll find a thread that discusses why it's needed in more detail. I've put up a web page showing the status of the NSS port. It's at http://www.fisicc-ufm.edu/~obonilla/nss/ In brief: nsdispatch() has been incorporated to the FreeBSD libc code. getpwent(), getpwnam(), and getpwuid() all call nsdispatch() and work for both files and nis. I wish I could say that work in this file is completed, but I still haven't got to the compat implementation. See below. There are a bunch of other files that need to be modified to make use of the new nsdispatch function. There's a list at the URL given above. I need help with the NIS code. In particular I wish someone could explain to me exactly what the unwind() function in getpwent() does. In detail: The nsdispatch() function is *exactly* the same as in NetBSD. Thus, the NSS mechanism currently works on FreeBSD exactly as it workd in NetBSD. NetBSD's way: Basically you have a file named /etc/nsswitch.conf which tells the C library where to get the info from. So if you have a line saying: hosts files nis it means that /etc/hosts is checked first and the yp maps are checked next. The man page explains this in more detail and is available in the URL given above for those who don't have NetBSD. NetBSD provides also a compatibility mode for two of the system's databases (passwd and group). For example: passwd compat means that the system will behave as it did before the nsdispatch function was added. e.d. lookup files first and if it finds a line +:::::: then it will lookup nis. NetBSD provides an extra parameter, namely: passwd_compat nis which tells the system which database to use *after* files and when it finds the +::::: token. This makes sense since NetBSD supports two different databases besides files out of the box: NIS, and Hesiod (extra DNS records). I personally don't see this as a big benefit, since if I wanted to have the system lookup stuff first in files and then in, say, hesiod. I would just get rid of the +:::: token in /etc/passwd and change the /etc/nsswitch.conf to be: passwd files dns instead of relaying on the compat stuff. I'm sure there's a good reason they did it like this, I just can't seem to find it. FreeBSD's proposed way: Given that FreeBSD doesn't support Hesiod, I think it would make sense to have nsswitch behave the following way: *exactly* like NetBSD for all databases minus compat. *only* for compat: get rid of the foo_compat blah to select blah as the source for database foo and simply make compat mode behave exactly as it behaves now (pre nss); which is, lookup files and if it finds the +::::: token, lookup NIS. Specific Question: For the FreeBSD implementation of NSS: is it worth to have a way to tell the compat database which source to use for the +::::: token in /etc/passwd or should it just default to NIS? Help: If someone is interested in helping with this I would appreciate it. Thanks and Regards, -Oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 8:49:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id A80A137C0BA for ; Thu, 23 Mar 2000 08:49:24 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JNDQ572YAA000YHC@research.kpn.com> for freebsd-hackers@freebsd.org; Thu, 23 Mar 2000 17:49:22 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Thu, 23 Mar 2000 17:49:22 +0100 Content-return: allowed Date: Thu, 23 Mar 2000 17:49:19 +0100 From: "Koster, K.J." Subject: getting a libgcc.so To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522013139CB@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear -hackers, I've traced the unsatisfied link error I get from the Swing demo's in the new JDK1.2.2 port to a missing __pure_virtual symbol. It is defined in /usr/lib/libgcc*.a. However, I suspect that I need a libgcc.so instead. How do I convert libgcc_pic.a into libgcc.so? After looking in the mailing list archives I tried: gcc -shared /usr/lib/libgcc_pic.a -o libgcc.so This yields a shared library that defines no symbols, however. What am I doing wrong? How do I convert a static library into a dynamic one? I then created my own libgcc.so from the source files of libgcc_pic.a, and that seems to work. Why is libgcc.so not created by default? Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 9: 1:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 04A4837B57C for ; Thu, 23 Mar 2000 09:01:30 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 866913E42; Thu, 23 Mar 2000 18:01:28 +0100 (CET) Date: Thu, 23 Mar 2000 18:01:28 +0100 From: Jesper Skriver To: sthaug@nethelp.no Cc: brooks@one-eyed-alien.net, dmiller@search.sparks.net, freebsd-hackers@FreeBSD.ORG Subject: Re: NCR/FXP and coredumps Message-ID: <20000323180128.B8230@skriver.dk> References: <20000322211607.A7582@orion.ac.hmc.edu> <36763.953798308@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <36763.953798308@verdi.nethelp.no>; from sthaug@nethelp.no on Thu, Mar 23, 2000 at 08:58:28AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 08:58:28AM +0100, sthaug@nethelp.no wrote: > > > 1) I managed to crash an intel N440BX mobo with an fxp card and the > > > onboard ncr drivers. Lots of network traffic (ping floods) and disk IO > > > (rawio in parallel on two disks) took it down in something like two > > > hours. I know this is a known bug, I'm just offering core dumps and > > > testing services in fixing it if anyone wants to take a stab at it. > > > > DG has looked at this extensively and the current feeling is that this is > > a hardware bug. Using the sym driver instead of the ncr driver > > apparently helps somewhat, but the problem still happens. The generally > > recommended option is to buy an Adaptec SCSI controller and use that > > instead of the on-board SCSI. That works flawlessly. > > I can confirm that the sym driver has cured all such problems for us. > Not a single crash after switching to the sym driver. Same here on a box that get's severe beating - I've just ordered 3 additional Tecram controllers for that box, hope it remains stable ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 10: 0:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BF68537BEB3 for ; Thu, 23 Mar 2000 10:00:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA02229; Thu, 23 Mar 2000 10:00:20 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 10:00:20 -0800 (PST) From: Matthew Dillon Message-Id: <200003231800.KAA02229@apollo.backplane.com> To: Andrew Cc: hackers@FreeBSD.ORG Subject: Re: Getting Data From Inodes (SOLVED) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :1) use dd to make the partition a file: : : dd conv=noerror,sync if=/dev/wd1s1e of=var.file : :2) use ffsrecov (from ports) to scan that file for backup superblocks (my :primary super block was corrupt so ffsrecov would crash if I tried to :recover anything) : : ffsrecov -s var.file :... You can also run fsck on the file directly, believe it or not! Use the -b option to specify the alternate superblock. You can then use the VN device to mount the file as a filesystem and copy it off, or you can run dump specifying the file directly (not use vn) to copy it off. Example: dd if=/dev/da0s1a of=fubar bs=32k fsck fubar fubar is not a disk device CONTINUE? [yn] y ... vnconfig -r labels -c vn0 fubar mount /dev/vn0 /mnt Or (WARNING: make sure you specify the proper arguments to dump or you may accidently overwrite the image file): dd if=/dev/da0s1a of=fubar bs=32k fsck fubar fubar is not a disk device CONTINUE? [yn] y ... dump 0af - fubar > fubar.dump :Thankyou again, : :Andrew : -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 Thu Mar 23 10:10:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.indy.net (postal.indy.net [199.3.65.16]) by hub.freebsd.org (Postfix) with ESMTP id 7AB1B37C199 for ; Thu, 23 Mar 2000 10:10:42 -0800 (PST) (envelope-from jon@hiarc.com) Received: from indy3.indy.net (uucp@indy3 [199.3.65.14]) by postal.indy.net (8.9.3/8.9.3) with ESMTP id NAA27553 for ; Thu, 23 Mar 2000 13:10:13 -0500 (EST) Received: (from uucp@localhost) by indy3.indy.net (8.8.7/8.8.7) with UUCP id NAA23055 for freebsd-hackers@freebsd.org; Thu, 23 Mar 2000 13:13:42 -0500 (EST) Received: from hiarc.hiarc.com (hiarc.hiarc.com [134.68.1.13]) by gate.hiarc.com (8.9.3/8.9.3) with ESMTP id NAA02151 for ; Thu, 23 Mar 2000 13:08:41 -0500 (EST) (envelope-from jon@hiarc.com) Received: (from jon@localhost) by hiarc.hiarc.com (8.9.3/8.9.3) id NAA15635 for freebsd-hackers@freebsd.org; Thu, 23 Mar 2000 13:14:09 -0500 (EST) Date: Thu, 23 Mar 2000 13:14:09 -0500 (EST) From: Jon Burgoyne Message-Id: <200003231814.NAA15635@hiarc.hiarc.com> To: freebsd-hackers@freebsd.org Subject: HELP.. Can't install 4.0 on 486/100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gang, Have not been able to resolve this problem of failure to install on the following platform: Alaris Tornado motherboard with 486/100 IBM Blue Lightning CPU 28MB ram 1 built in IDE (OPTI??? chipset) with 2 disks (170MB Master, 20GB secondary) 1 SoundBlaster IDE set to 3rd IDE bus hooked to an IDE CDROM 3c509a Ethernet card Diamond SpeedStar PRO VLB Video card 256k external cache I get through both install floppies and go to the Visual config page. As soon as I quit/save that, the machine goes through a few kernel lines, last one is npx0 and then: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xca57 fault code = supervisor read, page not present instruction pointer = 0x8:0xca57 stack pointer = 0x10:0xc060ee58 frame pointer = 0x10:0xc060ee74 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio cam trap number = 12 panic: page fault Automatic reboot in 15 seconds ... The fault address is different every time I run it. Have tried taking everything out of the machine except the Video card (have even tried different video cards) also have taken it down to 16MB. Have tried turning off ALL cache and increasing wait states on RAM, always get the same error at the same place. This machine runs RedHat 6.1 just fine, also spent years running DOS/WIn3.1, I have not been happy with RedHat and would REALLY like to convert it to BSD. Any ideas? Please email as I don't have access to the group.. thank you, jon +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Jon Burgoyne Hiarc Inc | + jon@hiarc.com Tech Support / Software Development + | Voice: US 765-349-0037 Fax: US 765-349-0336 | + + | "The Internet is like a town that leaves its streets unmarked on the | + principle that people who don't already know don't belong" + | -James Glieck | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 10:29:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DC71037C4EB for ; Thu, 23 Mar 2000 10:29:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA02591; Thu, 23 Mar 2000 10:29:52 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 10:29:52 -0800 (PST) From: Matthew Dillon Message-Id: <200003231829.KAA02591@apollo.backplane.com> To: Jim Mercer Cc: hackers@FreeBSD.ORG Subject: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, lets see what we have here. %ebx is NULL at the point the code fails. (the <------ below at c01997c8) %ebx is the 'm' pointer. if (m->m_len < sizeof(struct arphdr) && :0xc0199794 : cmpl $0x7,0xc(%ebx) :0xc0199798 : ja 0xc01997c8 :0xc019979a : pushl $0x8 :0xc019979c : pushl %ebx (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { :0xc019979d : call 0xc016e4b8 :0xc01997a2 : addl $0x8,%esp :0xc01997a5 : testl %eax,%eax :0xc01997a7 : sete %al :0xc01997aa : movzbl %al,%ebx BING BING BING! :0xc01997ad : testl %ebx,%ebx The compiler is screwed. The call to m_pullup returns the new 'm' pointer in %eax. This should be copied to %ebx verbatim. What the frig is this 'sete' instruction? And the movzbl ? Move byte to long? No wonder %ebx is screwed! The compiler is producing shit for code! Can one of the compiler gurus take a look at this? Jim, what C flags is make using when you compile up your kernel? Are you trying to do weird optimizations? I don't see anything in your kernel config, do you have anything weird in your /etc/make.conf[.local]? -Matt :0xc01997af : je 0xc01997c8 :0xc01997b1 : pushl $0xc024bae0 :0xc01997b6 : pushl $0x3 :0xc01997b8 : call 0xc015f524 :0xc01997bd : addl $0x8,%esp :0xc01997c0 : jmp 0xc0199731 :0xc01997c5 : leal 0x0(%esi),%esi :0xc01997c8 : movl 0x8(%ebx),%ecx <------------ :0xc01997cb : movzwl (%ecx),%eax :0xc01997ce : xchgb %ah,%al :0xc01997d0 : cmpw $0x1,%ax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 10:45:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by hub.freebsd.org (Postfix) with ESMTP id 5678537BFEB for ; Thu, 23 Mar 2000 10:45:54 -0800 (PST) (envelope-from lconrad@Go2France.com) Received: from sv.Go2France.com [212.73.210.79] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A76A59F0344; Thu, 23 Mar 2000 19:50:18 +0100 Message-Id: <4.3.2.20000323194016.020dbef0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Thu, 23 Mar 2000 19:45:08 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: gmake pb's Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Really axious to give Listar a whirl, please help me get through gmake. tia, Len ================= FreeBSD 3.4-release, gmake on 0.128a gives me (newbie) this: gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/usr/ports/mail/listar/listar-0.128a/src/modules/pa ssword' [Build: password] Built module successfully. gcc -Wall -Werror -I./inc -DGNU_STRFTIME -DDYNMOD -DBSDMOD -c inte rnal.c internal.c: In function `cmdarg_upgrade': internal.c:65: parse error before `)' internal.c:68: parse error before `)' cc1: warnings being treated as errors internal.c:71: warning: control reaches end of non-void function internal.c: At top level: internal.c:71: parse error before `else' internal.c:75: warning: parameter names (without types) in function declaration internal.c:75: warning: data definition has no type or storage class internal.c:76: parse error before `}' gmake: *** [internal.o] Error 1 ========================== Thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 10:55:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9671D37C6E6 for ; Thu, 23 Mar 2000 10:55:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA02948; Thu, 23 Mar 2000 10:55:38 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 10:55:38 -0800 (PST) From: Matthew Dillon Message-Id: <200003231855.KAA02948@apollo.backplane.com> To: Matthew Dillon Cc: Jim Mercer , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found it. The code itself is broken. I missed the lack of parens. if (m->m_len < sizeof(struct arphdr) && (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { log(LOG_ERR, "arp: runt packet -- m_pullup failed."); continue; Should be: if (m->m_len < sizeof(struct arphdr) && ((m = m_pullup(m, sizeof(struct arphdr))) == NULL)) { log(LOG_ERR, "arp: runt packet -- m_pullup failed."); continue; I'm committing the fix now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:23:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ptd.net (mail2.ha-net.ptd.net [207.44.96.66]) by hub.freebsd.org (Postfix) with SMTP id C505637BE35 for ; Thu, 23 Mar 2000 11:23:54 -0800 (PST) (envelope-from tms2@mail.ptd.net) Received: (qmail 2011 invoked from network); 23 Mar 2000 19:24:04 -0000 Received: from du208.cli.ptd.net (HELO mail.ptd.net) (204.186.33.208) by mail.ptd.net with SMTP; 23 Mar 2000 19:24:04 -0000 Message-ID: <38DA6F22.90DB3388@mail.ptd.net> Date: Thu, 23 Mar 2000 14:23:14 -0500 From: "Thomas M. Sommers" X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@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: > > :0xc01997a7 : sete %al > :0xc01997aa : movzbl %al,%ebx BING BING BING! > :0xc01997ad : testl %ebx,%ebx > [snip] > What the frig is this 'sete' instruction? And the movzbl ? Move byte > to long? > sete is set byte if equal (zf set). movzbl is as you supposed, but with zero extend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:42:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id D78F437BA8D for ; Thu, 23 Mar 2000 11:42:44 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA22649; Thu, 23 Mar 2000 12:42:21 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA04132; Thu, 23 Mar 2000 12:42:21 -0700 (MST) (envelope-from nate) Date: Thu, 23 Mar 2000 12:42:21 -0700 (MST) Message-Id: <200003231942.MAA04132@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: Jim Mercer , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) In-Reply-To: <200003231855.KAA02948@apollo.backplane.com> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found it. The code itself is broken. I missed the lack of parens. > > if (m->m_len < sizeof(struct arphdr) && > (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > continue; > > > Should be: > > if (m->m_len < sizeof(struct arphdr) && > ((m = m_pullup(m, sizeof(struct arphdr))) == NULL)) { > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > continue; Umm, I see what you've done, but doesn't == have greater precedence than &&, so the code was fine as it was, wasn't it? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:45:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id C81F437BDC3 for ; Thu, 23 Mar 2000 11:45:18 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA22680; Thu, 23 Mar 2000 12:45:07 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA04154; Thu, 23 Mar 2000 12:45:07 -0700 (MST) (envelope-from nate) Date: Thu, 23 Mar 2000 12:45:07 -0700 (MST) Message-Id: <200003231945.MAA04154@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: nate@yogotech.com (Nate Williams) Cc: Matthew Dillon , Jim Mercer , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) In-Reply-To: <200003231942.MAA04132@nomad.yogotech.com> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> <200003231942.MAA04132@nomad.yogotech.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I found it. The code itself is broken. I missed the lack of parens. > > > > if (m->m_len < sizeof(struct arphdr) && > > (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { > > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > > continue; > > > > > > Should be: > > > > if (m->m_len < sizeof(struct arphdr) && > > ((m = m_pullup(m, sizeof(struct arphdr))) == NULL)) { > > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > > continue; > > Umm, I see what you've done, but doesn't == have greater precedence than > &&, so the code was fine as it was, wasn't it? Never mind, I missed the paren. However, I would have written the fix as follow so I wouldn't have missed the fix. :) if (m->m_len < sizeof(struct arphdr) && (m = m_pullup(m, sizeof(struct arphdr))) == NULL) { log(LOG_ERR, "arp: runt packet -- m_pullup failed."); continue; To each his own. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:49: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 8999837BE71 for ; Thu, 23 Mar 2000 11:48:13 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (1932 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 23 Mar 2000 14:47:59 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 23 Mar 2000 14:47:59 -0500 From: Jim Mercer To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) Message-ID: <20000323144759.C983@reptiles.org> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003231829.KAA02591@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Mar 23, 2000 at 10:29:52AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 10:29:52AM -0800, Matthew Dillon wrote: > Jim, what C flags is make using when you compile up your kernel? Are > you trying to do weird optimizations? I don't see anything in your > kernel config, do you have anything weird in your /etc/make.conf[.local]? /etc/make.conf: USA_RESIDENT=YES RSAREF= YES CFLAGS= -O -pipe COPTFLAGS= -O -pipe NO_SENDMAIL= true # do not build sendmail and related programs FORCE_PKG_REGISTER= YES incidentally, i did an "ifconfig rl0 media 10baseT/UTP mediaopt full-duplex" last night (and updated /etc/rc.conf and rebooted) and i haven't had a crash since. i don't know that the ifconfig "fixed" it, but the interface was stuck with a media type of "autoselect" with no clarification of what it autoselected to. i thought maybe the code was getting confused because the interface media type was not specifically set (or at least ifconfig didn't think so). -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:54: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 49C9537BA8D for ; Thu, 23 Mar 2000 11:54:02 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (2048 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 23 Mar 2000 14:53:58 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 23 Mar 2000 14:53:58 -0500 From: Jim Mercer To: Nate Williams Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) Message-ID: <20000323145358.D983@reptiles.org> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> <200003231942.MAA04132@nomad.yogotech.com> <200003231945.MAA04154@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003231945.MAA04154@nomad.yogotech.com>; from nate@yogotech.com on Thu, Mar 23, 2000 at 12:45:07PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 12:45:07PM -0700, Nate Williams wrote: > Never mind, I missed the paren. However, I would have written the fix > as follow so I wouldn't have missed the fix. :) > > To each his own. :) so, with this fix, do you think i can consider the box stable enough for production? ie. was the code obviously broken to cause the problem i was seeing, or is it possible that there are other issues (heat, bad memory, etc) that could be causing it? i'm really getting pushed to get the server running, and, well i'm nervous to put it in if it is going to continue to spontaneously reboot. and, since the server has a "Powered by FreeBSD" sticker on it, stability would be a good thing for these corporate types to see. 8^) i'm looking for opinion here, i won't hold you to it. (in fact, i'm really, really pleased that you guys jumped on this so quickly) -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 11:56:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id A42B637B799 for ; Thu, 23 Mar 2000 11:56:40 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA22779; Thu, 23 Mar 2000 12:56:36 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA04252; Thu, 23 Mar 2000 12:56:35 -0700 (MST) (envelope-from nate) Date: Thu, 23 Mar 2000 12:56:35 -0700 (MST) Message-Id: <200003231956.MAA04252@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jim Mercer Cc: Nate Williams , Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) In-Reply-To: <20000323145358.D983@reptiles.org> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> <200003231942.MAA04132@nomad.yogotech.com> <200003231945.MAA04154@nomad.yogotech.com> <20000323145358.D983@reptiles.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Never mind, I missed the paren. However, I would have written the fix > > as follow so I wouldn't have missed the fix. :) > > > > To each his own. :) > > so, with this fix, do you think i can consider the box stable enough for > production? I'll let Matt answer it, but based on the back-trace and Matt's sleuthing, I'd say he fixed the cause of the panic. > (in fact, i'm really, really pleased that you guys jumped on this so quickly) Matt did all the work, I just whined (bogusly) about some parens. ;-) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 12: 2:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id CCFA837B7CF for ; Thu, 23 Mar 2000 12:02:35 -0800 (PST) (envelope-from jim@reptiles.org) Received: from localhost (2061 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 23 Mar 2000 15:02:32 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 23 Mar 2000 15:02:32 -0500 From: Jim Mercer To: Nate Williams Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) Message-ID: <20000323150231.F983@reptiles.org> References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> <200003231942.MAA04132@nomad.yogotech.com> <200003231945.MAA04154@nomad.yogotech.com> <20000323145358.D983@reptiles.org> <200003231956.MAA04252@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003231956.MAA04252@nomad.yogotech.com>; from nate@yogotech.com on Thu, Mar 23, 2000 at 12:56:35PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 12:56:35PM -0700, Nate Williams wrote: > > so, with this fix, do you think i can consider the box stable enough for > > production? > > I'll let Matt answer it, but based on the back-trace and Matt's > sleuthing, I'd say he fixed the cause of the panic. cool. when he said "i've committed the change" does that mean that i'll get the fix if i "cvsup 4.x-stable-supfile"? bah, why don't i just do it and see? 8^) > > (in fact, i'm really, really pleased that you guys jumped on this so quickly) > > Matt did all the work, I just whined (bogusly) about some parens. ;-) to some degree, it was a passive, co-operative effort. if matt's changes were bogus, you would have whined (unbogusly), and maybe help redirect the effort. matt: beer/pizza is on me, lemme know where you hang out. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 12:16:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A208237B579 for ; Thu, 23 Mar 2000 12:16:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA03852; Thu, 23 Mar 2000 12:16:18 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 12:16:18 -0800 (PST) From: Matthew Dillon Message-Id: <200003232016.MAA03852@apollo.backplane.com> To: Jim Mercer Cc: Nate Williams , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@apollo.backplane.com> <200003231942.MAA04132@nomad.yogotech.com> <200003231945.MAA04154@nomad.yogotech.com> <20000323145358.D983@reptiles.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Thu, Mar 23, 2000 at 12:45:07PM -0700, Nate Williams wrote: :> Never mind, I missed the paren. However, I would have written the fix :> as follow so I wouldn't have missed the fix. :) :> :> To each his own. :) : :so, with this fix, do you think i can consider the box stable enough for :production? : :ie. was the code obviously broken to cause the problem i was seeing, or is : it possible that there are other issues (heat, bad memory, etc) that could : be causing it? Yes, the code was obviously broken. In fact, the code in question is less then a month old -- it was committed in the rush prior to the release. Officially our production quality releases are .1 and higher releases, not .0 releases. Unofficially I think that 4.0 is very close to production quality -- good enough for me to use, definitely! It's way ahead of the curve compared to earlier .0 releases (e.g. 3.0), way ahead of NT and, judging from the linux-kernel lists I think we are way ahead of linux in regards to reliability and heavy-load handling with this release too (note that linux has other strengths, in particular they are about a year ahead of us in regards to SMP performance). Solaris on Sun hardware is the only thing that beats us reliability-wise at the moment, and not by much. The problems cropping up seem to be due more to cockpit trouble during the pre-release rush then to longer-term issues. Consequently, problems should be fairly easy to find and fix. There are still bugs, of course - I haven't tracked down why an NFS client can crash if a file is ripped out from under it on the server, for example. But when you take the intersection between known bugs and your use of the system there is a good chance of not having any overlap at all. The number one issue for me has been and always will be reliability first, performance second. I can always throw another machine into a rack, but an extra employee to deal with failures costs real money! I think FreeBSD gets a bum-rap sometimes for being behind the SMP curve - it's a favorite point of the linux masses and Microsoft likes to bludgeon both Linux and FreeBSD with their superior SMP implementation in NT. But when it comes right down to it the real cost savings to a company (or individual) these days has little to do with machine performance and a whole lot to do with the man hours wasted fixing problems. In any ongoing development new bugs will always be introduced. The key is to manage development in such a way that newly introduced bugs become immediately obvious and easily fixed. In my opinion, FreeBSD is far ahead of all the other open source projects in regards to this management goal. -Matt Matthew Dillon :i'm really getting pushed to get the server running, and, well i'm nervous to :put it in if it is going to continue to spontaneously reboot. : :and, since the server has a "Powered by FreeBSD" sticker on it, stability :would be a good thing for these corporate types to see. 8^) : :i'm looking for opinion here, i won't hold you to it. :(in fact, i'm really, really pleased that you guys jumped on this so quickly) : :-- :[ Jim Mercer jim@reptiles.org +1 416 506-0654 ] :[ Reptilian Research -- Longer Life through Colder Blood ] :[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 12:42:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7F02037B942 for ; Thu, 23 Mar 2000 12:42:11 -0800 (PST) (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 NAA35697; Thu, 23 Mar 2000 13:42:09 -0700 (MST) (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 NAA43568; Thu, 23 Mar 2000 13:42:05 -0700 (MST) Message-Id: <200003232042.NAA43568@harmony.village.org> To: "Allen Pulsifer" Subject: Re: Question about PCI vendor 0x127a Cc: ulf@Alameda.net, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 22:15:43 EST." References: Date: Thu, 23 Mar 2000 13:42:05 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Allen Pulsifer" writes: : Device ID: : 0x2005 : Chip Number: RS56/SP-PCI11P1 : Description: Single chip 56K V90 modem/spkrphone Changes are very good this won't be supported by the pci serial code I'm getting ready to commit to -current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 13:27:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 8830B37B52A for ; Thu, 23 Mar 2000 13:27:39 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id NAA05166; Thu, 23 Mar 2000 13:27:12 -0800 (PST) (envelope-from ulf) Date: Thu, 23 Mar 2000 13:27:12 -0800 From: Ulf Zimmermann To: Warner Losh Cc: Allen Pulsifer , ulf@Alameda.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Question about PCI vendor 0x127a Message-ID: <20000323132712.H95709@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <200003232042.NAA43568@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003232042.NAA43568@harmony.village.org>; from imp@village.org on Thu, Mar 23, 2000 at 01:42:05PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 01:42:05PM -0700, Warner Losh wrote: > In message "Allen Pulsifer" writes: > : Device ID: > : 0x2005 > : Chip Number: RS56/SP-PCI11P1 > : Description: Single chip 56K V90 modem/spkrphone > > Changes are very good this won't be supported by the pci serial code > I'm getting ready to commit to -current. I looked a bit around and this is reported to be a Winmodem. Never use a modem anyways and if I really have to ....... I still have a good trusty pcmcia card. I should just test it with 4.0 > > Warner -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 13:33:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1939F37B64A for ; Thu, 23 Mar 2000 13:33:17 -0800 (PST) (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 OAA35873; Thu, 23 Mar 2000 14:33:13 -0700 (MST) (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 OAA43894; Thu, 23 Mar 2000 14:33:09 -0700 (MST) Message-Id: <200003232133.OAA43894@harmony.village.org> To: ulf@Alameda.net Subject: Re: Question about PCI vendor 0x127a Cc: Allen Pulsifer , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Mar 2000 13:27:12 PST." <20000323132712.H95709@PacHell.TelcoSucks.org> References: <20000323132712.H95709@PacHell.TelcoSucks.org> <200003232042.NAA43568@harmony.village.org> Date: Thu, 23 Mar 2000 14:33:09 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000323132712.H95709@PacHell.TelcoSucks.org> Ulf Zimmermann writes: : I looked a bit around and this is reported to be a Winmodem. Never use : a modem anyways and if I really have to ....... I still have a good : trusty pcmcia card. I should just test it with 4.0 Yup. The 99.99% of all pci modems are winmodems of some flavor or another. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 14:26:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moebius2.Space.Net (moebius2.Space.Net [195.30.1.100]) by hub.freebsd.org (Postfix) with SMTP id 6D3CE37CA05 for ; Thu, 23 Mar 2000 14:26:15 -0800 (PST) (envelope-from maex@Space.Net) Received: (qmail 79900 invoked by uid 1013); 23 Mar 2000 22:26:10 -0000 Date: Thu, 23 Mar 2000 23:26:10 +0100 From: Markus Stumpf To: freebsd-hackers@freebsd.org Subject: 3.4 - large file - seek problems Message-ID: <20000323232610.E11408@Space.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: SpaceNet GmbH, Muenchen, Germany Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is FreeBSD 3.4 Hmmm ... I've thought files larger than 2 GB are supported since around 2.2.5. Now I have a logfile of a apache server that is -rw-rw-r-- 1 root wheel 2412880509 Mar 23 22:05 access.http.200003-01 If I do $ less access.http.200003-01 Cannot seek to that file position if I do $ tail access.http.200003-01 tail: access.http.200003-01: Invalid argument and then tail just starts outputting the file starting at the first line. Has anybody else seen this problem or did I screw something up? Thanks, \Maex -- SpaceNet GmbH | http://www.Space.Net/ | Stress is when you wake Research & Development | mailto:maex-sig@Space.Net | up screaming and you Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 14:27: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5610537CA0B; Thu, 23 Mar 2000 14:26:31 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12YFz6-0005Cn-00; Thu, 23 Mar 2000 22:21:44 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12YFzB-000DHx-00; Thu, 23 Mar 2000 22:21:49 +0000 Date: Thu, 23 Mar 2000 22:21:49 +0000 From: Ben Smithurst To: hackers@freebsd.org, stable@freebsd.org Subject: repeatable lockup (pipe related?) Message-ID: <20000323222149.C87103@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed a problem which seems to cause a repeatable lockup in both RELENG_3 and RELENG_4 (I don't have any -current machines to test on). basically, I've been able to repeat it by creating a file containing .SH foo, bar, baz and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, when I do nroff -ms foo.ms 2>&1 | less and quit 'less' straight away, the whole system seems to lockup. ^T worked (sometimes), and showed troff using lots of system time (no user time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, but that was about all. (ctrl-alt-del didn't work.) Of course, when it first happened I wasn't trying to process /etc/rc* files with nroff, :-) that's just a case which works (or not) and you guys should be able to use to reproduce it. There's probably an easier way, too, but what the hell. (It seems it doesn't always happen, but normally within a few tries it does.) Can anyone else repeat this? If not, I'll be happy to try to supply any other details you want. (Either that or assume my system is seriously screwed in some way, and you can assume I'm an idiot.) part of the backtrace is: #12 0xc01ecd30 in atkbd_isa_intr (arg=0xc023c5e0) at ../../isa/atkbd_isa.c:120 #13 0xc0131f1c in tsleep (ident=0xc5fdfca0, priority=272, wmesg=0xc01f557d "pipbww", timo=0) at ../../kern/kern_synch.c:480 #14 0xc013df68 in pipe_write (fp=0xc0893a40, uio=0xc601ceec, cred=0xc07bf880, flags=0, p=0xc5afdbe0) at ../../kern/sys_pipe.c:794 #15 0xc013c363 in dofilewrite (p=0xc5afdbe0, fp=0xc0893a40, fd=2, buf=0x807dc60, nbyte=32, offset=-1, flags=0) at ../../sys/file.h:156 #16 0xc013c267 in write (p=0xc5afdbe0, uap=0xc601cf80) at ../../kern/sys_generic.c:298 #17 0xc01e7336 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134732896, tf_esi = 134732696, tf_ebp = -1077938268, tf_isp = -972959788, tf_ebx = 672301476, tf_edx = 134732696, tf_ecx = 134732696, tf_eax = 4, tf_trapno = 22, tf_err = 2, tf_eip = 672262004, tf_cs = 31, tf_eflags = 663, tf_esp = -1077938312, tf_ss = 47}) at ../../i386/i386/trap.c:1073 everything above frame 13 looks like it's DDB related to me. ps shows, root@strontium:/var/crash# ps -N debug.14 -M vmcore.14 -axl UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1000 55894 1 0 18 0 1320 0 opause Is #C2 0:00.13 (zsh) 1000 60555 55894 0 28 0 1004 0 - R+ #C2 0:00.01 (groff) 1000 60703 55894 0 -6 0 892 0 pipecl DE+ #C2 0:00.01 (less) 1000 61398 60555 295 -6 0 1692 0 - R+ #C2 0:00.16 (troff) ... [unrelated things, I think] If anyone can shed any light on this, that'd be great. Thanks... -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 14:39:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1DB7A37C62E for ; Thu, 23 Mar 2000 14:38:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA05012; Thu, 23 Mar 2000 14:38:44 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 14:38:44 -0800 (PST) From: Matthew Dillon Message-Id: <200003232238.OAA05012@apollo.backplane.com> To: Markus Stumpf Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.4 - large file - seek problems References: <20000323232610.E11408@Space.Net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This is FreeBSD 3.4 : :Hmmm ... I've thought files larger than 2 GB are supported since around :2.2.5. :Now I have a logfile of a apache server that is :-rw-rw-r-- 1 root wheel 2412880509 Mar 23 22:05 access.http.200003-01 : :If I do : $ less access.http.200003-01 : Cannot seek to that file position :if I do : $ tail access.http.200003-01 : tail: access.http.200003-01: Invalid argument :and then tail just starts outputting the file starting at the first line. : :Has anybody else seen this problem or did I screw something up? : :Thanks, : : \Maex :SpaceNet GmbH | http://www.Space.Net/ | Stress is when you wake The system supports files over 2GB fine, but obviously 'less' and 'tail' do not. A quick look at 'tail' shows that it is attempting to mmap() the entire file, and this will obviosly fail since the address space isn't big enough. So 'less' and 'tail' are broken. -Matt Matthew Dillon :Research & Development | mailto:maex-sig@Space.Net | up screaming and you :Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't :D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet. : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 14:45: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AFF4737C5F2; Thu, 23 Mar 2000 14:44:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA05041; Thu, 23 Mar 2000 14:44:41 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 14:44:41 -0800 (PST) From: Matthew Dillon Message-Id: <200003232244.OAA05041@apollo.backplane.com> To: Ben Smithurst Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) References: <20000323222149.C87103@strontium.scientia.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : .SH foo, bar, baz : :and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, :when I do : : nroff -ms foo.ms 2>&1 | less : :and quit 'less' straight away, the whole system seems to lockup. ^T :worked (sometimes), and showed troff using lots of system time (no user :time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, :but that was about all. (ctrl-alt-del didn't work.) : :Of course, when it first happened I wasn't trying to process /etc/rc* Awweeesome :-) I was able to repeat it. Should be trivial to fix... obviously a bug in the pipe code somewhere. I'm working on it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 14:46: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7E8D037C5F2; Thu, 23 Mar 2000 14:45:10 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA29693; Thu, 23 Mar 2000 14:45:10 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 23 Mar 2000 14:45:04 -0800 (PST) From: Kris Kennaway To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: gmake pb's In-Reply-To: <4.3.2.20000323194016.020dbef0@mail.Go2France.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, 23 Mar 2000, Len Conrad wrote: > Really axious to give Listar a whirl, please help me get through gmake. The code needs some kind of patch to compile on FreeBSD, from the error you gave. Talk to the listar developers about it or convince someone over on -ports to do the work and make a port for it (and submit back their changes to the developers). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 15:18:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C28A537BB8E for ; Thu, 23 Mar 2000 15:18:46 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA61563; Thu, 23 Mar 2000 17:18:36 -0600 (CST) (envelope-from dan) Date: Thu, 23 Mar 2000 17:18:36 -0600 From: Dan Nelson To: Markus Stumpf Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.4 - large file - seek problems Message-ID: <20000323171836.A59166@dan.emsphone.com> References: <20000323232610.E11408@Space.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.5i In-Reply-To: <20000323232610.E11408@Space.Net>; from "Markus Stumpf" on Thu Mar 23 23:26:10 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 23), Markus Stumpf said: > This is FreeBSD 3.4 > > Hmmm ... I've thought files larger than 2 GB are supported since > around 2.2.5. Large files are supported yes. It's up to the applications to accomodate them though (by using fseeko() instead of fseek(), and off_t instead of int for file positions). > Now I have a logfile of a apache server that is > -rw-rw-r-- 1 root wheel 2412880509 Mar 23 22:05 access.http.200003-01 > > If I do > $ less access.http.200003-01 > Cannot seek to that file position > if I do > $ tail access.http.200003-01 > tail: access.http.200003-01: Invalid argument > and then tail just starts outputting the file starting at the first line. The tail bug has been reported as PR bin/14786, and it looks like there's a patch in there. See if it fixes your problem. As for less, you can contact the author and see if he can fix it; it's not a stock FreeBSD program. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 15:52:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law-f205.hotmail.com [209.185.130.115]) by hub.freebsd.org (Postfix) with SMTP id D751337B942 for ; Thu, 23 Mar 2000 15:52:04 -0800 (PST) (envelope-from jonne30@hotmail.com) Received: (qmail 79953 invoked by uid 0); 23 Mar 2000 23:52:04 -0000 Message-ID: <20000323235204.79952.qmail@hotmail.com> Received: from 212.242.97.165 by www.hotmail.com with HTTP; Thu, 23 Mar 2000 15:52:04 PST X-Originating-IP: [212.242.97.165] From: "Jonas Hakansson" To: hackers@freebsd.org Subject: Help Me Date: Fri, 24 Mar 2000 00:52:04 CET Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When i log in whit telnet this does not show why ??? if ( $?prompt ) then if (-e /var/mail) then set prompt = "`hostname`> " set mail = ( /var/mail/$home:t ) else set prompt = "`uname -n`> " set mail = ( /var/mail/$home:t ) endif stty erase ^H kill ^U intr ^C set erasechar="^H" (echo "stty erase $erasechar kill ^U intr ^C " > /dev/null) >& /dev/tty unset erasechar set history = 200 set savehist = 200 endif ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 16: 8:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5FE6337B9FD for ; Thu, 23 Mar 2000 16:08:08 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p39-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.104]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id JAA18217; Fri, 24 Mar 2000 09:07:55 +0900 (JST) Message-ID: <38DAAB22.5430E144@newsguy.com> Date: Fri, 24 Mar 2000 08:39:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Matthew Dillon Cc: Jim Mercer , hackers@FreeBSD.ORG Subject: Re: Doh, compiler bug... (was Re: possible bug in kernel/if_ether.c) References: <20000322225639.T983@reptiles.org> <200003230515.VAA96507@apollo.backplane.com> <20000323054731.W983@reptiles.org> <200003231829.KAA02591@apollo.backplane.com> <200003231855.KAA02948@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: > > I found it. The code itself is broken. I missed the lack of parens. > > if (m->m_len < sizeof(struct arphdr) && > (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) { > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > continue; > > Should be: > > if (m->m_len < sizeof(struct arphdr) && > ((m = m_pullup(m, sizeof(struct arphdr))) == NULL)) { > log(LOG_ERR, "arp: runt packet -- m_pullup failed."); > continue; > > I'm committing the fix now. Funny. The parenthesis was the FIRST thing I noticed. I just assumed I was remembering the priorities wrong... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 16:54: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9A03F37BB0B; Thu, 23 Mar 2000 16:53:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA06073; Thu, 23 Mar 2000 16:53:53 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 16:53:53 -0800 (PST) From: Matthew Dillon Message-Id: <200003240053.QAA06073@apollo.backplane.com> To: Matthew Dillon Cc: Ben Smithurst , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) References: <20000323222149.C87103@strontium.scientia.demon.co.uk> <200003232244.OAA05041@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: .SH foo, bar, baz :: ::and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, ::when I do :: :: nroff -ms foo.ms 2>&1 | less :: ::and quit 'less' straight away, the whole system seems to lockup. ^T ::worked (sometimes), and showed troff using lots of system time (no user ::time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, I've committed a fix to this in -current, 4.x, and 3.x. Rev 1.61 kern/sys_pipe.c (current), 1.60.2.1 in RELENG_4, something else in RELENG_3. Sorry 2.2.x'rs, three is my limit :-) What happens is that the pipe writer checks for the reader going away before entering the while() loop on the write, but only checks sporatically inside that loop. There are situations where the reader may go away while the writer is blocked and cause the writer to enter into an infinite loop because the writer believes there is a reader 'reading' when, in fact, the reader side is stuck in pipeclose(). They two sides then play ping-pong tsleep/wakeup with each other forever. -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 Thu Mar 23 17: 7:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2DFAB37C635; Thu, 23 Mar 2000 17:07:40 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA49222; Thu, 23 Mar 2000 17:07:40 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 23 Mar 2000 17:07:40 -0800 (PST) From: Kris Kennaway To: Dan Nelson Cc: Markus Stumpf , freebsd-hackers@FreeBSD.ORG Subject: Re: 3.4 - large file - seek problems In-Reply-To: <20000323171836.A59166@dan.emsphone.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, 23 Mar 2000, Dan Nelson wrote: > The tail bug has been reported as PR bin/14786, and it looks like > there's a patch in there. See if it fixes your problem. As for less, > you can contact the author and see if he can fix it; it's not a stock > FreeBSD program. This is certainly the path to pursue, although I'm not sure how much luck it would have. The GNU maintainers typically are focussed mainly on linux, which I believe does not have support for 64-bit file sizes at the kernel level (perhaps this has been fixed). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 21:33:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 3000637B5B7 for ; Thu, 23 Mar 2000 21:33:26 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 3B9117555; Thu, 23 Mar 2000 21:34:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 2E17C1D89 for ; Thu, 23 Mar 2000 21:34:45 -0800 (PST) Date: Thu, 23 Mar 2000 21:34:45 -0800 (PST) From: Jamie Bowden To: hackers@FreeBSD.org Subject: Possible bug in 3.4 Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the following setup on my machine at home: 12:09am animaniacs /home/jamie %cat /var/run/dmesg.boot 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.4-RELEASE #1: Fri Mar 10 20:15:03 EST 2000 jamie@animaniacs:/usr/src/sys/compile/animaniacs Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233865082 Hz CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> real memory = 134217728 (131072K bytes) avail memory = 127811584 (124816K bytes) Preloaded elf kernel "kernel" at 0xc0290000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc029009c. Probing for devices on PCI bus 0: chip0: rev 0x06 on pci0.0.0 chip1: rev 0x27 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 uhci0: rev 0x02 int d irq 9 on pci0.7.2 ahc0: rev 0x01 int a irq 10 on pci0.8.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x00 int a irq 12 on pci0.9.0 fxp0: rev 0x05 int a irq 9 on pci0.11.0 fxp0: Ethernet address 00:a0:c9:e1:6d:b0 Probing for PnP devices: CSN 1 Vendor ID: ADP1510 [0x10159004] Serial 0x37b48d60 Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <8 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppb0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 aic0 at 0x340-0x35f irq 11 on isa aic0: aic6360, disconnection vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick usb0: uhub0 at usb0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Waiting 5 seconds for SCSI devices to settle pass3 at aic0 bus 0 target 3 lun 0 pass3: Fixed Processor SCSI-2 device pass3: 3.300MB/s transfers changing root device to da0s4a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4148MB (8496884 512 byte sectors: 255H 63S/T 528C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) camcontrol shows the following: 12:14am animaniacs /home/jamie %runas camcontrol devlist -v scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on ahc0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 6 lun 0 (pass2,cd0) < > at scbus0 target -1 lun -1 () scbus1 on aic0 bus 0: at scbus1 target 3 lun 0 (pass3) < > at scbus1 target -1 lun -1 () What I am attempting to do is add a tape drive to scbus1 at SCSI ID 4. aic0 is an Adaptec 1510B PnP ISA card, which works fine as evidenced above. The problem is when I add the tape drive to the chain. The tape device is internal, with termination on the end of the internal cable. The scanner terminates the external segment. Termination on the card is disabled. Once I plug the tape drive in, FreeBSD will not boot. NT and 98 both come up fine, and recognize the tape drive. They both use the 4mm DAT device. I ran a test backup under 98 just to make sure the drive is functioning properly. The drive is a python archive (or maybe the other way around). If I plug the drive in after boot, and attempt to rescan the SCSI bus FreeBSD locks up, which isn't a huge surprise, since I can't quiesce the bus before plugging in the tape drive. It was worth a shot. From a cold or warm boot the kernel loads, and when it probes SCSI devices, the machine locks up if the tape drive is plugged in. Here's the config file from the machine in question: 12:15am animaniacs /home/jamie %cat /usr/src/sys/i386/conf/animaniacs machine "i386" cpu "I586_CPU" #aka Pentium(tm) ident animaniacs maxusers 64 options INCLUDE_CONFIG_FILE #Include this file in kernel options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options IDE_DELAY=5000 #Be optimistic about Joe IDE device options UCONSOLE #Allow users to grab the console options USER_LDT #allow user-level control of i386 ldt options "CPU_FASTER_5X86_FPU" options "CPU_WT_ALLOC" options "NO_F00F_HACK" options "NO_MEMORY_HOLE" options SYSVSHM options SYSVSEM options SYSVMSG options AHC_ALLOW_MEMIO options "VM86" options VESA #needs VM86 defined too!! options MROUTING #Multicast routing options "ICMP_BANDLIM" options MAXCONS=8 #number of virtual consoles options "AUTO_EOI_1" options "AUTO_EOI_2" config kernel root on da0 controller pnp0 controller isa0 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 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 controller aic0 at isa? port ? cam irq ? controller ahc0 controller scbus0 at ahc0 #base SCSI code controller scbus1 at aic0 device da0 #SCSI direct access devices (aka disks) device pass0 #CAM passthrough driver device cd0 #SCSI CD-ROMs device ch0 #SCSI media changer device sa0 #SCSI tape device device od0 #SCSI optical device device sc0 at isa? tty controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device vga0 at isa? port ? conflicts device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 #device psm0 at isa? tty irq 12 device fxp0 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device joy0 at isa? port "IO_GAME" controller uhci0 controller usb0 device uhub0 device ugen0 controller ppc0 at isa? port? net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? pseudo-device loop #Network loopback device pseudo-device ether #Generic Ethernet pseudo-device pty 64 #Pseudo ttys - can go as high as 256 pseudo-device ppp 2 #Point-to-point protocol pseudo-device splash pseudo-device gzip # Exec gzipped a.out's Am I just being an idiot and missing something plain as day here, or is there a real problem? Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:17:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id D7D0337B815 for ; Thu, 23 Mar 2000 23:17:55 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id AAA13028 for ; Fri, 24 Mar 2000 00:25:11 -0700 (MST) (envelope-from davidc@acns.ab.ca) Date: Fri, 24 Mar 2000 00:25:11 -0700 (MST) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: freebsd-hackers@freebsd.org Subject: vm_await() 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 vm_await(), asleep() is called with "vmwait", and then vm_await() just returns. What then happens to the memory at "vmwait" that was passed to asleep()? Am I missing something, other than vm_await is never called so it doesn't really matter? Also, with a quick find, it looks like atapi_queue_cmd() does the same thing in atapi-all.c, but I might be missing something here. Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:27:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A2F9237B56D for ; Thu, 23 Mar 2000 23:27:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA08899; Thu, 23 Mar 2000 23:27:46 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:27:46 -0800 (PST) From: Matthew Dillon Message-Id: <200003240727.XAA08899@apollo.backplane.com> To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In vm_await(), asleep() is called with "vmwait", and then :vm_await() just returns. What then happens to the memory at :"vmwait" that was passed to asleep()? : :Am I missing something, other than vm_await is never called :so it doesn't really matter? : :Also, with a quick find, it looks like atapi_queue_cmd() does the :same thing in atapi-all.c, but I might be missing something here. : :Chad The memory at the 'wait' address you tsleep and wakeup on is never actually accessed, the address is simply used as a placemarker in the hash table. So it's ok to asleep() on an address and then never use it, and it's ok if the object represented by the address is ripped out from under you in that case. -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 Thu Mar 23 23:34:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 670DB37B815 for ; Thu, 23 Mar 2000 23:34:26 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id AAA13075; Fri, 24 Mar 2000 00:41:37 -0700 (MST) (envelope-from davidc@acns.ab.ca) Date: Fri, 24 Mar 2000 00:41:36 -0700 (MST) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() In-Reply-To: <200003240727.XAA08899@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't mean the wait (ident) address, but instead the wmesg address, which is placed in p->p_wmesg, and I think later read by things like top... or am I being obtuse :). Chad On Thu, 23 Mar 2000, Matthew Dillon wrote: > :In vm_await(), asleep() is called with "vmwait", and then > :vm_await() just returns. What then happens to the memory at > :"vmwait" that was passed to asleep()? > : > :Am I missing something, other than vm_await is never called > :so it doesn't really matter? > : > :Also, with a quick find, it looks like atapi_queue_cmd() does the > :same thing in atapi-all.c, but I might be missing something here. > : > :Chad > > The memory at the 'wait' address you tsleep and wakeup on is > never actually accessed, the address is simply used as a > placemarker in the hash table. So it's ok to asleep() on an > address and then never use it, and it's ok if the object > represented by the address is ripped out from under you in > that case. > > -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 Thu Mar 23 23:36: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7206837B885 for ; Thu, 23 Mar 2000 23:36:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA08970; Thu, 23 Mar 2000 23:35:57 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:35:57 -0800 (PST) From: Matthew Dillon Message-Id: <200003240735.XAA08970@apollo.backplane.com> To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I didn't mean the wait (ident) address, but instead the wmesg :address, which is placed in p->p_wmesg, and I think later read :by things like top... or am I being obtuse :). : :Chad The wmesg is always a string constant. Is there a case where it isn't? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:42:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 1B81B37B68D for ; Thu, 23 Mar 2000 23:42:19 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id AAA13099; Fri, 24 Mar 2000 00:49:34 -0700 (MST) (envelope-from davidc@acns.ab.ca) Date: Fri, 24 Mar 2000 00:49:34 -0700 (MST) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() In-Reply-To: <200003240735.XAA08970@apollo.backplane.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 In the case of malloc(), wmesg is set to type->ks_shortdesc, which is not part of the current functions stack, so it is safe for malloc to return. Unless I am wrong, "string", is an automatic variable, and when the current function returns it is no longer vaild. With tsleep() this would never be a problem as tsleep() blocks. Chad On Thu, 23 Mar 2000, Matthew Dillon wrote: > > :I didn't mean the wait (ident) address, but instead the wmesg > :address, which is placed in p->p_wmesg, and I think later read > :by things like top... or am I being obtuse :). > : > :Chad > > The wmesg is always a string constant. Is there a case where it > isn't? > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:44:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DD6BD37B56D for ; Thu, 23 Mar 2000 23:44:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA09084; Thu, 23 Mar 2000 23:44:14 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:44:14 -0800 (PST) From: Matthew Dillon Message-Id: <200003240744.XAA09084@apollo.backplane.com> To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In the case of malloc(), wmesg is set to type->ks_shortdesc, which is :not part of the current functions stack, so it is safe for malloc :to return. Unless I am wrong, "string", is an automatic variable, and :when the current function returns it is no longer vaild. : :With tsleep() this would never be a problem as tsleep() blocks. : :Chad No. "string" is a 'const char *' -- it is global read-only data. It is most certainly not an automatic function variable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:46:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 227B737BC38 for ; Thu, 23 Mar 2000 23:46:08 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id VAA08875 for freebsd-hackers@freebsd.org; Thu, 23 Mar 2000 21:48:49 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003240748.VAA08875@mauibuilt.com> Subject: ahc0: Signaled a Target Abort To: freebsd-hackers@freebsd.org Date: Thu, 23 Mar 2000 21:48:43 -1000 (HST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to get a adaptec 3940 AUW controller to work with an Asus Athlon motherboard (newer AMD 751 chipset) and I have tried 3.3-R 3-4R and 4.0-R and all boot untill it says,... Waiting 15 Seconds for SCSI devices to settle ahc0: Signaled a Target Abort (this is after about 15 seconds) I have no Idea what it is.. I have tried the card in every PCI slot with every other PCI card removed.. I have played with the only PCI setting in the mother board BIOS and I have upgraded teh 3940's bios to the latest 2.11 release. This board and drives work fine in an older P-200 system... if anyone has any ideas please let me know.. Thanks in advance for any reply... Mahalo Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:47:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 11B7437C689 for ; Thu, 23 Mar 2000 23:47:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA09124; Thu, 23 Mar 2000 23:47:27 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:47:27 -0800 (PST) From: Matthew Dillon Message-Id: <200003240747.XAA09124@apollo.backplane.com> To: Matthew Dillon Cc: Chad David , freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: <200003240744.XAA09084@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::to return. Unless I am wrong, "string", is an automatic variable, and ::when the current function returns it is no longer vaild. :: ::With tsleep() this would never be a problem as tsleep() blocks. :: ::Chad : : No. "string" is a 'const char *' -- it is global read-only data. : It is most certainly not an automatic function variable. : : -Matt I will clarify: void blah(void) { fubar("abcdefgh"); } .file "x.c" .version "01.01" gcc2_compiled.: .section .rodata <------- read only global data .LC0: .ascii "abcdefgh\0" <------- string physically here .text .p2align 2,0x90 .globl blah .type blah,@function blah: pushl %ebp movl %esp,%ebp subl $8,%esp addl $-12,%esp pushl $.LC0 call fubar addl $16,%esp .L2: leave ret .Lfe1: .size blah,.Lfe1-blah .ident "GCC: (GNU) 2.95.2 19991024 (release)" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 23 23:50:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id BDBAE37C08A for ; Thu, 23 Mar 2000 23:50:44 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id AAA13132; Fri, 24 Mar 2000 00:57:59 -0700 (MST) (envelope-from davidc@acns.ab.ca) Date: Fri, 24 Mar 2000 00:57:59 -0700 (MST) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() In-Reply-To: <200003240744.XAA09084@apollo.backplane.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 After thinking about it, I don't know what I was thinking :(. Sorry for wasting you time. Chad On Thu, 23 Mar 2000, Matthew Dillon wrote: > > : > :In the case of malloc(), wmesg is set to type->ks_shortdesc, which is > :not part of the current functions stack, so it is safe for malloc > :to return. Unless I am wrong, "string", is an automatic variable, and > :when the current function returns it is no longer vaild. > : > :With tsleep() this would never be a problem as tsleep() blocks. > : > :Chad > > No. "string" is a 'const char *' -- it is global read-only data. > It is most certainly not an automatic function variable. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 0: 2:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 84D4937B56D; Fri, 24 Mar 2000 00:02:34 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from daniel.sobral (root@p08-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.137]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA11290; Fri, 24 Mar 2000 17:02:30 +0900 (JST) Received: (from dcs@localhost) by daniel.sobral (8.9.3/8.9.3) id RAA00373; Fri, 24 Mar 2000 17:01:00 +0900 (JST) (envelope-from dcs) From: "Daniel C. Sobral" Message-Id: <200003240801.RAA00373@daniel.sobral> Subject: ATA problems with changer code To: hackers@freebsd.org Date: Fri, 24 Mar 2000 17:00:54 +0900 (JST) Cc: sos@freebsd.org Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL68 (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 With the latest ata, I get instant panic whenever I call /stand/sysinstall. It seems acdopen() is trying to read the contents of cdp->changer_info, but that pointer is NULL. (kgdb) bt #0 boot (howto=260) at /home/src/sys/kern/kern_shutdown.c:304 #1 0xc0151fc9 in panic (fmt=0xc0214e94 "from debugger") at /home/src/sys/kern/kern_shutdown.c:554 #2 0xc0128ddd in db_panic (addr=-1071797232, have_addr=0, count=-1, modif=0xc6914bd8 "") at /home/src/sys/ddb/db_command.c:433 #3 0xc0128d7c in db_command (last_cmdp=0xc024225c, cmd_table=0xc02420bc, aux_cmd_tablep=0xc0276850) at /home/src/sys/ddb/db_command.c:333 #4 0xc0128e42 in db_command_loop () at /home/src/sys/ddb/db_command.c:455 #5 0xc012af9b in db_trap (type=12, code=0) at /home/src/sys/ddb/db_trap.c:71 #6 0xc01ef5eb in kdb_trap (type=12, code=0, regs=0xc6914d3c) at /home/src/sys/i386/i386/db_interface.c:158 #7 0xc01fc41c in trap_fatal (frame=0xc6914d3c, eva=0) at /home/src/sys/i386/i386/trap.c:919 #8 0xc01fc105 in trap_pfault (frame=0xc6914d3c, usermode=0, eva=0) at /home/src/sys/i386/i386/trap.c:817 #9 0xc01fbcd3 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1063859328, tf_ebp = -963555960, tf_isp = -963555992, tf_ebx = -1063852032, tf_edx = 1, tf_ecx = 64, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071797232, tf_cs = 8, tf_eflags = 66118, tf_esp = -956099232, tf_ss = -948398080}) at /home/src/sys/i386/i386/trap.c:423 #10 0xc01dac10 in acdopen (dev=0xc096cb80, flags=1, fmt=8192, p=0xc7031560) at /home/src/sys/dev/ata/atapi-cd.c:497 #11 0xc018b2ce in spec_open (ap=0xc6914e04) at /home/src/sys/miscfs/specfs/spec_vnops.c:191 #12 0xc018b1d5 in spec_vnoperate (ap=0xc6914e04) at /home/src/sys/miscfs/specfs/spec_vnops.c:117 #13 0xc01c4ee9 in ufs_vnoperatespec (ap=0xc6914e04) at /home/src/sys/ufs/ufs/ufs_vnops.c:2301 #14 0xc0185da0 in vn_open (ndp=0xc6914ed0, fmode=1, cmode=228) at vnode_if.h:189 #15 0xc0181d3d in open (p=0xc7031560, uap=0xc6914f80) at /home/src/sys/kern/vfs_syscalls.c:994 #16 0xc01fc666 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077940188, tf_esi = 0, tf_ebp = -1077943580, tf_isp = -963555372, tf_ebx = -1077938884, tf_edx = 135059519, tf_ecx = 0, tf_eax = 5, tf_trapno = 7, tf_err = 2, tf_eip = 134872180, tf_cs = 31, tf_eflags = 659, tf_esp = -1077943720, tf_ss = 47}) at /home/src/sys/i386/i386/trap.c:1073 #17 0xc01efee6 in Xint0x80_syscall () #18 0x804aea8 in ?? () #19 0x805705f in ?? () #20 0x80480f5 in ?? () (kgdb) up 10 #10 0xc01dac10 in acdopen (dev=0xc096cb80, flags=1, fmt=8192, p=0xc7031560) at /home/src/sys/dev/ata/atapi-cd.c:497 497 if (cdp->slot != cdp->changer_info->current_slot) { (kgdb) list acdopen 484 static int 485 acdopen(dev_t dev, int32_t flags, int32_t fmt, struct proc *p) 486 { 487 struct acd_softc *cdp = dev->si_drv1; 488 489 if (!cdp) 490 return ENXIO; 491 492 if (flags & FWRITE) { 493 if (count_dev(dev) > 1) 494 return EBUSY; 495 } 496 if (count_dev(dev) == 1) { 497 if (cdp->slot != cdp->changer_info->current_slot) { 498 acd_select_slot(cdp); 499 tsleep(&cdp->changer_info, PRIBIO, "acdopn", 0); 500 } (kgdb) p dev->si_drv1 $4 = (void *) 0xc096e800 (kgdb) p cdp $5 = (struct acd_softc *) 0x0 (???? -- this doesn't seem to be the problem, though) (kgdb) print *(struct acd_softc*)dev->si_drv1 $6 = {atp = 0xc067c1e0, lun = 0, flags = 0, buf_queue = {queue = { tqh_first = 0x0, tqh_last = 0xc096e80c}, last_pblkno = 0, insert_point = 0x0, switch_point = 0x0}, toc = {hdr = {len = 0, starting_track = 0 '\000', ending_track = 0 '\000'}, tab = {{0, control = 0, addr_type = 0, track = 0 '\000', 0, addr = {msf = { unused = 0 '\000', minute = 0 '\000', second = 0 '\000', frame = 0 '\000'}, lba = 0, addr = "\000\000\000"}} }}, info = {volsize = 0, blksize = 0}, au = {data_length = 0, medium_type = 0 '\000', dev_spec = 0 '\000', unused = "\000", blk_desc_len = 0, page_code = 0 '\000', param_len = 0 '\000', flags = 0 '\000', reserved3 = 0 '\000', reserved4 = 0 '\000', reserved5 = 0 '\000', lb_per_sec = 0, port = {{channels = 0 '\000', volume = 0 '\000'}, { channels = 0 '\000', volume = 0 '\000'}, {channels = 0 '\000', volume = 0 '\000'}, {channels = 0 '\000', volume = 0 '\000'}}}, cap = { data_length = 6656, medium_type = 3 '\003', dev_spec = 0 '\000', unused = "\000", blk_desc_len = 0, page_code = 42 '*', param_len = 18 '\022', read_cdr = 1 '\001', read_cdrw = 1 '\001', read_packet = 0 '\000', read_dvdrom = 0 '\000', read_dvdr = 0 '\000', read_dvdram = 0 '\000', reserved2_67 = 0 '\000', write_cdr = 0 '\000', write_cdrw = 0 '\000', test_write = 0 '\000', reserved3_3 = 0 '\000', write_dvdr = 0 '\000', write_dvdram = 0 '\000', reserved3_67 = 0 '\000', audio_play = 1 '\001', composite = 0 '\000', dport1 = 0 '\000', dport2 = 0 '\000', mode2_form1 = 1 '\001', mode2_form2 = 1 '\001', multisession = 1 '\001', 0 '\000', cd_da = 1 '\001', cd_da_stream = 1 '\001', rw = 1 '\001', rw_corr = 0 '\000', c2 = 1 '\001', isrc = 1 '\001', upc = 1 '\001', 0 '\000', lock = 1 '\001', locked = 0 '\000', prevent = 0 '\000', eject = 1 '\001', 0 '\000', mech = 1 '\001', sep_vol = 1 '\001', sep_mute = 1 '\001', 0 '\000', max_read_speed = 3528, max_vol_levels = 255, buf_size = 128, cur_read_speed = 3528, reserved3 = 0 '\000', bckf = 0 '\000', rch = 0 '\000', lsbf = 0 '\000', dlen = 0 '\000', 0 '\000', max_write_speed = 0, cur_write_speed = 0}, aumask = {data_length = 0, medium_type = 0 '\000', dev_spec = 0 '\000', unused = "\000", blk_desc_len = 0, page_code = 0 '\000', param_len = 0 '\000', flags = 0 '\000', reserved3 = 0 '\000', reserved4 = 0 '\000', reserved5 = 0 '\000', lb_per_sec = 0, port = {{channels = 0 '\000', volume = 0 '\000'}, {channels = 0 '\000', volume = 0 '\000'}, { channels = 0 '\000', volume = 0 '\000'}, {channels = 0 '\000', volume = 0 '\000'}}}, subchan = {void0 = 0 '\000', audio_status = 0 '\000', data_length = 0, data_format = 0 '\000', control = 0 '\000', track = 0 '\000', indx = 0 '\000', abslba = 0, rellba = 0}, changer_info = 0x0, driver = 0x0, slot = -1, timestamp = 0, block_size = 2048, disklabel = {d_magic = 0, d_type = 0, d_subtype = 0, d_typename = '\000' , d_un = { un_d_packname = '\000' , un_b = {un_d_boot0 = 0x0, un_d_boot1 = 0x0}}, d_secsize = 0, d_nsectors = 0, d_ntracks = 0, d_ncylinders = 0, d_secpercyl = 0, d_secperunit = 0, d_sparespertrack = 0, d_sparespercyl = 0, d_acylinders = 0, d_rpm = 0, d_interleave = 0, d_trackskew = 0, d_cylskew = 0, d_headswitch = 0, d_trkseek = 0, d_flags = 0, d_drivedata = {0, 0, 0, 0, 0}, d_spare = {0, 0, 0, 0, 0}, d_magic2 = 0, d_checksum = 0, d_npartitions = 0, d_bbsize = 0, d_sbsize = 0, d_partitions = {{p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}, {p_size = 0, p_offset = 0, p_fsize = 0, p_fstype = 0 '\000', p_frag = 0 '\000', __partition_u1 = {cpg = 0, sgs = 0}}}}, stats = 0xc095ab00, dev1 = 0xc096cc00, dev2 = 0xc096cb80} (kgdb) disassemble acdopen Dump of assembler code for function acdopen: 0xc01dabbc : pushl %ebp 0xc01dabbd : movl %esp,%ebp 0xc01dabbf : pushl %edi 0xc01dabc0 : pushl %esi 0xc01dabc1 : pushl %ebx 0xc01dabc2 : movl 0x8(%ebp),%esi 0xc01dabc5 : movl 0xc(%ebp),%edi 0xc01dabc8 : movl 0x24(%esi),%ebx 0xc01dabcb : testl %ebx,%ebx 0xc01dabcd : jne 0xc01dabdc 0xc01dabcf : movl $0x6,%eax 0xc01dabd4 : jmp 0xc01dac6e 0xc01dabd9 : leal 0x0(%esi),%esi 0xc01dabdc : testl $0x2,%edi 0xc01dabe2 : je 0xc01dabfc 0xc01dabe4 : pushl %esi 0xc01dabe5 : call 0xc017fc00 0xc01dabea : addl $0x4,%esp 0xc01dabed : cmpl $0x1,%eax 0xc01dabf0 : jle 0xc01dabfc 0xc01dabf2 : movl $0x10,%eax 0xc01dabf7 : jmp 0xc01dac6e 0xc01dabf9 : leal 0x0(%esi),%esi 0xc01dabfc : pushl %esi 0xc01dabfd : call 0xc017fc00 0xc01dac02 : addl $0x4,%esp 0xc01dac05 : cmpl $0x1,%eax 0xc01dac08 : jne 0xc01dac66 0xc01dac0a : movl 0x3ac(%ebx),%eax 0xc01dac10 : movb (%eax),%al 0xc01dac12 : andb $0x1f,%al 0xc01dac14 : movzbl %al,%eax 0xc01dac17 : cmpl %eax,0x3b4(%ebx) 0xc01dac1d : je 0xc01dac3d 0xc01dac1f : pushl %ebx 0xc01dac20 : call 0xc01dc500 0xc01dac25 : pushl $0x0 0xc01dac27 : pushl $0xc022fee8 0xc01dac2c : pushl $0x10 0xc01dac2e : leal 0x3ac(%ebx),%eax 0xc01dac34 : pushl %eax 0xc01dac35 : call 0xc0154888 0xc01dac3a : addl $0x14,%esp 0xc01dac3d : pushl $0x1 0xc01dac3f : pushl %ebx 0xc01dac40 : call 0xc01dcdf4 0xc01dac45 : orb $0x1,0x8(%ebx) 0xc01dac49 : addl $0x8,%esp 0xc01dac4c : testl $0x6,%edi 0xc01dac52 : jne 0xc01dac5c 0xc01dac54 : pushl %ebx 0xc01dac55 : call 0xc01dc108 0xc01dac5a : jmp 0xc01dac63 0xc01dac5c : pushl (%ebx) 0xc01dac5e : call 0xc01d983c 0xc01dac63 : addl $0x4,%esp 0xc01dac66 : pushl %ebx 0xc01dac67 : call 0xc01dc254 0xc01dac6c : xorl %eax,%eax 0xc01dac6e : leal 0xfffffff4(%ebp),%esp 0xc01dac71 : popl %ebx 0xc01dac72 : popl %esi 0xc01dac73 : popl %edi 0xc01dac74 : leave 0xc01dac75 : ret End of assembler dump. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@there.is.no.bsdconspiracy.net [He] took me into his library and showed me his books, of which he had a complete set. -- Ring Lardner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 1:45: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0924D37BA3F; Fri, 24 Mar 2000 01:45:00 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA67462; Fri, 24 Mar 2000 10:44:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003240944.KAA67462@freebsd.dk> Subject: Re: ATA problems with changer code In-Reply-To: <200003240801.RAA00373@daniel.sobral> from "Daniel C. Sobral" at "Mar 24, 2000 05:00:54 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Fri, 24 Mar 2000 10:44:53 +0100 (CET) Cc: hackers@freebsd.org, sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daniel C. Sobral wrote: You are too late, I have committed a fix for that already :) > With the latest ata, I get instant panic whenever I call > /stand/sysinstall. It seems acdopen() is trying to read the contents of > cdp->changer_info, but that pointer is NULL. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 1:47: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3D65137BD79; Fri, 24 Mar 2000 01:47:00 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Mar 2000 09:46:58 +0000 (GMT) Date: Fri, 24 Mar 2000 09:46:58 +0000 From: David Malone To: Kris Kennaway Cc: Dan Nelson , Markus Stumpf , freebsd-hackers@FreeBSD.org Subject: Re: 3.4 - large file - seek problems Message-ID: <20000324094658.A76992@walton.maths.tcd.ie> References: <20000323171836.A59166@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@FreeBSD.org on Thu, Mar 23, 2000 at 05:07:40PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 05:07:40PM -0800, Kris Kennaway wrote: > On Thu, 23 Mar 2000, Dan Nelson wrote: > > > The tail bug has been reported as PR bin/14786, and it looks like > > there's a patch in there. See if it fixes your problem. As for less, > > you can contact the author and see if he can fix it; it's not a stock > > FreeBSD program. > > This is certainly the path to pursue, although I'm not sure how much luck > it would have. The GNU maintainers typically are focussed mainly on linux, > which I believe does not have support for 64-bit file sizes at the kernel > level (perhaps this has been fixed). I think the patch there is one wrote. However I only patched tail, and not "tail -r". I was waiting for someone to test and review my fix before implementing a similar fix for "tail -r". (For reference, it mmaps the file in chunks instead of the whole thing at one time. It made tail very slightly slower, but probably better to have it working properly.) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 2:11:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f171.law8.hotmail.com [216.33.241.171]) by hub.freebsd.org (Postfix) with SMTP id B702737B5EB for ; Fri, 24 Mar 2000 02:11:49 -0800 (PST) (envelope-from swatsa@hotmail.com) Received: (qmail 36837 invoked by uid 0); 24 Mar 2000 10:11:45 -0000 Message-ID: <20000324101145.36836.qmail@hotmail.com> Received: from 202.54.89.15 by www.hotmail.com with HTTP; Fri, 24 Mar 2000 02:11:45 PST X-Originating-IP: [202.54.89.15] From: "svatsa vs" To: freebsd-hackers@freebsd.org Subject: FreeBSD USB Date: Fri, 24 Mar 2000 15:41:45 IST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 2:16:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f304.law8.hotmail.com [216.33.240.179]) by hub.freebsd.org (Postfix) with SMTP id 9BC0337B54B for ; Fri, 24 Mar 2000 02:16:26 -0800 (PST) (envelope-from swatsa@hotmail.com) Received: (qmail 73349 invoked by uid 0); 24 Mar 2000 10:16:25 -0000 Message-ID: <20000324101625.73348.qmail@hotmail.com> Received: from 202.54.89.15 by www.hotmail.com with HTTP; Fri, 24 Mar 2000 02:16:25 PST X-Originating-IP: [202.54.89.15] From: "svatsa vs" To: freebsd-hackers@freebsd.org Subject: FreeBSD USB stack & Class Drivers Date: Fri, 24 Mar 2000 15:46:25 IST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, This mail is from Srivatsa , a member of USB developers in bsd-usb e-group .I would like to know the information about the FreeBSD USB stack & Class Drivers , basically what it contains & from which versions onwards it is available on FreeBSD. I do not know whether it is the stack of only USB drivers or more than it .So I request you to kindly let me know the details as early as possible. Presently i am using FreeBSD 3.4 version . Does this Operating system contain all the above required information ? .Is yes, kindly let me know the path of existence of USB stack & Class Drivers. Looking forward for your reply, Thanking you, Yours sincerely, Srivatsa ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 3:27:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from swebase.com (mail.swebase.com [212.75.75.45]) by hub.freebsd.org (Postfix) with ESMTP id 5689F37B5D0 for ; Fri, 24 Mar 2000 03:27:39 -0800 (PST) (envelope-from kasper@swebase.com) Received: from ns1 [212.75.75.43] by swebase.com (SMTPD32-6.00) id A1E516400D2; Fri, 24 Mar 2000 12:30:45 +0100 From: "Kasper" To: Subject: .cshrc problem Date: Fri, 24 Mar 2000 12:30:23 +0100 Message-ID: <000201bf9584$581ed2e0$2b4b4bd4@swebase.com> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello i have done this in the dot.cshrc file ********************************************** alias h history 25 alias j jobs -l alias la ls -a alias lf ls -FA alias ll ls -lA alias rm rm -i setenv EDITOR pico setenv PAGER more setenv BLOCKSIZE K stty erase '^h' if ($?prompt) then set filec set history = 100 set savehist = 100 endif ***************************************************** But my aliases does not work and when i add * set prompt = "$LOGNAME %" * it does not work either. Whats wrong and how do i fix this? ./kasper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 4:19:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fort.wn.net.ua (fort.wn.net.ua [207.241.164.249]) by hub.freebsd.org (Postfix) with ESMTP id 88E1237B68B; Fri, 24 Mar 2000 04:19:30 -0800 (PST) (envelope-from romik@ASN.WN.net.UA) Received: from ASN.WN.net.UA ([195.5.1.174]) by fort.wn.net.ua (8.9.3/8.9.3) with ESMTP id OAA77698; Fri, 24 Mar 2000 14:20:53 +0200 (EET) Received: (from romik@localhost) by ASN.WN.net.UA (8.9.3/8.9.3) id OAA22334; Fri, 24 Mar 2000 14:24:49 +0200 (EET) (envelope-from romik) Date: Fri, 24 Mar 2000 14:24:48 +0200 From: romik@WN.com.UA To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: WaveLAN PCI Adapter Message-ID: <20000324142448.A22279@WN.NET.UA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i X-Operating-System: FreeBSD ASN.WN.net.UA 3.2-RELEASE FreeBSD 3.2-RELEASE Organization: WN Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello We bought WaveLAN PCI Adapter PCMCIA Controller (SCM Microsystems GMBH PCIC2CPR10 based on PCI1225PDV chip) and have trouble with installing it in FreeBSD 3.4 Does FreeBSD support this device if yes were we can read about this problem ? Please help -- Alex Bolshakov W-Net ISP Kiev Ukraine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 5: 1:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 8CE0E37B5FF; Fri, 24 Mar 2000 05:01:30 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id NAA67212; Fri, 24 Mar 2000 13:01:28 GMT (envelope-from joe) Date: Fri, 24 Mar 2000 13:01:28 +0000 From: Josef Karthauser To: hackers@freebsd.org Cc: dillon@freebsd.org Subject: Growing a memory file system. Message-ID: <20000324130127.F40544@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, 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 I'm embarking on some ufs growing code, and need a test bed other than my harddisk :) Is there a way of allocating a memory filesystem, (or file system on a disk file), that's got empty space at the end? I know that I can use mount_mfs to construct a memory fs, but IIRC if can't allocate more memory on the end that isn't part of the file system. Has anyone any tips? (I'm sure there's a way of doing it with the vn driver, Matt?) Tnx in advance, Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@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 Fri Mar 24 6: 7:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id EF37F37B5BA for ; Fri, 24 Mar 2000 06:07:06 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id JAA12216; Fri, 24 Mar 2000 09:06:56 -0500 (EST) Date: Fri, 24 Mar 2000 09:06:56 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Josef Karthauser Cc: hackers@FreeBSD.ORG Subject: Re: Growing a memory file system. In-Reply-To: <20000324130127.F40544@florence.pavilion.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 Fri, 24 Mar 2000, Josef Karthauser wrote: > I'm embarking on some ufs growing code, and need a test bed other > than my harddisk :) Is there a way of allocating a memory > filesystem, (or file system on a disk file), that's got empty space > at the end? > > I know that I can use mount_mfs to construct a memory fs, but IIRC > if can't allocate more memory on the end that isn't part of the > file system. > > Has anyone any tips? (I'm sure there's a way of doing it with the > vn driver, Matt?) > I would expect that you could use vn to create a device out of a file, newfs that, and play all you want. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 7:46:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 54E7D37B506 for ; Fri, 24 Mar 2000 07:46:35 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id SAA27928; Fri, 24 Mar 2000 18:51:31 +0300 (MSK) Message-Id: <200003241551.SAA27928@aaz.links.ru> Subject: Re: .cshrc problem In-Reply-To: <000201bf9584$581ed2e0$2b4b4bd4@swebase.com> from "Kasper" at "Mar 24, 0 12:30:23 pm" To: kasper@swebase.com (Kasper) Date: Fri, 24 Mar 2000 18:51:30 +0300 (MSK) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Kasper writes: [Charset Windows-1252 unsupported, skipping...] > Hello i have done this in the dot.cshrc file move to .cshrc in your home directory > ********************************************** > alias h history 25 > alias j jobs -l ............... > ***************************************************** > But my aliases does not work and when i add * set prompt = "$LOGNAME %" * it > does not work either. Whats wrong and how do i fix this? PS use -questions list for such questions please -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 8:35:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id D71EC37B775; Fri, 24 Mar 2000 08:35:06 -0800 (PST) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id RAA18239; Fri, 24 Mar 2000 17:35:58 +0100 (CET) (envelope-from tobez) Date: Fri, 24 Mar 2000 17:35:58 +0100 From: Anton Berezin To: Kris Kennaway Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: gmake pb's Message-ID: <20000324173558.A17952@plab.ku.dk> References: <4.3.2.20000323194016.020dbef0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.ORG on Thu, Mar 23, 2000 at 02:45:04PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 02:45:04PM -0800, Kris Kennaway wrote: > On Thu, 23 Mar 2000, Len Conrad wrote: > > > Really axious to give Listar a whirl, please help me get through gmake. > > The code needs some kind of patch to compile on FreeBSD, from the error > you gave. Talk to the listar developers about it or convince someone over > on -ports to do the work and make a port for it (and submit back their > changes to the developers). > > Kris This is from current- list, almost 6 months ago, so prod David about it: Date: Thu, 14 Oct 1999 13:04:11 -0500 (CDT) From: David Scheidt To: Ollivier Robert Cc: jt traub , current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch On Thu, 14 Oct 1999, Ollivier Robert wrote: > According to Jonathan M. Bresler: >> thanks for the note on bouncefilter. >> i'll take a look at it. > > Someday, when you have 5 minutes free (aha!) have a look at Listar. It > is a small, fast and feature-full list manager written in C with > automatic bounce handling (among other things). It also builds almost out of the box on FreeBSD. You have to define BSDMOD, build it, install it, and add a listar user. I have a port that is nearly finished, pending acquistion of a round tuit. > > www.listar.org David Scheidt Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 9:35:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9685637B757 for ; Fri, 24 Mar 2000 09:35:32 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2OHxGR21850; Fri, 24 Mar 2000 09:59:16 -0800 (PST) Date: Fri, 24 Mar 2000 09:59:16 -0800 From: Alfred Perlstein To: svatsa vs Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD USB stack & Class Drivers Message-ID: <20000324095916.L21029@fw.wintelcom.net> References: <20000324101625.73348.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000324101625.73348.qmail@hotmail.com>; from swatsa@hotmail.com on Fri, Mar 24, 2000 at 03:46:25PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * svatsa vs [000324 02:40] wrote: > Hello, > This mail is from Srivatsa , a member of USB developers in bsd-usb e-group > .I would like to know the information about the FreeBSD USB stack & Class > Drivers , basically what it contains & from which versions onwards it is > available on FreeBSD. > I do not know whether it is the stack of only USB drivers or more than it > .So I request you to kindly let me know the details as early as possible. > Presently i am using FreeBSD 3.4 version . Does this Operating system > contain all the above required information ? .Is yes, kindly let me know the > path of existence of USB stack & Class Drivers. > > Looking forward for your reply, Please don't send the same message to list daily, do some research instead, you can browse the FreeBSD kernel source tree at: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys I think the USB stuff is in the 'dev' directory. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 9:35:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from daemon.sofiaonline.com (daemon.sofiaonline.com [212.5.144.1]) by hub.freebsd.org (Postfix) with SMTP id BE54237B5FD for ; Fri, 24 Mar 2000 09:35:35 -0800 (PST) (envelope-from zethix@sofiaonline.com) Received: (qmail 68545 invoked from network); 24 Mar 2000 17:11:27 -0000 Received: from carnivoro.sofiaonline.com (212.5.144.5) by daemon.sofiaonline.com with SMTP; 24 Mar 2000 17:11:27 -0000 Content-Length: 1577 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 24 Mar 2000 18:35:47 +0200 (EET) From: Dungeonkeeper To: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Subject: shell issue Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, First of all: I want to apologise for my poor english. Today me and a few friends of mine discussed the shells' (well, shell is actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion routines, mainly because of a problem discovered by one of my friends. I'm not sure if this is something new... So, let me explain what he found. It seems that the shell wants to allocate enough memory to hold the entire command line when expanding all of the arguments and we can force it to allocate hudge ammount of memory with a tricky command like this: carnivoro# /bin/csh -c `cat /dev/urandom` (I use tcsh here (the carnivoro# prompt), but the same thing happens when testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough memory to hold what it reads from /dev/urandom, because it must be passed as a command line argument to /bin/csh ( actually, any command will be ok ). So, the shell eats more and more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to take some action (like killing some processes... started by other users? system services? or... in my case... crash :). My friend said that he sent a mail to bugtraq describing this problem. Those who are interested can read it. I believe that the shells have a maximum command lenght, so... I'm trying now to make the shell use the same command lenght when expanding such commands. I think this is the best way to avoid this problem. Any ideas? Best regards: zethix What is worth doing is worth the trouble of asking somebody to do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 9:40: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CCBF237B9D5 for ; Fri, 24 Mar 2000 09:40:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA14582; Fri, 24 Mar 2000 09:39:59 -0800 (PST) (envelope-from dillon) Date: Fri, 24 Mar 2000 09:39:59 -0800 (PST) From: Matthew Dillon Message-Id: <200003241739.JAA14582@apollo.backplane.com> To: Kelly Yancey Cc: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: Growing a memory file system. References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> file system. :> :> Has anyone any tips? (I'm sure there's a way of doing it with the :> vn driver, Matt?) :> : : I would expect that you could use vn to create a device out of a file, :newfs that, and play all you want. : : Kelly : :-- :Kelly Yancey - kbyanc@posi.net - Richmond, VA The man page in 4.x for 'vnconfig' has some nifty examples. -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 Fri Mar 24 9:46:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 1620937B59C; Fri, 24 Mar 2000 09:46:26 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id LAA40821; Fri, 24 Mar 2000 11:43:36 -0600 (CST) (envelope-from dan) Date: Fri, 24 Mar 2000 11:43:35 -0600 From: Dan Nelson To: Dungeonkeeper Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: shell issue Message-ID: <20000324114335.A35279@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.5i In-Reply-To: ; from "Dungeonkeeper" on Fri Mar 24 18:35:47 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 24), Dungeonkeeper said: > I believe that the shells have a maximum command lenght, so... I'm > trying now to make the shell use the same command lenght when > expanding such commands. I think this is the best way to avoid this > problem. Any ideas? The kernel has a maximum command-line length, but it that only gets checked when an external executable is run. Something like echo `cat /dev/urandom` would still work, since echo is usually a shell builtin command. The better way to stop malicious people from using up all your memory is to specify a datasize limit in /etc/login.conf . -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10: 1:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from atlas.pathcom.com (pathway1.pathcom.com [209.250.128.4]) by hub.freebsd.org (Postfix) with ESMTP id AED1C37B71D for ; Fri, 24 Mar 2000 10:01:26 -0800 (PST) (envelope-from lwh@pathcom.com) Received: from dial-0428.tor.pathcom.com (dial-0428.tor.pathcom.com [216.249.1.174]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id NAA14379 for ; Fri, 24 Mar 2000 13:01:00 -0500 (EST) Date: Fri, 24 Mar 2000 13:00:54 -0500 (EST) From: Luke Hollins Reply-To: lwh@pathcom.com To: freebsd-hackers@freebsd.org Subject: top sorting error Message-ID: Confirm-Reading-To: "Me" Disposition-Notification-To: "luke" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if this is specific to FreeBSD but I just noticed it when i picked o time in top: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 79364 root 2 0 2696K 1636K select 8:23 0.00% 0.00% apache 235 mysql 2 0 13372K 6384K poll 361:14 0.15% 0.15% mysqld I am pretty sure 361:14 > 8:23 (unless its 8 weeks, 23 days ? ) I tried on solaris : PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 3158 root 1 59 0 20M 14M sleep 357:55 6.44% Xsun 4133 root 1 44 0 32M 21M sleep 36:10 0.00% netscape 3250 root 1 57 0 4868K 3368K sleep 23:05 0.55% wmaker which seems the right way. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10: 5: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 420AD37B7CE; Fri, 24 Mar 2000 10:04:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA14795; Fri, 24 Mar 2000 10:04:25 -0800 (PST) (envelope-from dillon) Date: Fri, 24 Mar 2000 10:04:25 -0800 (PST) From: Matthew Dillon Message-Id: <200003241804.KAA14795@apollo.backplane.com> To: Dungeonkeeper Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: shell issue References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi there, : :First of all: I want to apologise for my poor english. : :Today me and a few friends of mine discussed the shells' (well, shell is :actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion :routines, mainly because of a problem discovered by one of my friends. I'm not :sure if this is something new... So, let me explain what he found. It seems :that the shell wants to allocate enough memory to hold the entire command line :when expanding all of the arguments and we can force it to allocate hudge :ammount of memory with a tricky command like this: : :carnivoro# /bin/csh -c `cat /dev/urandom` You can trivially write any program to allocate memory continuously. This isn't really a security problem with shells. If you want to cap memory useage you can set a datasize limit. It doesn't cap everything (i.e. it doesn't cap mmap() use), but it does cover the most common mistakes that users make. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:17:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 03EE537B9A3 for ; Fri, 24 Mar 2000 10:17:10 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA20268 for ; Fri, 24 Mar 2000 13:17:03 -0500 (EST) Date: Fri, 24 Mar 2000 10:52:11 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Software RAID and vinum 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 searched the mailing list archive. I am not sure whether Vinum has solved the problem of atomic writes in a stripe to both the data fragment and parity fragment (RAID 5). In the case of a crash, you have no idea of where the writes have finished (even worse, a fragment may contain several sectors). If this problem is not easily solved in software, does it mean that only hardware RAID can guarantee availability of data and software RAID can only be used to increase performance? How about the Linux software RAID support? Any enlightment is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:23:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-072.ricochet.net [204.179.134.72]) by hub.freebsd.org (Postfix) with ESMTP id 9326237B71D for ; Fri, 24 Mar 2000 10:23:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00964; Fri, 24 Mar 2000 10:26:22 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003241826.KAA00964@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Software RAID and vinum In-reply-to: Your message of "Fri, 24 Mar 2000 10:52:11 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 10:26:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I searched the mailing list archive. I am not sure whether Vinum has > solved the problem of atomic writes in a stripe to both the data fragment > and parity fragment (RAID 5). In the case of a crash, you have no idea of > where the writes have finished (even worse, a fragment may contain > several sectors). This problem can't be solved with software-only RAID, and no (sensible) software RAID implementation attempts to deal with it. Software RAID reliability is predicated on the correct functioning of the system; it's there to provide fault tolerance for the high-failure-rate hardware (eg. disks). > If this problem is not easily solved in software, does it mean that only > hardware RAID can guarantee availability of data and software RAID can > only be used to increase performance? How about the Linux software RAID > support? Typically you work around this by using a hardware RAID adapter with battery-backed memory; you need nonvolatile storage to achieve the results you're looking for. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:31:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2608C37B8CB; Fri, 24 Mar 2000 10:31:51 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA15389; Fri, 24 Mar 2000 11:31:44 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38DBB4EA.3334F7AE@softweyr.com> Date: Fri, 24 Mar 2000 11:33:14 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Dan Nelson , Markus Stumpf , freebsd-hackers@FreeBSD.ORG Subject: Re: 3.4 - large file - seek problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Thu, 23 Mar 2000, Dan Nelson wrote: > > > The tail bug has been reported as PR bin/14786, and it looks like > > there's a patch in there. See if it fixes your problem. As for less, > > you can contact the author and see if he can fix it; it's not a stock > > FreeBSD program. > > This is certainly the path to pursue, although I'm not sure how much luck > it would have. The GNU maintainers typically are focussed mainly on linux, > which I believe does not have support for 64-bit file sizes at the kernel > level (perhaps this has been fixed). A patch for the less port maintainer would be equally useful, if the GNU owner is uninterested. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:44:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FEDB37B9C1 for ; Fri, 24 Mar 2000 10:44:05 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA15422; Fri, 24 Mar 2000 11:43:53 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38DBB7C3.ED4E7F57@softweyr.com> Date: Fri, 24 Mar 2000 11:45:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jamie Bowden Cc: hackers@FreeBSD.ORG Subject: Re: Possible bug in 3.4 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jamie Bowden wrote: > > 12:14am animaniacs /home/jamie %runas camcontrol devlist -v > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on ahc0 bus 0: > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 6 lun 0 (pass2,cd0) > < > at scbus0 target -1 lun -1 () > scbus1 on aic0 bus 0: > at scbus1 target 3 lun 0 (pass3) > < > at scbus1 target -1 lun -1 () > > What I am attempting to do is add a tape drive to scbus1 at SCSI ID 4. > > aic0 is an Adaptec 1510B PnP ISA card, which works fine as evidenced > above. > > The problem is when I add the tape drive to the chain. The tape device is > internal, with termination on the end of the internal cable. The scanner > terminates the external segment. Termination on the card is disabled. The 1510 is a notoriously weak little piece of compu-trash. Put the internal tape drive on your 2940 and be happy. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:49:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8010C37B5EB; Fri, 24 Mar 2000 10:49:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA15441; Fri, 24 Mar 2000 11:48:41 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38DBB8E3.12B2834A@softweyr.com> Date: Fri, 24 Mar 2000 11:50:11 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems with changer code References: <200003240944.KAA67462@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Daniel C. Sobral wrote: > > You are too late, I have committed a fix for that already :) > > > With the latest ata, I get instant panic whenever I call > > /stand/sysinstall. It seems acdopen() is trying to read the contents of > > cdp->changer_info, but that pointer is NULL. We need a T-1 between these two, so Søren can just fix things on DCS' system as it is booting. Then Søren can commit them when even DCS can't break it. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:52:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60]) by hub.freebsd.org (Postfix) with ESMTP id B3B2C37B74A; Fri, 24 Mar 2000 10:52:19 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA00657; Fri, 24 Mar 2000 13:52:18 -0500 (EST) Date: Fri, 24 Mar 2000 11:27:25 -0500 (EST) From: Zhihui Zhang Reply-To: Zhihui Zhang To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Software RAID and vinum In-Reply-To: <200003241826.KAA00964@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Mike Smith wrote: > > > > I searched the mailing list archive. I am not sure whether Vinum has > > solved the problem of atomic writes in a stripe to both the data fragment > > and parity fragment (RAID 5). In the case of a crash, you have no idea of > > where the writes have finished (even worse, a fragment may contain > > several sectors). > > This problem can't be solved with software-only RAID, and no (sensible) > software RAID implementation attempts to deal with it. Software RAID > reliability is predicated on the correct functioning of the system; it's > there to provide fault tolerance for the high-failure-rate hardware (eg. > disks). Thanks. It seems to me that you are saying software RAID can NOT cope with system crash and power failure? What about the Zebra filesystem or something like two-phase commit? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 10:57:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-072.ricochet.net [204.179.134.72]) by hub.freebsd.org (Postfix) with ESMTP id 33AA637BA84 for ; Fri, 24 Mar 2000 10:57:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01113; Fri, 24 Mar 2000 11:00:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003241900.LAA01113@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Software RAID and vinum In-reply-to: Your message of "Fri, 24 Mar 2000 11:27:25 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 11:00:56 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 24 Mar 2000, Mike Smith wrote: > > > > > > > I searched the mailing list archive. I am not sure whether Vinum has > > > solved the problem of atomic writes in a stripe to both the data fragment > > > and parity fragment (RAID 5). In the case of a crash, you have no idea of > > > where the writes have finished (even worse, a fragment may contain > > > several sectors). > > > > This problem can't be solved with software-only RAID, and no (sensible) > > software RAID implementation attempts to deal with it. Software RAID > > reliability is predicated on the correct functioning of the system; it's > > there to provide fault tolerance for the high-failure-rate hardware (eg. > > disks). > > Thanks. It seems to me that you are saying software RAID can NOT cope with > system crash and power failure? What about the Zebra filesystem or > something like two-phase commit? On a software RAID volume? That still has the same atomicity and ordering issues, so it doesn't help. As far as filesystems are concerned, you're still at the mercy of the local buffer cache and the drives' caching behaviour. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 11:22:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id A9FBB37B5C8; Fri, 24 Mar 2000 11:22:32 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12YY2R-0006Eo-00; Fri, 24 Mar 2000 17:38:23 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12YY2Q-0004rv-00; Fri, 24 Mar 2000 17:38:22 +0000 Date: Fri, 24 Mar 2000 17:38:22 +0000 From: Ben Smithurst To: Matthew Dillon Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) Message-ID: <20000324173822.G87103@strontium.scientia.demon.co.uk> References: <20000323222149.C87103@strontium.scientia.demon.co.uk> <200003232244.OAA05041@apollo.backplane.com> <200003240053.QAA06073@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003240053.QAA06073@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I've committed a fix to this in -current, 4.x, and 3.x. Rev 1.61 > kern/sys_pipe.c (current), 1.60.2.1 in RELENG_4, something else in > RELENG_3. Sorry 2.2.x'rs, three is my limit :-) Thanks! I'll try it tonight. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 11:29:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 7D11337B77D for ; Fri, 24 Mar 2000 11:29:55 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA31658; Fri, 24 Mar 2000 13:29:30 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 24 Mar 2000 13:29:30 -0600 (CST) From: David Scheidt To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: gmake pb's In-Reply-To: <4.3.2.20000323194016.020dbef0@mail.Go2France.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, 23 Mar 2000, Len Conrad wrote: > Really axious to give Listar a whirl, please help me get through gmake. I don't have a 3.x development enviornment, so I can't see what happens on 3.4. I've built listar on 3.2 systems with no trouble. The changes you need to make are to define BSDMOD, or undefine DYNMOD, if you don't want dynamic modules. This was .126, not .128. I don't see anything that would break it though. Under 4.0 .128 compiles just fine, though I haven't tried running it. If I can get accessto a 3.4 system, I should be able to figure it out. Regards, David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 11:57:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DD5EC37BC87 for ; Fri, 24 Mar 2000 11:57:10 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2OKJWf25252; Fri, 24 Mar 2000 12:19:32 -0800 (PST) Date: Fri, 24 Mar 2000 12:19:32 -0800 From: Alfred Perlstein To: Dungeonkeeper Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: shell issue Message-ID: <20000324121932.R21029@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from zethix@sofiaonline.com on Fri, Mar 24, 2000 at 06:35:47PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dungeonkeeper [000324 10:03] wrote: > > > Hi there, > > First of all: I want to apologise for my poor english. > > Today me and a few friends of mine discussed the shells' (well, shell is > actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion > routines, mainly because of a problem discovered by one of my friends. I'm not > sure if this is something new... So, let me explain what he found. It seems > that the shell wants to allocate enough memory to hold the entire command line > when expanding all of the arguments and we can force it to allocate hudge > ammount of memory with a tricky command like this: > > carnivoro# /bin/csh -c `cat /dev/urandom` > > (I use tcsh here (the carnivoro# prompt), but the same thing happens when > testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough > memory to hold what it > reads from /dev/urandom, because it must be passed as a command line argument > to /bin/csh ( actually, any command will be ok ). So, the shell eats more and > more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to > take some action (like killing some processes... started by other users? > system services? or... in my case... crash :). My friend said that he sent a > mail to bugtraq describing this problem. Those who are interested can read it. > > I believe that the shells have a maximum command lenght, so... I'm trying now > to make the shell use the same command lenght when expanding such commands. I > think this is the best way to avoid this problem. Any ideas? Yes, that's a good idea, I'd file a problem report with send-pr and it will probably be addressed. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 12: 4:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5F82D37B77D for ; Fri, 24 Mar 2000 12:04:23 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Mar 2000 20:04:21 +0000 (GMT) Date: Fri, 24 Mar 2000 20:04:21 +0000 From: David Malone To: Luke Hollins Cc: freebsd-hackers@freebsd.org Subject: Re: top sorting error Message-ID: <20000324200421.A59323@bell.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from lwh@pathcom.com on Fri, Mar 24, 2000 at 01:00:54PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 24, 2000 at 01:00:54PM -0500, Luke Hollins wrote: > I don't know if this is specific to FreeBSD but I just noticed it when i > picked o time in top: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 79364 root 2 0 2696K 1636K select 8:23 0.00% 0.00% apache > 235 mysql 2 0 13372K 6384K poll 361:14 0.15% 0.15% mysqld It seems to be an overflow problem - top was reilying on things fitting into a int, which were 64 bits long. It looks like someone ran into the problem before for the %cpu field, and fixed it in a different way. This patch below should fix it regardless of the type of the variable. It's for a file in /usr/src/usr.bin/top. David. --- machine.c.orig Fri Mar 24 19:57:36 2000 +++ machine.c Fri Mar 24 19:58:17 2000 @@ -737,26 +737,26 @@ 4 /* stop */ }; +#define CMP(a,b) ( (a) == (b) ? 0 : (a) < (b) ? -1 : 1 ) #define ORDERKEY_PCTCPU \ - if (lresult = (long) PP(p2, p_pctcpu) - (long) PP(p1, p_pctcpu), \ - (result = lresult > 0 ? 1 : lresult < 0 ? -1 : 0) == 0) + if ((result = CMP(PP(p2, p_pctcpu),PP(p1, p_pctcpu))) == 0) #define ORDERKEY_CPTICKS \ - if ((result = PP(p2, p_runtime) - PP(p1, p_runtime)) == 0) + if ((result = CMP(PP(p2, p_runtime),PP(p1, p_runtime))) == 0) #define ORDERKEY_STATE \ - if ((result = sorted_state[(unsigned char) PP(p2, p_stat)] - \ - sorted_state[(unsigned char) PP(p1, p_stat)]) == 0) + if ((result = CMP(sorted_state[(unsigned char) PP(p2, p_stat)], \ + sorted_state[(unsigned char) PP(p1, p_stat)])) == 0) #define ORDERKEY_PRIO \ - if ((result = PP(p2, p_priority) - PP(p1, p_priority)) == 0) + if ((result = CMP(PP(p2, p_priority),PP(p1, p_priority))) == 0) #define ORDERKEY_RSSIZE \ - if ((result = VP(p2, vm_rssize) - VP(p1, vm_rssize)) == 0) + if ((result = CMP(VP(p2, vm_rssize),VP(p1, vm_rssize))) == 0) #define ORDERKEY_MEM \ - if ( (result = PROCSIZE(p2) - PROCSIZE(p1)) == 0 ) + if ((result = CMP(PROCSIZE(p2),PROCSIZE(p1))) == 0 ) /* compare_cpu - the comparison function for sorting by cpu percentage */ @@ -774,7 +774,6 @@ register struct kinfo_proc *p1; register struct kinfo_proc *p2; register int result; - register pctcpu lresult; /* remove one level of indirection */ p1 = *(struct kinfo_proc **) pp1; @@ -816,7 +815,6 @@ register struct kinfo_proc *p1; register struct kinfo_proc *p2; register int result; - register pctcpu lresult; /* remove one level of indirection */ p1 = *(struct kinfo_proc **) pp1; @@ -845,7 +843,6 @@ register struct kinfo_proc *p1; register struct kinfo_proc *p2; register int result; - register pctcpu lresult; /* remove one level of indirection */ p1 = *(struct kinfo_proc **) pp1; @@ -874,7 +871,6 @@ register struct kinfo_proc *p1; register struct kinfo_proc *p2; register int result; - register pctcpu lresult; /* remove one level of indirection */ p1 = *(struct kinfo_proc **) pp1; @@ -903,7 +899,6 @@ register struct kinfo_proc *p1; register struct kinfo_proc *p2; register int result; - register pctcpu lresult; /* remove one level of indirection */ p1 = *(struct kinfo_proc **) pp1; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 14:59:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 863DF37BAB1; Fri, 24 Mar 2000 14:59:26 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc343042.tokyo.jcom.ne.jp [203.140.143.42]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 03/13/00) with ESMTP id HAA12795; Sat, 25 Mar 2000 07:59:23 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id HAA49397; Sat, 25 Mar 2000 07:58:52 +0900 (JST) Date: Sat, 25 Mar 2000 07:58:50 +0900 Message-ID: <86ln38vutx.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: freebsd-hackers@freebsd.org Cc: freebsd-ports@freebsd.org, shige@freebsd.org Subject: zsh compdef collection for FreeBSD User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, FreeBSD hackers! I suppose FreeBSD users who use zsh (the Z shell) must have been customizing it so well and got some neat definitions for FreeBSD (or *BSD rather) environment. Now I have a suggestion. Why not we collect those useful compdef's to send to the zsh development team? You know, the latest zsh 3.1.6-dev-19 includes Debian specific functions in `Completion/Debian', then why not we have ours? I'm afraid that zsh will only have Linux/Solaris oriented configurations if we don't feed anything to the zsh team. It might take so long, but we always have a port. :) Anyway, I open mine at the following site. http://people.freebsd.org/~knu/etc/zsh/functions/ The stock contents: - cvsup - kldload / kldunload - pkg_add / pkg_delete / pkg_info - mount / umount (very poor for the present) Then, who's next? :) Any input is welcome! -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 15:36:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f87.law6.hotmail.com [216.32.241.87]) by hub.freebsd.org (Postfix) with SMTP id 2038137BC8A for ; Fri, 24 Mar 2000 15:36:10 -0800 (PST) (envelope-from mofo_junkhead@hotmail.com) Received: (qmail 25436 invoked by uid 0); 24 Mar 2000 23:36:09 -0000 Message-ID: <20000324233609.25435.qmail@hotmail.com> Received: from 195.100.133.214 by www.hotmail.com with HTTP; Fri, 24 Mar 2000 15:36:09 PST X-Originating-IP: [195.100.133.214] From: "Crash Override" To: freebsd-hackers@freebsd.org Subject: Missing keyboard symbols Date: Sat, 25 Mar 2000 11:36:09 NZST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm an NT admin that has been using FreeBSD at work for 5 years now. But since we changed many of the servers in our company to FreeBSD I have had a rather serious error while doing administrative work. The consolemode programs (Why don't they all just have a GUI? argh :-) ask me to press some Annykey to continue installation. But I can't find this function key anywhere on my keyboard! Most of these now-BSD boxes still have Windows keyboards, so I assume that this is the problem..., but it seems braindamaged to me that FreeBSD wouldn't function just because of such a trivial thing. So far (since I don't want to risk messing our business servers up!) I have been forced to press Reset, and some of the users have been complaining recently, so I really need to sort this out. Are there ms-keyboard patches that provide Annykey compatibility, and if not, will FreeBSD support this properly in the future? Sincerely, Arne R. Muhsson. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 15:56:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A9D9537B796 for ; Fri, 24 Mar 2000 15:56:33 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Mar 2000 23:56:33 +0000 (GMT) Date: Fri, 24 Mar 2000 23:56:32 +0000 From: David Malone To: Luke Hollins Cc: freebsd-hackers@freebsd.org Subject: Re: top sorting error Message-ID: <20000324235632.A5605@walton.maths.tcd.ie> References: <20000324200421.A59323@bell.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000324200421.A59323@bell.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Fri, Mar 24, 2000 at 08:04:21PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 24, 2000 at 08:04:21PM +0000, David Malone wrote: > It seems to be an overflow problem - top was reilying on things > fitting into a int, which were 64 bits long. It looks like someone > ran into the problem before for the %cpu field, and fixed it in a > different way. This patch below should fix it regardless of the > type of the variable. I notice this was fixed in version 1.28 by bde, though he only changed the check on the 64 bit field. The commit message says: Fixed sorting on time. On i386's, time differences of more than 2147 seconds caused overflow. Use a type-safe but slightly slower comparison. Comparisons for other fields are still fragile. Maybe this could be MFC'ed into RELENG_3? My patch would make all the comparisons in the robust, but slightly slower way. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 16:49: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id DDB3737BD32 for ; Fri, 24 Mar 2000 16:49:03 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12YelA-000Krc-00 for hackers@freebsd.org; Sat, 25 Mar 2000 02:49:00 +0200 Date: Sat, 25 Mar 2000 02:49:00 +0200 From: Neil Blakey-Milner To: FreeBSD Hackers Subject: 3.x -> 4.x kernel config converter Message-ID: <20000325024900.A80168@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wrote a quick hackish perl script to hopefully automatically convert 3.4 kernel configurations to 4.0 configurations. I can pipe RELENG_3 LINT through it and get a 4.0 config'able configuration, but I'm not sure if it's likely to produce booting kernels. Anyway, I thought some people might be interested in this - if it works well enough, it might even be useful to put in the tools directory, or integrate it into any 'update' target that may appear. It's at http://people.FreeBSD.org/~nbm/three-to-four-conf.pl Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 16:52:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 1547737B796; Fri, 24 Mar 2000 16:52:43 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA06757; Fri, 24 Mar 2000 16:52:35 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 24 Mar 2000 16:52:35 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Akinori -Aki- MUSHA Cc: freebsd-hackers@freebsd.org, shige@freebsd.org Subject: Re: zsh compdef collection for FreeBSD In-Reply-To: <86ln38vutx.wl@archon.local.idaemons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Mar 2000, Akinori -Aki- MUSHA wrote: > Hi, FreeBSD hackers! > > I suppose FreeBSD users who use zsh (the Z shell) must have been > customizing it so well and got some neat definitions for FreeBSD (or > *BSD rather) environment. > > Now I have a suggestion. > > Why not we collect those useful compdef's to send to the zsh > development team? I use the following in my .bashrc. I'm operating on the assumption that zsh has aliases of some sort, otherwise feel free to ignore this entire post. :) (Beware linewrap) case $MACHTYPE in *[Ff]ree[Bb][Ss][Dd]*) alias mergemaster='mergemaster -w ${COLUMNS}' alias kern='make depend && make && make install' alias cleanobj='rm -f -r /usr/obj/* || chflags -R noschg /usr/obj/* && rm -r /usr/obj/*' alias myps='/bin/ps -axo user,pid,ppid,%cpu,%mem,vsz,rss,state,start,time,command' ;; esac Enjoy, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 16:57:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 11D6837BEDA for ; Fri, 24 Mar 2000 16:57:18 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA06818; Fri, 24 Mar 2000 16:57:15 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 24 Mar 2000 16:57:15 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Crash Override Cc: freebsd-hackers@freebsd.org Subject: Re: Missing keyboard symbols In-Reply-To: <20000324233609.25435.qmail@hotmail.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, 25 Mar 2000, Crash Override wrote: > Hello, > I'm an NT admin that has been using FreeBSD at work for 5 years now. > But since we changed many of the servers in our company to FreeBSD I have > had a rather serious error while doing administrative work. The consolemode > programs (Why don't they all just have a GUI? argh :-) ask me to press some > Annykey to continue installation. Errr... If this is a joke, you should have sent it to -chat. If this is a serious question you should send them to freebsd-questions@freebsd.org in the future. If you are seriously asking about the "Any" key, think about it for a second. The message doesn't say, "Push THE Any key ..." It says push any key. If that's too complicated, just press the space bar. Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 17: 3:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 97D4637BE73 for ; Fri, 24 Mar 2000 17:03:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA17731; Fri, 24 Mar 2000 17:03:44 -0800 (PST) (envelope-from dillon) Date: Fri, 24 Mar 2000 17:03:44 -0800 (PST) From: Matthew Dillon Message-Id: <200003250103.RAA17731@apollo.backplane.com> To: Doug Barton Cc: Crash Override , freebsd-hackers@FreeBSD.ORG Subject: Re: Missing keyboard symbols References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Errr... If this is a joke, you should have sent it to -chat. If :this is a serious question you should send them to :freebsd-questions@freebsd.org in the future. : : If you are seriously asking about the "Any" key, think about it for a :second. The message doesn't say, "Push THE Any key ..." It says push any :key. If that's too complicated, just press the space bar. : :Good luck, : :Doug The space bar? The SPACE BAR? Oh my god, I've been hitting the wrong key for *YEARS*!!! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 17: 4:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 74DBA37BD93; Fri, 24 Mar 2000 17:04:26 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12YezO-000KuY-00; Sat, 25 Mar 2000 03:03:42 +0200 Date: Sat, 25 Mar 2000 03:03:42 +0200 From: Neil Blakey-Milner To: Doug Barton Cc: Akinori -Aki- MUSHA , freebsd-hackers@freebsd.org, shige@freebsd.org Subject: Re: zsh compdef collection for FreeBSD Message-ID: <20000325030342.A80255@mithrandr.moria.org> References: <86ln38vutx.wl@archon.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-03-24 (16:52), Doug Barton wrote: > I use the following in my .bashrc. I'm operating on the assumption > that zsh has aliases of some sort, otherwise feel free to ignore this > entire post. :) My ~/.tcsh/os-FreeBSD (which get auto-called by my .tcshrc) has: /---- setenv PR_FORM ~/.send-pr # bsd make allows knowing the targets like so: uncomplete make complete make 'p@*@`if -e Makefile make -dg1 -q | grep "^[^.#][-_a-z. \t]*:" | awk '"'"'{print $1}'"'"'`@' # if I have a local copy of the cvs tree, add aliases to easy moving # into it alias ncvs 'if ( "\!*" == "" ) then \ pushd $NCVS/`pwd | cut -f 3- -d/`; \ else \ pushd $NCVS/\!*; \ endif' complete ncvs "p%*%D:$NCVS/%" alias uncvs 'popd' complete pkg_delete 'p%*%D:/var/db/pkg/% %' complete pkg_info 'p%*%D:/var/db/pkg/% %' # indt alias compares given code to code given by indent(1) alias indt 'cat \!\!:1 | indent -st | diff \!\!:1 - | $PAGER' # show the rlog of a file through favourite pager alias rl 'rlog \!:1 | $PAGER' /--- That basically sets up 'make' completion: (nbm@mithrandr) /usr/src> make afterdistribute everything move-aout-libs all hierarchy obj aout-to-elf includes objlink aout-to-elf-build install regress aout-to-elf-install installkernel rerelease ... It also completes pkg_delete and pkg_info: (nbm@mithrandr) /usr/home/nbm> pkg_delete c cdd-1.0/ checkpassword-0.81/ cvsup-mirror-1.0/ cdrecord-1.8a33/ cvsup-bin-16.1/ cvsupd-bin-16.1/ ncvs pops me into the cvs tree of the directory I'm in: (nbm@mithrandr) /usr/src/contrib/cvs> ncvs (nbm@mithrandr) /home/ncvs/src/contrib/cvs> uncvs pushes me back. ncvs could be made much more intelligent, of course. Anyway, enough of that. Time for me to finally learn zsh. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 17:14:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 53F4937BE11 for ; Fri, 24 Mar 2000 17:13:51 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA06932; Fri, 24 Mar 2000 17:13:40 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 24 Mar 2000 17:13:40 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing keyboard symbols In-Reply-To: <200003250103.RAA17731@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Matthew Dillon wrote: > : Errr... If this is a joke, you should have sent it to -chat. If > :this is a serious question you should send them to > :freebsd-questions@freebsd.org in the future. > : > : If you are seriously asking about the "Any" key, think about it for a > :second. The message doesn't say, "Push THE Any key ..." It says push any > :key. If that's too complicated, just press the space bar. > : > :Good luck, > : > :Doug > > The space bar? The SPACE BAR? Oh my god, I've been hitting the > wrong key for *YEARS*!!! Heh... You know, I started to type out something to the effect of, "... space bar. FreeBSD has been mapping the Space Bar to the Any key combination since about 1992 to get around the restrictions of modern PC keyboards." But I thought there was an outside chance that this was a serious question, and I didn't want to run the risk that the poor doofus would repeat that statement in front of someone with a clue... Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 17:51:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 77C8937B75A; Fri, 24 Mar 2000 17:51:36 -0800 (PST) (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 SAA41801; Fri, 24 Mar 2000 18:51:33 -0700 (MST) (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 SAA54672; Fri, 24 Mar 2000 18:51:25 -0700 (MST) Message-Id: <200003250151.SAA54672@harmony.village.org> To: romik@WN.com.UA Subject: Re: WaveLAN PCI Adapter Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 24 Mar 2000 14:24:48 +0200." <20000324142448.A22279@WN.NET.UA> References: <20000324142448.A22279@WN.NET.UA> Date: Fri, 24 Mar 2000 18:51:25 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000324142448.A22279@WN.NET.UA> romik@WN.com.UA writes: : We bought WaveLAN PCI Adapter PCMCIA Controller (SCM Microsystems GMBH PCIC2CPR10 based on PCI1225PDV chip) and have trouble with installing it in FreeBSD 3.4 Does : FreeBSD support this device if yes were we can read about this problem ? Not really in 3.4. I have some patches knocking around my tree that I need to clean up. I got them from isawaki-san and other Japanese laptop users and haven't had the chance to look into them in detail. You may have to use 4.0 instead. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 20:38:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id BEFBA37B5EE for ; Fri, 24 Mar 2000 20:38:40 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id E644E7555; Fri, 24 Mar 2000 20:40:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id E3BCD1D89; Fri, 24 Mar 2000 20:40:01 -0800 (PST) Date: Fri, 24 Mar 2000 20:40:01 -0800 (PST) From: Jamie Bowden To: Wes Peters Cc: hackers@FreeBSD.ORG Subject: Re: Possible bug in 3.4 In-Reply-To: <38DBB7C3.ED4E7F57@softweyr.com> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Wes Peters wrote: :The 1510 is a notoriously weak little piece of compu-trash. Put the :internal tape drive on your 2940 and be happy. While I can appreciate your disdain for the card in question, I'd still like to know if anyone has any ideas on why FreeBSD won't boot when I plug the tape drive in. It's an Archive Python 25588-xxx according to NT and 98, in case anyone cares. After I upgrade in the near future, I should have enough PCI slots to dump the 1510 and plug in the Symbios Logic card I have. The goal is to get the hard drives on one bus, and the misc. peripherals on another. Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 24 21:30: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5B0DA37B7AF for ; Fri, 24 Mar 2000 21:29:59 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA21252; Fri, 24 Mar 2000 21:29:32 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DC4EBB.C9A4B4B7@gorean.org> Date: Fri, 24 Mar 2000 21:29:31 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: FreeBSD Hackers Subject: Re: 3.x -> 4.x kernel config converter References: <20000325024900.A80168@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > Hi, > > I wrote a quick hackish perl script to hopefully automatically > convert 3.4 kernel configurations to 4.0 configurations. I don't want to cast cold water on your plans here, but we try to encourage users to start with a GENERIC kernel, and work their way from there. The problem with converting is that there will likely be something missing from their old kernel file that should be in the new one. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 3: 7:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from stringline.southcom.com.au (stringline.southcom.com.au [203.31.83.239]) by hub.freebsd.org (Postfix) with SMTP id E918037B70B for ; Sat, 25 Mar 2000 03:07:23 -0800 (PST) (envelope-from vrdredge@stringline.com.au) Received: from robocomputer (unverified [203.39.128.154]) by localhost.stringline.com.au (EMWAC SMTPRS 0.83) with SMTP id ; Sat, 25 Mar 2000 22:06:55 +1100 From: "VR Dredge" To: Subject: Dreamweaver 2 Date: Sat, 25 Mar 2000 22:13:31 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, my name is Robert. I came across your address while trying to find a crack for Dreamweaver 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm asking if you have or know where I can it. Also are there any programs for generating cracks, passwords and so on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 8:47:16 2000 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 4E98A37B6AA for ; Sat, 25 Mar 2000 08:47:01 -0800 (PST) (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 LAA07585 for ; Sat, 25 Mar 2000 11:46:23 -0500 (EST) Date: Sat, 25 Mar 2000 11:46:23 -0500 (EST) From: Bosko Milekic To: freebsd-hackers@freebsd.org Subject: Comments above kmem_malloc() (vm/vm_kern.c) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the following comment above kmem_malloc()'s definition in: /sys/vm/vm_kern.c ... still valid? (I hope and suspect not): " * Note that this still only works in a uni-processor environment and * when called at splhigh(). " The only places, as far as I've seen, that call kmem_malloc are the kernel's malloc() and the mbuf allocation routines. Niether of these seems to do it at splhigh(), either. --Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 9:34:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id A9F8037B8A8 for ; Sat, 25 Mar 2000 09:34:29 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id LAA22880; Sat, 25 Mar 2000 11:34:32 -0600 (CST) (envelope-from chris) Date: Sat, 25 Mar 2000 11:34:31 -0600 From: Chris Costello To: VR Dredge Cc: hackers@FreeBSD.ORG Subject: Re: Dreamweaver 2 Message-ID: <20000325113431.B18325@holly.calldei.com> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, March 25, 2000, VR Dredge wrote: > Hi, my name is Robert. > I came across your address while trying to find a crack for Dreamweaver > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > asking if you have or know where I can it. Also are there any programs for > generating cracks, passwords and so on Where did you get this address as a place to get cracks for Windows software? This mailing list is for general FreeBSD technical discussion. -- |Chris Costello |All the simple programs have been written, and all the good names taken. `------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 10:30:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 857BB37B65C for ; Sat, 25 Mar 2000 10:30:38 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id TAA11239 for freebsd-hackers@freebsd.org; Sat, 25 Mar 2000 19:30:36 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id SAA84122 for freebsd-hackers@freebsd.org; Sat, 25 Mar 2000 18:34:19 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Unicode on FreeBSD Date: 25 Mar 2000 18:34:19 +0100 Message-ID: <8bitar$2i4f$1@bigeye.rhein-neckar.de> References: <20000320194702.11223.qmail@web3101.mail.yahoo.com> To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MikeM wrote: > Has anyone thought of Unicode support on FreeBSD? It has crossed my mind... > I think that it is inevitable that eventually FreeBSD > will *need* to support unicode if it wants to continue > as a viable operating system in the future. Probably. The demand for Unicode support is currently rather limited, but I expect it to pick up somewhat once it is pervasive under Linux and applications programmers come to expect its availability. > This means that it probably will need to be modified from the > ground up. Not at all. > Is there any way of implementing partial support, > working in stages, untill it is fully supported? Just that. I suggest you read these documents: "UTF-8 and Unicode FAQ" by Markus Kuhn http://www.cl.cam.ac.uk/~mgk25/unicode.html "The Unicode HOWTO" by Bruno Haible ftp://ftp.ilog.fr/pub/Users/haible/utf8/Unicode-HOWTO.html "Unicode Fonts and Tools for X11" by Markus Kuhn http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html These are written for Linux but they are largely applicable to BSD in general and FreeBSD in particular, too. The practical relevance of Unicode has taken a huge leap forward when Thomas Dickey made xterm became capable of displaying UTF-8 encoded Unicode character streams and Markus Kuhn coordinated the creation of some suitable fonts. This work has been merged into XFree86 4.0. For those of us still relying on an older release or actually requiring an even newer version of xterm, I have made ports available: http://home.pages.de/~naddy/unix/freebsd/xterm.shar http://home.pages.de/~naddy/unix/freebsd/ucs-fixed.shar (Earlier versions of) these have been submitted in PRs #15545 and #15840, but for some reason they have never been committed. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 10:53:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by hub.freebsd.org (Postfix) with ESMTP id 6094937B81A for ; Sat, 25 Mar 2000 10:53:34 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-09-43.nv.iinet.net.au [203.59.67.43]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id CAA11315; Sun, 26 Mar 2000 02:53:13 +0800 Message-ID: <38DD0A7C.13728473@elischer.org> Date: Sat, 25 Mar 2000 10:50:36 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-hackers@freebsd.org Subject: Re: Unicode on FreeBSD References: <20000320194702.11223.qmail@web3101.mail.yahoo.com> <8bitar$2i4f$1@bigeye.rhein-neckar.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > > > (Earlier versions of) these have been submitted in PRs #15545 and > #15840, but for some reason they have never been committed. > don't give up. It's not immediatly who is responsible for this, but it's something that is generally considered an important future subject for freebsd development. But you just need to figure out who is the right 'sponsor'. > -- > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 11:33:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 0FC6437B66E; Sat, 25 Mar 2000 11:33:16 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id NAA19618; Sat, 25 Mar 2000 13:35:53 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 13:35:53 -0600 From: Jonathan Lemon To: net@freebsd.org, hackers@freebsd.org Subject: Request for review (HW checksum patches) Message-ID: <20000325133553.D71371@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a set of patches which allows offloading checksums to NICs which support it (right now, only the Alteon based cards). The patch is at . Note that the alpha bits are currently untested. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 12:43:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 289A237B51B for ; Sat, 25 Mar 2000 12:43:27 -0800 (PST) (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 NAA46355 for ; Sat, 25 Mar 2000 13:43:22 -0700 (MST) (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 NAA73526 for ; Sat, 25 Mar 2000 13:43:12 -0700 (MST) Message-Id: <200003252043.NAA73526@harmony.village.org> To: hackers@freebsd.org Subject: Shim Code #error needed Date: Sat, 25 Mar 2000 13:43:12 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been burned about 6 times now by the shim device support becoming optional. Oh well, that's current. However, I was thinking that it would be nice if there was something simple to grep for to see what drivers still needed to be converted. What would people think of my adding the following to the shim using devices: cvs diff: Diffing . Index: amd.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/pci/amd.c,v retrieving revision 1.3 diff -u -r1.3 amd.c --- amd.c 2000/01/14 03:39:30 1.3 +++ amd.c 2000/03/25 18:07:31 @@ -50,6 +50,10 @@ /* #define AMD_DEBUG0 */ /* #define AMD_DEBUG_SCSI_PHASE */ +#ifndef COMPAT_OLDPCI +#error "The amd device requires the old pci compatibility shims" +#endif + #include #include At least this way you get a decent error message when it fails to work. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 12:50:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 7419A37B936; Sat, 25 Mar 2000 12:50:51 -0800 (PST) (envelope-from justin@apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id MAA15611; Sat, 25 Mar 2000 12:50:41 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Sat, 25 Mar 2000 12:50:36 -0800 Received: from grinch ([17.219.158.67]) by scv1.apple.com (8.9.3/8.9.3) with SMTP id MAA08969; Sat, 25 Mar 2000 12:50:40 -0800 (PST) Message-Id: <200003252050.MAA08969@scv1.apple.com> To: hackers@freebsd.org, net@freebsd.org Subject: Re: Request for review (HW checksum patches) Date: Sat, 25 Mar 2000 12:49:07 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: Apple Mail (2.303) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Jonathan Lemon > Date: Sat, 25 Mar 2000 13:35:53 -0600 > To: net@FreeBSD.ORG, hackers@FreeBSD.ORG > Subject: Request for review (HW checksum patches) > X-Mailer: Mutt 1.0pre2i > Delivered-to: freebsd-net@freebsd.org > X-Loop: FreeBSD.org > > I have a set of patches which allows offloading checksums to > NICs which support it (right now, only the Alteon based cards). > The patch is at . This prompts a question on a related issue: there seems to be an increase in support of protocol operations on NICs (e.g., tickle/keep-alive support while the system is sleeping; IPSec; ...). Is there enough there to let us build a general mechanism for communication between stack and driver for this sort of thing (e.g., a "meta-data" slot in the packet header which points to an mbuf, or other structure, that contains the details)? We're currently trying to deal with this in Mac OS X, and it'd be nice to avoid having multiple wheels of different size and shape in the same source base. Regards, Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 13:17:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7595737BA39; Sat, 25 Mar 2000 13:17:38 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA87501; Sat, 25 Mar 2000 13:17:39 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 25 Mar 2000 13:17:38 -0800 (PST) From: Kris Kennaway To: VR Dredge Cc: hackers@FreeBSD.ORG Subject: Re: Dreamweaver 2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Mar 2000, VR Dredge wrote: > Hi, my name is Robert. > I came across your address while trying to find a crack for Dreamweaver > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > asking if you have or know where I can it. Also are there any programs for > generating cracks, passwords and so on You can download the dreamweaver 2 crack by installing FreeBSD and installing the /usr/ports/cracks/drmwvr2 port. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 13:31:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.rdc3.on.home.com (mail1.rdc3.on.home.com [24.2.9.40]) by hub.freebsd.org (Postfix) with ESMTP id 8148537B91A for ; Sat, 25 Mar 2000 13:31:49 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail1.rdc3.on.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000325213148.RSY6372.mail1.rdc3.on.home.com@tristan.net> for ; Sat, 25 Mar 2000 13:31:48 -0800 Content-Length: 340 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 25 Mar 2000 16:26:32 -0500 (EST) From: Colin To: hackers@FreeBSD.ORG Subject: Mylex Support Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend of mine (FreeBSD user, between ISP'S) would like to know if anybody is working on support for Mylex Flashpoint BT950. He has one and is willing to port the driver from either Linux or BSDI, but is unwilling to duplicate the effort if someone else already has this beast in hand. Thanks for your comments. Cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 13:46:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ionet.net (mail.ionet.net [206.41.128.16]) by hub.freebsd.org (Postfix) with ESMTP id A966037B7D3 for ; Sat, 25 Mar 2000 13:46:42 -0800 (PST) (envelope-from ssamalin@ionet.net) Received: from ionet.net (ip2.bedford4.ma.pub-ip.psi.net [38.32.73.2]) by ionet.net (8.9.1a/8.9.1) with ESMTP id OAA08922 for ; Sat, 25 Mar 2000 14:51:26 -0600 (CST) Message-ID: <38DD26F8.C05B017E@ionet.net> Date: Sat, 25 Mar 2000 15:52:09 -0500 From: Sam Samalin X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #792 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers freebsd-hackers-digest wrote: > freebsd-hackers-digest Saturday, March 25 2000 Volume 04 : Number 792 > > In this issue: > Re: shell issue > Re: top sorting error > zsh compdef collection for FreeBSD > Missing keyboard symbols > Re: top sorting error > 3.x -> 4.x kernel config converter > Re: zsh compdef collection for FreeBSD > Re: Missing keyboard symbols > Re: Missing keyboard symbols > Re: zsh compdef collection for FreeBSD > Re: Missing keyboard symbols > Re: WaveLAN PCI Adapter > Re: Possible bug in 3.4 > Re: 3.x -> 4.x kernel config converter > Dreamweaver 2 > Comments above kmem_malloc() (vm/vm_kern.c) > Re: Dreamweaver 2 > Re: Unicode on FreeBSD > Re: Unicode on FreeBSD > Request for review (HW checksum patches) > Shim Code #error needed > > ---------------------------------------------------------------------- > > Date: Fri, 24 Mar 2000 12:19:32 -0800 > From: Alfred Perlstein > Subject: Re: shell issue > > * Dungeonkeeper [000324 10:03] wrote: > > > > > > Hi there, > > > > First of all: I want to apologise for my poor english. > > > > Today me and a few friends of mine discussed the shells' (well, shell is > > actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion > > routines, mainly because of a problem discovered by one of my friends. I'm not > > sure if this is something new... So, let me explain what he found. It seems > > that the shell wants to allocate enough memory to hold the entire command line > > when expanding all of the arguments and we can force it to allocate hudge > > ammount of memory with a tricky command like this: > > > > carnivoro# /bin/csh -c `cat /dev/urandom` > > > > (I use tcsh here (the carnivoro# prompt), but the same thing happens when > > testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough > > memory to hold what it > > reads from /dev/urandom, because it must be passed as a command line argument > > to /bin/csh ( actually, any command will be ok ). So, the shell eats more and > > more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to > > take some action (like killing some processes... started by other users? > > system services? or... in my case... crash :). My friend said that he sent a > > mail to bugtraq describing this problem. Those who are interested can read it. > > > > I believe that the shells have a maximum command lenght, so... I'm trying now > > to make the shell use the same command lenght when expanding such commands. I > > think this is the best way to avoid this problem. Any ideas? > > Yes, that's a good idea, I'd file a problem report with send-pr and > it will probably be addressed. > > thanks, > - -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 20:04:21 +0000 > From: David Malone > Subject: Re: top sorting error > > On Fri, Mar 24, 2000 at 01:00:54PM -0500, Luke Hollins wrote: > > > I don't know if this is specific to FreeBSD but I just noticed it when i > > picked o time in top: > > > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > > 79364 root 2 0 2696K 1636K select 8:23 0.00% 0.00% apache > > 235 mysql 2 0 13372K 6384K poll 361:14 0.15% 0.15% mysqld > > It seems to be an overflow problem - top was reilying on things > fitting into a int, which were 64 bits long. It looks like someone > ran into the problem before for the %cpu field, and fixed it in a > different way. This patch below should fix it regardless of the > type of the variable. > > It's for a file in /usr/src/usr.bin/top. > > David. > > - --- machine.c.orig Fri Mar 24 19:57:36 2000 > +++ machine.c Fri Mar 24 19:58:17 2000 > @@ -737,26 +737,26 @@ > 4 /* stop */ > }; > > +#define CMP(a,b) ( (a) == (b) ? 0 : (a) < (b) ? -1 : 1 ) > > #define ORDERKEY_PCTCPU \ > - - if (lresult = (long) PP(p2, p_pctcpu) - (long) PP(p1, p_pctcpu), \ > - - (result = lresult > 0 ? 1 : lresult < 0 ? -1 : 0) == 0) > + if ((result = CMP(PP(p2, p_pctcpu),PP(p1, p_pctcpu))) == 0) > > #define ORDERKEY_CPTICKS \ > - - if ((result = PP(p2, p_runtime) - PP(p1, p_runtime)) == 0) > + if ((result = CMP(PP(p2, p_runtime),PP(p1, p_runtime))) == 0) > > #define ORDERKEY_STATE \ > - - if ((result = sorted_state[(unsigned char) PP(p2, p_stat)] - \ > - - sorted_state[(unsigned char) PP(p1, p_stat)]) == 0) > + if ((result = CMP(sorted_state[(unsigned char) PP(p2, p_stat)], \ > + sorted_state[(unsigned char) PP(p1, p_stat)])) == 0) > > #define ORDERKEY_PRIO \ > - - if ((result = PP(p2, p_priority) - PP(p1, p_priority)) == 0) > + if ((result = CMP(PP(p2, p_priority),PP(p1, p_priority))) == 0) > > #define ORDERKEY_RSSIZE \ > - - if ((result = VP(p2, vm_rssize) - VP(p1, vm_rssize)) == 0) > + if ((result = CMP(VP(p2, vm_rssize),VP(p1, vm_rssize))) == 0) > > #define ORDERKEY_MEM \ > - - if ( (result = PROCSIZE(p2) - PROCSIZE(p1)) == 0 ) > + if ((result = CMP(PROCSIZE(p2),PROCSIZE(p1))) == 0 ) > > /* compare_cpu - the comparison function for sorting by cpu percentage */ > > @@ -774,7 +774,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -816,7 +815,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -845,7 +843,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -874,7 +871,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -903,7 +899,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 07:58:50 +0900 > From: "Akinori -Aki- MUSHA" > Subject: zsh compdef collection for FreeBSD > > Hi, FreeBSD hackers! > > I suppose FreeBSD users who use zsh (the Z shell) must have been > customizing it so well and got some neat definitions for FreeBSD (or > *BSD rather) environment. > > Now I have a suggestion. > > Why not we collect those useful compdef's to send to the zsh > development team? You know, the latest zsh 3.1.6-dev-19 includes > Debian specific functions in `Completion/Debian', then why not we have > ours? I'm afraid that zsh will only have Linux/Solaris oriented > configurations if we don't feed anything to the zsh team. > > It might take so long, but we always have a port. :) > > Anyway, I open mine at the following site. > > http://people.freebsd.org/~knu/etc/zsh/functions/ > > The stock contents: > - cvsup > - kldload / kldunload > - pkg_add / pkg_delete / pkg_info > - mount / umount (very poor for the present) > > Then, who's next? :) Any input is welcome! > > - -- > / > /__ __ > / ) ) ) ) / > Akinori -Aki- MUSHA aka / (_ / ( (__( > > "If you choose not to decide you still have made a choice." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:36:09 NZST > From: "Crash Override" > Subject: Missing keyboard symbols > > Hello, > I'm an NT admin that has been using FreeBSD at work for 5 years now. > But since we changed many of the servers in our company to FreeBSD I have > had a rather serious error while doing administrative work. The consolemode > programs (Why don't they all just have a GUI? argh :-) ask me to press some > Annykey to continue installation. > But I can't find this function key anywhere on my keyboard! Most of these > now-BSD boxes still have Windows keyboards, so I assume that this is the > problem..., but it seems braindamaged to me that FreeBSD wouldn't function > just because of such a trivial thing. > So far (since I don't want to risk messing our business servers up!) I have > been forced to press Reset, and some of the users have been complaining > recently, so I really need to sort this out. > Are there ms-keyboard patches that provide Annykey compatibility, > and if not, will FreeBSD support this properly in the future? > > Sincerely, > Arne R. Muhsson. > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 23:56:32 +0000 > From: David Malone > Subject: Re: top sorting error > > On Fri, Mar 24, 2000 at 08:04:21PM +0000, David Malone wrote: > > > It seems to be an overflow problem - top was reilying on things > > fitting into a int, which were 64 bits long. It looks like someone > > ran into the problem before for the %cpu field, and fixed it in a > > different way. This patch below should fix it regardless of the > > type of the variable. > > I notice this was fixed in version 1.28 by bde, though he only changed > the check on the 64 bit field. The commit message says: > > Fixed sorting on time. On i386's, time differences of more than 2147 > seconds caused overflow. Use a type-safe but slightly slower comparison. > Comparisons for other fields are still fragile. > > Maybe this could be MFC'ed into RELENG_3? My patch would make all the > comparisons in the robust, but slightly slower way. > > David. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 02:49:00 +0200 > From: Neil Blakey-Milner > Subject: 3.x -> 4.x kernel config converter > > Hi, > > I wrote a quick hackish perl script to hopefully automatically > convert 3.4 kernel configurations to 4.0 configurations. I can > pipe RELENG_3 LINT through it and get a 4.0 config'able configuration, > but I'm not sure if it's likely to produce booting kernels. > > Anyway, I thought some people might be interested in this - if it > works well enough, it might even be useful to put in the tools > directory, or integrate it into any 'update' target that may appear. > > It's at http://people.FreeBSD.org/~nbm/three-to-four-conf.pl > > Neil > - -- > Neil Blakey-Milner > nbm@rucus.ru.ac.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 16:52:35 -0800 (PST) > From: Doug Barton > Subject: Re: zsh compdef collection for FreeBSD > > On Sat, 25 Mar 2000, Akinori -Aki- MUSHA wrote: > > > Hi, FreeBSD hackers! > > > > I suppose FreeBSD users who use zsh (the Z shell) must have been > > customizing it so well and got some neat definitions for FreeBSD (or > > *BSD rather) environment. > > > > Now I have a suggestion. > > > > Why not we collect those useful compdef's to send to the zsh > > development team? > > I use the following in my .bashrc. I'm operating on the assumption > that zsh has aliases of some sort, otherwise feel free to ignore this > entire post. :) > > (Beware linewrap) > > case $MACHTYPE in > *[Ff]ree[Bb][Ss][Dd]*) > alias mergemaster='mergemaster -w ${COLUMNS}' > alias kern='make depend && make && make install' > alias cleanobj='rm -f -r /usr/obj/* || chflags -R noschg /usr/obj/* && > rm -r /usr/obj/*' > alias myps='/bin/ps -axo > user,pid,ppid,%cpu,%mem,vsz,rss,state,start,time,command' > ;; > esac > > Enjoy, > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 16:57:15 -0800 (PST) > From: Doug Barton > Subject: Re: Missing keyboard symbols > > On Sat, 25 Mar 2000, Crash Override wrote: > > > Hello, > > I'm an NT admin that has been using FreeBSD at work for 5 years now. > > But since we changed many of the servers in our company to FreeBSD I have > > had a rather serious error while doing administrative work. The consolemode > > programs (Why don't they all just have a GUI? argh :-) ask me to press some > > Annykey to continue installation. > > Errr... If this is a joke, you should have sent it to -chat. If > this is a serious question you should send them to > freebsd-questions@freebsd.org in the future. > > If you are seriously asking about the "Any" key, think about it for a > second. The message doesn't say, "Push THE Any key ..." It says push any > key. If that's too complicated, just press the space bar. > > Good luck, > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 17:03:44 -0800 (PST) > From: Matthew Dillon > Subject: Re: Missing keyboard symbols > > : Errr... If this is a joke, you should have sent it to -chat. If > :this is a serious question you should send them to > :freebsd-questions@freebsd.org in the future. > : > : If you are seriously asking about the "Any" key, think about it for a > :second. The message doesn't say, "Push THE Any key ..." It says push any > :key. If that's too complicated, just press the space bar. > : > :Good luck, > : > :Doug > > The space bar? The SPACE BAR? Oh my god, I've been hitting the > wrong key for *YEARS*!!! > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 03:03:42 +0200 > From: Neil Blakey-Milner > Subject: Re: zsh compdef collection for FreeBSD > > On Fri 2000-03-24 (16:52), Doug Barton wrote: > > I use the following in my .bashrc. I'm operating on the assumption > > that zsh has aliases of some sort, otherwise feel free to ignore this > > entire post. :) > > My ~/.tcsh/os-FreeBSD (which get auto-called by my .tcshrc) has: > > /---- > setenv PR_FORM ~/.send-pr > # bsd make allows knowing the targets like so: > uncomplete make > complete make 'p@*@`if -e Makefile make -dg1 -q | grep "^[^.#][-_a-z. \t]*:" | awk '"'"'{print $1}'"'"'`@' > > # if I have a local copy of the cvs tree, add aliases to easy moving > # into it > alias ncvs 'if ( "\!*" == "" ) then \ > pushd $NCVS/`pwd | cut -f 3- -d/`; \ > else \ > pushd $NCVS/\!*; \ > endif' > complete ncvs "p%*%D:$NCVS/%" > alias uncvs 'popd' > > complete pkg_delete 'p%*%D:/var/db/pkg/% %' > complete pkg_info 'p%*%D:/var/db/pkg/% %' > > # indt alias compares given code to code given by indent(1) > alias indt 'cat \!\!:1 | indent -st | diff \!\!:1 - | $PAGER' > > # show the rlog of a file through favourite pager > alias rl 'rlog \!:1 | $PAGER' > /--- > > That basically sets up 'make' completion: > > (nbm@mithrandr) /usr/src> make > afterdistribute everything move-aout-libs > all hierarchy obj > aout-to-elf includes objlink > aout-to-elf-build install regress > aout-to-elf-install installkernel rerelease > ... > > It also completes pkg_delete and pkg_info: > > (nbm@mithrandr) /usr/home/nbm> pkg_delete c > cdd-1.0/ checkpassword-0.81/ cvsup-mirror-1.0/ > cdrecord-1.8a33/ cvsup-bin-16.1/ cvsupd-bin-16.1/ > > ncvs pops me into the cvs tree of the directory I'm in: > > (nbm@mithrandr) /usr/src/contrib/cvs> ncvs > (nbm@mithrandr) /home/ncvs/src/contrib/cvs> > > uncvs pushes me back. ncvs could be made much more intelligent, of > course. > > Anyway, enough of that. Time for me to finally learn zsh. > > Neil > - -- > Neil Blakey-Milner > nbm@rucus.ru.ac.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 17:13:40 -0800 (PST) > From: Doug Barton > Subject: Re: Missing keyboard symbols > > On Fri, 24 Mar 2000, Matthew Dillon wrote: > > > : Errr... If this is a joke, you should have sent it to -chat. If > > :this is a serious question you should send them to > > :freebsd-questions@freebsd.org in the future. > > : > > : If you are seriously asking about the "Any" key, think about it for a > > :second. The message doesn't say, "Push THE Any key ..." It says push any > > :key. If that's too complicated, just press the space bar. > > : > > :Good luck, > > : > > :Doug > > > > The space bar? The SPACE BAR? Oh my god, I've been hitting the > > wrong key for *YEARS*!!! > > Heh... You know, I started to type out something to the effect of, > "... space bar. FreeBSD has been mapping the Space Bar to the Any key > combination since about 1992 to get around the restrictions of modern PC > keyboards." But I thought there was an outside chance that this was a > serious question, and I didn't want to run the risk that the poor doofus > would repeat that statement in front of someone with a clue... > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 18:51:25 -0700 > From: Warner Losh > Subject: Re: WaveLAN PCI Adapter > > In message <20000324142448.A22279@WN.NET.UA> romik@WN.com.UA writes: > : We bought WaveLAN PCI Adapter PCMCIA Controller (SCM Microsystems GMBH PCIC2CPR10 based on PCI1225PDV chip) and have trouble with installing it in FreeBSD 3.4 Does > : FreeBSD support this device if yes were we can read about this problem ? > > Not really in 3.4. I have some patches knocking around my tree that I > need to clean up. I got them from isawaki-san and other Japanese > laptop users and haven't had the chance to look into them in detail. > You may have to use 4.0 instead. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 20:40:01 -0800 (PST) > From: Jamie Bowden > Subject: Re: Possible bug in 3.4 > > On Fri, 24 Mar 2000, Wes Peters wrote: > > :The 1510 is a notoriously weak little piece of compu-trash. Put the > :internal tape drive on your 2940 and be happy. > > While I can appreciate your disdain for the card in question, I'd still > like to know if anyone has any ideas on why FreeBSD won't boot when I plug > the tape drive in. It's an Archive Python 25588-xxx according to NT and > 98, in case anyone cares. > > After I upgrade in the near future, I should have enough PCI slots to dump > the 1510 and plug in the Symbios Logic card I have. The goal is to get > the hard drives on one bus, and the misc. peripherals on another. > > Jamie Bowden > > - -- > > "Of course, that's sort of like asking how other than Marketing, > Microsoft is different from any other software company..." > Kenneth G. Cavness > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 21:29:31 -0800 > From: Doug Barton > Subject: Re: 3.x -> 4.x kernel config converter > > Neil Blakey-Milner wrote: > > > > Hi, > > > > I wrote a quick hackish perl script to hopefully automatically > > convert 3.4 kernel configurations to 4.0 configurations. > > I don't want to cast cold water on your plans here, but we try to > encourage users to start with a GENERIC kernel, and work their way from > there. The problem with converting is that there will likely be > something missing from their old kernel file that should be in the new > one. > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 22:13:31 +1100 > From: "VR Dredge" > Subject: Dreamweaver 2 > > Hi, my name is Robert. > I came across your address while trying to find a crack for Dreamweaver > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > asking if you have or know where I can it. Also are there any programs for > generating cracks, passwords and so on > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:46:23 -0500 (EST) > From: Bosko Milekic > Subject: Comments above kmem_malloc() (vm/vm_kern.c) > > Is the following comment above kmem_malloc()'s definition in: > /sys/vm/vm_kern.c > ... still valid? (I hope and suspect not): > > " * Note that this still only works in a uni-processor environment and > * when called at splhigh(). " > > The only places, as far as I've seen, that call kmem_malloc are the > kernel's malloc() and the mbuf allocation routines. Niether of these > seems to do it at splhigh(), either. > > - --Bosko Milekic > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:34:31 -0600 > From: Chris Costello > Subject: Re: Dreamweaver 2 > > On Saturday, March 25, 2000, VR Dredge wrote: > > Hi, my name is Robert. > > I came across your address while trying to find a crack for Dreamweaver > > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > > asking if you have or know where I can it. Also are there any programs for > > generating cracks, passwords and so on > > Where did you get this address as a place to get cracks for > Windows software? This mailing list is for general FreeBSD > technical discussion. > > - -- > |Chris Costello > |All the simple programs have been written, and all the good names taken. > `------------------------------------------------------------------------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: 25 Mar 2000 18:34:19 +0100 > From: naddy@mips.rhein-neckar.de (Christian Weisgerber) > Subject: Re: Unicode on FreeBSD > > MikeM wrote: > > > Has anyone thought of Unicode support on FreeBSD? > > It has crossed my mind... > > > I think that it is inevitable that eventually FreeBSD > > will *need* to support unicode if it wants to continue > > as a viable operating system in the future. > > Probably. The demand for Unicode support is currently rather limited, > but I expect it to pick up somewhat once it is pervasive under > Linux and applications programmers come to expect its availability. > > > This means that it probably will need to be modified from the > > ground up. > > Not at all. > > > Is there any way of implementing partial support, > > working in stages, untill it is fully supported? > > Just that. > > I suggest you read these documents: > > "UTF-8 and Unicode FAQ" by Markus Kuhn > http://www.cl.cam.ac.uk/~mgk25/unicode.html > > "The Unicode HOWTO" by Bruno Haible > ftp://ftp.ilog.fr/pub/Users/haible/utf8/Unicode-HOWTO.html > > "Unicode Fonts and Tools for X11" by Markus Kuhn > http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html > > These are written for Linux but they are largely applicable to BSD > in general and FreeBSD in particular, too. > > The practical relevance of Unicode has taken a huge leap forward > when Thomas Dickey made xterm became capable of displaying UTF-8 > encoded Unicode character streams and Markus Kuhn coordinated the > creation of some suitable fonts. This work has been merged into > XFree86 4.0. For those of us still relying on an older release or > actually requiring an even newer version of xterm, I have made > ports available: > > http://home.pages.de/~naddy/unix/freebsd/xterm.shar > http://home.pages.de/~naddy/unix/freebsd/ucs-fixed.shar > > (Earlier versions of) these have been submitted in PRs #15545 and > #15840, but for some reason they have never been committed. > > - -- > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 10:50:36 -0800 > From: Julian Elischer > Subject: Re: Unicode on FreeBSD > > Christian Weisgerber wrote: > > > > > > (Earlier versions of) these have been submitted in PRs #15545 and > > #15840, but for some reason they have never been committed. > > > > don't give up. > It's not immediatly who is responsible for this, but > it's something that is generally considered > an important future subject for freebsd development. > But you just need to figure out who is the right 'sponsor'. > > > -- > > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > > - -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > - ---> X_.---._/ presently in: Perth > v > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 13:35:53 -0600 > From: Jonathan Lemon > Subject: Request for review (HW checksum patches) > > I have a set of patches which allows offloading checksums to > NICs which support it (right now, only the Alteon based cards). > The patch is at . > > Note that the alpha bits are currently untested. > - -- > Jonathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 13:43:12 -0700 > From: Warner Losh > Subject: Shim Code #error needed > > I've been burned about 6 times now by the shim device support becoming > optional. Oh well, that's current. > > However, I was thinking that it would be nice if there was something > simple to grep for to see what drivers still needed to be converted. > What would people think of my adding the following to the shim using > devices: > > cvs diff: Diffing . > Index: amd.c > =================================================================== > RCS file: /home/imp/FreeBSD/CVS/src/sys/pci/amd.c,v > retrieving revision 1.3 > diff -u -r1.3 amd.c > - --- amd.c 2000/01/14 03:39:30 1.3 > +++ amd.c 2000/03/25 18:07:31 > @@ -50,6 +50,10 @@ > /* #define AMD_DEBUG0 */ > /* #define AMD_DEBUG_SCSI_PHASE */ > > +#ifndef COMPAT_OLDPCI > +#error "The amd device requires the old pci compatibility shims" > +#endif > + > #include > > #include > > At least this way you get a decent error message when it fails to > work. > > Comments? > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > End of freebsd-hackers-digest V4 #792 > ************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 15:16: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.errno.com (node-d1d4bd7a.powerinter.net [209.212.189.122]) by hub.freebsd.org (Postfix) with ESMTP id D8A1C37B921; Sat, 25 Mar 2000 15:16:03 -0800 (PST) (envelope-from sam@errno.com) Received: from MELANGE (melange.errno.com [209.212.166.36]) by gw.errno.com (8.9.0/8.9.0) with SMTP id PAA22995; Sat, 25 Mar 2000 15:16:01 -0800 (PST) Message-ID: <077a01bf96af$73dab720$0132a8c0@MELANGE> From: "Sam Leffler" To: , , References: <200003252050.MAA08969@scv1.apple.com> Subject: Re: Request for review (HW checksum patches) Date: Sat, 25 Mar 2000 15:11:29 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, Win2000 has a mechanism for dealing with what they call task offloading. If you decide to attack the problem, an inexpensive device you can use for testing is the 3C905B; it does IP+TCP checksums. Sam ----- Original Message ----- From: "Justin C. Walker" To: ; Sent: Saturday, March 25, 2000 12:49 PM Subject: Re: Request for review (HW checksum patches) > > From: Jonathan Lemon > > Date: Sat, 25 Mar 2000 13:35:53 -0600 > > To: net@FreeBSD.ORG, hackers@FreeBSD.ORG > > Subject: Request for review (HW checksum patches) > > X-Mailer: Mutt 1.0pre2i > > Delivered-to: freebsd-net@freebsd.org > > X-Loop: FreeBSD.org > > > > I have a set of patches which allows offloading checksums to > > NICs which support it (right now, only the Alteon based cards). > > The patch is at . > > This prompts a question on a related issue: there seems to be an increase > in support of protocol operations on NICs (e.g., tickle/keep-alive support > while the system is sleeping; IPSec; ...). Is there enough there to let us > build a general mechanism for communication between stack and driver for > this sort of thing (e.g., a "meta-data" slot in the packet header which > points to an mbuf, or other structure, that contains the details)? > > We're currently trying to deal with this in Mac OS X, and it'd be nice to > avoid having multiple wheels of different size and shape in the same source > base. > > Regards, > > Justin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 15:17:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3DAAF37B742 for ; Sat, 25 Mar 2000 15:17:11 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA08872; Sat, 25 Mar 2000 16:17:00 -0700 (MST) (envelope-from ken) Date: Sat, 25 Mar 2000 16:17:00 -0700 From: "Kenneth D. Merry" To: Colin Cc: hackers@FreeBSD.ORG Subject: Re: Mylex Support Message-ID: <20000325161659.A8845@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cwass99@home.com on Sat, Mar 25, 2000 at 04:26:32PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 16:26:32 -0500, Colin wrote: > A friend of mine (FreeBSD user, between ISP'S) would like to know if > anybody is working on support for Mylex Flashpoint BT950. He has one and is > willing to port the driver from either Linux or BSDI, but is unwilling to > duplicate the effort if someone else already has this beast in hand. > Thanks for your comments. You should talk to Justin Gibbs . He has the hardware, and I think he has documentation, and he has been planning on doing a driver for a while. He hasn't gotten around to it yet, though, so he might be open to someone else doing a driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 15:56:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 1CB5737B94C for ; Sat, 25 Mar 2000 15:56:20 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id PAA10184; Sat, 25 Mar 2000 15:56:13 -0800 (PST) Date: Sat, 25 Mar 2000 15:56:11 -0800 From: Brooks Davis To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Shim Code #error needed Message-ID: <20000325155611.A18633@orion.ac.hmc.edu> References: <200003252043.NAA73526@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200003252043.NAA73526@harmony.village.org>; from imp@village.org on Sat, Mar 25, 2000 at 01:43:12PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 01:43:12PM -0700, Warner Losh wrote: > > I've been burned about 6 times now by the shim device support becoming > optional. Oh well, that's current. > > However, I was thinking that it would be nice if there was something > simple to grep for to see what drivers still needed to be converted. > What would people think of my adding the following to the shim using > devices: > > cvs diff: Diffing . > Index: amd.c > =================================================================== > RCS file: /home/imp/FreeBSD/CVS/src/sys/pci/amd.c,v > retrieving revision 1.3 > diff -u -r1.3 amd.c > --- amd.c 2000/01/14 03:39:30 1.3 > +++ amd.c 2000/03/25 18:07:31 > @@ -50,6 +50,10 @@ > /* #define AMD_DEBUG0 */ > /* #define AMD_DEBUG_SCSI_PHASE */ > > +#ifndef COMPAT_OLDPCI > +#error "The amd device requires the old pci compatibility shims" > +#endif > + > #include > > #include > > At least this way you get a decent error message when it fails to > work. > > Comments? I like it. The new entry in UPDATING should help, but it's easy to forget and the current errors aren't very obvious. Don't bother with tx if you do it though. I've got a patch I'll probalby submit sometime today. It's running without COMPAT_OLDPCI right now, I just want to take a stab and adding bus_space support while I'm messing around with it. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 16: 4:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4730537B51B for ; Sat, 25 Mar 2000 16:04:23 -0800 (PST) (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 RAA47191; Sat, 25 Mar 2000 17:04:21 -0700 (MST) (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 RAA75925; Sat, 25 Mar 2000 17:04:11 -0700 (MST) Message-Id: <200003260004.RAA75925@harmony.village.org> To: Brooks Davis Subject: Re: Shim Code #error needed Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 15:56:11 PST." <20000325155611.A18633@orion.ac.hmc.edu> References: <20000325155611.A18633@orion.ac.hmc.edu> <200003252043.NAA73526@harmony.village.org> Date: Sat, 25 Mar 2000 17:04:11 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000325155611.A18633@orion.ac.hmc.edu> Brooks Davis writes: : I like it. The new entry in UPDATING should help, but it's easy to : forget and the current errors aren't very obvious. Well, I *WROTE* the entry in UPDATING (or at least committed it, I can't recall now). The only person I can think of that should know better more than me would be Peter Wemm who committed the changes :-) : Don't bother with : tx if you do it though. I've got a patch I'll probalby submit sometime : today. It's running without COMPAT_OLDPCI right now, I just want to : take a stab and adding bus_space support while I'm messing around with : it. OK. I'll give things a couple of days then. I have all the pci ones marked in my local tree, and some of the isa ones. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 16:17:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id A29FE37B510 for ; Sat, 25 Mar 2000 16:17:00 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id QAA17037; Sat, 25 Mar 2000 16:16:56 -0800 (PST) Date: Sat, 25 Mar 2000 16:16:56 -0800 From: Brooks Davis To: Warner Losh Cc: Brooks Davis , hackers@FreeBSD.ORG Subject: Re: Shim Code #error needed Message-ID: <20000325161656.A15487@orion.ac.hmc.edu> References: <20000325155611.A18633@orion.ac.hmc.edu> <200003252043.NAA73526@harmony.village.org> <20000325155611.A18633@orion.ac.hmc.edu> <200003260004.RAA75925@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200003260004.RAA75925@harmony.village.org>; from imp@village.org on Sat, Mar 25, 2000 at 05:04:11PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 05:04:11PM -0700, Warner Losh wrote: > In message <20000325155611.A18633@orion.ac.hmc.edu> Brooks Davis writes: > : I like it. The new entry in UPDATING should help, but it's easy to > : forget and the current errors aren't very obvious. > > Well, I *WROTE* the entry in UPDATING (or at least committed it, I > can't recall now). The only person I can think of that should know > better more than me would be Peter Wemm who committed the changes :-) I know you commited it. Actually, I wrote it. I wasn't suggesting that you should have read UPDATING. That would have been rather silly. I was really just saying that while the message in UPDATING will help, adding these #errors is a very good idea because just knowing about the problem isn't quite sufficient to avoid it. As both of use seem to have proved. ;-) -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 16:51:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id DAB4A37B7B2 for ; Sat, 25 Mar 2000 16:51:39 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id SAA29035; Sat, 25 Mar 2000 18:54:14 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 18:54:14 -0600 (CST) From: Jonathan Lemon Message-Id: <200003260054.SAA29035@prism.flugsvamp.com> To: sam@errno.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >FWIW, Win2000 has a mechanism for dealing with what they call task >offloading. If you decide to attack the problem, an inexpensive device you >can use for testing is the 3C905B; it does IP+TCP checksums. Yes, unfortunately it doesn't handle fragments at all. I looked at the card specs when devising the interface, to make sure that the new interface will be able to handle various chips. I haven't changed the 3com driver though, as I didn't want to spend time trying to figure out what the chip actually does vs what the manual says it does. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 16:54:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id D303937B6AD for ; Sat, 25 Mar 2000 16:54:06 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id SAA29089; Sat, 25 Mar 2000 18:56:42 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 18:56:42 -0600 (CST) From: Jonathan Lemon Message-Id: <200003260056.SAA29089@prism.flugsvamp.com> To: justin@apple.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >> From: Jonathan Lemon >> Date: Sat, 25 Mar 2000 13:35:53 -0600 >> To: net@FreeBSD.ORG, hackers@FreeBSD.ORG >> Subject: Request for review (HW checksum patches) >> X-Mailer: Mutt 1.0pre2i >> Delivered-to: freebsd-net@freebsd.org >> X-Loop: FreeBSD.org >> >> I have a set of patches which allows offloading checksums to >> NICs which support it (right now, only the Alteon based cards). >> The patch is at . > >This prompts a question on a related issue: there seems to be an increase >in support of protocol operations on NICs (e.g., tickle/keep-alive support >while the system is sleeping; IPSec; ...). Is there enough there to let us >build a general mechanism for communication between stack and driver for >this sort of thing (e.g., a "meta-data" slot in the packet header which >points to an mbuf, or other structure, that contains the details)? The patches I have were designed to solve a single problem, just checksum offloading. There are enough bits left in the new flag field that you could use for something else, I don't know enough about what you'd want to do to say if it's enough for a general mechanism. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 17: 3:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4BE4237B6AD for ; Sat, 25 Mar 2000 17:03:25 -0800 (PST) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id DAA73391; Sun, 26 Mar 2000 03:01:24 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id BAA14730; Sun, 26 Mar 2000 01:47:19 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 26 Mar 2000 01:47:19 +0100 (CET) From: Leif Neland To: Dungeonkeeper Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: shell issue In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Dungeonkeeper wrote: > > > Hi there, > > First of all: I want to apologise for my poor english. > > Today me and a few friends of mine discussed the shells' (well, shell is > actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion > routines, mainly because of a problem discovered by one of my friends. I'm not > sure if this is something new... So, let me explain what he found. It seems > that the shell wants to allocate enough memory to hold the entire command line > when expanding all of the arguments and we can force it to allocate hudge > ammount of memory with a tricky command like this: > > carnivoro# /bin/csh -c `cat /dev/urandom` > > (I use tcsh here (the carnivoro# prompt), but the same thing happens when > testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough > memory to hold what it > reads from /dev/urandom, because it must be passed as a command line argument > to /bin/csh ( actually, any command will be ok ). So, the shell eats more and > more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to > take some action (like killing some processes... started by other users? > system services? or... in my case... crash :). My friend said that he sent a > mail to bugtraq describing this problem. Those who are interested can read it. > I tried this too: /bin/csh -c `cat /dev/urandom` My shell grew to around 260MB, then "bash: xrealloc: cannot reallocate 134217728 bytes (0 bytes allocated)" Then it exited to the logon prompt. The rest of the system didn't notice. Happened both as root and normal. I tried this with ridiculously 8GB swap (just for fun...). With 128MB swap, the system complained when the swap got full, but then only killed the shell, returning me to the logonprompt on that window. No other problems either. Leif > I believe that the shells have a maximum command lenght, so... I'm trying now > to make the shell use the same command lenght when expanding such commands. I > think this is the best way to avoid this problem. Any ideas? > > Best regards: zethix > > > What is worth doing is worth the trouble of asking somebody to do. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 17:30:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 3BBDC37B51B for ; Sat, 25 Mar 2000 17:30:21 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12Z14p-0009cb-00; Sun, 26 Mar 2000 00:38:47 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12Z14p-000K8X-00; Sun, 26 Mar 2000 00:38:47 +0000 Date: Sun, 26 Mar 2000 00:38:47 +0000 From: Ben Smithurst To: Sam Samalin Cc: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #792 Message-ID: <20000326003847.G86036@strontium.scientia.demon.co.uk> References: <38DD26F8.C05B017E@ionet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38DD26F8.C05B017E@ionet.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sam Samalin wrote: > unsubscribe freebsd-hackers which part of the following didn't you understand? >> 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 >> 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 ... -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 18:25:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id C0B1C37B744 for ; Sat, 25 Mar 2000 18:25:34 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 34BBF24D15; Sat, 25 Mar 2000 21:25:34 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 4B8DB18605; Sat, 25 Mar 2000 21:25:33 -0500 (EST) Date: Sat, 25 Mar 2000 21:25:33 -0500 From: Keith Stevenson To: Jonathan Lemon Cc: justin@apple.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) Message-ID: <20000325212533.B73602@osaka.louisville.edu> References: <200003260056.SAA29089@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003260056.SAA29089@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Sat, Mar 25, 2000 at 06:56:42PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 06:56:42PM -0600, Jonathan Lemon wrote: > > The patches I have were designed to solve a single problem, just > checksum offloading. There are enough bits left in the new flag field > that you could use for something else, I don't know enough about what > you'd want to do to say if it's enough for a general mechanism. Which card(s) do your patches support? I have a 3Com 3CR990-TX (typhoon) which does both TCP checksumming and 3DES (for IPSec). I'd love to give it a try. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 20: 3: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 64E5F37B652; Sat, 25 Mar 2000 20:02:56 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id OAA55956; Sun, 26 Mar 2000 14:02:46 +1000 (EST) (envelope-from sue) Date: Sun, 26 Mar 2000 14:02:43 +1000 From: Sue Blake To: freebsd-questions@freebsd.org Subject: syslogd stops logging - caught in the act Message-ID: <20000326140241.C43926@welearn.com.au> 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 Let's solve this once and for all. I've run syslogd -d and sent output to a file and waited for the inevitable cessation of logging although syslogd is still running. (Refer PRs 2191 5548 6216 8847 8865 10553 and two or three threads in -isp and/or -questions earlier this year that summarised the problems and their scope but didn't reach the list archives) Now logging's stopped and I need to get it restarted again soon, but I'd like to collect some useful information first. I need help to do that. This has been reported for almost all -release and -stable versions since early 2.2, and it's been hard to pin down what circumstances cause it or to repeat it on unaffected machines. The common facts are that syslogd is running, using CPU, but nothing goes to the logs, not mark messages, logger messages, nothing. One exception: the logs dutifully rotate and log that they have rotated. Sending a sighup does not fix it, only completely killing and restarting syslogd gets it going. Unless this is done, it will continue with the same behaviour (running but not logging) until reboot. All past speculation as to the cause has been met with counterexamples. There are five freebsd machines that exhibit this problem which I only have access to for another couple of days, so if anyone is interested in solving this long-standing failure of syslogd please take this opportunity to work with me on it. These machines range from almost idle very vanilla 3.3R workstations with only sendmail running, up to 3.4-STABLE of january running many daemons and with reasonable load, for which reliable logging is critical. Replies to my email address would be appreciated. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 20:33:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id DC45237B908 for ; Sat, 25 Mar 2000 20:33:51 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id WAA35057; Sat, 25 Mar 2000 22:36:24 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 22:36:24 -0600 From: Jonathan Lemon To: Keith Stevenson Cc: Jonathan Lemon , justin@apple.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) Message-ID: <20000325223624.L71371@prism.flugsvamp.com> References: <200003260056.SAA29089@prism.flugsvamp.com> <20000325212533.B73602@osaka.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000325212533.B73602@osaka.louisville.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 09:25:33PM -0500, Keith Stevenson wrote: > On Sat, Mar 25, 2000 at 06:56:42PM -0600, Jonathan Lemon wrote: > > > > The patches I have were designed to solve a single problem, just > > checksum offloading. There are enough bits left in the new flag field > > that you could use for something else, I don't know enough about what > > you'd want to do to say if it's enough for a general mechanism. > > Which card(s) do your patches support? I have a 3Com 3CR990-TX (typhoon) > which does both TCP checksumming and 3DES (for IPSec). I'd love to give > it a try. Right now, just the Alteon cards. Support for the 3Com-XL can probably be added without too much trouble. I don't see a driver for the 3Com-990 though, and I can't find a reference to it on the 3Com website, is this a new card? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 20:37:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 68C4A37B9A9; Sat, 25 Mar 2000 20:37:44 -0800 (PST) From: "Jonathan M. Bresler" To: ben@scientia.demon.co.uk Cc: ssamalin@ionet.net, hackers@FreeBSD.ORG In-reply-to: <20000326003847.G86036@strontium.scientia.demon.co.uk> (message from Ben Smithurst on Sun, 26 Mar 2000 00:38:47 +0000) Subject: Re: freebsd-hackers-digest V4 #792 Message-Id: <20000326043744.68C4A37B9A9@hub.freebsd.org> Date: Sat, 25 Mar 2000 20:37:44 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben, relax, the gentleman in question subscribed to freebsd-hackers-digest and confused that list with freebsd-hackers. i have sent him email explaining the situation. > > >> 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 > > >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 21:48:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 2810137B999 for ; Sat, 25 Mar 2000 21:48:29 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id XAA37498; Sat, 25 Mar 2000 23:51:03 -0600 (CST) (envelope-from jlemon) Date: Sat, 25 Mar 2000 23:51:03 -0600 (CST) From: Jonathan Lemon Message-Id: <200003260551.XAA37498@prism.flugsvamp.com> To: sue@welearn.com.au, hackers@freebsd.org Subject: Re: syslogd stops logging - caught in the act X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I asked Sue to get a ktrace of the syslogd, and here's the output: 18869 syslogd 954045445.977145 PSIG SIGALRM caught handler=0x804b068 mask=0x0 code=0x0 18869 syslogd 954045445.977343 RET poll -1 errno 4 Interrupted system call 18869 syslogd 954045445.977366 CALL gettimeofday(0xbfbfc5f0,0) 18869 syslogd 954045445.977382 RET gettimeofday 0 18869 syslogd 954045445.977403 CALL setitimer(0,0xbfbfc5e8,0xbfbfc5d8) 18869 syslogd 954045445.977424 RET setitimer 0 18869 syslogd 954045445.977438 CALL old.sigreturn(0xbfbfc624) 18869 syslogd 954045445.977456 RET old.sigreturn JUSTRETURN 18869 syslogd 954045445.977476 CALL poll(0xbfbfc6f0,0x1,0x9c40) 18869 syslogd 954045475.987785 PSIG SIGALRM caught handler=0x804b068 mask=0x0 code=0x0 18869 syslogd 954045475.987859 RET poll -1 errno 4 Interrupted system call 18869 syslogd 954045475.987879 CALL gettimeofday(0xbfbfc5f0,0) 18869 syslogd 954045475.987895 RET gettimeofday 0 18869 syslogd 954045475.987917 CALL setitimer(0,0xbfbfc5e8,0xbfbfc5d8) 18869 syslogd 954045475.987938 RET setitimer 0 18869 syslogd 954045475.987952 CALL old.sigreturn(0xbfbfc624) 18869 syslogd 954045475.987969 RET old.sigreturn JUSTRETURN 18869 syslogd 954045475.987990 CALL poll(0xbfbfc6f0,0x1,0x9c40) 18869 syslogd 954045505.997954 PSIG SIGALRM caught handler=0x804b068 mask=0x0 code=0x0 18869 syslogd 954045505.998120 RET poll -1 errno 4 Interrupted system call The poll() calls are from libc/net/res_send, while the gettimeofday() calls are from the alarm handler (in syslogd). The res_send code does roughly the following: msec = (timeout calculated based on # of tries) repeat: poll(pfd, 1, msec); if (errno == EINTR) goto repeat; So what's happening here is it seems that after the # of tries grows to a certain point, the timeout being passed to poll() is larger than the timeout between calls to the SIGALRM handler. Since the poll() timeout is not reset, this leads to an infinite loop. In the traces above, the poll() timeout is 40000msec (== 40 sec), and the alarm handler is called every 30 sec. The fix should probably be to change res_send.c so that it properly decrements it's timeout value after being interrrupted. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 22:22:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 7345337B62D for ; Sat, 25 Mar 2000 22:22:47 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.57]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FS0003QOMW5P5@mta3.snfc21.pbi.net> for freebsd-hackers@FreeBSD.ORG; Sat, 25 Mar 2000 22:19:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 776E77C171; Sat, 25 Mar 2000 22:19:22 -0800 (PST) Date: Sat, 25 Mar 2000 22:19:22 -0800 (PST) From: Alex Zepeda Subject: Re: Missing keyboard symbols In-reply-to: To: Doug Barton Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Doug Barton wrote: > Heh... You know, I started to type out something to the effect of, > "... space bar. FreeBSD has been mapping the Space Bar to the Any key > combination since about 1992 to get around the restrictions of modern PC > keyboards." But I thought there was an outside chance that this was a > serious question, and I didn't want to run the risk that the poor doofus > would repeat that statement in front of someone with a clue... A serious question from Mr. Override? Uh yeah :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 25 22:56:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 0541D37B992 for ; Sat, 25 Mar 2000 22:56:14 -0800 (PST) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id WAA11314 for freebsd-hackers@freebsd.org; Sat, 25 Mar 2000 22:56:15 -0800 Date: Sat, 25 Mar 2000 22:56:15 -0800 From: Arun Sharma To: FreeBSD Hackers Subject: RTLD thread safety Message-ID: <20000325225615.A11307@sharmas.dhs.org> 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 When I try to compile a simple multi threaded program using a wrapper around rfork (from linuxthreads port), I get the following core dump: ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:54 Investigation into code reveals that lazy resolution of symbols (using PLTs) was happening in multiple threads in the linker simultaneously. Also, the code in lockdflt.c is achieving mutual exclusion by blocking signals. This doesn't work on a SMP machine using kernel threads. What would be the right solution for this ? A new set of primitives registered using dllockinit or making the defaults SMP thread-safe ? I suppose the linuxthreads port works because it has been tested only with Linux executables and Linux executables don't use lazy resolution of symbols ? I'm just speculating here. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message