From owner-freebsd-hackers Sun Jul 5 00:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00874 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 00:40:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from sos@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00863; Sun, 5 Jul 1998 00:40:11 -0700 (PDT) (envelope-from sos) Message-Id: <199807050740.AAA00863@hub.freebsd.org> Subject: Re: Console driver (was: Problems with irq 9(2)?) In-Reply-To: <199807050521.WAA03651@dog.farm.org> from Dmitry Kohmanyuk at "Jul 4, 98 10:21:16 pm" To: dk+@ua.net Date: Sun, 5 Jul 1998 00:40:11 -0700 (PDT) Cc: smoergrd@oslo.geco-prakla.slb.com, freebsd-hackers@FreeBSD.ORG From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Dmitry Kohmanyuk who wrote: > > by the way, while we are talking syscons, Soren, what ever happened > to my `invert border color in cyrillic mode' and `visual bell by > blinking border' patches I sent to you in, what, 1996? Should I dig > them up and port to 2.2.6?? I guess they are lying dormant somewhere, demand hasn't exactly been overwhelming :) If you port them, do it to -current... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 00:57:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02761 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 00:57:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02756 for ; Sun, 5 Jul 1998 00:57:04 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id EAA03879; Sun, 5 Jul 1998 04:56:49 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199807050756.EAA03879@roma.coe.ufrj.br> Subject: Re: accton on a append-only file ? In-Reply-To: <199807041545.RAA13938@semyam.dinoco.de> from Stefan Eggers at "Jul 4, 98 05:45:36 pm" To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Sun, 5 Jul 1998 04:56:49 -0300 (EST) Cc: jonny@jonny.eng.br, seggers@semyam.dinoco.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Stefan Eggers) // > I've created the /var/account/acct file with sappend,sunlink flags, // > but accton return EPERM. If I run accton before setting those flags, // // > This seems to be a bug, but I still have much to learn from VFS // // To me, too. It is because kern_acct.c in 2.2-stable opens the file // for writing, not for appending. There is the problem: // // /* // * If accounting is to be started to a file, open that file for // * writing and make sure it's a 'normal'. // */ // if (uap->path != NULL) { // NDINIT(&nd, LOOKUP, NOFOLLOW, UIO_USERSPACE, uap->path, p); // error = vn_open(&nd, FWRITE, 0); // if (error) // return (error); // // // Unless there is already a PR for this (check the PR database on the // FreeBSD web pages) I'd suggest sending in a new one. I've just sent it. It's kern/7169. // > before searching for the culprit myself. Does it deserve a send-pr, // > even without patches ? // // I think it's as easy as adding FAPPEND to the mode. The only problem // is making sure that it has no unexpected side effects. If you like // quote this email in the PR to point at a possible way to fix it. This worked for me at home. But since file writing at kernel level is somewhat tricky, I'd be a lot more happy if some FS expert verified it before commiting. If it's safe, please don't forget -stable, folks. :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 01:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06588 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 01:28:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06581 for ; Sun, 5 Jul 1998 01:28:20 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA10501 for ; Sun, 5 Jul 1998 01:25:56 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010499; Sun Jul 5 08:25:53 1998 Date: Sun, 5 Jul 1998 01:25:50 -0700 (PDT) From: Julian Elischer To: hackers@FreeBSD.ORG Subject: something screwed with CVSup.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 I put in a HEAP of changes today and I have yet to receive any of them back via CVSUP even though I have run it several time in the last 10 hours. I really want to see my changes coma all the way back so I can 'make world' with the checked out sources and know it still works.. is cvsup1.freebsd.org ill? has it not updated? I also tried cvsup3 with the same result.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 01:59:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09982 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 01:59:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09976 for ; Sun, 5 Jul 1998 01:59:50 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id FAA04617; Sun, 5 Jul 1998 05:59:48 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199807050859.FAA04617@roma.coe.ufrj.br> Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: from Julian Elischer at "Jul 5, 98 01:25:50 am" To: julian@whistle.com (Julian Elischer) Date: Sun, 5 Jul 1998 05:59:48 -0300 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Julian Elischer) // I put in a HEAP of changes today // and I have yet to receive any of them back via CVSUP // even though I have run it several time in the last 10 hours. I've noticed that the cvsup log from cvsup.br.freebsd.org that I received today was too small. And this saturday had lots of commits announced in the cvs-all list. Now, somebody has to check if the problem is indeed at cvsup.freebsd.org (from where cvsup.br gets its files) or at freefall. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 02:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10367 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 02:03:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (ulf@gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10357 for ; Sun, 5 Jul 1998 02:02:58 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.9.0/8.8.6) id CAA12762; Sun, 5 Jul 1998 02:03:00 -0700 (PDT) Message-ID: <19980705020259.A1138@Alameda.net> Date: Sun, 5 Jul 1998 02:02:59 -0700 From: Ulf Zimmermann To: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Sun, Jul 05, 1998 at 01:25:50AM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.2-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 05, 1998 at 01:25:50AM -0700, Julian Elischer wrote: > > I put in a HEAP of changes today > and I have yet to receive any of them back via CVSUP > even though I have run it several time in the last 10 hours. > > I really want to see my changes coma all the way back so I can > 'make world' with the checked out sources and know it still works.. > > > is cvsup1.freebsd.org ill? > has it not updated? > I also tried cvsup3 with the same result.. I just tried to use cvsup2.freebsd.org (rdy's machine) and got connection refused. running cvsup from cvsup.freebsd.org right now. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- 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 Sun Jul 5 02:13:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11455 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 02:13:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11446 for ; Sun, 5 Jul 1998 02:13:51 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id GAA04742; Sun, 5 Jul 1998 06:12:28 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199807050912.GAA04742@roma.coe.ufrj.br> Subject: Loopback mounts (Was: Variant Link implementation) In-Reply-To: <199807042109.OAA02700@usr02.primenet.com> from Terry Lambert at "Jul 4, 98 09:09:42 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 5 Jul 1998 06:12:28 -0300 (EST) Cc: witr@rwwa.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Terry Lambert) // > Note that AMD solves a similiar problem in different way. For // > example, /usr/global/bin gets directed to the correct filesystem // > based on the architecture/os. // // One issue with amd (which is only partially resolvable using the // symlink generation on the mounted fs instead of loopback) is that // loopback mounts via NFS are poison. It is rather easy to hang // every process using the loopback with a nice starvation deadlock // when using it for programs for which the loopback is a swap store. Is mount_null working ? Last time I tried it paniced my machine very often. And mount_umap would be wonderful for some applications, but the effects were even worse. If they work, we could patch amd to use them IFF rhost==thishost. AFAIK, Solaris has been doing this for a long time. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 02:18:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11978 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 02:18:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11949 for ; Sun, 5 Jul 1998 02:18:18 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id CAA11454; Sun, 5 Jul 1998 02:12:23 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011450; Sun Jul 5 09:12:23 1998 Date: Sun, 5 Jul 1998 02:12:17 -0700 (PDT) From: Julian Elischer To: Ulf Zimmermann cc: hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: <19980705020259.A1138@Alameda.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 Sun, 5 Jul 1998, Ulf Zimmermann wrote: > On Sun, Jul 05, 1998 at 01:25:50AM -0700, Julian Elischer wrote: > > > > I put in a HEAP of changes today > > and I have yet to receive any of them back via CVSUP > > even though I have run it several time in the last 10 hours. > > > > I really want to see my changes coma all the way back so I can > > 'make world' with the checked out sources and know it still works.. > > > > > > is cvsup.freebsd.org ill? > > has it not updated? > > I also tried cvsup3 with the same result.. > > I just tried to use cvsup2.freebsd.org (rdy's machine) and got > connection refused. running cvsup from cvsup.freebsd.org right now. I bet it doesn't have any changes I put in today. (compare conf.h using the cgi interface on www.freebsd.org with what you get.) > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > 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 Sun Jul 5 02:24:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12820 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 02:24:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12781 for ; Sun, 5 Jul 1998 02:24:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id SAA29700; Sun, 5 Jul 1998 18:53:31 +0930 (CST) Message-ID: <19980705185330.K18970@freebie.lemis.com> Date: Sun, 5 Jul 1998 18:53:30 +0930 From: Greg Lehey To: ulf@Alameda.net, Julian Elischer , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? References: <19980705020259.A1138@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980705020259.A1138@Alameda.net>; from Ulf Zimmermann on Sun, Jul 05, 1998 at 02:02:59AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 5 July 1998 at 2:02:59 -0700, Ulf Zimmermann wrote: > On Sun, Jul 05, 1998 at 01:25:50AM -0700, Julian Elischer wrote: >> >> I put in a HEAP of changes today >> and I have yet to receive any of them back via CVSUP >> even though I have run it several time in the last 10 hours. >> >> I really want to see my changes coma all the way back so I can >> 'make world' with the checked out sources and know it still works.. Admit it, Julian, you've caused it to become comatose :-) >> is cvsup1.freebsd.org ill? >> has it not updated? >> I also tried cvsup3 with the same result.. > > I just tried to use cvsup2.freebsd.org (rdy's machine) and got > connection refused. running cvsup from cvsup.freebsd.org right now. Right. That happened to me this morning, too (about 7 hours ago). Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 03:24:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19537 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 03:24:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19480 for ; Sun, 5 Jul 1998 03:23:55 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id MAA15640; Sun, 5 Jul 1998 12:15:17 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id LAA15803; Sun, 5 Jul 1998 11:57:55 +0200 (CEST) (envelope-from andreas) Message-ID: <19980705115752.A15795@klemm.gtn.com> Date: Sun, 5 Jul 1998 11:57:52 +0200 From: Andreas Klemm To: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Sun, Jul 05, 1998 at 01:25:50AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 05, 1998 at 01:25:50AM -0700, Julian Elischer wrote: > > I put in a HEAP of changes today > and I have yet to receive any of them back via CVSUP > even though I have run it several time in the last 10 hours. > > I really want to see my changes coma all the way back so I can > 'make world' with the checked out sources and know it still works.. Same for me using the german mirror site cvsup.de.freebsd.org -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 04:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25335 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 04:08:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25313 for ; Sun, 5 Jul 1998 04:08:46 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA09519; Sun, 5 Jul 1998 13:07:45 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id MAA05304; Sun, 5 Jul 1998 12:42:00 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807051042.MAA05304@semyam.dinoco.de> Cc: David Kelly , Stefan Eggers To: freebsd-hackers@FreeBSD.ORG Subject: Re: permission confusion at mount points In-reply-to: Your message of "Thu, 02 Jul 1998 19:21:25 CDT." <199807030021.TAA18905@nospam.hiwaay.net> Date: Sun, 05 Jul 1998 12:41:59 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off: Thanks to the people who responded. I'll now sending in a PR to get a small note into the BUGS section of mount(2) and mount(8) to give others a chance to solve it a bit faster. > For kicks, "cd /usr2; pwd". Bet it'll fail. Same for SGI's Irix 6.2. Bash was irritating me at first (it internally stores the name of the current working directory) but with sh it doesn't work. Interesting. :-) > Use 755 permissions on your underlying mount point and put the problem > out of your misery. That's how I solved it. It was just irritating. To avoid this sort of problems bothering others I think the man pages should mention it. See above. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 04:09:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25364 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 04:09:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25346 for ; Sun, 5 Jul 1998 04:09:01 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA09538; Sun, 5 Jul 1998 13:07:48 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id MAA05621; Sun, 5 Jul 1998 12:53:31 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807051053.MAA05621@semyam.dinoco.de> Cc: Joao Carlos Mendes Luis , seggers@semyam.dinoco.de To: hackers@FreeBSD.ORG Subject: Re: accton on a append-only file ? In-reply-to: Your message of "Sun, 05 Jul 1998 04:56:49 -0300." <199807050756.EAA03879@roma.coe.ufrj.br> Date: Sun, 05 Jul 1998 12:53:31 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > // I think it's as easy as adding FAPPEND to the mode. The only problem > This worked for me at home. But since file writing at kernel level > is somewhat tricky, I'd be a lot more happy if some FS expert verified > it before commiting. I was confused by the file not specifying it is appending but that is handled by the write operation itself. For my personal machine I'd say it is correct, but I still have to get a bit more aquainted with the internal vnode operations used in kern_acct.c to be 100% sure. > If it's safe, please don't forget -stable, folks. :) If they forget it just ask for it. I think Jordan was it who said to ask for those patches needed to be transfered to -stable if someone forgets. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 05:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01572 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 05:01:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01447; Sun, 5 Jul 1998 05:00:44 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id OAA20335; Sun, 5 Jul 1998 14:00:40 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id OAA13829; Sun, 5 Jul 1998 14:00:40 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807051200.OAA13829@surf.IAE.nl> Subject: Re: Apollo tapes (was: Variant Link implementation, continued) In-Reply-To: <19980705104647.O358@freebie.lemis.com> from Greg Lehey at "Jul 5, 98 10:46:47 am" To: grog@lemis.com (Greg Lehey) Date: Sun, 5 Jul 1998 14:00:40 +0200 (MET DST) Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You ( Greg Lehey ) write: => On Saturday, 4 July 1998 at 15:28:37 +0200, Willem Jan Withagen wrote: => > In article <199807030025.TAA18925@nospam.hiwaay.net> you write: => >> In the early bad old days of DAT (more correctly known as DSS) there => >> were more problems than there should have been with one tape drive not => >> being able to read tapes from another, all other things the same. => > => > Oke, My drive is again on line: => > => > [~] wjw@digi> mt stat => > Present Mode: Density = X3B5/88-185A Blocksize variable => > ---------available modes--------- => > Mode 0: Density = 0x00 Blocksize variable => > Mode 1: Density = X3.136-1986 Blocksize = 512 bytes => > Mode 2: Density = X3.39-1986 Blocksize variable => > Mode 3: Density = X3.54-1986 Blocksize variable => > => > looking at: man mt: => > The different density codes are as follows: => > => > 0x0 default for device => > 0xE reserved for ECMA => > => > Value Tracks Density(bpi) Code Type Reference Note => > ........ => > 0x13 1 61000 DDS CS X3B5/88-185A 4 => > 0x14 1 43245 RLL CS X3.202-1991 4 => > 0x15 1 45434 RLL CS ECMA TC17 4 => > => > Which are 3 DAT formats. And thus it is a DDS-coded tape. => => This describes the tape unit, not the tape. We've already established => that it can't read the tape. => => > Anybody with more suggestions?? (other than finding the "old" tapedrive) => => Give up? Or send them to Mike? Julian suggested to change the density codes and/or the blocksize. But changing blocksizes only gets EOF errors. Changing densities doesn't generate errors, but it also does nothing else. I've still got some very old (semi-defective) DAT's which I'm going to give a shot. And perhaps go back to my old University group, to see if they still have the drive. :-( --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 07:51:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12218 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 07:51:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12184 for ; Sun, 5 Jul 1998 07:50:50 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA11925; Sun, 5 Jul 1998 07:49:56 -0700 (PDT) Message-Id: <199807051449.HAA11925@implode.root.com> To: Terry Lambert cc: drosih@rpi.edu, hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-reply-to: Your message of "Sat, 04 Jul 1998 20:36:29 -0000." <199807042036.NAA01481@usr02.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Jul 1998 07:49:56 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >I agree that the possible keys (ie, variable names) for symbolic >> >links should not be something that's fixed at system build time. >> >> I sure don't agree with that. I also think Jordan's desire to have symlinks >> translated with the user environment is either not attainable or undesirable >> or both. I personally would rather that the info be kept in a seperate name >> table (like what Terry suggested). I also prefer to have a hierarchical >> structure (also like Terry suggested, except that I'd have the system table >> as a seperate autonomous thing and not attached to the init process). > >Hmmm. > >I think "#kern.osrelease" or "#hw.machine" might be a sufficient >escape mechanism. Thanks, Terry for quoting this text...I just noticed that I read what I was replying to backwards. I *do* agree that the "possible keys should _not_ be something that is fixed at system build time". For some reason, I read just the opposite, but I'm awake this morning. :-) >The point was really the the init PID (or 0) be used to reference >an inherited system space. It's not as important that it actually >be hung off a proc structure, it just makes it more orthoganal to >have one type of object backing the logical name table. It seems more orthagonal to me for pid 0/1 to have their own, local name table and the system one to be entirely seperate. The same struct type would be used in all cases, of course, but the system table should be completely seperate, IMO... -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 09:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17792 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 09:05:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17787 for ; Sun, 5 Jul 1998 09:05:43 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id JAA26049; Sun, 5 Jul 1998 09:05:34 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sun, 5 Jul 1998 09:05:34 -0700 (PDT) From: Chris Timmons To: Joao Carlos Mendes Luis cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: <199807050859.FAA04617@roma.coe.ufrj.br> 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 cvsup.freebsd.org's updates from freefall were being rejected: opus:/usr/users/skynyrd> more /var/log/cvsup.log.1 CVSup update begins at 1998/07/05 07:02:01 Updating from freefall.freebsd.org Connected to freefall.freebsd.org Rejected by server: Access limit exceeded; try again later CVSup update ends at 1998/07/05 07:02:07 It looks like this hour's updates are coming through. Perhaps something was wedged on freefall? -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 09:11:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18296 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 09:11:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18291; Sun, 5 Jul 1998 09:11:27 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) id 0ysrNq-0004gV-00; Sun, 5 Jul 1998 18:11:22 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id SAA00913; Sun, 5 Jul 1998 18:10:23 +0200 (SAT) Date: Sun, 5 Jul 1998 18:10:23 +0200 (SAT) From: Peter van Heusden To: Stefan Esser cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI drive not remapping bad block: Any solution (fwd) In-Reply-To: <19980704194719.60384@mi.uni-koeln.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 Sat, 4 Jul 1998, Stefan Esser wrote: [snip] > In order to recover from that error, you may want to write new > data to the replacement sector, and the easiest way to do this > is to "dd if=/dev/zero of=/dev/rsd1c bs=64k" (assuming that the > drive is "sd1" ...). Thanks, I tried this, but dd returned: dd: /dev/rsd2c: Read-only file system which I can't understand, because ls -l /dev/rsd2c gives: crw-r----- 1 root operator 13, 18 Jul 5 18:07 /dev/rsd2c Is there something I should do before I can write to this device? Thanks, Peter P.S. Is there anywhere I can find out more about SCSI so that I understand this stuff better? -- Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 09:44:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21064 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 09:44:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21051 for ; Sun, 5 Jul 1998 09:44:42 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id JAA26485; Sun, 5 Jul 1998 09:44:39 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sun, 5 Jul 1998 09:44:39 -0700 (PDT) From: Chris Timmons To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? 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 It appears that the avalanche of repository tagging at least contributed to a situation in which freefall was unable to keep up with the load. I'll let jdp explain when he figures out what really happened. cvsup.freebsd.org is almost caught up now... -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 10:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25650 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 10:10:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22999 for ; Sun, 5 Jul 1998 10:10:31 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA05317; Sun, 5 Jul 1998 09:42:56 -0700 (PDT) Message-Id: <199807051642.JAA05317@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Willem Jan Withagen cc: hackers@FreeBSD.ORG Subject: Re: adding to sysctl env. In-reply-to: Your message of "Sun, 05 Jul 1998 00:15:22 +0200." <199807042215.AAA00277@hobby.digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 09:42:56 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I'm trying to add things to the sysctl environment, and I thought to take > a simple step first: > make a debug.switch for the vlink module. > So I added: > ---- > /* > * For the vlink module debugging > */ > static int vlinkxlatedebug = 0; > SYSCTL_INT(_debug, OID_AUTO, vlinkxlate, CTLFLAG_RW, &vlinkxlatedebug, 0, > ""); > ---- > expecting to see it apear in my sysctl -a output. > > But guess what: I didn't. :-{ It should have. Make sure that the source file is actually being built as part of the kernel. You could be more paranoid and remove the 'static', then try # nm /kernel | grep vlinkxlate in order to make sure that the symbol is present in the running kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 10:10:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02205 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 10:10:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29441 for ; Sun, 5 Jul 1998 10:10:48 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA05255; Sun, 5 Jul 1998 09:34:40 -0700 (PDT) Message-Id: <199807051634.JAA05255@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joe Abley cc: hackers@FreeBSD.ORG Subject: Re: ethernet peculiarity In-reply-to: Your message of "Sun, 05 Jul 1998 12:23:51 +1200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 09:34:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This may well be a completely inappropriate list for this (in which case > "sorry"); however, I _was_ interested in what could cause a generic > kernel-wide ethernet (or ISA?) failure in a machine. You probably forgot to dink the BIOS setup to assign the interrupt(s) you're using to the ISA bus. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24052 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from msmith@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24045 for hackers@freebsd.org; Sun, 5 Jul 1998 13:33:03 -0700 (PDT) (envelope-from msmith) Date: Sun, 5 Jul 1998 13:33:03 -0700 (PDT) From: Michael Smith Message-Id: <199807052033.NAA24045@hub.freebsd.org> To: hackers@FreeBSD.ORG Subject: freebsd.org cluster outage Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The cluster was sick this morning for two reasons: - dg rebooted freefall, but it failed to go down correctly - /var on hub was full (for once, not due to oversize user mailboxes) Freefall is back up, and I'm hoping that with a little more space on hub in /var, the 200M+ of queued mail will drain. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24232 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24074; Sun, 5 Jul 1998 13:33:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from smap@localhost) by gatekeeper.whistle.com (8.7.5/8.6.12) id MAA21246; Sun, 5 Jul 1998 12:08:30 -0700 (PDT) Received: from alpo.whistle.com(alpo 207.76.204.38) by gatekeeper via smap (V2.0) id xma021244; Sun, 5 Jul 98 12:08:14 -0700 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21012; Sun, 5 Jul 1998 11:56:02 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021010; Sun Jul 5 18:55:53 1998 Date: Sun, 5 Jul 1998 11:55:50 -0700 (PDT) From: Julian Elischer To: Peter van Heusden cc: Stefan Esser , freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI drive not remapping bad block: Any solution (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 fistly, use rsd2 not rsd2c (if it's dange=ously dedicated..) or rsd2s1 if it has slices.. secondly many drives go read-only when they run out of replacement sectors.. I have one here (a Quantum) that has done this.. On Sun, 5 Jul 1998, Peter van Heusden wrote: > On Sat, 4 Jul 1998, Stefan Esser wrote: > > [snip] > > > In order to recover from that error, you may want to write new > > data to the replacement sector, and the easiest way to do this > > is to "dd if=/dev/zero of=/dev/rsd1c bs=64k" (assuming that the > > drive is "sd1" ...). > > Thanks, I tried this, but dd returned: > > dd: /dev/rsd2c: Read-only file system > > which I can't understand, because ls -l /dev/rsd2c gives: > > crw-r----- 1 root operator 13, 18 Jul 5 18:07 /dev/rsd2c > > Is there something I should do before I can write to this device? > > Thanks, > Peter > P.S. Is there anywhere I can find out more about SCSI so that I understand > this stuff better? > -- > Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa > pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! > > > 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 Sun Jul 5 13:33:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24250 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24218 for ; Sun, 5 Jul 1998 13:33:42 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA26526; Sun, 5 Jul 1998 22:05:14 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id WAA06547; Sun, 5 Jul 1998 22:02:56 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807052002.WAA06547@semyam.dinoco.de> To: zhihuizhang Cc: hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Lock mechanism questions In-reply-to: Your message of "Sat, 04 Jul 1998 16:20:57 EDT." Date: Sun, 05 Jul 1998 22:02:55 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By the way, I know spin lock is not suitable for interrupt routines that > access the same data structures. Can anyone give me a reason for this? Isn't that because of the problems you have when a higher priority interrupt occurs while serving a lower priority interrupt and both want to access the data structures? Then the lower priority one would have to get at least to the place where it frees the lock to allow the higher priority one to continue. But how does it achieve this? The higher priority interrupt gets serviced first. Deadlock. The same for an interrupt and a normal kernel function which both try to access the same spin lock protected data structure. Then a similar situation arises. For processes it works as the waiting process eventually has to give up the CPU. Then the process holding the lock can work further toward releasing it. That's how I understand this problem with what I know as spin lock. I might be wrong of course. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00376 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:40:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (root@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00282 for ; Sun, 5 Jul 1998 13:40:06 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA15367; Sun, 5 Jul 1998 12:13:26 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd015330; Sun Jul 5 12:13:17 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA27026; Sun, 5 Jul 1998 12:13:15 -0700 (MST) From: Terry Lambert Message-Id: <199807051913.MAA27026@usr08.primenet.com> Subject: Re: adding to sysctl env. To: wjw@hobby.digiware.nl (Willem Jan Withagen) Date: Sun, 5 Jul 1998 19:13:15 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199807042215.AAA00277@hobby.digiware.nl> from "Willem Jan Withagen" at Jul 5, 98 00:15:22 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > make a debug.switch for the vlink module. > So I added: > ---- > /* > * For the vlink module debugging > */ > static int vlinkxlatedebug = 0; > SYSCTL_INT(_debug, OID_AUTO, vlinkxlate, CTLFLAG_RW, &vlinkxlatedebug, 0, > ""); > ---- > expecting to see it apear in my sysctl -a output. > > But guess what: I didn't. :-{ You are using "options DEBUG", right? Also: you are staticaly linking this driver, not loading it as an LKM, right? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00694 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:41:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from digi.digiware.nl (gtw.digiware.nl [194.151.72.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00635 for ; Sun, 5 Jul 1998 13:41:24 -0700 (PDT) (envelope-from wjw@digi.digiware.nl) Received: by digi.digiware.nl (8.8.7/1.63) id UAA10241; Sun, 5 Jul 1998 20:39:31 GMT From: wjw@digi.digiware.nl (Willem Jan Withagen) Message-Id: <199807052039.UAA10241@digi.digiware.nl> Subject: Re: adding to sysctl env. To: mike@smith.net.au (mike) Date: Sun, 5 Jul 1998 22:39:30 +0200 (CEST) Cc: terry@lambert.org (Terry Lambert), hackers@FreeBSD.ORG Reply-To: wjw@digiware.nl X-Mailer: ELM [version 2.4ME+ PL31H (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 mike, Terry, I've created a SYSCTL_INT.9 manpage. I've appended it so you can comment. And/or perhaps can commit it, if you have commit-rights Next question: If an include file requires another include file. eg. sys/sysctl.h requires sys/kernel.h Does the include for kernel.h go into sysctl.h? Reason I ask, is that there were no errors when I compiled without the inclusion, but that was the problem I could not see the debug.vlinkxlate in sysctl. :-( --WjW .\" -*- nroff -*- .\" .\" Copyright (c) 1998 Willem Jan Withagen .\" .\" All rights reserved. .\" .\" This program is free software. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $Id: $ .\" .Dd July 4, 1998 .Os .Dt SYSCTL_INT 9 .Sh NAME .Nm SYSCTL_INT .Nd Create an integer type entry in the sysctl table .Sh SYNOPSIS .Fd #include .Fd #include .Ft void .Fn SYSCTL_INT "parent" "nbr" "name" "access" "ptr" "val" "descr" .Sh DESCRIPTION A MACRO to create an integer type entry in the sysctl table. .Pp Its arguments are: .Bl -tag -width 8X .It Ar parent a name from the "class" of top level names, currently: _kern, _debug, _net, _machdep, _vm, _hw, _user, _vfs. .It Ar nbr the number of the sub-OID in the selected class, OR OID_AUTO in which case a number is automagically assigned .It Ar name the name which is used in the text interface with sysctl(8) .It Ar access what acctions are allowed: CTLFLAG_RD (read only), CTLFLAG_WR (write only??), CTLFLAG_RW (read and write) .It Ar ptr a pointer to the storage which actually contains the data used by the entry .It Ar val mostly 0 .It Ar descr mostly "" .El .Sh Example .Bd -literal static int vlinkxlatedebug; SYSCTL_INT(_debug, OID_AUTO, vlinkxlate, CTLFLAG_RW, &vlinkxlatedebug, 0, ""); .Ed .Sh SEE ALSO .Xr sysctl 3 .Xr sysctl 8 .Sh AUTHORS This man page was written by Willem Jan Withagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:42:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00870 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:42:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00856 for ; Sun, 5 Jul 1998 13:42:10 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id UAA02069; Sun, 5 Jul 1998 20:51:32 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id UAA04997; Sun, 5 Jul 1998 20:51:31 +0200 (MET DST) Date: Sun, 5 Jul 1998 20:51:31 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807051851.UAA04997@surf.IAE.nl> To: mike@smith.net.au Subject: Re: adding to sysctl env. X-Newsgroups: list.freebsd.hackers In-Reply-To: <199807051642.JAA05317@antipodes.cdrom.com> References: <199807042215.AAA00277@hobby.digiware.nl> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG, wjw@digiware.nl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807051642.JAA05317@antipodes.cdrom.com> you write: >> Hi, >> >> I'm trying to add things to the sysctl environment, and I thought to take >> a simple step first: >> make a debug.switch for the vlink module. >> So I added: >> ---- >> /* >> * For the vlink module debugging >> */ >> static int vlinkxlatedebug = 0; >> SYSCTL_INT(_debug, OID_AUTO, vlinkxlate, CTLFLAG_RW, &vlinkxlatedebug, 0, >> ""); >> ---- >> expecting to see it apear in my sysctl -a output. >> >> But guess what: I didn't. :-{ > >It should have. Make sure that the source file is actually being built >as part of the kernel. You could be more paranoid and remove the >'static', then try > ># nm /kernel | grep vlinkxlate > >in order to make sure that the symbol is present in the running kernel. It is in the kernel, even the sysctl_entry: f014b740 t _sysctl___debug_vlinkxlate as are the variable and the function: f014b7f0 T _vlink_xlate f0276f80 d _vlinkxlatedebug However it was a good hint: wjw@hobby> nm /kernel | grep __debug f011cd2c t ___set_sysctl__debug_sym_sysctl___debug f014dd24 t ___set_sysctl__debug_sym_sysctl___debug_busyprt f0120990 t ___set_sysctl__debug_sym_sysctl___debug_debugger_on_panic f01e5290 t ___set_sysctl__debug_sym_sysctl___debug_doasyncfree f010efe8 t ___set_sysctl__debug_sym_sysctl___debug_elf_trace f011603c t ___set_sysctl__debug_sym_sysctl___debug_fdexpand f01657c0 t ___set_sysctl__debug_sym_sysctl___debug_if_tun_debug f01373d8 t ___set_sysctl__debug_sym_sysctl___debug_ttydebug f0148cf8 t ___set_sysctl__debug_sym_sysctl___debug_vfscache f011cd28 t ___set_sysctl__sym_sysctl___debug f011cd04 t _sysctl___debug f014dd00 t _sysctl___debug_busyprt f0120960 t _sysctl___debug_debugger_on_panic f01e5264 t _sysctl___debug_doasyncfree f010efc0 t _sysctl___debug_elf_trace f0116014 t _sysctl___debug_fdexpand f0165794 t _sysctl___debug_if_tun_debug f01373b0 t _sysctl___debug_ttydebug f0148cd0 t _sysctl___debug_vfscache f014b740 t _sysctl___debug_vlinkxlate f0281a0c ? _sysctl__debug But I'm for shure that there a lot more debug variables which aren't shown wjw@hobby> sysctl -a | grep debug debug.elf_trace: 0 debug.fdexpand: 0 debug.debugger_on_panic: 1 debug.ttydebug: 0 debug.vfscache: 1 debug.if_tun_debug: 0 debug.doasyncfree: 1 Which is also missing busyprt! Obviously I'd atleast have to have an entry like: ___set_sysctl__debug_sym_sysctl___debug_vlinkxlate And then still run the risk that it doesn't show 'cause it is treated like busyprt Which leads me to the following question: Is there a large difference between sysctl on -stable and on -current? Why: I just feel like ripping it out because in the long run I'll problably have to do it anyways, since I need dynamic allocation for my vlink-stuff. I'd then create a double linked chain (for top level) with double-linked subschains for all the sub.mib.levels. [my first hunch] --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01209 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:44:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01196; Sun, 5 Jul 1998 13:44:19 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA19389; Sun, 5 Jul 1998 12:11:41 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd019377; Sun Jul 5 12:11:40 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA26965; Sun, 5 Jul 1998 12:11:38 -0700 (MST) From: Terry Lambert Message-Id: <199807051911.MAA26965@usr08.primenet.com> Subject: Re: block device on wst device. To: julian@whistle.com (Julian Elischer) Date: Sun, 5 Jul 1998 19:11:38 +0000 (GMT) Cc: hackers@FreeBSD.ORG, sos@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Jul 4, 98 01:58:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ther is a block interface to wst > > is this used by anyone? > does it work? > > I think the block interface should go away > as it doesn't really make much sense on tapes. > (same for wt.c) > > In effect it went a way some time ago for st.c I still see this as a problem, specifically for tape devices. I see the block device for tape drives capable of providing a kernel side buffer that is not statically allocated to a particular driver and which provides bufferring for streaming tape devices. The examples I can come up with where the user space write to the buffer should return immediately so that the user space program can read, and therefore overlap physical tape and disk I/O, are DAT devices and QIC-40/80/120/etc. devices. This is specifically relevent to the FT (QIC-40/etc.) devices because of there use of a (normally) non-FIFO-ed serial interface, to wit, the floppy controller. Some people will say "yeah, but no one with any sense uses those"; however, I could make the same argument against IDE on the same basis (specifically, number of tagged commands drives allow in their queues). For a destop machine, cheap is often good enough, and FT drives are certainly cheap. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01607 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:46:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (root@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01596 for ; Sun, 5 Jul 1998 13:46:31 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id PAA27542; Sun, 5 Jul 1998 15:38:17 -0400 (EDT) Date: Sun, 5 Jul 1998 15:38:16 -0400 (EDT) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: Un-rolling token-ring packets? Need a little 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 am near having a working token-ring driver (IBM Shared ram only) but I am having trouble figuring out how to unroll the packets and pass them up the layers of network code. I am at the stage where I need to put the packets into mbufs and pass them off the an iso88025_input routine. I can already pull the packets out of the adapter's shared ram. I need help with the headers mostly and the iso88025_input routine. Any takers? Here is some sample output from the driver (I only dumped the beggining of the packets): Jul 5 14:47:50 anarchy /kernel: tok0: Packet received data: Jul 5 14:47:50 anarchy /kernel: cmd[81] station_id[100] Jul 5 14:47:50 anarchy /kernel: bptr[a3e] lhdr[e] dhdr[3] len[32] ncb[6] Jul 5 14:47:50 anarchy /kernel: tok0:Packet data: Jul 5 14:47:50 anarchy /kernel: 18 40 ff ff ff ff ff ff 0 0 83 2d 9f 35 aa aa 3 0 0 0 8 6 0 6 8 0 6 4 0 1 0 0 83 2d 9f 35 a what I know (or at least what I think) ---- Token ring mac header ----- 18 40 - Access control/Frame control (don't care - at least for now) ff ff ff ff ff ff - (Destination address to me - no previous arp) 00 00 83 2d 9f 35 - (Source address my olicom card in another machine) ---- Token ring llc header ----- aa aa - dest sap / source sap (both ip) 03 - control field, no clue? (Only one byte because dlc_hdr_len = 3?) after that I am lost. Jul 5 14:47:50 anarchy /kernel: tok0: ack'ing packet to adapter (rc=0). Jul 5 14:47:50 anarchy /kernel: tok: isrp e[2] o[8] isra e[3] o[10] (tok_rx_intr 2). Jul 5 14:47:50 anarchy /kernel: tok0: asb->bptr [a3e] arb->bptr [a3e]. Jul 5 14:47:51 anarchy /kernel: tok0: Interrupt received. Jul 5 14:47:51 anarchy /kernel: tok: isrp e[42] o[8] isra e[3] o[0] (tok_intr 1a). Jul 5 14:47:51 anarchy /kernel: tok: isrp e[2] o[8] isra e[3] o[0] (tok_intr 1b). Jul 5 14:47:51 anarchy /kernel: tok0: interrupt received (isrp_o = 8). Jul 5 14:47:51 anarchy /kernel: tok0: Receive interrupt called. Jul 5 14:47:51 anarchy /kernel: tok: isrp e[2] o[8] isra e[7] o[0] (tok_rx_intr 1). Jul 5 14:47:51 anarchy /kernel: tok0: Packet received data: Jul 5 14:47:51 anarchy /kernel: cmd[81] station_id[100] Jul 5 14:47:51 anarchy /kernel: bptr[aae] lhdr[10] dhdr[3] len[34] ncb[6] Jul 5 14:47:51 anarchy /kernel: tok0:Packet data: Jul 5 14:47:51 anarchy /kernel: 18 40 ff ff ff ff ff ff 80 0 83 2d 9f 35 82 70 aa aa 3 0 0 0 8 6 0 6 8 0 6 4 0 1 0 0 83 2d 9f 35 a what I know (or at least what I think) ----- Token ring mac header ----- 18 40 - Access control/Frame control (don't care - at least for now) ff ff ff ff ff ff - (Destination address to me - no previous arp) 80 00 83 2d 9f 35 - (Source address my olicom card in another machine, but with source routing) 82 70 - RCF (no RIF) RCF 100 - All routes broadcast 00000 - Length of RIF (0 bytes) 0 - direction (forward) 000 - largest frame (516 bytes) 0010 - reserved (no touch!) ----- Token ring llc header ------ aa aa - dest sap / source sap (both ip) 03 - control field, no clue? (Only one byte because dlc_hdr_len = 3?) after that I am lost. Jul 5 14:47:51 anarchy /kernel: tok0: ack'ing packet to adapter (rc=0). Jul 5 14:47:51 anarchy /kernel: tok: isrp e[2] o[8] isra e[7] o[10] (tok_rx_intr 2). Jul 5 14:47:51 anarchy /kernel: tok0: asb->bptr [aae] arb->bptr [aae]. I am getting very very close, I would hate to see this be for nothing because I don't understand mbufs and the lower level protocols. Also where is the ethertype field, in the SNAP? Where's the SNAP header? Arrgh, I'm in over my head, ye` old gods of networking help me please. All the code and a longer copy of the dmesg are at http://anarchy.stdio.com Thanks in advance, Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 13:56:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04284 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:56:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04233 for ; Sun, 5 Jul 1998 13:56:06 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id LAA18346 for ; Sun, 5 Jul 1998 11:21:12 -0700 (PDT) (envelope-from jdp) Message-Id: <199807051821.LAA18346@austin.polstra.com> To: hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Date: Sun, 05 Jul 1998 11:21:12 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chris Timmons wrote: > > It appears that the avalanche of repository tagging at least contributed > to a situation in which freefall was unable to keep up with the load. > I'll let jdp explain when he figures out what really happened. Freefall became ill and a bunch of cvsupd processes ended up hung in D state, unkillable by any means. This caused the master cvsupd process to stop accepting clients, because its access limits were already maxxed out. We did a remote reboot of freefall, but unfortunately it did not make it back up again. It responds to pings but none of the daemons have started, including sshd. The operative hypothesis is that it is hung up waiting on an NFS mount from a machine that's down. It is a holiday weekend here in the US, and we haven't been able to find anybody physically near to the machines who could go in and get things running again. So we are without freefall at least for a while. Maybe this would be a good day to get a life and try doing something else for a change. :-) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 14:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08120 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 14:09:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from squirrel.tgsoft.com (cx20270-a.pwy1.sdca.home.com [24.0.169.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA08112 for ; Sun, 5 Jul 1998 14:09:49 -0700 (PDT) (envelope-from thompson@tgsoft.com) Received: (qmail 707 invoked by uid 128); 5 Jul 1998 21:09:47 -0000 Date: 5 Jul 1998 21:09:47 -0000 Message-ID: <19980705210947.706.qmail@squirrel.tgsoft.com> From: mark thompson To: freebsd-hackers@FreeBSD.ORG Subject: 3com etherlink xl pci Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a 3Com 3c900 (combo, rev A) that has lately developed a little fault. The behaviour suggests that it loses an output interrupt sometimes, or perhaps locks up... ifconfig reports that the link is OACTIVE, and nothing works. If you ifconfig down, ifconfig up, that fixes the problem, so it is within the ability of the driver to correct, given that a timeout or some such triggers the correct recovery. Anyway, I am willing to donate the card to anybody who WANTS TO FIX THE DRIVER to deal with this apparent failure mode, since the card is completely usable otherwise. Contact me if you want to work on this. -mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 14:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08922 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 14:15:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA08916 for ; Sun, 5 Jul 1998 14:15:15 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 560 invoked from network); 5 Jul 1998 18:27:53 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 5 Jul 1998 18:27:53 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id NAA10291 for hackers@freebsd.org; Sun, 5 Jul 1998 13:26:00 -0500 Date: Sun, 5 Jul 1998 13:26:00 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807051826.NAA10291@bonkers.taronga.com> To: hackers@FreeBSD.ORG Subject: A really hoopy idea for variant symlinks. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stop me if you've heard this one. OK, the thing you need for variant symlinks is a per-process inherited namespace, like the environment, but one that's in the kernel so symlinks can get to it, unlike the environment. IK, let's say you built one and hung it off the process structure. How are you going to access it? Well, you could create a couple new system calls to browse the namespace, or... and here's the hoopy idea... you hang it off /proc/*/syms. As symlinks. So yours would be under /proc/curproc/syms. and if you had permission you could browse other processes you own and examine them under /proc/pid/syms. AND, because you're exposing them as symlinks, you don't have to change how symlinks work. Instead of going through .../${USER}/... you'd just set up a symlink in the proper place to /proc/curproc/syms/user. And instead of creating new system calls, you could examine the buggers using "ls". Or diddle them from scripts. Does that look like a workable low-impact almost-transparent way to do this that works really well with the way UNIX already works or what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 14:45:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13800 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 14:45:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts01-44.waterford.indigo.ie [194.125.139.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13787 for ; Sun, 5 Jul 1998 14:44:54 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA05129; Sun, 5 Jul 1998 22:39:50 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807052139.WAA05129@indigo.ie> Date: Sun, 5 Jul 1998 22:39:49 +0000 In-Reply-To: abaram "Re: FreeBSD port?" (Jul 3, 4:35pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: abaram , ggi-develop@eskimo.com Subject: Re: FreeBSD port? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 3, 4:35pm, abaram wrote: } Subject: Re: FreeBSD port? > > Ok, i am cc'ing this to freebsd-hackers, hope they know whats going on:) > Btw, stable died at the same spot today, and i rm -rf'd since last time.. > thanks! > -Alex > > > > > gmake[2]: Entering directory `/usr/home/abaram/degas/lib/libggi/display/X' > > > ld -L/usr/X11R6/lib -lX11 -lXt -lXext -x -Bshareable -o > > > /usr/home/abaram/degas/lib/libggi/display/dll/X.so visual.o mode.o > > > events.o color.o > > > ld: internal error: RRS relocs exceed allocation 82 Have you rebuilt ld from recent sources? I had a problem similar to this a couple of months back a fix for which was committed. Also, try compiling at a different optimisation level. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 14:46:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14028 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 14:46:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14009 for ; Sun, 5 Jul 1998 14:46:31 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id XAA08382; Sun, 5 Jul 1998 23:46:26 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id XAA23454; Sun, 5 Jul 1998 23:46:26 +0200 (MET DST) Date: Sun, 5 Jul 1998 23:46:26 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807052146.XAA23454@surf.IAE.nl> To: tlambert@primenet.com Subject: Re: adding to sysctl env. X-Newsgroups: list.freebsd.hackers In-Reply-To: <199807051913.MAA27026@usr08.primenet.com> References: <199807042215.AAA00277@hobby.digiware.nl> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807051913.MAA27026@usr08.primenet.com> you write: >> make a debug.switch for the vlink module. >> So I added: >> ---- >> /* >> * For the vlink module debugging >> */ >> static int vlinkxlatedebug = 0; >> SYSCTL_INT(_debug, OID_AUTO, vlinkxlate, CTLFLAG_RW, &vlinkxlatedebug, 0, >> ""); >> ---- >> expecting to see it apear in my sysctl -a output. >> >> But guess what: I didn't. :-{ > >You are using "options DEBUG", right? > >Also: you are staticaly linking this driver, not loading it as an LKM, >right? Problem was even simpler: sys/sysctl.h require to include sys/kernel.h Which I didn't, so I've started to donate a first attempt man page. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 15:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24052 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from msmith@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24045 for hackers@freebsd.org; Sun, 5 Jul 1998 13:33:03 -0700 (PDT) (envelope-from msmith) Date: Sun, 5 Jul 1998 13:33:03 -0700 (PDT) From: Michael Smith Message-Id: <199807052033.NAA24045@hub.freebsd.org> To: hackers@FreeBSD.ORG Subject: freebsd.org cluster outage Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The cluster was sick this morning for two reasons: - dg rebooted freefall, but it failed to go down correctly - /var on hub was full (for once, not due to oversize user mailboxes) Freefall is back up, and I'm hoping that with a little more space on hub in /var, the 200M+ of queued mail will drain. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 15:11:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24250 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24218 for ; Sun, 5 Jul 1998 13:33:42 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA26526; Sun, 5 Jul 1998 22:05:14 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id WAA06547; Sun, 5 Jul 1998 22:02:56 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807052002.WAA06547@semyam.dinoco.de> To: zhihuizhang Cc: hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Lock mechanism questions In-reply-to: Your message of "Sat, 04 Jul 1998 16:20:57 EDT." Date: Sun, 05 Jul 1998 22:02:55 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By the way, I know spin lock is not suitable for interrupt routines that > access the same data structures. Can anyone give me a reason for this? Isn't that because of the problems you have when a higher priority interrupt occurs while serving a lower priority interrupt and both want to access the data structures? Then the lower priority one would have to get at least to the place where it frees the lock to allow the higher priority one to continue. But how does it achieve this? The higher priority interrupt gets serviced first. Deadlock. The same for an interrupt and a normal kernel function which both try to access the same spin lock protected data structure. Then a similar situation arises. For processes it works as the waiting process eventually has to give up the CPU. Then the process holding the lock can work further toward releasing it. That's how I understand this problem with what I know as spin lock. I might be wrong of course. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 15:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24232 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 13:33:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24074; Sun, 5 Jul 1998 13:33:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from smap@localhost) by gatekeeper.whistle.com (8.7.5/8.6.12) id MAA21246; Sun, 5 Jul 1998 12:08:30 -0700 (PDT) Received: from alpo.whistle.com(alpo 207.76.204.38) by gatekeeper via smap (V2.0) id xma021244; Sun, 5 Jul 98 12:08:14 -0700 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21012; Sun, 5 Jul 1998 11:56:02 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021010; Sun Jul 5 18:55:53 1998 Date: Sun, 5 Jul 1998 11:55:50 -0700 (PDT) From: Julian Elischer To: Peter van Heusden cc: Stefan Esser , freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI drive not remapping bad block: Any solution (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 fistly, use rsd2 not rsd2c (if it's dange=ously dedicated..) or rsd2s1 if it has slices.. secondly many drives go read-only when they run out of replacement sectors.. I have one here (a Quantum) that has done this.. On Sun, 5 Jul 1998, Peter van Heusden wrote: > On Sat, 4 Jul 1998, Stefan Esser wrote: > > [snip] > > > In order to recover from that error, you may want to write new > > data to the replacement sector, and the easiest way to do this > > is to "dd if=/dev/zero of=/dev/rsd1c bs=64k" (assuming that the > > drive is "sd1" ...). > > Thanks, I tried this, but dd returned: > > dd: /dev/rsd2c: Read-only file system > > which I can't understand, because ls -l /dev/rsd2c gives: > > crw-r----- 1 root operator 13, 18 Jul 5 18:07 /dev/rsd2c > > Is there something I should do before I can write to this device? > > Thanks, > Peter > P.S. Is there anywhere I can find out more about SCSI so that I understand > this stuff better? > -- > Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa > pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! > > > 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 Sun Jul 5 15:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20796 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 15:20:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20744 for ; Sun, 5 Jul 1998 15:20:41 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA00623; Sun, 5 Jul 1998 17:24:55 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199807051826.NAA10291@bonkers.taronga.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 5 Jul 1998 17:13:47 -0500 To: peter@taronga.com (Peter da Silva) From: Richard Wackerbarth Subject: Re: A really hoopy idea for variant symlinks. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:26 PM -0500 7/5/98, Peter da Silva wrote: >So yours would be under /proc/curproc/syms. and if you had permission you >could browse other processes you own and examine them under /proc/pid/syms. > >AND, because you're exposing them as symlinks, you don't have to change >how symlinks work. > >Instead of going through .../${USER}/... you'd just set up a symlink in >the proper place to /proc/curproc/syms/user. > >And instead of creating new system calls, you could examine the buggers >using "ls". > >Or diddle them from scripts. As for the mechanism to interogate and set them, this proposal seems OK to me. However, to have appropriate value, we need to have A SINGLE VALUE (eg: osversion) that can be referenced from multiple places. Thus changing a single value would change a number of links at the same time. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 17:44:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27805 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 17:44:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27735 for ; Sun, 5 Jul 1998 17:44:15 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id RAA02211; Sun, 5 Jul 1998 17:44:10 -0700 (PDT) Message-ID: <19980705174409.A786@Alameda.net> Date: Sun, 5 Jul 1998 17:44:09 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: -stable startup problem Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I upgraded a 2.2.2R machine to 2.2.6-stable as of last night. Now I get a startup in the automatic fsck the following problem: cannot alloc 1966082 bytes for lnctp So I backed up everything and made newfs, restored everything and the same happens. I needed to disable the automatic fsck for now. Any ideas ? -- 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 Sun Jul 5 18:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05846 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 18:37:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05825 for ; Sun, 5 Jul 1998 18:36:54 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA07972; Sun, 5 Jul 1998 18:36:53 -0700 (PDT) Message-ID: <19980705183652.A597@Alameda.net> Date: Sun, 5 Jul 1998 18:36:52 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: Re: -stable startup problem Reply-To: ulf@Alameda.net References: <19980705174409.A786@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980705174409.A786@Alameda.net>; from Ulf Zimmermann on Sun, Jul 05, 1998 at 05:44:09PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 05, 1998 at 05:44:09PM -0700, Ulf Zimmermann wrote: > I upgraded a 2.2.2R machine to 2.2.6-stable as of last night. Now I get a > startup in the automatic fsck the following problem: > > cannot alloc 1966082 bytes for lnctp > > So I backed up everything and made newfs, restored everything and the same > happens. I needed to disable the automatic fsck for now. Any ideas ? Updated /etc/login.conf via a hint from Garyp, seems to work now. > > -- > 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 -- 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 Sun Jul 5 18:50:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07986 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 18:50:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA07921 for ; Sun, 5 Jul 1998 18:49:39 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 3015 invoked from network); 6 Jul 1998 01:48:53 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (206.109.2.48) by mushi.colo.neosoft.com with SMTP; 6 Jul 1998 01:48:53 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id UAA21768; Sun, 5 Jul 1998 20:18:14 -0500 Date: Sun, 5 Jul 1998 20:18:14 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807060118.UAA21768@bonkers.taronga.com> To: hackers@FreeBSD.ORG Newsgroups: taronga.freebsd.hackers Subject: Re: A really hoopy idea for variant symlinks. References: <199807051826.NAA10291@bonkers.taronga.com> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Richard Wackerbarth wrote: >As for the mechanism to interogate and set them, this proposal seems OK to me. >However, to have appropriate value, we need to have A SINGLE VALUE (eg: >osversion) >that can be referenced from multiple places. Thus changing a single value would >change a number of links at the same time. I see what you're getting at now. If you want to be able to change one variable and effect a bunch of links at once you need to be able to make subdirectories so you can get *out* of the /proc directory with variance intact. mkdir /proc/curproc/syms/2.2.6 ln -s /usr/arch/2.2.6/bin /proc/curproc/syms/2.2.6/bin ln -s /etc/arch/2.2.6/make.conf /proc/curproc/syms/2.2.6/make.conf ln -s 2.2.6 /proc/curproc/syms/osversion Then you'd use /proc/curproc/syms/osversion/bin ... I was thinking that you'd use multiple symlinks, but then it's more work to change, less work to set up. ln -s /usr/arch/2.2.6/bin /proc/curproc/syms/bin ln -s /usr/arch/2.2.6/make.conf /proc/curproc/syms/make.conf The other thing you could do is put the os-specific-bits tree outside of /proc, so you don't have to carry all that baggage around: ln -s /usr/arch/FreeBSD-2.2.6 /proc/curproc/syms/osversion Anyway, I do admit it's a little more cumbersome to set up an environment that's keyed off a single variable. But you can do it, and even get some benefit from a central configuration directory (/usr/arch/FreeBSD-2.2.6) where all that stuff is collected. In all of this, of course, you need to make damn sure that security-related software is aware of this mechanism (and any other variant symlink mechanism) and avoids letting people hijack privs by playing sillybuggers with it. -- This is The Reverend Peter da Silva's Boring Sig File - there are no references to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 19:05:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10943 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 19:05:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10921 for ; Sun, 5 Jul 1998 19:05:35 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt3-173.HiWAAY.net [208.147.146.173]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id VAA23582; Sun, 5 Jul 1998 21:05:27 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA12035; Sun, 5 Jul 1998 19:31:30 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807060031.TAA12035@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: permission confusion at mount points In-reply-to: Message from Stefan Eggers of "Sun, 05 Jul 1998 12:41:59 +0200." <199807051042.MAA05304@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 19:31:30 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Eggers writes: > First off: Thanks to the people who responded. I'll now sending in a > PR to get a small note into the BUGS section of mount(2) and mount(8) > to give others a chance to solve it a bit faster. A wise man once told me, "If its documented its not a bug, its a feature." :-) > > Use 755 permissions on your underlying mount point and put the problem > > out of your misery. > > That's how I solved it. It was just irritating. To avoid this sort > of problems bothering others I think the man pages should mention it. > See above. Am fairly sure 755 isn't the minimum permissions required. A little playing around suggests 111 (execute) is all thats needed. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 22:23:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04767 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 22:23:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04762 for ; Sun, 5 Jul 1998 22:23:27 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id OAA07737; Mon, 6 Jul 1998 14:53:10 +0930 (CST) Message-ID: <19980706145310.C6528@freebie.lemis.com> Date: Mon, 6 Jul 1998 14:53:10 +0930 From: Greg Lehey To: FreeBSD Hackers Subject: HEADS UP: Sleeping in strategy routines? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At USENIX I discussed the idea of calling block^H^H^H^H^H device strategy routines from the bottom half of a driver, and the general consensus was yes, you can do this. I've just had a panic which seems to point to other problems. Here's the trace: Program received signal SIGSEGV, Segmentation fault. tsleep (ident=0xf0278964, priority=0x10, wmesg=0xf01f7536 "bncwai", timo=0x0) at ../../kern/kern_synch.c:374 374 if (KTRPOINT(p, KTR_CSW)) (kgdb) bt #0 tsleep (ident=0xf0278964, priority=0x10, wmesg=0xf01f7536 "bncwai", timo=0x0) at ../../kern/kern_synch.c:374 #1 0xf01f75b3 in vm_bounce_page_find (count=0x1) at ../../i386/i386/vm_machdep.c:160 #2 0xf01f7be7 in vm_bounce_alloc (bp=0xf0783018) at ../../i386/i386/vm_machdep.c:397 #3 0xf01bae01 in sd_strategy (bp=0xf0783018, sc_link=0xf075dd80) at ../../scsi/sd.c:623 #4 0xf01b792c in scsi_strategy (bp=0xf0783018, device=0xf025333c) at ../../scsi/scsi_driver.c:220 #5 0xf01ba804 in sdstrategy (bp=0xf0783018) at ../../scsi/sd.c:173 #6 0xf01494de in spec_strategy (ap=0xf024ae2c) at ../../miscfs/specfs/spec_vnops.c:557 #7 0xf0148bc9 in spec_vnoperate (ap=0xf024ae2c) at ../../miscfs/specfs/spec_vnops.c:127 #8 0xf01cb6f1 in ufs_vnoperatespec (ap=0xf024ae2c) at ../../ufs/ufs/ufs_vnops.c:2282 #9 0xf430a04f in VOP_STRATEGY (bp=0xf0783018) at vnode_if.h:1100 #10 0xf4309fd8 in complete_raid5_write (rqe=0xf0783018) at raid5.c:767 #11 0xf4307ae0 in complete_rqe (bp=0xf0783160) at request.c:797 #12 0xf0137d52 in biodone (bp=0xf0783160) at ../../kern/vfs_bio.c:1912 #13 0xf01b6954 in scsi_done (xs=0xf07b9000) at ../../scsi/scsi_base.c:448 #14 0xf01f924b in aha_done (aha=0xf075f000, ccb=0xf075fa64) at ../../i386/isa/aha1542.c:945 #15 0xf01f8d39 in ahaintr (unit=0x0) at ../../i386/isa/aha1542.c:751 (kgdb) l 369 struct proc *p = curproc; 370 int s, sig, catch = priority & PCATCH; 371 struct callout_handle thandle; 372 373 #ifdef KTRACE 374 if (KTRPOINT(p, KTR_CSW)) 375 ktrcsw(p->p_tracep, 1, 0); 376 #endif 377 s = splhigh(); 378 if (cold || panicstr) { (kgdb) p p $1 = (struct proc *) 0x0 I can't make up my mind whose fault this is. If it's true that you should be able to call a strategy routine from the lower half, then vm_bounce_page_find shouldn't be tsleeping. But so far this is an assertion, even if it's shared by others. On the other hand, I've been working quite happily with this driver (well, I haven't run into problems like this :-) until I changed to a system with more than 16 MB of memory and didn't change the controller (AHA 1542, as the trace shows). This really boils down to a policy question: should strategy routines do anything that requires a process context? Do *you* have code which relies on being in a process context? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 22:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07674 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 22:52:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07668 for ; Sun, 5 Jul 1998 22:52:41 -0700 (PDT) (envelope-from g-nakai@internetsolutions.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.8.8+2.7Wbeta7/3.6W-astecMX2.3) with ESMTP id OAA29908 for ; Mon, 6 Jul 1998 14:52:36 +0900 (JST) Received: from apricot (isi05.astec.co.jp [172.20.12.205]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with SMTP id OAA05870 for ; Mon, 6 Jul 1998 14:52:35 +0900 (JST) Date: Mon, 6 Jul 1998 14:52:35 +0900 (JST) Message-Id: <199807060552.OAA05870@amont.astec.co.jp> From: =?ISO-2022-JP?B?GyRCQ2YwZhsoQg==?= =?ISO-2022-JP?B?GyRCOSxHbhsoQg==?= To: freebsd-hackers@FreeBSD.ORG Subject: Re: GNUstep 0.5.0 In-Reply-To: <9807031437.AA06969@ringworld.uniscape.com> References: <9807031437.AA06969@ringworld.uniscape.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone been able to get GNUstep (dgs-0.5.0) to work on FreeBSD. I > managed to compile the source code, but I can't seem to get the demos to use DGS. > > Is anyone working with GNUstep on FreeBSD? I'm not working on the whole of GNUstep but have made a port of DGS-0.5.0. --------------- Yukihiro Nakai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:21:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10756 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:21:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from marshotel.coapt.com (matt@marshotel.coapt.com [207.137.152.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10741 for ; Sun, 5 Jul 1998 23:21:11 -0700 (PDT) (envelope-from matt@marshotel.coapt.com) Received: (from matt@localhost) by marshotel.coapt.com (8.9.1/8.9.0) id XAA08246; Sun, 5 Jul 1998 23:21:04 -0700 (PDT) Message-ID: <19980705232103.07591@marshotel.coapt.com> Date: Sun, 5 Jul 1998 23:21:03 -0700 From: Matt Wilbur To: freebsd-hackers@FreeBSD.ORG Subject: problems with natd and -STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Just as a sanity check, I'd be curious to hear if anyone else is having problems with natd/IPDIVERT and -STABLE? I cvsup'd -STABLE last night, made world today, and have had little to no luck getting natd working again, or finding out what the problem is :-/ I've triple checked, all the config files have stayed the same.. I built my kernel using my old 2.2.6R config file (which had IPFIREWALL/IPDIVERT), am using the same natd.cf I cooked up a long time ago.. IP forwarding's on, my ipfw rules are same as they ever were.. ARGH.. tcpdump shows packets going to the gateway, and not carrying on :) verbose is pretty tight lipped.. Anyone else seeing this? Matt Wilbur EFS Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:31:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12441 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:31:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles137.castles.com [208.214.165.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12434 for ; Sun, 5 Jul 1998 23:31:10 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00406; Sun, 5 Jul 1998 12:01:28 -0700 (PDT) Message-Id: <199807051901.MAA00406@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Garance A Drosihn cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-reply-to: Your message of "Fri, 03 Jul 1998 01:40:56 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 12:01:28 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 9:16 PM -0700 7/2/98, Mike Smith wrote: > > Allowing links to indicate that they *should* be keyed off the > > environment space, OTOH, isn't such a sin. eg: > > > > ${sysctl:hw.arch} and ${env:USER} > > > > but this creates a new union space with yet another different > > syntax. > > > > ${space=sysctl, mib=hw.arch} and ${space=env, var=USER} > > > > perhaps? > > Hmm, not quite the strategy I was leaning towards, but I do feel > much less concerned with this than the earlier alternative. If > the creator of the link really *wants* the link to change based on > an environment value, then any headaches caused are their fault, > and not the implementation's fault. More to the point, the variant link should be allowed to key off more than just values in the environment space. > I must admit I don't understand your comment about a "new union > space", so I would lean toward a more terse syntax, such as your > first suggestion. Perhaps that just proves I should go home and > get some sleep... You need to look at the issue of parametric information from a very broad perspective. You can consider parametric information as an identifier and a value, and these parameters live in "parameter space", ie. the set of all parameters (this is basically the same as "tuple space"). At the moment, this space is segregated into lots of little separate spaces (eg. the parameters in /etc/rc.conf, DNS, /usr/local/etc/rc.d and so on). Each of these subspaces have different naming conventions, different access methods, etc. By allowing the variant symlink implementation to use parameters from more than one subspace, we create a new space which is the union of these separate subspaces. Because we now transcend the naming conventions for each of these subspaces, we need a new naming convention that provides the extra identification information. The danger in coming up with a new "just good enough" naming convention is that it's _yet_another_ naming convention that's incompatible with everything else. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13845 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:46:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13833 for ; Sun, 5 Jul 1998 23:46:56 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA17441; Sun, 5 Jul 1998 23:46:50 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd017404; Sun Jul 5 23:46:40 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id XAA21779; Sun, 5 Jul 1998 23:46:21 -0700 (MST) From: Terry Lambert Message-Id: <199807060646.XAA21779@usr02.primenet.com> Subject: Re: adding to sysctl env. To: wjw@digiware.nl Date: Mon, 6 Jul 1998 06:46:20 +0000 (GMT) Cc: mike@smith.net.au, terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <199807052039.UAA10241@digi.digiware.nl> from "Willem Jan Withagen" at Jul 5, 98 10:39:30 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If an include file requires another include file. > eg. sys/sysctl.h requires sys/kernel.h > > Does the include for kernel.h go into sysctl.h? No. If it compiles without it, it's not "required". In general, this is so you can put things that are in the kernel.h namespace (like your own functions with the same name) and still include sysctl.h. Admittedly, the dependency you describe seems like an organizational bug. At the very least, it should have #warn'ed you. > Reason I ask, is that there were no errors when I compiled without > the inclusion, but that was the problem I could not see the > debug.vlinkxlate in sysctl. :-( You need to look into why there were no errors. At a minimum, there should have been a linktime error, if a macro was confused as an external function reference. The man page is useful, but the inclusion of the kernel.h was probably for some other prototype, not the sysctl prototype, IMO. You need to narrow down your problem to make sure you aren't documenting an #include that is necessary for your implementation, and not for sysctl's in general. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:52:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14624 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:52:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14611 for ; Sun, 5 Jul 1998 23:52:28 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA15425; Sun, 5 Jul 1998 23:52:27 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd015402; Sun Jul 5 23:52:20 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id XAA22028; Sun, 5 Jul 1998 23:52:18 -0700 (MST) From: Terry Lambert Message-Id: <199807060652.XAA22028@usr02.primenet.com> Subject: Re: A really hoopy idea for variant symlinks. To: rkw@dataplex.net (Richard Wackerbarth) Date: Mon, 6 Jul 1998 06:52:18 +0000 (GMT) Cc: peter@taronga.com, hackers@FreeBSD.ORG In-Reply-To: from "Richard Wackerbarth" at Jul 5, 98 05:13:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As for the mechanism to interogate and set them, this proposal seems OK to me. > However, to have appropriate value, we need to have A SINGLE VALUE (eg: > osversion) > that can be referenced from multiple places. Thus changing a single value > would change a number of links at the same time. It's a bit "plan9"-ish, depending on kernel enforcement of parsing semantics; I'd try to avoid that... The point about referential commutation is a good one. There are currently too many places values are duplicated. One that comes to mind is that IP addresses are both stored in a database, and stored as a transient attribute of a physical interface. Another example that doesn't exist too many places in FreeBSD is the storage of the machine name in multiple places (OK, it exists in the "port" and "packages", like "CAP" and "Samba" and "Apache" and ...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15176 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:55:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15152 for ; Sun, 5 Jul 1998 23:54:55 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id CAA14221; Mon, 6 Jul 1998 02:54:50 -0400 (EDT) Date: Mon, 6 Jul 1998 02:54:50 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: <199807051821.LAA18346@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We did a remote reboot of freefall, but unfortunately it did not make > it back up again. It responds to pings but none of the daemons have > started, including sshd. The operative hypothesis is that it is hung > up waiting on an NFS mount from a machine that's down. If anyone who maintains these machines is interested, I have a gigantic box of modems if that would help in the future. Ever since I started putting remote console access on all of our machines, I sleep better ;) Let me know if freefall and friends could use a modem, and give me an address to ship to. They aren't the best, but they work. Let me know if there's interest... Thanks, Charles > > It is a holiday weekend here in the US, and we haven't been able to > find anybody physically near to the machines who could go in and get > things running again. So we are without freefall at least for a > while. > > Maybe this would be a good day to get a life and try doing something > else for a change. :-) > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 5 23:58:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15825 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 23:58:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15812 for ; Sun, 5 Jul 1998 23:58:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA04524; Sun, 5 Jul 1998 23:53:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd004519; Mon Jul 6 06:53:52 1998 Date: Sun, 5 Jul 1998 23:53:46 -0700 (PDT) From: Julian Elischer To: Greg Lehey cc: FreeBSD Hackers Subject: Re: HEADS UP: Sleeping in strategy routines? In-Reply-To: <19980706145310.C6528@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998, Greg Lehey wrote: > At USENIX I discussed the idea of calling block^H^H^H^H^H device > strategy routines from the bottom half of a driver, and the general > consensus was yes, you can do this. I've just had a panic which seems > to point to other problems. Here's the trace: > > Program received signal SIGSEGV, Segmentation fault. > tsleep (ident=0xf0278964, priority=0x10, wmesg=0xf01f7536 "bncwai", timo=0x0) at ../../kern/kern_synch.c:374 > 374 if (KTRPOINT(p, KTR_CSW)) > (kgdb) bt > #0 tsleep (ident=0xf0278964, priority=0x10, wmesg=0xf01f7536 "bncwai", timo=0x0) at ../../kern/kern_synch.c:374 > #1 0xf01f75b3 in vm_bounce_page_find (count=0x1) at ../../i386/i386/vm_machdep.c:160 > #2 0xf01f7be7 in vm_bounce_alloc (bp=0xf0783018) at ../../i386/i386/vm_machdep.c:397 > #3 0xf01bae01 in sd_strategy (bp=0xf0783018, sc_link=0xf075dd80) at ../../scsi/sd.c:623 > #4 0xf01b792c in scsi_strategy (bp=0xf0783018, device=0xf025333c) at ../../scsi/scsi_driver.c:220 > #5 0xf01ba804 in sdstrategy (bp=0xf0783018) at ../../scsi/sd.c:173 > #6 0xf01494de in spec_strategy (ap=0xf024ae2c) at ../../miscfs/specfs/spec_vnops.c:557 > #7 0xf0148bc9 in spec_vnoperate (ap=0xf024ae2c) at ../../miscfs/specfs/spec_vnops.c:127 > #8 0xf01cb6f1 in ufs_vnoperatespec (ap=0xf024ae2c) at ../../ufs/ufs/ufs_vnops.c:2282 > #9 0xf430a04f in VOP_STRATEGY (bp=0xf0783018) at vnode_if.h:1100 I don't think you asked me, or I wasn't thinking.. you can't call strategy from interupt level... (e.g. biodone()) but you seem to have noticed this :-) strategy is a top level routine, called directly from read->physio->strategy. there are other things you can do of course, but they really depend on having everything preallocated. > #10 0xf4309fd8 in complete_raid5_write (rqe=0xf0783018) at raid5.c:767 > #11 0xf4307ae0 in complete_rqe (bp=0xf0783160) at request.c:797 > #12 0xf0137d52 in biodone (bp=0xf0783160) at ../../kern/vfs_bio.c:1912 > #13 0xf01b6954 in scsi_done (xs=0xf07b9000) at ../../scsi/scsi_base.c:448 > #14 0xf01f924b in aha_done (aha=0xf075f000, ccb=0xf075fa64) at ../../i386/isa/aha1542.c:945 > #15 0xf01f8d39 in ahaintr (unit=0x0) at ../../i386/isa/aha1542.c:751 > (kgdb) l > 369 struct proc *p = curproc; > 370 int s, sig, catch = priority & PCATCH; > 371 struct callout_handle thandle; > 372 > 373 #ifdef KTRACE > 374 if (KTRPOINT(p, KTR_CSW)) > 375 ktrcsw(p->p_tracep, 1, 0); > 376 #endif > 377 s = splhigh(); > 378 if (cold || panicstr) { > (kgdb) p p > $1 = (struct proc *) 0x0 > > I can't make up my mind whose fault this is. If it's true that you > should be able to call a strategy routine from the lower half, then > vm_bounce_page_find shouldn't be tsleeping. I wouldn't expect to call strategy from that level. > But so far this is an > assertion, even if it's shared by others. On the other hand, I've > been working quite happily with this driver (well, I haven't run into > problems like this :-) until I changed to a system with more than 16 > MB of memory and didn't change the controller (AHA 1542, as the trace > shows). yes, but strategy is suppoosed to allocate resources needed for a transfer. It is conceivable that to do so may require sleeping. I personally would expect this. Maybe I'm in the minority. From my perspective the whole reason for having strategy and start separated in the way they are is to divide top/bottom operation. > > This really boils down to a policy question: should strategy routines > do anything that requires a process context? Do *you* have code which > relies on being in a process context? strategy expects to be called and to return to the caller, having done all that is needed to queue the work. This may require waiting on a structure to become 'unbusy' (for example). In practice it is nearly always possible to avoid sleeping in there, but I think making it 'illegal' would limit the flexibility for other users. On the other hand, it is possible that some people feel that strategy shouldn't sleep and that this is the reason that physio() sleeps rather than letting the strategy to do so. > > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 00:18:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19637 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 00:18:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19593 for ; Mon, 6 Jul 1998 00:18:25 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA04963; Mon, 6 Jul 1998 00:16:11 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd004949; Mon Jul 6 07:16:05 1998 Date: Mon, 6 Jul 1998 00:16:00 -0700 (PDT) From: Julian Elischer To: Matt Wilbur cc: freebsd-hackers@FreeBSD.ORG Subject: Re: problems with natd and -STABLE In-Reply-To: <19980705232103.07591@marshotel.coapt.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'm willing to bet that if you back out the contents of netinet to 6 days ago it will be fixed.. I'm investigating now. On Sun, 5 Jul 1998, Matt Wilbur wrote: > Hello, > > Just as a sanity check, I'd be curious to hear if anyone else is having > problems with natd/IPDIVERT and -STABLE? I cvsup'd -STABLE last night, > made world today, and have had little to no luck getting natd working again, > or finding out what the problem is :-/ > > I've triple checked, all the config files have stayed the same.. I built my > kernel using my old 2.2.6R config file (which had IPFIREWALL/IPDIVERT), > am using the same natd.cf I cooked up a long time ago.. IP forwarding's on, > my ipfw rules are same as they ever were.. ARGH.. > > tcpdump shows packets going to the gateway, and not carrying on :) > > verbose is pretty tight lipped.. > > Anyone else seeing this? > > Matt Wilbur > EFS Systems > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 00:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23761 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 00:46:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23755 for ; Mon, 6 Jul 1998 00:46:11 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id JAA22203 for ; Mon, 6 Jul 1998 09:49:51 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 6 Jul 1998 09:49:51 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-hackers@FreeBSD.ORG Subject: PCMCIA disk cards 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, Do we support them? I couldn't find any refrence to the cards other than ethernet/modem... Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 01:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25603 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 01:02:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25517 for ; Mon, 6 Jul 1998 01:01:35 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id KAA13430; Mon, 6 Jul 1998 10:01:19 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id KAA16227; Mon, 6 Jul 1998 10:01:18 +0200 (MET DST) Date: Mon, 6 Jul 1998 10:01:18 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807060801.KAA16227@surf.IAE.nl> To: rkw@dataplex.net Subject: Re: A really hoopy idea for variant symlinks. X-Newsgroups: list.freebsd.hackers In-Reply-To: References: <199807051826.NAA10291@bonkers.taronga.com> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >At 1:26 PM -0500 7/5/98, Peter da Silva wrote: >>So yours would be under /proc/curproc/syms. and if you had permission you >>could browse other processes you own and examine them under /proc/pid/syms. >> >>AND, because you're exposing them as symlinks, you don't have to change >>how symlinks work. >> >>Instead of going through .../${USER}/... you'd just set up a symlink in >>the proper place to /proc/curproc/syms/user. >> >>And instead of creating new system calls, you could examine the buggers >>using "ls". >> >>Or diddle them from scripts. > >As for the mechanism to interogate and set them, this proposal seems OK to me. >However, to have appropriate value, we need to have A SINGLE VALUE (eg: >osversion) >that can be referenced from multiple places. Thus changing a single value would >change a number of links at the same time. Also, an hierarchy in the name-space will be much more difficult. Your favorite link will be either in /proc/pid/syms, or not..... In which case access will just fail. And then we'de have to start doing special things anyway, next to the thing that I'm not so into /proc-items But then as it goes with code here, I you like it this way... feel free --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 01:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25973 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 01:05:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25962 for ; Mon, 6 Jul 1998 01:05:20 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id KAA14305; Mon, 6 Jul 1998 10:05:18 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id KAA16680; Mon, 6 Jul 1998 10:05:17 +0200 (MET DST) Date: Mon, 6 Jul 1998 10:05:17 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807060805.KAA16680@surf.IAE.nl> To: ulf@Alameda.net Subject: Re: -stable startup problem X-Newsgroups: list.freebsd.hackers In-Reply-To: <19980705183652.A597@Alameda.net> References: <19980705174409.A786@Alameda.net> Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980705183652.A597@Alameda.net> you write: >On Sun, Jul 05, 1998 at 05:44:09PM -0700, Ulf Zimmermann wrote: >> I upgraded a 2.2.2R machine to 2.2.6-stable as of last night. Now I get a >> startup in the automatic fsck the following problem: >> >> cannot alloc 1966082 bytes for lnctp >> >> So I backed up everything and made newfs, restored everything and the same >> happens. I needed to disable the automatic fsck for now. Any ideas ? > >Updated /etc/login.conf via a hint from Garyp, seems to work now. Could you share the hint. I've got the same problem, But then went into single mode, were everything was dandy. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 01:06:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26178 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 01:06:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26109 for ; Mon, 6 Jul 1998 01:06:04 -0700 (PDT) (envelope-from smoergrd@geos01.oslo.geco-prakla.slb.com) Received: from sunw132.geco-prakla.slb.com (sunw132 [134.32.45.120]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA10353 ; Mon, 6 Jul 1998 10:05:28 +0200 (MET DST) Received: by sunw132.geco-prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA02107; Mon, 6 Jul 1998 10:05:28 +0200 To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? References: <199807051821.LAA18346@austin.polstra.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 06 Jul 1998 10:05:27 +0200 In-Reply-To: John Polstra's message of Sun, 05 Jul 1998 11:21:12 -0700 Message-ID: Lines: 9 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > Maybe this would be a good day to get a life and try doing something > else for a change. :-) Eh? A life? Spooky... DES (geek to the bone) -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 01:14:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27562 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 01:14:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27495 for ; Mon, 6 Jul 1998 01:14:15 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id BAA21197; Mon, 6 Jul 1998 01:14:11 -0700 (PDT) Message-ID: <19980706011410.B13625@Alameda.net> Date: Mon, 6 Jul 1998 01:14:10 -0700 From: Ulf Zimmermann To: Willem Jan Withagen Cc: hackers@FreeBSD.ORG Subject: Re: -stable startup problem Reply-To: ulf@Alameda.net References: <19980705174409.A786@Alameda.net> <19980705183652.A597@Alameda.net> <199807060805.KAA16680@surf.IAE.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807060805.KAA16680@surf.IAE.nl>; from Willem Jan Withagen on Mon, Jul 06, 1998 at 10:05:17AM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 10:05:17AM +0200, Willem Jan Withagen wrote: > In article <19980705183652.A597@Alameda.net> you write: > >On Sun, Jul 05, 1998 at 05:44:09PM -0700, Ulf Zimmermann wrote: > >> I upgraded a 2.2.2R machine to 2.2.6-stable as of last night. Now I get a > >> startup in the automatic fsck the following problem: > >> > >> cannot alloc 1966082 bytes for lnctp > >> > >> So I backed up everything and made newfs, restored everything and the same > >> happens. I needed to disable the automatic fsck for now. Any ideas ? > > > >Updated /etc/login.conf via a hint from Garyp, seems to work now. > > Could you share the hint. > I've got the same problem, But then went into single mode, were everything > was dandy. I upgraded from 2.2.2-RELEASE via make world to 2.2.6-stable. I merged most of the files from 2.2.6's /etc, but must have forgot login.conf, which seemed to restrict the resources too much. > > --WjW > > -- > Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 > P.O. 928, 5600 AX Eindhoven, The Netherlands > Full Internet connectivity for only fl 12.95 a month. > Call now, and login as 'new'. -- 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 Mon Jul 6 03:33:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16518 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 03:33:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16513 for ; Mon, 6 Jul 1998 03:33:44 -0700 (PDT) (envelope-from smoergrd@geos01.oslo.geco-prakla.slb.com) Received: from sunw132.geco-prakla.slb.com (sunw132 [134.32.45.120]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA19327 ; Mon, 6 Jul 1998 12:32:49 +0200 (MET DST) Received: by sunw132.geco-prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA02290; Mon, 6 Jul 1998 12:32:48 +0200 To: Willem Jan Withagen Cc: ulf@alameda.net, hackers@FreeBSD.ORG Subject: Re: -stable startup problem References: <19980705174409.A786@Alameda.net> <199807060805.KAA16680@surf.IAE.nl> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 06 Jul 1998 12:32:48 +0200 In-Reply-To: Willem Jan Withagen's message of Mon, 6 Jul 1998 10:05:17 +0200 (MET DST) Message-ID: Lines: 64 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Willem Jan Withagen writes: > In article <19980705183652.A597@Alameda.net> you write: > >On Sun, Jul 05, 1998 at 05:44:09PM -0700, Ulf Zimmermann wrote: > > > cannot alloc 1966082 bytes for lnctp > > Updated /etc/login.conf via a hint from Garyp, seems to work now. > Could you share the hint. Quite simply, fsck runs in login class daemon (IIRC) which has quite strict memory limits - too strict to fsck a large file system. This was fixed before 2.2.5 shipped, so if you are seeing this on -stable, you have forgotten to update your /etc after make world. RCS file: /c/ncvs/src/etc/login.conf,v Working file: login.conf head: 1.20 branch: locks: strict access list: symbolic names: RELENG_2_2_6_RELEASE: 1.9.2.7 RELENG_2_2_5_RELEASE: 1.9.2.3 RELENG_2_2_2_RELEASE: 1.9 RELENG_2_2: 1.9.0.2 keyword substitution: kv total revisions: 27; selected revisions: 27 description: ---------------------------- [...] ---------------------------- revision 1.14 date: 1997/09/23 03:09:51; author: peter; state: Exp; lines: +4 -2 Raise some of the 'daemon' class limits as used by things started from /etc/rc, including inetd and it's children, stuff from /usr/local/etc/rc.d (eg: squid, apache). The default limits are causing a lot of problems including things like fsck failing on large disks. I hope I've understood the quirks of the override mechanism properly. ---------------------------- revision 1.13 date: 1997/07/11 22:11:13; author: guido; state: Exp; lines: +2 -2 Fix typo ---------------------------- revision 1.12 date: 1997/05/23 12:46:52; author: ache; state: Exp; lines: +6 -6 Fix "daemon" class, Apache not works from /etc/rc otherwise. Among bumping several limits, most interesting thing is that Apache requires than "filesize=64M" restriction must be removed. I think it is due to mmap() usage in apache, but I am not shure. ---------------------------- [...] ---------------------------- revision 1.9.2.4 date: 1997/10/25 11:39:21; author: peter; state: Exp; lines: +8 -5 Merge in login.conf relaxations from -current, including a typo fix. ---------------------------- revision 1.9.2.3 date: 1997/05/23 12:59:16; author: ache; state: Exp; lines: +6 -6 Merge "daemon" class limits bumping from -current ---------------------------- [...] DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 04:24:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23710 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 04:24:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA23699 for ; Mon, 6 Jul 1998 04:24:24 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 4572 invoked by uid 1001); 6 Jul 1998 11:24:19 +0000 (GMT) To: smoergrd@oslo.geco-prakla.slb.com Cc: hackers@FreeBSD.ORG Subject: Re: -stable startup problem In-Reply-To: Your message of "06 Jul 1998 12:32:48 +0200" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 06 Jul 1998 13:24:19 +0200 Message-ID: <4570.899724259@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Quite simply, fsck runs in login class daemon (IIRC) which has quite > strict memory limits - too strict to fsck a large file system. This > was fixed before 2.2.5 shipped, so if you are seeing this on -stable, > you have forgotten to update your /etc after make world. A general problem I have with the login.conf mechanism is that it's often difficult to see exactly *where* (which entry) the limits are taken from, and what are the consequences of changing the limits. For instance, I recently ran into trouble with ssh logins. Found that I could login just fine if the ssh binary was *not* setuid - but with the default (setuid root) installation, I bumped into the limit on the number of processes. I was able to find the relevant login.conf entry and change it, but: - It took some experimentation to find the correct entry (the "default" entry, in this case). - Now that I've changed it, I'm not at all sure what *other* parts of the system are going to be affected. - It's not obvious to me that different behavior for suid and non-suid programs is logical. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 04:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26640 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 04:54:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA26633 for ; Mon, 6 Jul 1998 04:54:28 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 3815 invoked from network); 6 Jul 1998 11:54:09 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 6 Jul 1998 11:54:09 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA17254; Mon, 6 Jul 1998 06:48:44 -0500 Date: Mon, 6 Jul 1998 06:48:44 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807061148.GAA17254@bonkers.taronga.com> To: hackers@FreeBSD.ORG Newsgroups: taronga.freebsd.hackers Subject: Re: A really hoopy idea for variant symlinks. References: <199807060652.XAA22028@usr02.primenet.com> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807060652.XAA22028@usr02.primenet.com>, Terry Lambert wrote: >It's a bit "plan9"-ish, depending on kernel enforcement of parsing >semantics; I'd try to avoid that... Mind elaborating on that? -- This is The Reverend Peter da Silva's Boring Sig File - there are no references to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 05:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28588 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 05:04:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28577 for ; Mon, 6 Jul 1998 05:04:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA24533; Mon, 6 Jul 1998 05:04:02 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: spork cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-reply-to: Your message of "Mon, 06 Jul 1998 02:54:50 EDT." Date: Mon, 06 Jul 1998 05:04:02 -0700 Message-ID: <24529.899726642@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If anyone who maintains these machines is interested, I have a gigantic > box of modems if that would help in the future. Ever since I started > putting remote console access on all of our machines, I sleep better ;) Well, I'm a bit short of phone lines in there so what I'd *really* like would be a single modem and an old Cisco cs500 that nobody's using (or a multiport comms card) so that I can make a console server to handle all our equipment. ;-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:01:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04658 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:01:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA04648 for ; Mon, 6 Jul 1998 06:01:31 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA25979; Mon, 6 Jul 1998 09:00:46 -0400 Date: Mon, 6 Jul 1998 09:00:45 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-Reply-To: <199807030000.RAA14014@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Certainly it is an attractive idea to base symlinks on environment > > variables, but maybe we should ask ourselves how hard it would be > > to implement a "nice clean private namespace somewhere". I think You want the code anyone? ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05454 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:06:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gw.mark-itt.ru (gw.MARK-ITT.ru [193.124.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05339; Mon, 6 Jul 1998 06:06:00 -0700 (PDT) (envelope-from volodya@ieeu.udm.ru) Received: from ieeu.udm.ru (IEEU.udm.ru [193.125.187.169]) by gw.mark-itt.ru (8.8.8/MARK-ITT) with ESMTP id SAA23463 ;Mon, 6 Jul 1998 18:08:19 +0500 (KSD) Received: from ieeu-nt by ieeu.udm.ru with SMTP id SAA18660; (8.8.7/vak/1.9) Mon, 6 Jul 1998 18:05:15 +0500 (SAMST) From: "Vladimir Shirokov" To: Cc: Subject: Need help with printer accounting Date: Sun, 19 Jul 1998 18:07:32 +0400 Message-ID: <01bdb31e$9298a530$050aa8c0@ieeu-nt.ieeu.udm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I use 3.0-SNAP of FreeBSD (for information) and have a little question: how I can start acoounting for my print server. I must count a number of pages, printed from network (samba server) from Microsoft word text editor for any user. I have /var/accounting directory, but all files are zero length. My /etc/printcap looks: lp|local line printer:\ :pc=500:af=/var/log/printlog:mx#0:sf:sh:rg=print :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: May be I must use filter, but I don't know how to do it. Command "pac -Plp" shows: > pac alex Login pages/feet runs price alex 0.00 0 $ 0.00 I will be very happy if anyone can help me with this problem. Regards, V. Shirokov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06490 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:14:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA06475 for ; Mon, 6 Jul 1998 06:14:02 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Mon Jul 6 08:14 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id IAA18927 for ; Mon, 6 Jul 1998 08:13:51 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9H2K9>; Mon, 6 Jul 1998 09:20:23 -0400 Message-ID: To: abial@nask.pl, freebsd-hackers@FreeBSD.ORG Subject: RE: PCMCIA disk cards Date: Mon, 6 Jul 1998 09:20:22 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Andrzej Bialecki [SMTP:abial@nask.pl] > > Do we support them? I couldn't find any refrence to the cards other > than > ethernet/modem... > Are not they just simulating standard IDE disks ? -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:19:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07171 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:19:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA07166 for ; Mon, 6 Jul 1998 06:19:16 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA26113; Mon, 6 Jul 1998 09:17:30 -0400 Date: Mon, 6 Jul 1998 09:17:29 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Peter da Silva cc: hackers@FreeBSD.ORG Subject: Re: A really hoopy idea for variant symlinks. In-Reply-To: <199807051826.NAA10291@bonkers.taronga.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 Sun, 5 Jul 1998, Peter da Silva wrote: > Stop me if you've heard this one. Heard it. Did something mostly like it. > OK, the thing you need for variant symlinks is a per-process inherited > namespace, like the environment, but one that's in the kernel so symlinks > can get to it, unlike the environment. Done that on Linux. Hoping to finish it up on freebsd this summer. Could use help. > IK, let's say you built one and hung it off the process structure. How > are you going to access it? Well, you could create a couple new system > calls to browse the namespace, or... and here's the hoopy idea... you > hang it off /proc/*/syms. As symlinks. Mine did not need to hang off the process structure. In fact it works as an LKM on linux. No hacking of any kernel structs. But it's still a private name space ... > So yours would be under /proc/curproc/syms. and if you had permission you > could browse other processes you own and examine them under /proc/pid/syms. Yep, I support that too. > AND, because you're exposing them as symlinks, you don't have to change > how symlinks work. Yep. > Instead of going through .../${USER}/... you'd just set up a symlink in > the proper place to /proc/curproc/syms/user. Yep. As I said, private name spaces are what you want. I agree with you! So, if anyone wants to help ... ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08527 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:29:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08491 for ; Mon, 6 Jul 1998 06:29:03 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id JAA28539; Mon, 6 Jul 1998 09:28:31 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id KAA12641; Mon, 6 Jul 1998 10:02:39 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id JAA26291; Mon, 6 Jul 1998 09:32:48 -0400 (EDT) Date: Mon, 6 Jul 1998 09:32:48 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807061332.JAA26291@lakes.dignus.com> To: mike@smith.net.au, rivers@dignus.com Subject: Re: Variant Link implementation, continued Cc: drosih@rpi.edu, hackers@FreeBSD.ORG, wjw@surf.IAE.nl In-Reply-To: <199807040226.TAA07461@antipodes.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > Then I'll be thinking about haveing 2 rules of resolution: > > > @{....} > > > and ${....} > > > > > > > I don't mean to badger... but what if you, in an existing installation, > > already have symlinks that contain that text? Won't adding this > > facility break those existing links? > > > > [And, don't laugh, but I do have links and files that begin with '$', > > and, even worse, have '$' embedded in the middle of them...] > > In the existing sample implementation, you would have to have links > whose names comply explicitly with the syntax ...${}... where > is a valid tag in the variant link namespace. > > I think that this is sufficiently unlikely given that there have been > only two respondents that actually use '$' in names at all... > Seems reasonable... [and, nope, I don't have file names like that, fortunately :-)]. However, can someone with the POSIX spec in-hand speak to the POSIX ramifications here? I mean, if we essentially "steal" this space, does it break any (future) POSIX conformance? - Just curious - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 06:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09834 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 06:40:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09783 for ; Mon, 6 Jul 1998 06:40:06 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id PAA02750; Mon, 6 Jul 1998 15:43:38 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 6 Jul 1998 15:43:38 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Babkin, Serge" cc: freebsd-hackers@FreeBSD.ORG Subject: RE: PCMCIA disk cards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998, Babkin, Serge wrote: > > -----Original Message----- > > From: Andrzej Bialecki [SMTP:abial@nask.pl] > > > > Do we support them? I couldn't find any refrence to the cards other > > than > > ethernet/modem... > > > Are not they just simulating standard IDE disks ? Probably. But what with inserting and removing them... I guess removing such a drive can panick your system. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 07:22:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16535 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 07:22:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16526 for ; Mon, 6 Jul 1998 07:22:25 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA12932 for ; Mon, 6 Jul 1998 07:22:01 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id QAA04520 for freebsd-hackers@freefall.cdrom.com; Mon, 6 Jul 1998 16:22:08 +0200 (MEST) (envelope-from kuku) Date: Mon, 6 Jul 1998 16:22:08 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807061422.QAA04520@gilberto.physik.RWTH-Aachen.DE> To: freebsd-hackers@freefall.cdrom.com Subject: mit-pthreads and gethostbyname Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Were there any changes in pthreads recently that makes 2.2.6-STABLE behave differently (correct) over 2.2.5 R or 2.2.6R? I have a strange problem with resolution of localhost (gethostbyname) when using mit-pthreads where localhost cannot be resolved by gethostbyname when search order is host->bind in /etc/host.conf and /etc/resolv.conf is present. -- 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 Mon Jul 6 07:25:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16986 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 07:25:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16971 for ; Mon, 6 Jul 1998 07:25:25 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id KAA27662; Mon, 6 Jul 1998 10:25:10 -0400 (EDT) Date: Mon, 6 Jul 1998 10:25:10 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Jordan K. Hubbard" cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: <24529.899726642@time.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 Mon, 6 Jul 1998, Jordan K. Hubbard wrote: > Well, I'm a bit short of phone lines in there so what I'd *really* > like would be a single modem and an old Cisco cs500 that nobody's > using (or a multiport comms card) so that I can make a console server > to handle all our equipment. ;-) Still, if you want a few modems, let me know. I've got tons... I'm sure you can find a good use for five or six, right? I'll cover shipping. Charles > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 07:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19901 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 07:40:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA19883 for ; Mon, 6 Jul 1998 07:40:36 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA26626; Mon, 6 Jul 1998 10:40:05 -0400 Date: Mon, 6 Jul 1998 10:40:04 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: .palign 2 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 tried -questions but no dice. So here I am: On the latest tree, at some point in the gnu side, I get an error due to an op in read.S, .palign 2 Any ideas? It appears to be hidden in one of the gnu standard Macros From Hell, since read.S itself is just two lines, an include and a macro invocation. (and no, macros from hell is not an insult. I've got macros i've done viz: #define MACRO_FROM_HELL ... :-) so I'm not complaining. thanks ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 08:54:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28945 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 08:54:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28925 for ; Mon, 6 Jul 1998 08:53:50 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03480; Mon, 6 Jul 1998 08:53:37 -0700 (PDT) Message-Id: <199807061553.IAA03480@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: spork , John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-reply-to: Your message of "Mon, 06 Jul 1998 05:04:02 PDT." <24529.899726642@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 08:53:36 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If anyone who maintains these machines is interested, I have a gigantic > > box of modems if that would help in the future. Ever since I started > > putting remote console access on all of our machines, I sleep better ;) > > Well, I'm a bit short of phone lines in there so what I'd *really* > like would be a single modem and an old Cisco cs500 that nobody's > using (or a multiport comms card) so that I can make a console server > to handle all our equipment. ;-) We have the CS500, actually. What we need is a more current set of ROMs for it, and someone that knows how to configure the stupid thing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 08:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29613 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 08:57:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29584 for ; Mon, 6 Jul 1998 08:57:17 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id LAA27062; Mon, 6 Jul 1998 11:56:40 -0400 Date: Mon, 6 Jul 1998 11:56:40 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: p2align Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it's in contrib/gcc/config/i386/freebsd.h if that rings any bells. There appears to be no such op in gas? This is a cvsup of freebsd-current. ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 08:59:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00274 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 08:59:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00227 for ; Mon, 6 Jul 1998 08:59:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03530; Mon, 6 Jul 1998 08:59:50 -0700 (PDT) Message-Id: <199807061559.IAA03530@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: "Babkin, Serge" , freebsd-hackers@FreeBSD.ORG Subject: Re: PCMCIA disk cards In-reply-to: Your message of "Mon, 06 Jul 1998 15:43:38 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 08:59:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 6 Jul 1998, Babkin, Serge wrote: > > > > -----Original Message----- > > > From: Andrzej Bialecki [SMTP:abial@nask.pl] > > > > > > Do we support them? I couldn't find any refrence to the cards other > > > than > > > ethernet/modem... > > > > > Are not they just simulating standard IDE disks ? > > Probably. But what with inserting and removing them... I guess removing > such a drive can panick your system. Yes. PCMCIA sucks. There are actually a couple of different ways of talking to PCCARD memory devices. The PAO people have driver support for some PCCARD ATA and CompactFlash devices. You should talk to Hosakawa-san (hosakawa@freebsd.org) and ask him why he hasn't committed these bits (he said he was going to quite a while back now...) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 09:55:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09207 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 09:55:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09202 for ; Mon, 6 Jul 1998 09:55:50 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA17539 for ; Mon, 6 Jul 1998 09:55:33 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id LAA27539; Mon, 6 Jul 1998 11:55:27 -0500 (CDT) Date: Mon, 6 Jul 1998 11:55:27 -0500 (CDT) From: Mark Tinguely Message-Id: <199807061655.LAA27539@plains.NoDak.edu> To: freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: mit-pthreads and gethostbyname Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a strange problem with resolution of localhost (gethostbyname) > when using mit-pthreads where localhost cannot be resolved by > gethostbyname when search order is host->bind in /etc/host.conf > and /etc/resolv.conf is present. using libc_r (which uses the libc gethostby* routines), the host.conf file is used. But using MIT threads like you mentioned, they implement their own gethostby* routines. I think there is a more generic problem MIT pthreads does not consult the /etc/hosts file. I test program that runs on a machine in an isolated network: joy (nameserver) / \ rest of net isolated network the isolated network have /etc/hosts and does a host, bind search order. If i run a program that uses gethostbyname from libc, the correct IP number is returned for joy (the hidden network IP taken from /etc/hosts). test 2, if I resolve a name that has multiple DNS entries, the libc version returns them all. If i run a program that uses gethostbyname from MIT pthreads, the DNS derived IP number is returned for joy. for test 2, only the first IP number of a host that resolves to multiple addresses is returned. check the command, "nslookup localhost", by guess is that it does not have an entry and that is why the MIT pthreads gethostbyname call does not not return a value. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 10:12:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11291 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:12:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11280 for ; Mon, 6 Jul 1998 10:12:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA18822; Mon, 6 Jul 1998 10:07:56 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd018807; Mon Jul 6 17:07:48 1998 Date: Mon, 6 Jul 1998 10:07:37 -0700 (PDT) From: Julian Elischer To: "Jordan K. Hubbard" cc: spork , John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-Reply-To: <24529.899726642@time.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 what about the paper ar USENIX about "Using FreeBSD as a console server" On Mon, 6 Jul 1998, Jordan K. Hubbard wrote: > > If anyone who maintains these machines is interested, I have a gigantic > > box of modems if that would help in the future. Ever since I started > > putting remote console access on all of our machines, I sleep better ;) > > Well, I'm a bit short of phone lines in there so what I'd *really* > like would be a single modem and an old Cisco cs500 that nobody's > using (or a multiport comms card) so that I can make a console server > to handle all our equipment. ;-) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 10:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11528 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:14:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11513 for ; Mon, 6 Jul 1998 10:13:57 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id KAA17933 for ; Mon, 6 Jul 1998 10:13:08 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id TAA05235; Mon, 6 Jul 1998 19:12:26 +0200 (MEST) (envelope-from kuku) Message-ID: <19980706191226.15709@gil.physik.rwth-aachen.de> Date: Mon, 6 Jul 1998 19:12:26 +0200 From: Christoph Kukulies To: Mark Tinguely Cc: freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: mit-pthreads and gethostbyname References: <199807061655.LAA27539@plains.NoDak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199807061655.LAA27539@plains.NoDak.edu>; from Mark Tinguely on Mon, Jul 06, 1998 at 11:55:27AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 11:55:27AM -0500, Mark Tinguely wrote: > > I have a strange problem with resolution of localhost (gethostbyname) > > when using mit-pthreads where localhost cannot be resolved by > > gethostbyname when search order is host->bind in /etc/host.conf > > and /etc/resolv.conf is present. > > using libc_r (which uses the libc gethostby* routines), the host.conf > file is used. But using MIT threads like you mentioned, they implement > their own gethostby* routines. > > I think there is a more generic problem MIT pthreads does not consult the > /etc/hosts file. I test program that runs on a machine in an isolated network: > > joy (nameserver) > / \ > rest of net isolated network > > the isolated network have /etc/hosts and does a host, bind search order. > > If i run a program that uses gethostbyname from libc, the correct IP > number is returned for joy (the hidden network IP taken from /etc/hosts). > test 2, if I resolve a name that has multiple DNS entries, the libc > version returns them all. > > If i run a program that uses gethostbyname from MIT pthreads, the DNS derived > IP number is returned for joy. for test 2, only the first IP number of a host > that resolves to multiple addresses is returned. > > check the command, "nslookup localhost", by guess is that it does not > have an entry and that is why the MIT pthreads gethostbyname call does not > not return a value. blues> nslookup localhost Server: acaxp.physik.rwth-aachen.de Address: 137.226.33.200 Non-authoritative answer: Name: localhost Address: 127.0.0.1 blues> ./resolveip localhost ./resolveip: Unable to find hostid for 'localhost' blues> resolveip is a program which comes with mysql-3.22.3alpha and is linked against mit-pthreads. blues> ldd resolveip resolveip: -lm.2 => /usr/lib/libm.so.2.0 (0x2002d000) -lz.2 => /usr/lib/libz.so.2.0 (0x20047000) -lcrypt.2 => /usr/lib/libcrypt.so.2.0 (0x20053000) -lc.3 => /usr/lib/libc.so.3.1 (0x20068000) Strangely though, I ran that program fine on hub.freebsd.org but in my network it fails although the nameserver has a localhost entry. What's up with all the different thread packages these days? I hear FreeBSD kernel threads aren't yet quite mature, or still too slow. mit-pthreads are supposedly faster than kernel threads (?). Does anyone know the whole story? Could be mysql made working with kernel threads? Are libc_r routines using kernel threads? > --mark. -- 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 Mon Jul 6 10:19:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12566 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:19:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12557 for ; Mon, 6 Jul 1998 10:19:54 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id NAA07341; Mon, 6 Jul 1998 13:17:00 -0400 (EDT) Date: Mon, 6 Jul 1998 13:16:58 -0400 (EDT) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: Object library formats Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could this library be linked into a kernel? COFF/TRLLD.O: 80386 COFF executable not stripped - version 30821 It is part of the Olicom device driver development kit for their token ring cards. They seem to think it would be compatible with a.out. Also would this library be compatible with an elf'd system? ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version 1, not stripped Thanks Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 10:43:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16530 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:43:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA16496 for ; Mon, 6 Jul 1998 10:43:10 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Mon Jul 6 12:43 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id MAA15406 for ; Mon, 6 Jul 1998 12:42:57 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9HJTL>; Mon, 6 Jul 1998 13:42:56 -0400 Message-ID: To: lile@stdio.com, hackers@FreeBSD.ORG Subject: RE: Object library formats Date: Mon, 6 Jul 1998 13:42:55 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Larry S. Lile [SMTP:lile@stdio.com] > > Could this library be linked into a kernel? > > COFF/TRLLD.O: 80386 COFF executable not stripped - version > 30821 > > It is part of the Olicom device driver development kit for their token > Is Olicom part of Olivetti or something different ? > ring cards. They seem to think it would be compatible with a.out. > Also > would this library be compatible with an elf'd system? > > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version > 1, > not stripped > A COFF binary file can be converted into a.out without much problems, I have even written that converter once but it was lost during a crash and I felt no urge to write it again. The problem is that this driver is probably relying on the SysV Device Driver Interface to call the kernel library functions that are missing in FreeBSD. For a network driver this is for sure because it should use the STREAMS framework which is not used in FreeBSD. -Serge P.S. A not stripped object file may be very useful for reverse engineering. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 10:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18655 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:51:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18610 for ; Mon, 6 Jul 1998 10:51:41 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id NAA07930; Mon, 6 Jul 1998 13:48:40 -0400 (EDT) Date: Mon, 6 Jul 1998 13:48:39 -0400 (EDT) From: "Larry S. Lile" To: sbabkin@dcn.att.com cc: hackers@FreeBSD.ORG Subject: RE: Object library formats In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998 sbabkin@dcn.att.com wrote: > > -----Original Message----- > > From: Larry S. Lile [SMTP:lile@stdio.com] > > > > Could this library be linked into a kernel? > > > > COFF/TRLLD.O: 80386 COFF executable not stripped - version > > 30821 > > > > It is part of the Olicom device driver development kit for their token > > > Is Olicom part of Olivetti or something different ? I have no idea as to Olicom's lineage. > > ring cards. They seem to think it would be compatible with a.out. > > Also > > would this library be compatible with an elf'd system? > > > > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version > > 1, > > not stripped > > > A COFF binary file can be converted into a.out without much problems, > I have even written that converter once but it was lost during a crash > and I > felt no urge to write it again. The problem is that this driver is > probably > relying on the SysV Device Driver Interface to call the kernel library > functions that are missing in FreeBSD. For a network driver this is for > sure because it should use the STREAMS framework which is not used > in FreeBSD. It is not a network driver in and of itself, it is just the hardware interface library. In other words, it is just enough to glue a driver to the card. So the question still stands, can I link it into the kernel and write a driver around it? > -Serge > > P.S. A not stripped object file may be very useful for reverse > engineering. I have no intrest in reverse engineering their code, I just want to get a driver written for their card after I finish my driver for the IBM shared ram token ring cards. The IBM driver is just about to start passing packets, now that I have talked to the local network guru about SNAP headers and the like. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 10:58:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20077 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:58:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19966; Mon, 6 Jul 1998 10:57:53 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id MAA10576; Mon, 6 Jul 1998 12:55:38 -0500 Received: from stlabcexg004.anheuser-busch.com(unknown 151.145.101.160) by gatewaya via smap (V2.1) id xma010567; Mon, 6 Jul 98 12:55:31 -0500 Received: by stlabcexg004.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3CR6WWH3>; Mon, 6 Jul 1998 18:58:32 +0100 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776600@STLABCEXG011> From: "Alton, Matthew" To: "'Erick Engelke'" Cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" , "Smallie, Scott" Subject: RE: lfs Date: Mon, 6 Jul 1998 18:58:50 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Erick Engelke [SMTP:erick@dark.uwaterloo.ca] > Sent: Friday, July 03, 1998 4:54 PM > To: Alton, Matthew > Subject: RE: lfs > > > > On Tue, 30 Jun 1998, Alton, Matthew wrote: > > > Like others in the past, I'm interested in seeing LFS completed. > > > I've been mucking around with this for awhile. We should cooperate. > > Sure, but this will be a bit embarrassing for the first message or > two. > > The first steps I've taken were obvious... even for me as a FreeBSD > kernal > new guy (all my other kernel work has been various RTOS, Microsoft and > OS/2)... compile this as a LKM and try her out. > > I see that a newlfs'd partition shows up nicely with the ifile log > file > and lost+found. But as soon as sync happens, whether timed or due to > a > umount or file i/o, we have a panic. [Alton, Matthew] Are you getting a core dump for kgdb? I don't have a scratch box running this code right now. I've got a nasty old 486/33 almost up for testing purposes but its imbecilic BIOS won't boot with an NE2000 clone in the bus. > > Since successive boots don't notice the updates, I'm assuming the log > is > never being updated. Possibly the kernel pages are not mapped to > backing > store... as a first guess. I'll try lfsdump to investigate. > > I've started adding debugging code to figure out how far we get. > Hmmm, where do printfs send their output... nowhere I happen to be > looking? [Alton, Matthew] I thought they went to /dev/console but the relevant descriptors may be closed when lfs is using them. Can anybody provide the correct poop on kernel-mode debug output to /dev/console before I go and spontaneously reinvent the wheel? > Also, how do I make this pop into the kernel debugger? [Alton, Matthew] See http://www.freebsd.org/handbook/handbook297.html#627 > Sorry for the startup questions. [Alton, Matthew] Don't apologise, for crying out loud. I've been starting up for 17 years ;-) > Erick > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 11:25:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25121 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 11:25:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25115 for ; Mon, 6 Jul 1998 11:25:52 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id UAA20652 for ; Mon, 6 Jul 1998 20:24:24 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id UAA10730 for ; Mon, 6 Jul 1998 20:24:55 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id UAA14772 for ; Mon, 6 Jul 1998 20:25:35 +0200 (CEST) From: Andre Albsmeier Message-Id: <199807061825.UAA24389@internal> Subject: Is it save to increase MSIZE on -STABLE? To: hackers@FreeBSD.ORG Date: Mon, 6 Jul 1998 20:25:30 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to the squid FAQ, it would be good to increase the size (not the number) of the mbuf buffers when running squid. See also http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 There they do it by adding options MSIZE="256" to the kernel config file. Since I found various references to MSIZE in userland, wouldn't it be better to tweak /usr/include/machine/param.h and build world and kernel? Or is it unadvisable to do that at all? WHat do the memory experts think? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 12:06:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00364 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 12:06:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from digi.digiware.nl (gtw.digiware.nl [194.151.72.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00288 for ; Mon, 6 Jul 1998 12:05:55 -0700 (PDT) (envelope-from wjw@digi.digiware.nl) Received: by digi.digiware.nl (8.8.7/1.63) id TAA16622; Mon, 6 Jul 1998 19:03:44 GMT From: wjw@digi.digiware.nl (Willem Jan Withagen) Message-Id: <199807061903.TAA16622@digi.digiware.nl> Subject: Re: adding to sysctl env. In-Reply-To: <199807060646.XAA21779@usr02.primenet.com> from Terry Lambert at "Jul 6, 98 06:46:20 am" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 6 Jul 1998 21:03:43 +0200 (CEST) Cc: wjw@digiware.nl, mike@smith.net.au, terry@lambert.org, hackers@FreeBSD.ORG Reply-To: wjw@digiware.nl X-Mailer: ELM [version 2.4ME+ PL31H (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 => > Reason I ask, is that there were no errors when I compiled without => > the inclusion, but that was the problem I could not see the => > debug.vlinkxlate in sysctl. :-( => => You need to look into why there were no errors. At a minimum, there => should have been a linktime error, if a macro was confused as an external => function reference. That's why I was suprised as well. I found out about the problem by compiling the module with 'cc -E' checking what cpp made of it. It just left the TEXT_SET in plain tekst there. So I suppose that there is a TEXT_SET to be linked against which doesn't harm the code. :-( => The man page is useful, but the inclusion of the kernel.h was probably => for some other prototype, not the sysctl prototype, IMO. You need to => narrow down your problem to make sure you aren't documenting an #include => that is necessary for your implementation, and not for sysctl's in => general. I'll undo the fix, and see what comes of it. Currently my kernel has not *TEXT_* items. --WjW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 12:41:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04721 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 12:41:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04704 for ; Mon, 6 Jul 1998 12:41:30 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id MAA23235; Mon, 6 Jul 1998 12:40:52 -0700 (PDT) Message-ID: <19980706124051.C19843@Alameda.net> Date: Mon, 6 Jul 1998 12:40:51 -0700 From: Ulf Zimmermann To: Mike Smith , "Jordan K. Hubbard" Cc: spork , John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? Reply-To: ulf@Alameda.net References: <24529.899726642@time.cdrom.com> <199807061553.IAA03480@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807061553.IAA03480@antipodes.cdrom.com>; from Mike Smith on Mon, Jul 06, 1998 at 08:53:36AM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 08:53:36AM -0700, Mike Smith wrote: > > > If anyone who maintains these machines is interested, I have a gigantic > > > box of modems if that would help in the future. Ever since I started > > > putting remote console access on all of our machines, I sleep better ;) > > > > Well, I'm a bit short of phone lines in there so what I'd *really* > > like would be a single modem and an old Cisco cs500 that nobody's > > using (or a multiport comms card) so that I can make a console server > > to handle all our equipment. ;-) > > We have the CS500, actually. What we need is a more current set of > ROMs for it, and someone that knows how to configure the stupid thing. Get me the hardware revision of the board in that CS500 and I will see if I can get ROMs from Cisco. And I should be able to handle the config too. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- 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 Mon Jul 6 15:38:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04289 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 15:38:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (root@ts01-62.waterford.indigo.ie [194.125.139.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04259; Mon, 6 Jul 1998 15:38:19 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id XAA01618; Mon, 6 Jul 1998 23:10:27 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807062210.XAA01618@indigo.ie> Date: Mon, 6 Jul 1998 23:10:25 +0000 In-Reply-To: rotel@indigo.ie "Re: Load related wd problem" (Jul 6, 10:13pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: rotel@indigo.ie, Tony Holmes , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Load related wd problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 6, 10:13pm, rotel@indigo.ie wrote: } Subject: Re: Load related wd problem > > > > When the IDE disks are under heavy load, they will take down the system with > > no warning. This occurs across all versions - it find it easy to duplicate > > the problem - on a web server, while the http server is up, I will do some > > custom processing on the log files (cat, grepping, etc.) which hits the IDE > > disks hard. After a time (usually after 10-15 minutes) the system hangs > > and can only be rescued with a hard reset. > > I saw a PR go on a while back for a similar problem, it was some > problem about using one variable for all disks instead of one each, > I can't remember the details. Anyway, I'm not sure if it was even > committed, but it might be worth searching freebsd.org to see if > you can find it, sorry I can't be more help. Damnit, I've searched GNATS, freebsd-bugs and freebsd-hackers and reviewed the changelog for wd.c and I can't find it. Does anyone else remember this? Sorry for the amount of cross-posting, but if the original patch was correct then its important. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: 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 Jul 6 16:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12659 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 16:45:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12643 for ; Mon, 6 Jul 1998 16:45:49 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id IAA05791; Tue, 7 Jul 1998 08:44:44 +0900 (JST) Date: Tue, 7 Jul 1998 08:44:44 +0900 (JST) Message-Id: <199807062344.IAA05791@afs.ntc.mita.keio.ac.jp> To: mike@smith.net.au Cc: abial@nask.pl, sbabkin@dcn.att.com, freebsd-hackers@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: PCMCIA disk cards In-Reply-To: Your message of "Mon, 06 Jul 1998 08:59:50 -0700". <199807061559.IAA03530@antipodes.cdrom.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807061559.IAA03530@antipodes.cdrom.com> mike@smith.net.au writes: >> There are actually a couple of different ways of talking to PCCARD >> memory devices. The PAO people have driver support for some PCCARD ATA >> and CompactFlash devices. You should talk to Hosakawa-san >> (hosakawa@freebsd.org) and ask him why he hasn't committed these bits >> (he said he was going to quite a while back now...) Hmm that's simply because it does not work on most of laptops that has internal CD-ROM drive because the ATAPI CD-ROM uses secondary IDE interface. I wrote the diff to use ATAPI PCMCIA card at any I/O address, but it does not work. This diff has not updated for a few month because I'm very busy these days. I'll cvs update the tree and post the diffs against today's -current again. Please check the code. Thanks. -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 17:05:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16152 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 17:05:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16125 for ; Mon, 6 Jul 1998 17:05:43 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id JAA10621; Tue, 7 Jul 1998 09:35:35 +0930 (CST) Message-ID: <19980707093535.M7792@freebie.lemis.com> Date: Tue, 7 Jul 1998 09:35:35 +0930 From: Greg Lehey To: "Larry S. Lile" , hackers@FreeBSD.ORG Subject: Re: Object library formats References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Larry S. Lile on Mon, Jul 06, 1998 at 01:16:58PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 6 July 1998 at 13:16:58 -0400, Larry S. Lile wrote: > > Could this library be linked into a kernel? > > COFF/TRLLD.O: 80386 COFF executable not stripped - version 30821 Do they really use upper-case file names? How strange. Nevertheless, I'd guess that file(1) is wrong, and it's really an object, not an executable or a library. You could convert it to a.out and link it, but I doubt it would do anything useful. > It is part of the Olicom device driver development kit for their token > ring cards. They seem to think it would be compatible with a.out. Also > would this library be compatible with an elf'd system? I don't know how to convert it to elf, but it doesn't look necessary. The following file appears to be the elf version. > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version 1, > not stripped The real problem is: what do you expect these files to do? In order to do anything useful in the kernel, they need to fit in, which means they need to be written for FreeBSD. You don't even say what system they're written for, but I'll bet my bottom dollar it's not *BSD. In summary, I'd say "forget it". If you can't get source code (which you'd almost certainly need to modify significantly), it's no use to you. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 17:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18374 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 17:28:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA18368 for ; Mon, 6 Jul 1998 17:28:10 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40759(1)>; Mon, 6 Jul 1998 17:27:29 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Mon, 6 Jul 1998 17:27:19 -0700 To: Andre Albsmeier cc: hackers@FreeBSD.ORG Subject: Re: Is it save to increase MSIZE on -STABLE? In-reply-to: Your message of "Mon, 06 Jul 98 11:25:30 PDT." <199807061825.UAA24389@internal> Date: Mon, 6 Jul 1998 17:27:15 PDT From: Bill Fenner Message-Id: <98Jul6.172719pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Instead, try applying the patch at: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c.diff?r1=1.40&r2=1.41 It solves the "100-byte write" problem in a better way. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 20:19:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06750 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 20:19:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA06736 for ; Mon, 6 Jul 1998 20:19:17 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 7154 invoked from network); 7 Jul 1998 03:18:44 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 7 Jul 1998 03:18:44 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id VAA00589; Mon, 6 Jul 1998 21:49:19 -0500 Date: Mon, 6 Jul 1998 21:49:19 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807070249.VAA00589@bonkers.taronga.com> To: hackers@FreeBSD.ORG Newsgroups: taronga.freebsd.hackers Subject: Re: Variant Link implementation, continued References: <199807040226.TAA07461@antipodes.cdrom.com> <199807061332.JAA26291@lakes.dignus.com> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807061332.JAA26291@lakes.dignus.com>, Thomas David Rivers wrote: >> I think that this is sufficiently unlikely given that there have been >> only two respondents that actually use '$' in names at all... That they know of. There are a number of programs that use user-provided strings as filenames. INN uses $ as a separator in message-IDs. Cnews uses the message-ID as part of a temporary file name. Put them together and make $ dangerous... boom. If it's possible to integrate the namespace into the filesystem and still achieve the desired result, it'd be a Good Thing to do it. -- This is The Reverend Peter da Silva's Boring Sig File - there are no references to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 20:37:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10155 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 20:37:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10141 for ; Mon, 6 Jul 1998 20:37:38 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id UAA09792 for ; Mon, 6 Jul 1998 20:37:27 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA04805; Mon, 6 Jul 1998 20:37:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807070337.UAA04805@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christoph Kukulies cc: Mark Tinguely , freebsd-hackers@freefall.cdrom.com Subject: Re: mit-pthreads and gethostbyname In-reply-to: Your message of "Mon, 06 Jul 1998 19:12:26 +0200." <19980706191226.15709@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 20:37:21 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that mysql thingie should be using libc_r and not the mit threads package unless they have a very specific technical reason for it. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 21:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21154 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 21:50:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21131 for ; Mon, 6 Jul 1998 21:50:18 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id GAA22968 for ; Tue, 7 Jul 1998 06:48:58 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id GAA21105 for ; Tue, 7 Jul 1998 06:49:29 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id GAA17473 for ; Tue, 7 Jul 1998 06:50:09 +0200 (CEST) From: Andre Albsmeier Message-Id: <199807070450.GAA28610@internal> Subject: Re: Is it save to increase MSIZE on -STABLE? In-Reply-To: <98Jul6.172719pdt.177515@crevenia.parc.xerox.com> from Bill Fenner at "Jul 6, 98 05:27:15 pm" To: fenner@parc.xerox.com (Bill Fenner) Date: Tue, 7 Jul 1998 06:50:01 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Instead, try applying the patch at: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c.diff?r1=1.40&r2=1.41 > > It solves the "100-byte write" problem in a better way. Thanks, will try that on -STABLE. It's far simpler than doing ht whole MSIZE thing :-) Thanks, -Andre > > Bill > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 23:00:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02183 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 23:00:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hen.scotland.net (hen.scotland.net [194.247.64.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02172 for ; Mon, 6 Jul 1998 23:00:47 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e2c10p50.scotland.net ([148.176.238.114] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for hackers@freebsd.org id 0ytQnY-0006mG-00; Tue, 7 Jul 1998 07:00:20 +0100 Received: (qmail 854 invoked by uid 1002); 6 Jul 1998 19:27:20 -0000 Message-ID: <19980706202720.A785@timog.prestel.co.uk> Date: Mon, 6 Jul 1998 20:27:20 +0100 From: Timo Geusch To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: PCMCIA disk cards Mail-Followup-To: Mike Smith , hackers@freebsd.org References: <199807061559.IAA03530@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807061559.IAA03530@antipodes.cdrom.com>; from Mike Smith on Mon, Jul 06, 1998 at 08:59:50AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 08:59:50AM -0700, Mike Smith wrote: > > Probably. But what with inserting and removing them... I guess removing > > such a drive can panick your system. > > Yes. PCMCIA sucks. > > There are actually a couple of different ways of talking to PCCARD > memory devices. The PAO people have driver support for some PCCARD ATA > and CompactFlash devices. You should talk to Hosakawa-san > (hosakawa@freebsd.org) and ask him why he hasn't committed these bits > (he said he was going to quite a while back now...) Well, to if I remember correctly, there are at least four different ways of handling storage devices in PCMCIA: 1. SRAM cards. Used as 'normal' memory, you map a part of their memory into the infamous 'above 640k' range because the bleedin' adapter still can't handle higher addresses (Ugh) and simply read/write from that memory. 2. Flash cards that come up as flash cards. IMHO, this is the worst part of 'em# all. The problem with those cards is that you have to determine exactly what kind of card it is, to make sure you get the erase block size and stuff like that right. Apart from that, you already know that the day after you are finished your customer will show up with yet another dubios card that will not work. 3. Flash cards and Hard drives that are using the ATA interface. From a driver point of view these are amongst the easiest to support, baring the one or two really weird cards that want to be configured as either primary or secondardy IDE devices. 4. The infamous non-ATA HD. Never came across one, but they are rumored to exist in the wild. Considering the file system problems (Guess were all this blabbing came from - I used to work on a PCMCIA driver suite for Windows NT, which incidentally has similar problems), I guess it should be possible to implement a partial working kind of hot swapping with a bit of reliance on the luser. Basically, the things that need to be assured are: - No write buffering. All the data has to go directly to the device. If that device has some kind of light, one can at least tell the luser that s/he can't remove the drive while the light is on. Pity that nobody bothered to create some kind of physical locking mechanism, otherwise we could simply lock the device until its unmounted. - When a PCMCIA ATA device is present, the kernel needs to know that it can go away at any time. Thus, the handling of sudden disk removals should be implemented in a way that will actually prevent the kernel from panicking. - Hot insertion would be nice, too :). Should not be to complicated, though. I actually did not look at the code for a long time, so if some of the features are already present, I have to apologize. Cheers, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 23:06:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03082 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 23:06:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03058 for ; Mon, 6 Jul 1998 23:06:31 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA09755; Mon, 6 Jul 1998 23:06:29 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd009745; Mon Jul 6 23:06:27 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA01460; Mon, 6 Jul 1998 23:06:26 -0700 (MST) From: Terry Lambert Message-Id: <199807070606.XAA01460@usr06.primenet.com> Subject: Re: A really hoopy idea for variant symlinks. To: peter@taronga.com (Peter da Silva) Date: Tue, 7 Jul 1998 06:06:19 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199807061148.GAA17254@bonkers.taronga.com> from "Peter da Silva" at Jul 6, 98 06:48:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199807060652.XAA22028@usr02.primenet.com>, > Terry Lambert wrote: > >It's a bit "plan9"-ish, depending on kernel enforcement of parsing > >semantics; I'd try to avoid that... > > Mind elaborating on that? No problem... The enforcement depends on the procfs (kernel code) parsing and enforcing against "absurd" values. I would prefer to put the vast majority of the enforcement in the libc, and limit the range of "absurd" to be "anything beginning with a ``#'' character". The idea of "null terminated name/value pairs as 8 bit clean strings" resolves all of the namespace and X/PG3 - X/PG4 multibyte byte stuffing crap that you would otherwise have to deal with, presumably in the kernel. Less work in the kernel means a smaller kernel. I'm a bit annoyed at the current sysctl mechanism because it is not data driven off a pageable data segment in the kernel files data section, but at least that's resolvable (via ELF) in some future release, assuming the deed ever happens (or FreeBSD gets off the pot). John Dyson was a big fan of not having parsing in the kernel. FreeBSD has a number of places where that occurs (the aforementioned sysctl, the mount options parsing, the NFS mounts -- basically, everywhere, other than namei(), where copyinstr() is used to copy a NUL terminated string into the kernel. Linux resolves this (inadequately for NFS, of course, and with race condition for SMP and kernel preemption because of prevalidation of a mutable address space, and with a big old memory leak in the failure case, which I fixed for them and submitted back via the indominatable Matt Day 8-)) by having a single method of copying in strings that is *very* specific for FS paths *only*. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 23:28:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06089 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 23:28:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06083 for ; Mon, 6 Jul 1998 23:28:23 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA18452; Mon, 6 Jul 1998 23:26:10 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd018425; Mon Jul 6 23:26:09 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA02268; Mon, 6 Jul 1998 23:25:57 -0700 (MST) From: Terry Lambert Message-Id: <199807070625.XAA02268@usr06.primenet.com> Subject: Re: Variant Link implementation, continued To: rivers@dignus.com (Thomas David Rivers) Date: Tue, 7 Jul 1998 06:25:57 +0000 (GMT) Cc: mike@smith.net.au, rivers@dignus.com, drosih@rpi.edu, hackers@FreeBSD.ORG, wjw@surf.IAE.nl In-Reply-To: <199807061332.JAA26291@lakes.dignus.com> from "Thomas David Rivers" at Jul 6, 98 09:32:48 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Seems reasonable... [and, nope, I don't have file names like that, > fortunately :-)]. > > However, can someone with the POSIX spec in-hand speak to the POSIX > ramifications here? I mean, if we essentially "steal" this space, > does it break any (future) POSIX conformance? Is "SOLO" good enough? Do you need specific rationale quoted? It's pretty obvious from context that the POSIX namespace doesn't apply below the system call (or library) impelementation of the POSIX interface, so long as the time update guarantees aren't affected by the implementation. The POSIX namespace escape is a dual "/" prefix. FreeBSD, of course, buggers this up, because it can't inherit the namespace escape down multiple iterations of path components; for example: //apple_hfs_semantic:rsrc/, where somepath: relative_path | absolute_path To access the resource fork of a file. This means that the escape is one path component, which is inadequate. The problem is in: 1) The use of mutual recustion to allow expansion into the path buffer (which also leads to prematurely reaching the MAXPATHLEN -- 1024 -- limit on some types of relative symlink expansion). 2) The non-opacity of the cn_pathbuf, et. al. values to the underlying FS, making it impossible to seperate an escaped lookup from an unescaped lookup. 3) The lack of a third "void *" context component for implementing various escape mechanisms. 4) The reset of the root because of the leading "/", even though it is part of the "//" token which is a namespace escape introducer. Of course, other OS's have also peed in the pool: I. Any Microsoft OS takes the "//" to mean "escape to the LanMan namespace", which is bogus as hell, since it leaves no room for other namespaces (perhaps this was their intent, but I prefer to ascribe it to stupidity). II. Intel Xenix, and similar OS's (such as PrimeOS using the Touch Communications, Inc. implementation) implementing Intel's "OpenNET", which implys the "//" to mean "escape to the OpenNET namespace" -- similarly bogus as hell. So at least we're not alone. The POSIX question boils down to whether or not you are permitted to implement a non-POSIX namespace in a POSIX system call. The technical anser is "no, but...". Because the expansion occurs at link expansion time, then the component reported to the POSIX evaluation of a path that contains a symlink that contains a variant target... is defined by the FS. This means that variant links are allowed. If you wanted to get entirely anal, you could always insist on a link target for a variant link beginning with: "//variant_link_semantic:freebsd/" But I think you can justify ommitting this prefix through the readlink(2)/symlink(2) "undefined" behaviours. After all, whose to say that the the implementation defined behaviour is not "variant links at all times". 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 6 23:39:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07149 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 23:39:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07136 for ; Mon, 6 Jul 1998 23:39:49 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id XAA15544 for ; Mon, 6 Jul 1998 23:39:37 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id IAA07960; Tue, 7 Jul 1998 08:39:15 +0200 (MEST) (envelope-from kuku) Message-ID: <19980707083914.59125@gil.physik.rwth-aachen.de> Date: Tue, 7 Jul 1998 08:39:14 +0200 From: Christoph Kukulies To: Amancio Hasty Cc: Christoph Kukulies , Mark Tinguely , freebsd-hackers@freefall.cdrom.com, freebsd-ports@FreeBSD.ORG, josh@ican.net Subject: mysql port (was Re: mit-pthreads and gethostbyname) References: <19980706191226.15709@gil.physik.rwth-aachen.de> <199807070337.UAA04805@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199807070337.UAA04805@rah.star-gate.com>; from Amancio Hasty on Mon, Jul 06, 1998 at 08:37:21PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 08:37:21PM -0700, Amancio Hasty wrote: > I think that mysql thingie should be using libc_r and not the mit threads > package unless they have a very specific technical reason for it. Your word in the porters ears :-) (Cc: MAINTAINER=josh@ican.net) Moreover in the light of the fact that 3.22.4 will be released today. I will try to link it against libc_r and see if that works. > > Amancio > > -- 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 Mon Jul 6 23:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07328 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 23:41:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07322 for ; Mon, 6 Jul 1998 23:41:29 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA16311; Mon, 6 Jul 1998 23:41:28 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd016265; Mon Jul 6 23:41:20 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA02881; Mon, 6 Jul 1998 23:41:17 -0700 (MST) From: Terry Lambert Message-Id: <199807070641.XAA02881@usr06.primenet.com> Subject: Re: Object library formats To: lile@stdio.com (Larry S. Lile) Date: Tue, 7 Jul 1998 06:41:17 +0000 (GMT) Cc: sbabkin@dcn.att.com, hackers@FreeBSD.ORG In-Reply-To: from "Larry S. Lile" at Jul 6, 98 01:48:39 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-MIME-Autoconverted: from 8bit to quoted-printable by usr06.primenet.com id XAA02881 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA07324 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is Olicom part of Olivetti or something different ? > > I have no idea as to Olicom's lineage. ] Olicom A/S was founded in Denmark in 1985 and has its world headquarters ] in suburban Copenhagen. The Company’s headquarters for the Americas, ] Olicom, Inc., is located in metropolitan Dallas, Texas. ] ] LASAT Communications, a division of The Olicom Group, develops and ] markets a full line of LASAT-branded modem and ISDN products. Olicom ] maintains R&D centers in the U.S. and Europe. The Company trades on the ] NASDAQ National Market System under the symbol OLCMF and the ] Copenhagen Stock Exchange. 8-). > > A COFF binary file can be converted into a.out without much problems, > > I have even written that converter once but it was lost during a crash > > and I > > felt no urge to write it again. The problem is that this driver is > > probably > > relying on the SysV Device Driver Interface to call the kernel library > > functions that are missing in FreeBSD. For a network driver this is for > > sure because it should use the STREAMS framework which is not used > > in FreeBSD. > > It is not a network driver in and of itself, it is just the hardware > interface library. In other words, it is just enough to glue a driver > to the card. So the question still stands, can I link it into the > kernel and write a driver around it? I think you can. The worst it will expect is the DDI on top, which really means "how Larry calls into the thing" and the DKI on the bottom, which may mean "you have to support some buffer allocation routines and things like bcopy/bzero/etc.", most of which FreeBSD alreay supports, or which is pretty easy to fake using wrapper routines. > > P.S. A not stripped object file may be very useful for reverse > > engineering. > > I have no intrest in reverse engineering their code, I just want to > get a driver written for their card after I finish my driver for > the IBM shared ram token ring cards. The IBM driver is just about > to start passing packets, now that I have talked to the local network > guru about SNAP headers and the like. The real issues here are: 1) Once you link a kernel to it, can you distribute the kernel, or does everyone who wants to use it have to link it as well. 2) Is the object file redistributable, in ELF or in COFF->a,out form, such that someone with a stallion board an a token ring card can use a driver that depends on the library. In other words, mostly legal, not technical. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 04:24:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10541 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 04:24:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10489 for ; Tue, 7 Jul 1998 04:24:36 -0700 (PDT) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id UAA16578; Tue, 7 Jul 1998 20:24:15 +0900 (JST) Date: Tue, 7 Jul 1998 20:24:15 +0900 (JST) Message-Id: <199807071124.UAA16578@afs.ntc.mita.keio.ac.jp> To: hosokawa@ntc.keio.ac.jp Cc: mike@smith.net.au, abial@nask.pl, sbabkin@dcn.att.com, freebsd-hackers@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: PCMCIA disk cards In-Reply-To: Your message of "Tue, 7 Jul 1998 08:44:44 +0900 (JST)". <199807062344.IAA05791@afs.ntc.mita.keio.ac.jp> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807062344.IAA05791@afs.ntc.mita.keio.ac.jp> hosokawa@ntc.keio.ac.jp writes: >> I'll cvs update the tree and post the diffs against today's -current >> again. Please check the code. This is it. hosokawa begin 644 wd-pccard-current.tar.gz M'XL(`(K]H34``^T[:W/;1I+Y"OV*MEQQ2/,)/B71[9P8/DI*2[#I['P2[!&!FNJ>GNZ=?`ZZ\IISZ8=/S M9[,O/M-EM]N#7@^^`+"'?9ON>`WU'9\&]A!@T.^WNT/\V\%A';L]^`+:GXN@ MXI7*Q(D!OIA',KIV5LY]XY!)?P4Y?_4U#CUQ>P!+UW5BSVOQWZ:[<_BO7SOO MCR]@Y@?B`%KS:"%:H7LC6S)V6ZF,6>E::M;6VN3UFYU8)+$O;OSP"F*\23\* MP6YV.SNDIM!(H1'3*QAR&XV&>;;L_?V]5KO7ZK3!'AQT>@?MKL6PM5IM;=`0 M_X/=/NCU#^SASC??0,,>MNL#J-%M"-]\LP.6/X.*7#9>N[ZLXJLUBX7`YZQM M5!P3A3/_J@I_WZD%T=5"7E5V\^;&:S],I8!#:(_^-]QE0&M[]WJ/%_LW(EX; M\8D)[N[UB>#NWJ"^IPB>_BKBJ/*"X/VH#M+_542SBGJM9N0BZ82=&N72<07\ M]AM4/#&C1GCQ`O1CUE^E51%929RZ"2#X1%$'+]WE:*=F67Z80#CQHY4?(HE, M/C)[DJTNFDR#:YD-)3[B:,?S8J2)4+M+A--T,0N(SF?KA%;5LO>[]30@M'@)'!ZBI.N0S$7(6@!>A+U^(C5D MM`K56%2ZIFK;J1FZ"6 M=A!U$RVA&P@G+I!3@*D##ROCJ17IA`;8FM9I+)SK429B^V`+!65MJCVB39^; MQ$Z)Q%#<)DC"[8*W3L68066^N`W-4=5@8IM9@,SMYG:`_U=\R#=]XS41K[=F MB16*N`(M>>-HR^`UPO-&/7@K_662\PGN[\F75)@V7]BG-3&C4W+2(%%R;KV$ MR[F(Q5>2K.CYL;+JZ"N2.`H"$:,E<1*8.Q(64; M13:536T(-5I::DF>V@R2:^QU.Q01]/I#$Q%D8+/`N9((,SX[^6[RTP7\IIZ. M+^R!>;8'WXXO>?6&[Z#E4+"NK&3KFZWQVJ`OSH;PS_T9"LXZ.?WVA_\B;"8T M^D%2?$=RX*6T;[^\5=L.OO0P0*K36"@S=MVH\GK[:KW#?1.RZ3V+7/&$=/$^ MRAL]<:-:O?BFV,P1%KS$UJ6)7DK!%^G?FBVP7CI30N'.*8$`<.DEFLTFY&GP M+CG6TGXG7DTT/XCF?KM7[PRAUD=989RJI63TKVW4#U@%<;E*457DURA*@OF@ M7%Q!OF4!J#Y*-G!D M?'8V`_K#6TP6,Y^=S\SMHZQ5(6W?=G4CLNFY"#$Y0"G-HIA1YCS#"&2*=QT2 MC_!M!-F`6DUW.].2]23"J,EPN&:56$Q=FK^U,JG4DYO5G%J#;'U'-/(=<22E M?Q6:7:$7\*6'6L^X"SN$'D'10H^\731S%%@=#$GJ"8'X@6&T>?WW3,NF_7?/ M"UI.187]35NDH^/+\8^G!;5PDX`5?8:TG(_/CB_&9W5X06F,UA!<@8CCRBX/ MA8H>4]W5051Q0Y7DMSZC\:*/3,E+?6#.FK5ETD_Y7F9SXR[O*FAFFJ&S0-:0 MP6F\OA9Q*`($^,OS_Y77E'?RLY9_'JG_='K=GJWK/[T^/]OV<-AYJO_\%=?7 M&#$MEGX@6N?'QT?O3W9T0M"*$*MM9GO+<,5*X"=4`32#4@ M]4C5G6'+MO$_M-L'O>%!V[8(CBI`^1!3`&IC_]Y!IZNBB7T.)DPLX?GRVK)6 M7MO"6'+EN6T5*:!GQ'`NCS5QA&O3$%\Z7V-2CE9S=WPV^>FDLXL98@1^_!'L M/MP(-T'OM/(P*HAW:@:YK9';1>31,L'E2LLZNCPZ'UO6\].02@'`KR#3)<]" MSFY\<@K35*Z#3"XNCR['Q];SDRC\"B,[!3*[=.ERCM!-G36Q]_]:N_ MQ#7!Z:UP@5Z6P@.G&:7)5Y)6_QR^OWQ_='P*@E>MRP)W,A&+AHL!&"2QXY)> MS/`6^,D=7%.+J'2JS9(*HT!:DH*.OTB!L_GN5]_V7EF!VWN@*"0-YB>MG8-6 MIP?M?53-@V['4I"DPL4Q10W>TT(==I14\:[%RCX7,/DX/GL[>?O#F\LQU2A4 M3D%^+PU1-PX/R1:@4LLH$%R76,:HJ+/*;AUT*SLYT\JN]%!%`:CX'D57WB1S M](R8)QR/WT\N/[P_^6\,=RHTL`HE]!AR)'-P8!I=I1*RTE\G,/.IV#;OO`WK,4',EWY6T3 M;[>CQ&NSA:*;%BZ&DI@B6F^//N"6>7?QW>E[J]/O4ZJY<&Y5W!;-:,.$F[>'-Z>OXW!,?^ MWI;^D[='V-.A'N)1!PT:\JC3[F=5_#"QO.N)=TV:/B+JR?A2@)M(8.T/T\64 M,D!:7QI20(P628,MTB#Q&8J?,EYJ=J03/#]M5S[M9-DPU4EWS)9WB:4RJBH1?B6@!M!X%KHPJJ(PUC16,YR3. M!J`,<""2C;#JD>%O_#A)G4"Y'[VHF\CW+!KG+1PWBJY]M2`M;O([R'34I/A& M86RINKS=K^]!K6L/ZW:WS[PG'OLNF$08A.^)RT7Z4(D"E;/4>(GS7OAEW$T%1,%:?#@E!.M>QK'.8TB7G$QCI!D:#;G1K`5BP@.=VJ4 M7>UB$,09I2)7/:G%TW/&47IIUY45.DK0!*.I0AULP!(W#FZWX`[W="J%HL!Z M@2'8Q%\X%&V5.$Y-K,IF$3CZTXAH/L$0:G)Q>EG19Y/QS40*3&D5O=5185W$ M'O4X\=F-@CTJ=09D7[!ODAW>E=0DB8.XW$O_M.J13'PGX#HAEP293CKL1'/L MJ7.@"U177$KH8%[*>@BX;69^+$E`P&3SX9.O<"%SW+EP>>$\.D?\E3[:$B%. M,A4X0!@HGXMU='9%(&M@M%JFD4);ACIY$4JB9K`B5%X7<.!C.> M"IJ*R_DP/N.63]ET3I(X[OQ/3'3$@+]G)MK$17W_[1!4#7%#!@5.?_CP`2[/ M3LX.^`VYC!(B)CI!+!SOCO40]X+2UY(F*MU*8\5_.8_2@,:5(+4&-^%O`K5] MA4`\C"'(FB100;N,.9V4_A3W#K91=:O*\\Q1,BN'9D4+I,@#9P$A;DB)TW+< M-:>M)(GD.ZKU8QZ6S'W9;&8ZJ!G%]:)/^=[/3!]N=_W`2U/VF6CB4PENY"W7 MW,*M2YR*M%';BU2F;`!69`\(D,TT]HO_0S]*RFK6@<$=<Y4SXD;P!..V@7$P9QNM#`WOE@9QB@Y,10M2(3,-8XEG?#.K!4M M>GR'$D!M0WN6HJHY4LL'22'`58PJ0*PESJ,?O5HS..1'R>(\[$B-S;$RNXR6 M9$,S1WI`H%],R3E(C>E17?"*C(A^J=4*&ZE2\@@O<`N\>L5-U2I]>K'R5!SV M,[?]@DV\V]::&Z\IX%1$'FIJ'QC)U0(:65J/'TWIY-34-LMT'<(_XW2YP7ZOH M7P<*!7?+@_$!-0!#5U)D$QGJ^&V;KWLT%LQ43]6&-GT2DZPMA9U9BK(_?2Q$ MT\]Z)EVGUF`5TZE0ZXH!E0RRX%L[)[9/0&&QL9CZ$QA%:,6G#K5\K;23M' M91H*T8@^7+A72'34[*5HBTH?/Z"6I75X.[D\?7M.]W=G/QV-+[-2#0$@1WYX M\V:#(\S)`7.RW[;KMOK@"J?(30L:EAM5`%(V993W.T%BAA0`J,R!]BN(\R1P MK;)$)TQ-OKC"9/#G)UA,=;$5.5:L-+"M,3A5AIWA4P;B$0K;MWO*4A!#*9OG MN!FG79'KOQ&9Q*7R6:LHOE;9,^KHM+*Q7.G-ZTCAQZ2N@2BY8%J>1'9>@CR_&_W/* M:LVX!UP:&;0'F1BW6`KTE,M1N7)`VE-H0K/AQ,X"$_\5??ZWMF&L0H(38:XP M,8RB#_$X."^-"#Q=F?D9-^0OQL%RX,[&3VH@I2?6NKZ#T6"M"P_N;F;"'IJ# M?>1"9[_>W2^42!D5>W/B`'UXA4S![!'=SP0-RXAR<36'WN+/V-]3J_+P#>.P MTN)FH&'E[5$UKNW9(QK,[HN#@DTQ<\O?LC+1@LI3WM99.Z+OH7/GP(C/BR0I5R9R*9IZX0*&*(NZ1:_!4%CK<^+`IN;^H5E@ M0SXJC'Q/60_)81TSVDF>=IK./K!&8/=*(R<=4I$(/4Y2K3^QH M9?DJ]7;L#P=DDX;HJ^VA,7CHW2F52?R%B*@0G25O2]QV>>91_DP4`T4UOL+( M-Q6@'.)FZ6;#,6+ZNIG;LH'@GHOPQX((6M(I M0I1*R&K5RI_?!Z@]C!YZ6+2D!>76WH.GF*@$QGQ;MT[U)D?N"S+`?,8")Z<_ M?G>1O5V\&1^?LEC)NMIMJ.VUA_6.;>1*@J6OW&(.]Y$L/R*+TC2=^GP!5[5: M+N3/>`]9I4C;>@AKMSO9K06=K4*V-OB0N_:,5QEFEO*]^]/:8/(ZX':?9)EO MITGR?Y+$AOW'*-/C[R=H:TG=Z,5!)NPML-E:0'\"O1YS;+,.9'74%A_@WNZ0 M+G0[]9[^X`U,N9C.C`@EGV3SQD,C(9P8DP(ZX45WK`Z]%?HF@[:,HZ;QA^B# MZ?ZJ,X):C35WD^OTVXTL3S\T6?HKSM%K-:7OV6[^`JD!]17K^M(>7L)#0.55P.8JMJNI-B/';T\P,;PG M4G$29^E/E/,JAWUU4'_78B,3OS!@5MFY*45%6TW_IP?VWY^CA#GQ`!V-YRI6 MNL\/9^0H#JFV?P^3MO+@WN7_8?RC_"/-^Q=GVO/5L<(<@,IYMF!0MH%IXA^@ M`)^%<6&3:HA9$4?"E0A%["2F3G`E$LH_*]4F*?`L2.77`Q5/V-93'T^UET&5.5,H@CF_M5NI MBEE%?A5J6H?DT?1"M1ILB!M^!XHM?"KHRZ;&;"M&E/(O4VLKI%+D)L)(#5,9 MK#K6*`MR(U,S&/B;>/4C-KNG?W8WV.ME::G)7I1WJZC:%&SD!/3#->\ZN5L* M'J*K@H6D+SN`V+;FA^S\QIIS3/?'R-LSC`?@P71Q+W:N!,14"+J&<@_`5#M?H@5__3 M'U@^74_7T_5T/5U/U]/U=#U=3]?3]70]74_7T_5T/5U/UW_P^B?W4 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13182 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 04:45:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA13177 for ; Tue, 7 Jul 1998 04:45:35 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 9317 invoked from network); 7 Jul 1998 11:45:09 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 7 Jul 1998 11:45:09 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA13575; Tue, 7 Jul 1998 06:42:58 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807071142.GAA13575@bonkers.taronga.com> Subject: Re: A really hoopy idea for variant symlinks. To: tlambert@primenet.com (Terry Lambert) Date: Tue, 7 Jul 1998 06:42:58 -0500 (CDT) Cc: peter@taronga.com, hackers@FreeBSD.ORG In-Reply-To: <199807070606.XAA01460@usr06.primenet.com> from "Terry Lambert" at Jul 7, 98 06:06:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The enforcement depends on the procfs (kernel code) parsing and enforcing > against "absurd" values. Like the file system does already? It's just namei! > I would prefer to put the vast majority of the enforcement in the libc, > and limit the range of "absurd" to be "anything beginning with a ``#'' > character". I would prefer to have a single namespace. > Less work in the kernel means a smaller kernel. But the kernel's already doing this work, in namei. Let it continue to do so. What parsing would you need to be doing other than what namei does? All the system calls you need already exist. They're all already doing all the parsing that they need to do. I guess I'm stupid, I still don't see the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 05:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21685 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 05:56:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21680 for ; Tue, 7 Jul 1998 05:56:27 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA27019 for ; Tue, 7 Jul 1998 05:56:13 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA24329 for ; Tue, 7 Jul 1998 08:56:22 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id IAA16529 for ; Tue, 7 Jul 1998 08:50:31 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA00339 for freebsd-hackers@freefall.cdrom.com; Tue, 7 Jul 1998 08:20:03 -0400 (EDT) Date: Tue, 7 Jul 1998 08:20:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807071220.IAA00339@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com Subject: Some panics on 2.2.6. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing 2.2.6; a machine which ran for months with 2.2.5 is now getting panics - about one a week. I just set up dumping, and have the following tracebacks (unfortunately, I don't have a debuggably kernel... I'm going to fix that :-) ) I mention these to see if anyone else has experienced them... The first just seems to be something in map'd pages. The second is "panic: vref used where vget required". - Dave Rivers - IdlePTD 254000 current pcb at 22d458 panic: page fault #0 0xf01125c3 in boot () (kgdb) where #0 0xf01125c3 in boot () #1 0xf0112882 in panic () #2 0xf01c82a6 in trap_fatal () #3 0xf01c7d94 in trap_pfault () #4 0xf01c7a37 in trap () #5 0xf01c5fa8 in pmap_remove_pages () #6 0xf010c193 in exit1 () #7 0xf010c054 in exit () #8 0xf01c853f in syscall () #9 0x2011eead in ?? () IdlePTD 254000 current pcb at 22d458 panic: vref used where vget required #0 0xf01125c3 in boot () (kgdb) where #0 0xf01125c3 in boot () #1 0xf0112882 in panic () #2 0xf012f572 in vref () #3 0xf01022b0 in iso_iget () #4 0xf0104319 in cd9660_root () #5 0xf012e298 in lookup () #6 0xf012dcab in namei () #7 0xf0131e00 in lstat () #8 0xf01c853f in syscall () #9 0x20067da1 in ?? () #10 0x2003dc7d in ?? () #11 0x2003d5de in ?? () #12 0x16a3 in ?? () #13 0x31f2 in ?? () #14 0x1095 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 06:18:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24026 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 06:18:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24021 for ; Tue, 7 Jul 1998 06:18:35 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id PAA11934 for ; Tue, 7 Jul 1998 15:26:13 +0200 (SAT) Received: by citadel via recvmail id 11931; Tue Jul 7 15:25:40 1998 From: Graham Wheeler Message-Id: <199807071323.PAA01453@cdsec.com> Subject: Deactivating the screen saver To: hackers@FreeBSD.ORG Date: Tue, 7 Jul 1998 15:23:38 +0200 (SAT) Cc: gram@gram.cdsec.com (Graham Wheeler) X-Mailer: ELM [version 2.4 PL25-h4.1] 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 all I was wondering if there was a way to deactivate the console screen saver from within a program. By deactivate, I don't mean disable, but switch off until the idle period elapses, when it can kick in again. A crude approach may be to unload the module and then reload it, but perhaps there is a better way (other than adding a new ioctl/sysctl to the kernel). Any ideas, anyone? TIA Graham -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 06:57:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29507 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 06:57:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29499 for ; Tue, 7 Jul 1998 06:57:49 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id JAA19281; Tue, 7 Jul 1998 09:54:52 -0400 (EDT) Date: Tue, 7 Jul 1998 09:54:51 -0400 (EDT) From: "Larry S. Lile" To: Terry Lambert cc: sbabkin@dcn.att.com, hackers@FreeBSD.ORG Subject: Re: Object library formats In-Reply-To: <199807070641.XAA02881@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Terry Lambert wrote: > The real issues here are: > > 1) Once you link a kernel to it, can you distribute the kernel, > or does everyone who wants to use it have to link it as well. I assume it will be a "contrib" kinda thing or at worst a go to olicom's website get this zip file and pull out this library and stuff it here. But they are in the business of selling cards so I don't think they will mind too much. They have a linux driver on their website which uses one of the libraries and it is just UU'ed into a patch file directly, I think olicom is credited for it in the readmes. As far as everyone linking it, I though once a library had been included into the kernel anyone who wanted to call a function from it just needed it header? Maybe I have misunderstood your question. > 2) Is the object file redistributable, in ELF or in COFF->a,out > form, such that someone with a stallion board an a token ring > card can use a driver that depends on the library. Is there any conversion process between COFF and the libraries that FreeBSD currently uses? I have always been able to recompile libraries on the native os, so I don't know much about this. Anyway, I assume it is redistributable, most things is ddks are, but I can't find anything in the kit that says yes or no. When I get a driver written I will have to call them and verify that I can pass along their object code, or if everybody who wants it will have to go to their website and get it. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 07:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04425 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 07:28:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA04412 for ; Tue, 7 Jul 1998 07:28:35 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id KAA18265; Tue, 7 Jul 1998 10:31:42 -0400 From: Bill Paul Message-Id: <199807071431.KAA18265@skynet.ctr.columbia.edu> Subject: Re: Object library formats To: lile@stdio.com (Larry S. Lile) Date: Tue, 7 Jul 1998 10:31:41 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Larry S. Lile" at Jul 6, 98 01:16:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Larry S. Lile had to walk into mine and say: > Could this library be linked into a kernel? > > COFF/TRLLD.O: 80386 COFF executable not stripped - version 30821 > > It is part of the Olicom device driver development kit for their token > ring cards. They seem to think it would be compatible with a.out. Also > would this library be compatible with an elf'd system? > > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version 1, > not stripped I would avoid trying to accomodate foreign object modules. It sets a bad precedent. Repeat after me: "You want source code. You want source code. These aren't the droids you're looking for." On a totally different note, somebody brought Olicom to my attention the other day: they also make PCI ethernet NICs based on the ThunderLAN chip. These are almost completely identical to the Compaq ThunderLAN NICs, except they use a different PCI vendor and product ID, and they have the station address encoded at a different location within the EEPROM (most ThunderLAN NICs have it at 0x83, they have it at 0xF8; accomodating this is easy). Unfortunately, I don't know where to find the PCI vendor and product IDs for their cards: all the 'datasheets' on their web server are basically just marketing hype. I found one place with patches for the Linux driver that claim to add Olicom support, but in typical Linux fashion, the patches are broken: the patch for the header file is incomplete and lists only the Olicom vendor ID, whereas the patch for the C code refers to product IDs for the OC-2183/2185, OC-2326 and 2326 NICs. These are nowhere to be found. I asked Olicom about getting more useful datasheets via their 'feedback' section on the web server but haven't heard anything back yet. May I ask where you got the token ring device driver kit? Do they have it available for download anywhere or did you have to speak to someone in particular at Olicom to get it? Do you know if they have kits for the ethernet NICs too? -Bill PS: The ThunderLAN chip appears to support both ethernet and token rin PHYs; if this is a PCI token-ring NIC thay you have, it may have this chip on it, in which case I would visit the Texas Instruments web server and obtain the programmer's guide from there. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 07:36:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05752 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 07:36:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05479 for ; Tue, 7 Jul 1998 07:34:54 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA08508 for freebsd-hackers@FreeBSD.ORG; Tue, 7 Jul 1998 16:30:36 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id JAA07032; Tue, 7 Jul 1998 09:56:25 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807070756.JAA07032@semyam.dinoco.de> To: freebsd-hackers@FreeBSD.ORG cc: seggers@semyam.dinoco.de Subject: Someone working on swapoff? Date: Tue, 07 Jul 1998 09:56:24 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Is there still anybody left working on swapoff? The only reference I have in my mail archive is a mail from John mentioning this briefly ("when I get swapoff working"). Now that he left the project does anybody know what happened to this? It is really cruel to have to reboot a machine just because one uses a swap file on a non-root filesystem and can't get back to multi user from single user because the "mount -a" complains that the filesystem is busy. And besides this I think there's something missing with this asymmetry. Would just look more complete with it. :-) As I am at it: Any hints on good books, papers, whatever about paging and swapping internals in BSD - especially FreeBSD? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 07:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07699 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 07:46:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dark.uwaterloo.ca (dark.uwaterloo.ca [129.97.50.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07675; Tue, 7 Jul 1998 07:46:05 -0700 (PDT) (envelope-from erick@dark.uwaterloo.ca) Received: from localhost (erick@localhost) by dark.uwaterloo.ca (8.8.7/8.8.7) with SMTP id KAA16379; Tue, 7 Jul 1998 10:38:59 -0400 (EDT) (envelope-from erick@dark.uwaterloo.ca) Date: Tue, 7 Jul 1998 10:38:58 -0400 (EDT) From: Erick Engelke To: "Alton, Matthew" cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" , "Smallie, Scott" Subject: RE: lfs In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776600@STLABCEXG011> 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, 6 Jul 1998, Alton, Matthew wrote: > erick wrote: > > I see that a newlfs'd partition shows up nicely with the ifile log > > file and lost+found. But as soon as sync happens, whether timed or > > due to a umount or file i/o, we have a panic. > [Alton, Matthew] > Are you getting a core dump for kgdb? I don't have a scratch > box running this code right now. I've got a nasty old 486/33 > almost up for testing purposes... Now that I'm more up to speed on kdb (thanks for the tips), I got a bit farther. My scratch pc is a 486/50... not much better, eh? The actual error is in the lfs_writeseg() of lfs_segment.c where lfs is copying individual bufs into contiguous memory for a big long write. (called from lfs_segwrite, from lfs_sync) It looks like I'm dying at ++cbp->b_vp->v_numoutput... and a quick look suggests it is possible the vnode points to garbage. I'll have to verify that with kdb and experiment some more. While on the topic, LFS has a lot of hacks, many specifically about bufferring. Some other PC OS's simply manipulate the page tables to map buffers into contiguous RAM... (and then instruct 3rd parties to never do the same). I don't imagine that pagetable fiddling practice is ever used with FreeBSD, is it? > > Hmmm, where do printfs send their output... nowhere I happen to be > > looking? > [Alton, Matthew] > I thought they went to /dev/console They do. My mistake. Thanks for the hints. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 07:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08473 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 07:50:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08461 for ; Tue, 7 Jul 1998 07:50:46 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id KAA20335; Tue, 7 Jul 1998 10:45:52 -0400 (EDT) Date: Tue, 7 Jul 1998 10:45:51 -0400 (EDT) From: "Larry S. Lile" To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: Object library formats In-Reply-To: <199807071431.KAA18265@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Larry S. Lile > had to walk into mine and say: > > > Could this library be linked into a kernel? > > > > COFF/TRLLD.O: 80386 COFF executable not stripped - version 30821 > > > > It is part of the Olicom device driver development kit for their token > > ring cards. They seem to think it would be compatible with a.out. Also > > would this library be compatible with an elf'd system? > > > > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version 1, > > not stripped > > I would avoid trying to accomodate foreign object modules. It sets a > bad precedent. Repeat after me: "You want source code. You want source > code. These aren't the droids you're looking for." I really like having the source, but sometimes that is just not possible. If I can make their object code work in a driver then I will use it, if not then I will push them for a native object or the source. I understand their point though, they have spent a lot of money to make good token ring cards and dont want to give away their technology but they are making an effort to provide third party accessability. > On a totally different note, somebody brought Olicom to my attention > the other day: they also make PCI ethernet NICs based on the ThunderLAN > chip. These are almost completely identical to the Compaq ThunderLAN > NICs, except they use a different PCI vendor and product ID, and they > have the station address encoded at a different location within the > EEPROM (most ThunderLAN NICs have it at 0x83, they have it at 0xF8; > accomodating this is easy). Unfortunately, I don't know where to find > the PCI vendor and product IDs for their cards: all the 'datasheets' > on their web server are basically just marketing hype. I found one > place with patches for the Linux driver that claim to add Olicom > support, but in typical Linux fashion, the patches are broken: the > patch for the header file is incomplete and lists only the Olicom > vendor ID, whereas the patch for the C code refers to product IDs for > the OC-2183/2185, OC-2326 and 2326 NICs. These are nowhere to be found. > > I asked Olicom about getting more useful datasheets via their > 'feedback' section on the web server but haven't heard anything back > yet. They were happy to help me, but it did take several days. July 2 is not a good day to start asking technical questions, oops. Also their development staff is in Denmark. > May I ask where you got the token ring device driver kit? Do they have > it available for download anywhere or did you have to speak to someone > in particular at Olicom to get it? Do you know if they have kits for > the ethernet NICs too? The tokenring kit is at: http://www.olicom.com software TOKEN-RING:Token-Ring PowerMACH Works I have not seen an ethernet ddk, but that does not mean there isn't one. You should call them (Corporate office) and ask about it. I will warn you that you will get passed around and finally end up most likely talking to the head marketing rep. in your area. The lady I ended up talking to however was very nice and got me the ddk (when it was not on the webserver/or the link was broken?) via e-mail. > PS: The ThunderLAN chip appears to support both ethernet and token rin > PHYs; if this is a PCI token-ring NIC thay you have, it may have > this chip on it, in which case I would visit the Texas Instruments > web server and obtain the programmer's guide from there. Why reinvent the wheel? Besides I already looked at the two olicom cards I have and couldn't find the chips on TI's website :( I found some very similar numbers but no matches. (Of course I was only looking for token ring stuff) Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 08:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13876 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 08:28:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13870 for ; Tue, 7 Jul 1998 08:28:50 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA12036; Tue, 7 Jul 1998 11:28:29 -0400 (EDT) Date: Tue, 7 Jul 1998 11:28:29 -0400 (EDT) From: "Matthew N. Dodd" To: "Larry S. Lile" cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Object library formats 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 Tue, 7 Jul 1998, Larry S. Lile wrote: > Why reinvent the wheel? Besides I already looked at the two olicom > cards I have and couldn't find the chips on TI's website :( I found > some very similar numbers but no matches. (Of course I was only looking > for token ring stuff) TI has a number of legacy and new chips that don't have complete doc on their web page. What are the model numbers on the chips? (Actually, posting all the labels on the ASICs would be nice, probably to token-ring@) I've been meaning to hit TI up for the relevent doc for the 380c16, 26 and 30 token ring controllers but have no had the time. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 09:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19477 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 09:08:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA19366; Tue, 7 Jul 1998 09:07:58 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id KAA26310; Tue, 7 Jul 1998 10:54:54 -0500 Received: from stlabcexg006.anheuser-busch.com(unknown 151.145.37.158) by gatewayb via smap (V2.1) id xma025437; Tue, 7 Jul 98 10:54:28 -0500 Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3CRV7TST>; Tue, 7 Jul 1998 10:57:14 -0500 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776602@STLABCEXG011> From: "Alton, Matthew" To: "'Erick Engelke'" Cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" , "Smallie, Scott" Subject: RE: lfs Date: Tue, 7 Jul 1998 10:57:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Erick Engelke [SMTP:erick@dark.uwaterloo.ca] > Sent: Tuesday, July 07, 1998 9:39 AM > To: Alton, Matthew > Cc: 'hackers@freebsd.org'; 'freebsd-fs@freebsd.org'; Smallie, Scott > Subject: RE: lfs > > > > The actual error is in the lfs_writeseg() of lfs_segment.c > where lfs is copying individual bufs into contiguous memory > for a big long write. (called from lfs_segwrite, from lfs_sync) > > It looks like I'm dying at ++cbp->b_vp->v_numoutput... and a quick > look > suggests it is possible the vnode points to garbage. I'll have to > verify > that with kdb and experiment some more. [Alton, Matthew] We need to know precisely where panic() is called and whether it is called there exclusively. The lfs code has been sitting stagnant for a good long time and changes made 'around' it in the rest of the system may be breaking some assumptions. I don't know how stable this code was ever considered to be, but it's surprisingly pre-alpha now. I'm looking into ways to do automated bounds checking for pointer arithmetic for another (rent- paying) project and we may be able to use them here. > While on the topic, LFS has a lot of hacks, many specifically about > bufferring. Some other PC OS's simply manipulate the page tables to > map > buffers into contiguous RAM... (and then instruct 3rd parties to never > do > the same). I don't imagine that pagetable fiddling practice is ever > used > with FreeBSD, is it? > > [Alton, Matthew] FreeBSD is, thank God, really anything but a PC OS. All our APIs are published and everything! 8^D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 09:58:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27502 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 09:58:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27497 for ; Tue, 7 Jul 1998 09:58:22 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id SAA23857 for ; Tue, 7 Jul 1998 18:56:59 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id SAA08948 for ; Tue, 7 Jul 1998 18:57:31 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id SAA00441 for ; Tue, 7 Jul 1998 18:58:12 +0200 (CEST) From: Andre Albsmeier Message-Id: <199807071658.SAA07088@internal> Subject: Re: Is it save to increase MSIZE on -STABLE? In-Reply-To: <98Jul6.172719pdt.177515@crevenia.parc.xerox.com> from Bill Fenner at "Jul 6, 98 05:27:15 pm" To: fenner@parc.xerox.com (Bill Fenner) Date: Tue, 7 Jul 1998 18:58:05 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Instead, try applying the patch at: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c.diff?r1=1.40&r2=1.41 > > It solves the "100-byte write" problem in a better way. > > Bill > Thanks again for the tip. It works great on my 12 rather busy -STABLE machines. Is it possible to commit this to the -STABLE branch as well? If yes, I would send a note to the squid maintainers that they could remove their entry in http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2 Thanks, -Andre -- "Amateurs like Linux, but professionals prefer FreeBSD." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 11:20:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10220 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 11:20:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10204 for ; Tue, 7 Jul 1998 11:20:31 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA25348; Tue, 7 Jul 1998 11:20:28 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd025313; Tue Jul 7 11:20:24 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA18878; Tue, 7 Jul 1998 11:20:18 -0700 (MST) From: Terry Lambert Message-Id: <199807071820.LAA18878@usr01.primenet.com> Subject: Re: Object library formats To: lile@stdio.com (Larry S. Lile) Date: Tue, 7 Jul 1998 18:20:18 +0000 (GMT) Cc: tlambert@primenet.com, sbabkin@dcn.att.com, hackers@FreeBSD.ORG In-Reply-To: from "Larry S. Lile" at Jul 7, 98 09:54:51 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1) Once you link a kernel to it, can you distribute the kernel, > > or does everyone who wants to use it have to link it as well. [ ... ] > As far as everyone linking it, I though once a library had been included > into the kernel anyone who wanted to call a function from it just needed > it header? Maybe I have misunderstood your question. The potential problem is that of ownership of the library. They may not want to cede publication rights to it by allowing you to distribute it, preferring to enforce a license that prohibits reverse engineering. > > 2) Is the object file redistributable, in ELF or in COFF->a,out > > form, such that someone with a stallion board an a token ring > > card can use a driver that depends on the library. > > Is there any conversion process between COFF and the libraries that > FreeBSD currently uses? I have always been able to recompile libraries > on the native os, so I don't know much about this. No, but very old versions of the GNU binutils allowed conversion from COFF to FreeBSD ELF. Writing the code to do this is not hard, just a bit tedious (as another poster pointed out). > Anyway, I assume it is redistributable, most things is ddks are, but > I can't find anything in the kit that says yes or no. When I get > a driver written I will have to call them and verify that I can pass > along their object code, or if everybody who wants it will have to > go to their website and get it. As long as it's available for relink (my second question), then it's less of an issue. You may want to contact John Polstra and John Birrell, and see how they are coming on an ELF snapshot system; then you could use the ELF code without conversion. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 11:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10261 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 11:20:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10240 for ; Tue, 7 Jul 1998 11:20:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA01098; Tue, 7 Jul 1998 11:20:37 -0700 (PDT) Message-Id: <199807071820.LAA01098@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Graham Wheeler cc: hackers@FreeBSD.ORG, gram@gram.cdsec.com (Graham Wheeler) Subject: Re: Deactivating the screen saver In-reply-to: Your message of "Sat, 07 Jul 1998 15:23:38 +0200." <199807071323.PAA01453@cdsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 11:20:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all > > I was wondering if there was a way to deactivate the console screen saver > from within a program. By deactivate, I don't mean disable, but switch off > until the idle period elapses, when it can kick in again. A crude approach > may be to unload the module and then reload it, but perhaps there is a better > way (other than adding a new ioctl/sysctl to the kernel). Any ideas, anyone? You want to 'wake' the screen from within an application, correct? You could do a VT switch; this looks like it will unblank the screen even if you are switching to the current console. Use the VT_GETACTIVE ioctl to get the current console, then VT_ACTIVATE to switch to it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 11:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12056 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 11:28:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12034 for ; Tue, 7 Jul 1998 11:28:46 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA05167; Tue, 7 Jul 1998 14:28:15 -0400 Date: Tue, 7 Jul 1998 14:28:12 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: case in point for (A really hoopy idea for variant symlinks.) 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 here ya go. This is working as of now. $ ls /proc c002 c012 c021 c030 c039 c048 c057 c003 c013 c022 c031 c040 c049 c059 c004 c014 c023 c032 c041 c050 c060 c005 c015 c024 c033 c042 c051 c061 c007 c016 c025 c034 c043 c052 localhost c008 c017 c026 c035 c044 c053 c009 c018 c027 c036 c045 c054 c010 c019 c028 c037 c046 c055 c011 c020 c029 c038 c047 c056 $ ls /proc/c00[23] /proc/c002: 1 183 207 6005 kcore pci 121 198 24 7 kmsg scsi 130 2 3 cmdline ksyms self 141 200 4 cpuinfo loadavg stat 14458 201 5 devices locks sys etc. etc. etc. $ cat /proc/c00[23]/1/status Name: init State: S (sleeping) Pid: 1 PPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 etc. etc. etc. you get the point ... note that I don't have all the nodes. Some of them I don't care about it right now, one of them is out due to power outage which ate the disk. Didn't make a big difference. didn't hang my machine. Didn't (and can't) do much of anything to the system, since it's in my private name space and won't affect anyone else. If the remote servers or machines die, then my process will get an error when it tries to read that directory, but that's about it. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 11:39:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14224 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 11:39:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA14218 for ; Tue, 7 Jul 1998 11:39:52 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40776(2)>; Tue, 7 Jul 1998 11:39:16 PDT Received: by crevenia.parc.xerox.com id <177515>; Tue, 7 Jul 1998 11:39:05 -0700 From: Bill Fenner To: andre.albsmeier@mchp.siemens.de, fenner@parc.xerox.com Subject: Re: Is it save to increase MSIZE on -STABLE? Cc: hackers@FreeBSD.ORG Message-Id: <98Jul7.113905pdt.177515@crevenia.parc.xerox.com> Date: Tue, 7 Jul 1998 11:38:57 PDT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It will be committed to -stable after some more testing (like yours! =). I've contacted the squid maintainers about the FAQ. Thanks for trying the fix! Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 11:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14426 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 11:40:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA14400 for ; Tue, 7 Jul 1998 11:40:25 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA05201; Tue, 7 Jul 1998 14:39:55 -0400 Date: Tue, 7 Jul 1998 14:39:55 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: unattended install 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 brought up unattended install at theo's talk on openbsd, and got something of a brushoff (understandable: they had done 40-ish machines in short order for the terminal room, so it did not seem necessary to them). Unattended install is critical to clustering, although it's nice for everything else (I've been using it for 10 years now, both my own hacks and vendor's hacks where available). Consider that all 128 machines in our new cluster *do not have video cards*, and you get an idea of the problem. You can't sit there and install the OS ineractively -- no video, no keyboard, no mouse! Every one of these machines was brought up with our own in-house unattended install. It's not something you want to show your children: we build a prototype machine, toss some scripts in /, then burn a CD rom from the root file system which along with the scripts does the job. You boot the CD and 7 minutes later you have a machine, complete with bootp-provided IP address, ready to go. Once you have that first CD, you clone 7 or so more to get the parallelism. Ugly, but: using our system we can reload the entire rack (128 machines) in less than an hour. (and yes, we used to do network reloads starting 10 years ago until about 5 years ago, but once you get above a certain number of machines things get slow due to contention) (although even absent contention the CDrom has proven to be faster). I'm mentioning it here cause it will take some good thinking. I should also mention that Solaris, Windows/NT and Linux have working unattended install support. We will probably chuck our in-house unattended install on the Linux boxes for the linux kickstart system. So for you good hackers out there who may be thinking on install tools, please give a thought to the need for unattended install. thanks ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 12:21:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19397 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 12:21:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19381 for ; Tue, 7 Jul 1998 12:21:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01451; Tue, 7 Jul 1998 12:21:09 -0700 (PDT) Message-Id: <199807071921.MAA01451@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: unattended install In-reply-to: Your message of "Tue, 07 Jul 1998 14:39:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 12:21:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I brought up unattended install at theo's talk on openbsd, and got > something of a brushoff (understandable: they had done 40-ish machines in > short order for the terminal room, so it did not seem necessary to them). Ow. (The brushoff, not the terminal room.) We have actually supported unattended installs for some time through sysinstall's scripting support. If there's an install.cfg file in the boot image MFS, it's run straight away. This lets you do everything that sysinstall handles, fully automatically. About the only missing item here is BOOTP/DHCP, granted. > So for you good hackers out there who may be thinking on install tools, > please give a thought to the need for unattended install. Thanks for the reminder, and thanks for the description of how you're currently doing things. Your input's always appreciated, and I expect to hear more of it. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 12:58:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24715 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 12:58:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24706 for ; Tue, 7 Jul 1998 12:58:15 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA10060; Tue, 7 Jul 1998 15:57:57 -0400 (EDT) Date: Tue, 7 Jul 1998 15:57:56 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Mike Smith cc: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: unattended install In-Reply-To: <199807071921.MAA01451@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Mike Smith wrote: > We have actually supported unattended installs for some time through > sysinstall's scripting support. If there's an install.cfg file in the > boot image MFS, it's run straight away. This lets you do everything > that sysinstall handles, fully automatically. Has anyone created support for creating an install.cfg interactively by doing an actual or dry-run install? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 13:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25776 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 13:03:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25770 for ; Tue, 7 Jul 1998 13:03:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01639; Tue, 7 Jul 1998 13:02:15 -0700 (PDT) Message-Id: <199807072002.NAA01639@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: ben@rosengart.com cc: Mike Smith , "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: unattended install In-reply-to: Your message of "Tue, 07 Jul 1998 15:57:56 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 13:02:15 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 7 Jul 1998, Mike Smith wrote: > > > We have actually supported unattended installs for some time through > > sysinstall's scripting support. If there's an install.cfg file in the > > boot image MFS, it's run straight away. This lets you do everything > > that sysinstall handles, fully automatically. > > Has anyone created support for creating an install.cfg interactively by > doing an actual or dry-run install? Not AFAIK. The amount of work involved would be inordinate by comparison to the relative ease of just writing the file by hand. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 13:36:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00160 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 13:36:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA00106 for ; Tue, 7 Jul 1998 13:36:13 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA18807; Tue, 7 Jul 1998 16:39:06 -0400 From: Bill Paul Message-Id: <199807072039.QAA18807@skynet.ctr.columbia.edu> Subject: Re: Object library formats To: lile@stdio.com (Larry S. Lile) Date: Tue, 7 Jul 1998 16:39:04 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Larry S. Lile" at Jul 7, 98 10:45:51 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Larry S. Lile had to walk into mine and say: [snippage] > > I would avoid trying to accomodate foreign object modules. It sets a > > bad precedent. Repeat after me: "You want source code. You want source > > code. These aren't the droids you're looking for." > > I really like having the source, but sometimes that is just not possible. Nothing is impossible. > If I can make their object code work in a driver then I will use it, > if not then I will push them for a native object or the source. I > understand their point though, they have spent a lot of money to make > good token ring cards and dont want to give away their technology > but they are making an effort to provide third party accessability. Unfortunately, this doesn't wash simply because there are many other companies in the world that manufacture hardware like this, and they don't have any problems at all releasing programming info. This includes companies that make their own silicon, not just their own boards. Remember: we're not talking about incredibly sensitive industry secrets here. We're not asking for their chip masks or the source to their own drivers. What we are asking for is decent documentation that others can use to write their own device drivers, without being smothered by an NDA. If they think their business will be hurt by providing such information, then they're wrong. And no, it won't cost tons of money of force them to reorganize their infrastructures or any such nonsense: all they have to do is exactly what they're doing now, only without puckering up their sphyncters so tightly. [chop] > Unfortunately, I don't know where to find > > the PCI vendor and product IDs for their cards: all the 'datasheets' > > on their web server are basically just marketing hype. I found one > > place with patches for the Linux driver that claim to add Olicom > > support, but in typical Linux fashion, the patches are broken: the > > patch for the header file is incomplete and lists only the Olicom > > vendor ID, whereas the patch for the C code refers to product IDs for > > the OC-2183/2185, OC-2326 and 2326 NICs. These are nowhere to be found. > > > > I asked Olicom about getting more useful datasheets via their > > 'feedback' section on the web server but haven't heard anything back > > yet. > > They were happy to help me, but it did take several days. July 2 is > not a good day to start asking technical questions, oops. Also their > development staff is in Denmark. Actually, I think I found what I needed. It turns out the patches were to add support for newer Olicom cards: the existing version of the Linux tlan driver at Caldera already had the initial support. I found the product IDs for the relevant cards in the source, and got the Olicom vendor ID from the netbsd pcidevs file. As a bonus, I also found some device IDs for some additional Compaq NICs. Of course, it would be nice if I actually had an Olicom card to test with. > > May I ask where you got the token ring device driver kit? Do they have > > it available for download anywhere or did you have to speak to someone > > in particular at Olicom to get it? Do you know if they have kits for > > the ethernet NICs too? > > The tokenring kit is at: > http://www.olicom.com > software > TOKEN-RING:Token-Ring PowerMACH Works The file they mention is a self-extracting .EXE, which is kinda useless for me since I have a SPARC IPX on my desk. :( > I have not seen an ethernet ddk, but that does not mean there isn't > one. You should call them (Corporate office) and ask about it. I > will warn you that you will get passed around and finally end up > most likely talking to the head marketing rep. in your area. The > lady I ended up talking to however was very nice and got me the > ddk (when it was not on the webserver/or the link was broken?) via > e-mail. I called the NJ office (the closest one) and left a message earlier today. Haven't heard anything yet. > > PS: The ThunderLAN chip appears to support both ethernet and token rin > > PHYs; if this is a PCI token-ring NIC thay you have, it may have > > this chip on it, in which case I would visit the Texas Instruments > > web server and obtain the programmer's guide from there. > > Why reinvent the wheel? Because your existing wheel is sealed in a decidedly non-wheel-shaped block of epoxy with part of an axle sticking out. > Besides I already looked at the two olicom > cards I have and couldn't find the chips on TI's website :( I found > some very similar numbers but no matches. (Of course I was only looking > for token ring stuff) I would try contacting TI directly then. The fact that they don't have the documentation on their web server doesn't mean it doesn't exist at all. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 13:50:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01737 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 13:50:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01732 for ; Tue, 7 Jul 1998 13:50:25 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA00949; Tue, 7 Jul 1998 13:50:20 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd000884; Tue Jul 7 13:50:10 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id NAA01036; Tue, 7 Jul 1998 13:50:08 -0700 (MST) From: Terry Lambert Message-Id: <199807072050.NAA01036@usr04.primenet.com> Subject: Re: A really hoopy idea for variant symlinks. To: peter@taronga.com (Peter da Silva) Date: Tue, 7 Jul 1998 20:50:07 +0000 (GMT) Cc: tlambert@primenet.com, peter@taronga.com, hackers@FreeBSD.ORG In-Reply-To: <199807071142.GAA13575@bonkers.taronga.com> from "Peter da Silva" at Jul 7, 98 06:42:58 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The enforcement depends on the procfs (kernel code) parsing and enforcing > > against "absurd" values. > > Like the file system does already? It's just namei! Multiple "//" within a path are treated as "/", unless it's the first two characters in the path, in which case it's implementation defined what it does. That covers the full gamut on what is or isn't allowable semantically in a path component. Gramatically, there are some FS's that make restrictions (31 characters, but FreeBSD has no HFS implementation, 128 characters, but FreeBSD has no HPFS implementation, 12 characters, but FreeBSD has no NWFS implementation, 16 characters, but FreeBSD has no S51k implemetnation, and 8.3 characters -- well, OK, FreeBSD has a FAT/VFAT implementation). Enforcement of grammar occurs, ideally, on "parsed path components", not on "path components". So what I'm talking about here is FS semantics, not grammar. > > I would prefer to put the vast majority of the enforcement in the libc, > > and limit the range of "absurd" to be "anything beginning with a ``#'' > > character". > > I would prefer to have a single namespace. Me too. There's nothing that prevents this when placing the POSIX environement requirements in libc. The *current* POSIX interface to the environment exists almost entirely in libc in user space anyway, so requirements that a system call API have a POSIX namespace instead of a superset are specious, at best. > > Less work in the kernel means a smaller kernel. > > But the kernel's already doing this work, in namei. Let it continue to do > so. What parsing would you need to be doing other than what namei does? You would need name/value pair reduction; specifically, you would need to seperate the token before and after the (initial) '=' token when traversing the list of environment "name/value pair, '=' token seperator" strings. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 13:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02051 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 13:53:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02036; Tue, 7 Jul 1998 13:53:10 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA08332; Tue, 7 Jul 1998 13:53:02 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd008307; Tue Jul 7 13:53:01 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id NAA01160; Tue, 7 Jul 1998 13:52:53 -0700 (MST) From: Terry Lambert Message-Id: <199807072052.NAA01160@usr04.primenet.com> Subject: Re: lfs To: Matthew.Alton@anheuser-busch.com (Alton, Matthew) Date: Tue, 7 Jul 1998 20:52:53 +0000 (GMT) Cc: erick@dark.uwaterloo.ca, hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, Scott.Smallie@anheuser-busch.com In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776602@STLABCEXG011> from "Alton, Matthew" at Jul 7, 98 10:57:45 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD is, thank God, really anything but a PC OS. All our > APIs are > published and everything! 8^D Snort! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 13:53:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02101 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 13:53:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1 (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA02084 for ; Tue, 7 Jul 1998 13:53:21 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1 (SMI-8.6/8.6.9) with SMTP id QAA25148 for ; Tue, 7 Jul 1998 16:53:16 -0400 Date: Tue, 7 Jul 1998 16:53:16 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: Default Pagers 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 While reading file default_pager.c, I find there is really little code in that file. I wonder why default pager is used and why we have to convert an object into a swap pager and when to do so. I search the Archives extensively and do find something which I quote below: A "default pager" has now been created which cleans up the transition of objects to the "swap" type. The previous checks throughout the code for swp->pg_data != NULL were really ugly. This change also provides the rudiments for future backing of "anonymous" memory by something other than the swap pager (via the vnode pager, for example), and it allows the decision about which of these pagers to use to be made dynamically (although will need some additional decision code to do this, of course). The 4.4 BSD book also talks little about this topic. I hope someone can enlighten me a little bit more. Thanks in advance. ------------------------------------------------- Zhihui Zhang Department of Computer Science State University of New York at Binghamton Web Site: http://cs.binghamton.edu/~zzhang ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 15:51:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14894 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 15:51:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA14888; Tue, 7 Jul 1998 15:51:30 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id RAA13117; Tue, 7 Jul 1998 17:49:27 -0500 Received: from stlabcexg004.anheuser-busch.com(unknown 151.145.101.160) by gatewayb via smap (V2.1) id xma013066; Tue, 7 Jul 98 17:49:17 -0500 Received: by stlabcexg004.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3CR6W803>; Tue, 7 Jul 1998 23:52:13 +0100 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776603@STLABCEXG011> From: "Alton, Matthew" To: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" Subject: lfs Date: Tue, 7 Jul 1998 23:52:47 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define LFS_MAGIC 0x070162 So who was born on 01 JULY 1962? ;-) Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 15:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15637 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 15:55:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA15626 for ; Tue, 7 Jul 1998 15:55:15 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 11819 invoked from network); 7 Jul 1998 22:55:04 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 7 Jul 1998 22:55:04 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id RAA24074; Tue, 7 Jul 1998 17:54:21 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807072254.RAA24074@bonkers.taronga.com> Subject: Re: A really hoopy idea for variant symlinks. To: tlambert@primenet.com (Terry Lambert) Date: Tue, 7 Jul 1998 17:54:20 -0500 (CDT) Cc: peter@taronga.com, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199807072050.NAA01036@usr04.primenet.com> from "Terry Lambert" at Jul 7, 98 08:50:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The enforcement depends on the procfs (kernel code) parsing and enforcing > > > against "absurd" values. > > Like the file system does already? It's just namei! > Multiple "//" within a path are treated as "/", unless it's the > first two characters in the path, in which case it's implementation > defined what it does. > That covers the full gamut on what is or isn't allowable semantically > in a path component. OK, which means that /proc/curproc/syms/osversion is allowed in a path. That was the point of my proposal, to avoid polluting the namespace by using part of it. > You would need name/value pair reduction; specifically, you would need > to seperate the token before and after the (initial) '=' token when > traversing the list of environment "name/value pair, '=' token seperator" > strings. You must be talking about someone else's hoopy idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 16:41:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20997 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 16:41:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20964; Tue, 7 Jul 1998 16:41:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA02573; Tue, 7 Jul 1998 16:40:47 -0700 (PDT) Message-Id: <199807072340.QAA02573@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Alton, Matthew" cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" Subject: Re: lfs In-reply-to: Your message of "Tue, 07 Jul 1998 23:52:47 BST." <31B3F0BF1C40D11192A700805FD48BF901776603@STLABCEXG011> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 16:40:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #define LFS_MAGIC 0x070162 > > So who was born on 01 JULY 1962? ;-) You mean January the 7th, right? 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 16:44:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21672 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 16:44:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bb.cc.wa.us (chris@bb.cc.wa.us [134.39.181.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21564 for ; Tue, 7 Jul 1998 16:44:05 -0700 (PDT) (envelope-from chris@bb.cc.wa.us) Received: from localhost (chris@localhost) by bb.cc.wa.us (8.8.8/8.6.9) with SMTP id XAA08532; Tue, 7 Jul 1998 23:36:30 GMT Date: Tue, 7 Jul 1998 16:36:30 -0700 (PDT) From: Chris Coleman To: ben@rosengart.com cc: Mike Smith , "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: unattended install 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 Tue, 7 Jul 1998, Snob Art Genre wrote: > On Tue, 7 Jul 1998, Mike Smith wrote: > > > We have actually supported unattended installs for some time through > > sysinstall's scripting support. If there's an install.cfg file in the > > boot image MFS, it's run straight away. This lets you do everything > > that sysinstall handles, fully automatically. > > Has anyone created support for creating an install.cfg interactively by > doing an actual or dry-run install? > What about a config page (curses or X) that helped you through the format for the install.cfg You would have to compile your own install disk wouldn't you? Is there any way to put a install.cfg file on a install disk without doing a make release? Christopher J. Coleman (whyareyou@lookingforme.com) Computer Support Analyst I (509)-762-6341 FreeBSD Book Project: http://www.vmunix.com/fbsd-book/ > > > Ben > > "You have your mind on computers, it seems." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 16:50:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22628 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 16:50:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA22618; Tue, 7 Jul 1998 16:49:38 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id SAA25513; Tue, 7 Jul 1998 18:47:30 -0500 Received: from stlabcexg006.anheuser-busch.com(unknown 151.145.37.158) by gatewayb via smap (V2.1) id xma025456; Tue, 7 Jul 98 18:47:05 -0500 Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3CRV7V8A>; Tue, 7 Jul 1998 18:50:02 -0500 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776604@STLABCEXG011> From: "Alton, Matthew" To: "'Mike Smith'" Cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" Subject: RE: lfs Date: Tue, 7 Jul 1998 18:50:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > Sent: Tuesday, July 07, 1998 6:41 PM > To: Alton, Matthew > Cc: 'hackers@freebsd.org'; 'freebsd-fs@freebsd.org' > Subject: Re: lfs > > > #define LFS_MAGIC 0x070162 > > > > So who was born on 01 JULY 1962? ;-) > > You mean January the 7th, right? 8) [Alton, Matthew] Nope. #define FS_MAGIC 0x011954 Bill Joy's Bday is January 19. We Yanks use MMDDYY except in the military where we don't. :-) > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 18:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02025 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 18:30:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02000 for ; Tue, 7 Jul 1998 18:30:27 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-112.HiWAAY.net [208.147.148.112]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id UAA32196 for ; Tue, 7 Jul 1998 20:30:25 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA18009 for ; Tue, 7 Jul 1998 19:38:28 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807080038.TAA18009@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: Someone working on swapoff? In-reply-to: Message from Stefan Eggers of "Tue, 07 Jul 1998 09:56:24 +0200." <199807070756.JAA07032@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 19:38:27 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Eggers writes: > Hi! > > Is there still anybody left working on swapoff? The only reference I > have in my mail archive is a mail from John mentioning this briefly > ("when I get swapoff working"). Now that he left the project does > anybody know what happened to this? Apparently /sbin/swapon is the traditional BSD tool to add swap to a system, but would it be breaking sacred tradition to merge swapon and the future swapoff into one "swap" management utility? The unified utility could do swapon tasks if linked to the name "swapon" and swapoff tasks if its named "swapoff". -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 7 18:42:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03702 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 18:42:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA03697 for ; Tue, 7 Jul 1998 18:42:44 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40809(2)>; Tue, 7 Jul 1998 18:42:08 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id SAA14009; Tue, 7 Jul 1998 18:42:00 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199807080142.SAA14009@mango.parc.xerox.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: spork , John Polstra , hackers@FreeBSD.ORG Subject: Re: something screwed with CVSup.freebsd.org? In-reply-to: Your message of "Mon, 06 Jul 1998 05:04:02 PDT." <24529.899726642@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 7 Jul 1998 18:42:00 PDT From: Bill Fenner Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <24529.899726642@time.cdrom.com>you write: >Well, I'm a bit short of phone lines in there so what I'd *really* >like would be a single modem and an old Cisco cs500 that nobody's >using (or a multiport comms card) so that I can make a console server >to handle all our equipment. ;-) /usr/ports/comms/conserver, anyone? It's much nicer than a terminal server since it keeps a console history (e.g. no more connecting and being at the db> prompt and wondering how it got there...) and also complete console log files. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 02:05:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00478 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 02:05:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00466; Wed, 8 Jul 1998 02:05:51 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id WAA15414; Tue, 7 Jul 1998 22:10:46 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd015350; Tue Jul 7 22:10:37 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id WAA02478; Tue, 7 Jul 1998 22:10:31 -0700 (MST) From: Terry Lambert Message-Id: <199807080510.WAA02478@usr08.primenet.com> Subject: Re: lfs To: Matthew.Alton@anheuser-busch.com (Alton, Matthew) Date: Wed, 8 Jul 1998 05:10:31 +0000 (GMT) Cc: hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776603@STLABCEXG011> from "Alton, Matthew" at Jul 7, 98 11:52:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #define LFS_MAGIC 0x070162 > > So who was born on 01 JULY 1962? ;-) The magic number for NXFS is 0x010763 (01 Jul 1963); that's my birthday. I think you mean 07 Jan 1962.... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 02:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00558 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 02:06:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00541 for ; Wed, 8 Jul 1998 02:06:03 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id BAA04073; Wed, 8 Jul 1998 01:57:08 -0400 (EDT) From: "Allen Smith" Message-Id: <9807080157.ZM4071@beatrice.rutgers.edu> Date: Wed, 8 Jul 1998 01:57:08 -0400 In-Reply-To: Stefan Eggers "Someone working on swapoff?" (Jul 7, 9:56am) References: <199807070756.JAA07032@semyam.dinoco.de> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 7, 9:56am, Stefan Eggers (possibly) wrote: > Hi! > > Is there still anybody left working on swapoff? The only reference I > have in my mail archive is a mail from John mentioning this briefly > ("when I get swapoff working"). Now that he left the project does > anybody know what happened to this? > > It is really cruel to have to reboot a machine just because one uses a > swap file on a non-root filesystem and can't get back to multi user > from single user because the "mount -a" complains that the filesystem > is busy. And besides this I think there's something missing with this > asymmetry. Would just look more complete with it. :-) While I've been looking at this problem (and related ones, such as the idea of a swap device (using swapping via the vnode driver) that can expand and contract as necessary - put it on an MFS and the MFS effectively just got the ability to expand and contract) on and off, I have neither the time nor the experience with C needed for solving it. What it looks like is necessary is the following: A. an rlist_remove or whatever (put in kern/subr_rlist.c) that is capable of removing a specified resource list entry; this would be called multiple times (ideally, make it a macro or inline) to remove each of the entries associated (in vm/vm_swap.c's swaponvp's call of rlist_free) with the given swap device - ideally, one that could remove from the list entry only the last portion, for maximal flexibility with the aforementioned idea of expandable and contractable swap devices; B. either keeping track of the object entries associated with a given rlist entry (via a list associated with the rlist entry, allocated via a modified rlist_alloc - rlist_obj_alloc, perhaps? - in vm/swap_pager.c's swap_pager_getswappages), or a search through the swap_pager_object_list for objects occupying the given swap space; the former would take more memory, the latter would take more time; given today's relatively cheap memory, and that some kernel memory may be freeable by making some currently wired memory pageable (look at sys/malloc.h for a list of some memory types - most of the NFS stuff seems possible, for instance, so long as you're not swapping to it), I'd say the former is preferable; one would then do a swap_pager_getpages for each of the objects and pages that were on the swap device in question, fetching them into memory, followed by a swap_pager_putpages to put them back out onto another swap device (perhaps with a check to make sure nothing was waiting on the page in question - then do a wakeup instead, unless there was a swap space crunch). One thing that would be nice in all of this is to add a priority field to the rlist entries, or better yet multiple rlists for swap, with the kern/subr_rlist.c stuff being bright enough to check in order of priority. That way: A. somebody could have emergency swapping over NFS, with it only used if other swap space fills up - thus avoiding network latency et al; B. vnode pager swap space, which is less efficient than direct device swapping, could be used only after other swap space was used up; C. in my idea of expandable/contractable swap space, these could be used only after dedicated swap space filled up, thus maximizing effectiveness of disk space usage; and D. in your situation, swap devices you were wanting to later deallocate could be used last, resulting in less objects to swap in and out. The rlist stuff isn't currently used except in vm, at least in -stable, so changing it shouldn't pose any problems. > As I am at it: Any hints on good books, papers, whatever about paging > and swapping internals in BSD - especially FreeBSD? I'd be curious about this also; the existing information that I've found (in the 4.4 BSD book) is not exactly copious, and is somewhat outdated. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 02:18:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04299 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 02:18:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03889; Wed, 8 Jul 1998 02:17:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA02211; Wed, 8 Jul 1998 10:06:59 +0200 (CEST) To: "Alton, Matthew" cc: "'hackers@freebsd.org'" , "'freebsd-fs@freebsd.org'" Subject: Re: lfs In-reply-to: Your message of "Tue, 07 Jul 1998 23:52:47 BST." <31B3F0BF1C40D11192A700805FD48BF901776603@STLABCEXG011> Date: Wed, 08 Jul 1998 10:06:57 +0200 Message-ID: <2206.899885217@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <31B3F0BF1C40D11192A700805FD48BF901776603@STLABCEXG011>, "Alton, Mat thew" writes: >#define LFS_MAGIC 0x070162 > >So who was born on 01 JULY 1962? ;-) Margo ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 05:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18309 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 05:22:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.capgemini.com.sg ([203.116.11.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18255 for ; Wed, 8 Jul 1998 05:21:50 -0700 (PDT) (envelope-from fschan@capgemini.com.sg) Received: from capgemini.com.sg (MIS_FSCHAN.capgemini.com.sg [10.64.0.177]) by mail.capgemini.com.sg (post.office MTA v2.0 0813 ID# 0-16936) with ESMTP id AAA120 for ; Wed, 8 Jul 1998 20:18:11 +0800 Message-ID: <35A364B3.B900A520@capgemini.com.sg> Date: Wed, 08 Jul 1998 20:23:15 +0800 From: fschan@capgemini.com.sg (Chan, Fook Sheng) X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: NIC drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Just curious, how do one find the neccesary info to write a driver of say 3c509 fro FreeBSD? Regards, Fook Sheng To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 06:25:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29424 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 06:25:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA29419 for ; Wed, 8 Jul 1998 06:25:51 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA10305; Wed, 8 Jul 1998 09:24:33 -0400 Date: Wed, 8 Jul 1998 09:24:33 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: unattended install In-Reply-To: <199807071921.MAA01451@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike: could you post a sample install.cfg for the benefit of -hackers. many thanks ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 07:13:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04843 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 07:13:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aaka.3skel.com (aaka.3skel.com [207.240.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04836 for ; Wed, 8 Jul 1998 07:13:26 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by aaka.3skel.com (8.8.5/8.8.2) with ESMTP id KAA19937; Wed, 8 Jul 1998 10:13:19 -0400 (EDT) Received: from 3skel.com (localhost.3skel.com [127.0.0.1]) by fnur.3skel.com (8.8.8/8.8.2) with ESMTP id KAA06797; Wed, 8 Jul 1998 10:13:17 -0400 (EDT) Message-ID: <35A37E7C.7CF9404F@3skel.com> Date: Wed, 08 Jul 1998 10:13:17 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: permission confusion at mount points (and NFS) References: <199807031017.DAA15756@usr04.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > I personally think that the idea of mapping a vnode into an existing > directory hierarchy should *not* require acess to the existing > hierarchy to implement. > > My idea is that you seperate the act of mapping from the act of lookup; > this is a little inconvenience, in that you ignopre the mapping point > in favor of that which is mapped. It has the advantage that "X" replaces > "Y" instead of "X" predicates "Y". In more simple terms, it means that > the mounted FS permissions are checked instead of the mount point > permissions before acces is granted. > > This is really an issue of data hiding more than anything else, since > it has to do with when permissions are evaluated. > The last time I checked, this limitation is amplified in NFS. A filesystem mount point that is under an imported NFS mount will not show the contents. IRIX allows access to mount points in directories within an NFS mount. Has there been any consideration given to changing this behavior? Dan -- danj@3skel.com Dan Janowski Triskelion Systems, Inc. Bronx, NY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 07:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05157 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 07:15:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05148 for ; Wed, 8 Jul 1998 07:15:32 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with SMTP id KAA13439; Wed, 8 Jul 1998 10:15:14 -0400 (EDT) Date: Wed, 8 Jul 1998 10:15:14 -0400 (EDT) From: jack To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: unattended install In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Jul 1998, Ron G. Minnich wrote: > Mike: could you post a sample install.cfg for the benefit of -hackers. If you've got source you've got one. /usr/src/release/sysinstall/install.cfg -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null Mail from netcom.com blocked until they stop relaying SPAM -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 07:54:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09886 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 07:54:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA09849 for ; Wed, 8 Jul 1998 07:53:57 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA10978; Wed, 8 Jul 1998 10:53:24 -0400 Date: Wed, 8 Jul 1998 10:53:24 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: Re: unattended install In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Jul 1998, jack wrote: > If you've got source you've got one. > /usr/src/release/sysinstall/install.cfg thanks jack. This looks even easier than kickstart. I'll test later this month and let the list know how it goes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 08:38:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15270 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 08:38:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15265 for ; Wed, 8 Jul 1998 08:38:41 -0700 (PDT) (envelope-from sysadmin@greeves.mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id KAA01347 for ; Wed, 8 Jul 1998 10:38:37 -0500 (CDT) (envelope-from sysadmin@greeves.mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDAA5C.B307FC00@noc.mfn.org>; Wed, 8 Jul 1998 10:39:35 -0500 Message-ID: <01BDAA5C.B307FC00@noc.mfn.org> From: NOC-IPAD To: "'freebsd-hackers@freebsd.org'" Subject: Specifying ICMP Subtypes to IPFW Date: Wed, 8 Jul 1998 10:39:34 -0500 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 Greetings. There has been a recent thread (mine) on "questions" which has not been resolved - the last comment in this thread was from Doug White, "No Idea...". I need to know how to specify an ICMP subtype to IPFW, for instance, rather than killing *all* ICMPtype 3 messages using ipfw add 1 deny icmp from any to 123.123.123.0/24 icmptype 3 I need to kill only icmptype 3, subtype 11. How would I specify this? I have tried using icmptype 3.11, 3/11, 311, 3-11, etc... Thanks! J.A. Terranson sysadmin@mfn.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 08:55:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18226 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 08:55:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18219 for ; Wed, 8 Jul 1998 08:55:35 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id LAA09042; Wed, 8 Jul 1998 11:55:17 -0400 (EDT) Date: Wed, 8 Jul 1998 11:55:17 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Allen Smith cc: Stefan Eggers , freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? In-Reply-To: <9807080157.ZM4071@beatrice.rutgers.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Jul 1998, Allen Smith wrote: > > As I am at it: Any hints on good books, papers, whatever about paging > > and swapping internals in BSD - especially FreeBSD? > > I'd be curious about this also; the existing information that I've > found (in the 4.4 BSD book) is not exactly copious, and is somewhat > outdated. How about /usr/share/doc/papers/newvm.ascii.gz? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 09:08:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19899 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 09:08:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19892 for ; Wed, 8 Jul 1998 09:08:36 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-110.camalott.com [208.229.74.110]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA17320; Wed, 8 Jul 1998 11:08:27 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA02079; Wed, 8 Jul 1998 11:07:45 -0500 (CDT) (envelope-from joelh) Date: Wed, 8 Jul 1998 11:07:45 -0500 (CDT) Message-Id: <199807081607.LAA02079@detlev.UUCP> To: ben@rosengart.com CC: easmith@beatrice.rutgers.edu, seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Snob Art Genre on Wed, 8 Jul 1998 11:55:17 -0400 (EDT)) Subject: Re: Someone working on swapoff? From: Joel Ray Holveck References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> As I am at it: Any hints on good books, papers, whatever about paging >>> and swapping internals in BSD - especially FreeBSD? >> I'd be curious about this also; the existing information that I've >> found (in the 4.4 BSD book) is not exactly copious, and is somewhat >> outdated. > How about /usr/share/doc/papers/newvm.ascii.gz? The daemon book and newvm are good for 4.4BSD, but FreeBSD uses a different system based on the Mach paging internals. Any papers on Mach should suffice. Besides that, unless John's written a paper on it and hasn't told us, the best I can suggest there is to UTSL. (I may be able to dig up a small file giving an overview of the entry points to the VM system if you need it.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 09:08:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19941 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 09:08:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19923 for ; Wed, 8 Jul 1998 09:08:51 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00539; Wed, 8 Jul 1998 09:09:07 -0700 (PDT) Message-Id: <199807081609.JAA00539@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: fschan@capgemini.com.sg (Chan, Fook Sheng) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "Wed, 08 Jul 1998 20:23:15 +0800." <35A364B3.B900A520@capgemini.com.sg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Jul 1998 09:09:06 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > Just curious, how do one find the neccesary info to write a driver of > say 3c509 fro FreeBSD? You mean like, eg. /sys/i386/isa/if_ep.c? (The 3c509 driver.) You go to the manufacturer of the card, and you ask them for the programmer's reference manual for it. In some cases, you look at the card and the chip(s) on it, and go to the chip manufacturer instead. Many of them put their datasheets on the web. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 09:10:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20325 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 09:10:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20181 for ; Wed, 8 Jul 1998 09:09:58 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id SAA19928; Wed, 8 Jul 1998 18:04:47 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id IAA01081; Wed, 8 Jul 1998 08:31:38 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807080631.IAA01081@semyam.dinoco.de> Cc: David Kelly To: freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? In-reply-to: Your message of "Tue, 07 Jul 1998 19:38:27 CDT." <199807080038.TAA18009@nospam.hiwaay.net> Date: Wed, 08 Jul 1998 08:31:38 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > system, but would it be breaking sacred tradition to merge swapon and > the future swapoff into one "swap" management utility? The unified > utility could do swapon tasks if linked to the name "swapon" and > swapoff tasks if its named "swapoff". I think deciding on the name how to behave is not that good an idea in the first place. Besides this: How long would the swapoff in user land be? About 50 lines or less I'd guess. Merging is not worth any effort as it does save nothing in C code lines but adds more code to do the check the program name and call the corresponding code. What would then be worth talking about is replacing swapon with a new command for swap management. But that can wait till there is any need for this i.e. the kernel support for swapoff or priorities or something like that is at least nearly finished! For that such a merger might be worthwhile as the swapon functionalty would be in the new command already and one would have to support swapon for compatibility at least for a while. That's like pstat and swapinfo. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 09:11:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20720 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 09:11:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20694 for ; Wed, 8 Jul 1998 09:11:22 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00564; Wed, 8 Jul 1998 09:11:13 -0700 (PDT) Message-Id: <199807081611.JAA00564@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Ron G. Minnich" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: unattended install In-reply-to: Your message of "Wed, 08 Jul 1998 09:24:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Jul 1998 09:11:12 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike: could you post a sample install.cfg for the benefit of -hackers. /usr/src/release/sysinstall/install.cfg (add ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current in front if you don't have a local source tree) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 09:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23025 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 09:31:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23018 for ; Wed, 8 Jul 1998 09:31:13 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-110.camalott.com [208.229.74.110]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA18887; Wed, 8 Jul 1998 11:31:17 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA02208; Wed, 8 Jul 1998 11:29:32 -0500 (CDT) (envelope-from joelh) Date: Wed, 8 Jul 1998 11:29:32 -0500 (CDT) Message-Id: <199807081629.LAA02208@detlev.UUCP> To: mike@smith.net.au CC: fschan@capgemini.com.sg, freebsd-hackers@FreeBSD.ORG In-reply-to: <199807081609.JAA00539@antipodes.cdrom.com> (message from Mike Smith on Wed, 08 Jul 1998 09:09:06 -0700) Subject: Re: NIC drivers From: Joel Ray Holveck References: <199807081609.JAA00539@antipodes.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Just curious, how do one find the neccesary info to write a driver of >> say 3c509 fro FreeBSD? > You mean like, eg. /sys/i386/isa/if_ep.c? (The 3c509 driver.) Last I heard, the 509 driver was buggy. (According to LINT, it still is.) When I last tried it about eight months ago, it was still buggy. Cursory tests now (I've got one in this box, on the same LAN as an NE2000) indicate that it may still be broken. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 10:38:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02059 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 10:38:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02043 for ; Wed, 8 Jul 1998 10:38:34 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA02806; Wed, 8 Jul 1998 10:37:57 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002802; Wed Jul 8 10:37:37 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA29377; Wed, 8 Jul 1998 10:37:36 -0700 (PDT) From: Archie Cobbs Message-Id: <199807081737.KAA29377@bubba.whistle.com> Subject: Re: Specifying ICMP Subtypes to IPFW In-Reply-To: <01BDAA5C.B307FC00@noc.mfn.org> from NOC-IPAD at "Jul 8, 98 10:39:34 am" To: sysadmin@greeves.mfn.org (NOC-IPAD) Date: Wed, 8 Jul 1998 10:37:36 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 NOC-IPAD writes: > There has been a recent thread (mine) on "questions" which has > not been resolved - the last comment in this thread was from Doug White, > "No Idea...". > > I need to know how to specify an ICMP subtype to IPFW, for > instance, rather than killing *all* ICMPtype 3 messages using > > ipfw add 1 deny icmp from any to 123.123.123.0/24 icmptype 3 > > I need to kill only icmptype 3, subtype 11. How would I specify this? > > I have tried using icmptype 3.11, 3/11, 311, 3-11, etc... You must create a patch to add this functionality and apply it :-) :-) That is, ipfw doesn't currently support ICMP subtypes. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 11:30:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08039 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 11:30:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08034 for ; Wed, 8 Jul 1998 11:30:36 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id SAA08753; Wed, 8 Jul 1998 18:30:35 GMT Message-ID: <19980708113034.B8731@nuxi.com> Date: Wed, 8 Jul 1998 11:30:34 -0700 From: "David O'Brien" To: hackers@FreeBSD.ORG Subject: manually using procmail Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody know if a way to take a Berkeley mailbox-formated file and "pipe" it thru procmail so that it would be processed as if you received the mail the usual way? As long as Hub isn't allowing POPing, getting FreeBSD mail is painful; but would be if I could just copy hub:/var/mail/obrien to my local machine and have it procmail processed. I've tried ``cat obrien | procmail -Yf-'', but it treats the mbox as a single giant message. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 11:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09947 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 11:44:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ranma.nectar.com (nat.gulfsouth.verio.net [204.27.64.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09940 for ; Wed, 8 Jul 1998 11:44:27 -0700 (PDT) (envelope-from nectar@ranma.nectar.com) Received: from ranma.nectar.com (localhost.gulfsouth.verio.net [127.0.0.1]) by ranma.nectar.com (8.8.8/8.8.8) with ESMTP id NAA04723 for ; Wed, 8 Jul 1998 13:40:30 -0500 (CDT) Message-Id: <199807081840.NAA04723@ranma.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: multiple video cards & monitors? To: hackers@FreeBSD.ORG Date: Wed, 08 Jul 1998 13:40:29 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Does anyone have experience running a multiheaded FreeBSD box? Would one need to run one X server per video card? Would the video cards need to be the same brand / different brands? Any advice would be appreciated! Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNaO9HTeRhT8JRySpAQHNQgQAiuV+6CZQQsaSv53xUxCIYUfe+rPkPU6J uxTqoz5jl4KObYRMVr40/VdmzJ8SWLtDz4zk7/P/GjarkSQLL4MKc7Ij1KjeW1BP KFdM0JqqqZd610l7STbdFV1opScgHxiMepQc2VyYqsipbNbPiGPl4SObfwN2qnI6 rJRZfdBUgLc= =AEG5 -----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 Wed Jul 8 11:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11793 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 11:55:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11782 for ; Wed, 8 Jul 1998 11:55:03 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id NAA10012; Wed, 8 Jul 1998 13:54:53 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980708113034.B8731@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Jul 1998 13:53:08 -0500 To: obrien@NUXI.com From: Richard Wackerbarth Subject: Re: manually using procmail Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:30 PM -0500 7/8/98, David O'Brien wrote: >Does anybody know if a way to take a Berkeley mailbox-formated file and >"pipe" it thru procmail so that it would be processed as if you received >the mail the usual way? > >As long as Hub isn't allowing POPing, getting FreeBSD mail is painful; >but would be if I could just copy hub:/var/mail/obrien to my local >machine and have it procmail processed. > >I've tried ``cat obrien | procmail -Yf-'', but it treats the mbox as a >single giant message. Off the top of my head, I think you need "formail". In any case, there was a description of just this sort of thing in the documentation that came with the package. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12871 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:05:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from superior.mooseriver.com (dynamic28.pm05.sf3d.best.com [209.24.235.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12866 for ; Wed, 8 Jul 1998 12:05:42 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id MAA15378; Wed, 8 Jul 1998 12:05:40 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980708120539.A15241@mooseriver.com> Date: Wed, 8 Jul 1998 12:05:39 -0700 From: Josef Grosch To: obrien@NUXI.com, hackers@FreeBSD.ORG Subject: Re: manually using procmail Reply-To: jgrosch@superior.mooseriver.com References: <19980708113034.B8731@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980708113034.B8731@nuxi.com>; from David O'Brien on Wed, Jul 08, 1998 at 11:30:34AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 11:30:34AM -0700, David O'Brien wrote: > Does anybody know if a way to take a Berkeley mailbox-formated file and > "pipe" it thru procmail so that it would be processed as if you received > the mail the usual way? > > As long as Hub isn't allowing POPing, getting FreeBSD mail is painful; > but would be if I could just copy hub:/var/mail/obrien to my local > machine and have it procmail processed. > > I've tried ``cat obrien | procmail -Yf-'', but it treats the mbox as a > single giant message. > Yes, this is how I get my mail from Best. The magic incantation is formail -s procmail < mail_file If interested I can provide the Perl script I use to grab my mail. Josef -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15891 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:34:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from niobe.ewox.org (ppp032.uio.no [129.240.240.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15884 for ; Wed, 8 Jul 1998 12:34:41 -0700 (PDT) (envelope-from finrod@niobe.ewox.org) Received: (from finrod@localhost) by niobe.ewox.org (8.8.8/8.8.8) id VAA26052; Wed, 8 Jul 1998 21:34:27 +0200 (CEST) (envelope-from finrod) To: hackers@FreeBSD.ORG Subject: Y2K compliance Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: finrod@niobe.ewox.org (Dag-Erling Coidan Smørgrav) Date: 08 Jul 1998 21:34:26 +0200 Message-ID: <86yau4b0hp.fsf@niobe.ewox.org> Lines: 32 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I feel like committing the following patch to /usr/src/release/Makefile: Index: Makefile =================================================================== RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.359 diff -u -r1.359 Makefile --- Makefile 1998/06/26 18:54:06 1.359 +++ Makefile 1998/07/08 18:54:19 @@ -17,7 +17,7 @@ #BUILDNAME=2.2-RELEASE # # Automatic SNAP versioning: -DATE != date +%y%m%d +DATE != date +%Y%m%d BASE = 3.0 BUILDNAME?=${BASE}-${DATE}-SNAP # I mentioned this to Jordan once before I got commits, but his reply was "we'll get around to it some day". Niobe is running make release with that patch right now, but I don't think I'll encounter any trouble. The only thing I can think of that it might break is ordering, i.e. if anybody is relying on collating order to sort snapshots, since 1998 is lexically less than 98. Comments? DES -- Sorry, no .sig today. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17344 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:43:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17339 for ; Wed, 8 Jul 1998 12:43:53 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with SMTP id PAA14323; Wed, 8 Jul 1998 15:43:40 -0400 (EDT) Date: Wed, 8 Jul 1998 15:43:40 -0400 (EDT) From: jack To: "David O'Brien" cc: hackers@FreeBSD.ORG Subject: Re: manually using procmail In-Reply-To: <19980708113034.B8731@nuxi.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, 8 Jul 1998, David O'Brien wrote: > Does anybody know if a way to take a Berkeley mailbox-formated file and > "pipe" it thru procmail so that it would be processed as if you received > the mail the usual way? Haven't read man procmail(1), have we? :) Procmail can also be invoked to postprocess an already filled system mailbox. This can be useful if you don't want to or can't use a $HOME/.forward file (in which case the following script could periodically be called from within cron(1), or whenever you start reading mail): #!/bin/sh ORGMAIL=/var/mail/$LOGNAME if cd $HOME && test -s $ORGMAIL && lockfile -r0 -l1024 .newmail.lock 2>/dev/null then trap "rm -f .newmail.lock" 1 2 3 13 15 umask 077 lockfile -l1024 -ml cat $ORGMAIL >>.newmail && cat /dev/null >$ORGMAIL lockfile -mu formail -s procmail <.newmail && rm -f .newmail rm -f .newmail.lock fi exit 0 -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null Mail from netcom.com blocked until they stop relaying SPAM -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:44:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17633 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:44:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17599 for ; Wed, 8 Jul 1998 12:44:40 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA09868; Wed, 8 Jul 1998 21:41:57 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA28323; Wed, 8 Jul 1998 21:31:43 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807081931.VAA28323@semyam.dinoco.de> Cc: ben@rosengart.com, Stefan Eggers To: freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? In-reply-to: Your message of "Wed, 08 Jul 1998 11:55:17 EDT." Date: Wed, 08 Jul 1998 21:31:43 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about /usr/share/doc/papers/newvm.ascii.gz? Too shallow for my taste. Besides that no mentioning of the coloring of pages. :-( It's a document in which one expresses the general idea of the new VM but nothing more. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17791 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:45:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17692 for ; Wed, 8 Jul 1998 12:44:57 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA09862; Wed, 8 Jul 1998 21:41:55 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA25030; Wed, 8 Jul 1998 21:28:15 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807081928.VAA25030@semyam.dinoco.de> Cc: Joel Ray Holveck To: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? In-reply-to: Your message of "Wed, 08 Jul 1998 11:07:45 CDT." <199807081607.LAA02079@detlev.UUCP> Date: Wed, 08 Jul 1998 21:28:13 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How about /usr/share/doc/papers/newvm.ascii.gz? > > The daemon book and newvm are good for 4.4BSD, but FreeBSD uses a > different system based on the Mach paging internals. Any papers on > Mach should suffice. I looked for technical reports on this matter from CMU but have not found one dealing with VM, yet. :-( But maybe I find something in the next few weeks. > Besides that, unless John's written a paper on it and hasn't told us, > the best I can suggest there is to UTSL. (I may be able to dig up a That's exactly the method I am using at present and which I think isn't that bad. But a map of the terrain would of course make the task a little bit easier. ;-) I started to read it a bit today and must say it looks pretty under- standable for such a beast. I don't expect it to be too hard. The hardest part will be to get FreeBSD-current on a 386/33 (the machine I intend to use for testing) with the least financial effort. :-) Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 12:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18368 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 12:47:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18341 for ; Wed, 8 Jul 1998 12:47:06 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA19556; Wed, 8 Jul 1998 13:46:59 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA03036; Wed, 8 Jul 1998 13:46:52 -0600 Date: Wed, 8 Jul 1998 13:46:52 -0600 Message-Id: <199807081946.NAA03036@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: obrien@NUXI.com Cc: hackers@FreeBSD.ORG Subject: Re: manually using procmail In-Reply-To: <19980708113034.B8731@nuxi.com> References: <19980708113034.B8731@nuxi.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anybody know if a way to take a Berkeley mailbox-formated file and > "pipe" it thru procmail so that it would be processed as if you received > the mail the usual way? Sure, I've got a script that does it. #!/bin/sh formail -s procmail < $1 Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 13:43:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25768 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 13:43:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25748 for ; Wed, 8 Jul 1998 13:43:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00362; Wed, 8 Jul 1998 13:34:31 -0700 (PDT) Message-Id: <199807082034.NAA00362@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joel Ray Holveck cc: mike@smith.net.au, fschan@capgemini.com.sg, freebsd-hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "Wed, 08 Jul 1998 11:29:32 CDT." <199807081629.LAA02208@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Jul 1998 13:34:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Just curious, how do one find the neccesary info to write a driver of > >> say 3c509 fro FreeBSD? > > You mean like, eg. /sys/i386/isa/if_ep.c? (The 3c509 driver.) > > Last I heard, the 509 driver was buggy. (According to LINT, it still > is.) When I last tried it about eight months ago, it was still buggy. > Cursory tests now (I've got one in this box, on the same LAN as an > NE2000) indicate that it may still be broken. Yes; the driver is not spectacular, and neither is the card. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 13:43:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25798 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 13:43:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25763 for ; Wed, 8 Jul 1998 13:43:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-130.camalott.com [208.229.74.130]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA01033; Wed, 8 Jul 1998 15:43:54 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA00578; Wed, 8 Jul 1998 15:43:09 -0500 (CDT) (envelope-from joelh) Date: Wed, 8 Jul 1998 15:43:09 -0500 (CDT) Message-Id: <199807082043.PAA00578@detlev.UUCP> To: Stefan Eggers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? From: Joel Ray Holveck In-reply-to: <199807081928.VAA25030@semyam.dinoco.de> References: <199807081607.LAA02079@detlev.UUCP> <199807081928.VAA25030@semyam.dinoco.de> <199804070553.AAA10297@dyson.iquest.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Remember that this doc was old when I got it in April. Happy hacking, joelh ------- Start of forwarded message ------- From: "John S. Dyson" Subject: Re: swap-leak in 2.2.5 ? To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 7 Apr 1998 00:53:33 -0500 (EST) Cc: joelh@gnu.org, toor@dyson.iquest.net Message-Id: <199804070553.AAA10297@dyson.iquest.net> > > A lot of what I'm asking is stuff that is fairly basic to the VM > > system, and not really that related to monitoring. Have you a white > > paper (or something that serves the same function) on FreeBSD VM? > > (You said that you don't have something on monitoring, but if you can > > point me to something else it may help.) > > > I'll append a doc that talks about entry points, etc. However, the > MACH VM is probably the best intro to FreeBSD VM. They are similar, > (but FreeBSD is more specific to U**X), and the terminology is similar. > Sorry about not appending the out-of-date roadmap doc!!! Here it is: Here is a very rough description of the FreeBSD MACH-based VM system internals... This document is not definitive, but meant as a quick reference or overview. The source code is currently the ONLY definitive documentation. If there is enough positive feedback from this document, I might be motivated enough to fill this in with more detail. Routines or symbols that will probably be supported forever in one way or another have a "SUPPORTED" notation. Those routines that could be at risk sometime in the future have no such notation. Definitions: Data Structure Equivalent vm_map ............... Address space vm_map_entry ......... Portion of address space pointing to only one vm_object or another vm_map vm_object ............ Repository for data vm_page .............. Indivisible amount of data pmap ................. Physical representation of Address space (Note that the names above, with "_t" appended refer to pointers as opposed to the structure itself... e.g. vm_map_t is a pointer to a struct vm_map.) Terminology Equivalent pager ................ A sort-of class that is described by information in the vm_object and the type of access to external data vnode_pager .......... Code in the vm system that knows how to do paging I/O with filesystem files. swap_pager ........... Code in the vm system that knows how to do paging I/O with swap partitions and files. Anonymous data in the system (e.g. bss) is paged using this. default_pager ........ A logical "placeholder" pager that takes few system resources until paging is needed. The default_pager is currently used only for vm_object's that might need to be paged using the swap_pager. When pageouts are needed, objects that are marked "default" are converted to "swap" with the associated allocation of swap data structures. device_pager ......... Code in the vm system that can provide memory mapped I/O with memory mapped devices. Most common use of this is X-Windows. kva .................. Kernel virtual address, usually of type vm_offset_t or caddr_t. sva,eva,va ........... Virtual address(s). sva - start virtual address, eva - end virtual address. pa ................... Physical address. m,p .................. Usually used for vm_page_t. offset ............... Offsets into objects are usually vm_ooffset_t, which translates into a long long (equiv to the filesystem off_t.) wired ................ Not pageable. clean ................ (As in "the page is clean"), means it is in sync with the backing store. page_coloring ........ Unless a VM system provides special support for direct mapped caches, the system will often allocate pages suboptimally for machines with such caching schemes. The term "page_coloring" as I use it, consists of various ways that the system provides support for improving utilization of system caches. FreeBSD provides support for processor caches that helps even the more sophisticated 4-way caching schemes (as in a PPro.) Useful "handles" describing address spaces: (warning -- in the most general case, you should make sure that there is a "curproc"!!!). If your code is being called from a system call or I/O initiation routine, you should be safe. Current process address space (vm_map_t): (SUPPORTED) &curproc->p_vmspace->vm_map Current process pmap (pmap_t): (SUPPORTED) &curproc->p_vmspace->vm_pmap Kernel address space (vm_map_t): (SUPPORTED) kernel_map Kernel pmap (pmap_t): (SUPPORTED) kernel_pmap, (best referred to as vm_map_pmap(kernel_map)) Less commonly used "handles": Address spaces (submaps of kernel_map, unless noted otherwise): never checked for modification: clean_map buffer cache: buffer_map (submap of clean_map) pager and cluster buffers: pager_map (submap of clean_map) used for bounce buffers: io_map (submap of clean_map) malloc and mbuf cluster area: kmem_map mbuf clusters: mb_map (submap of kmem_map) args during exec: exec_map temporary mapping of exec hdr: exech_map UPAGES per process: upage_map Important macros: pa = VM_PAGE_TO_PHYS(m); (SUPPORTED) returns the physical address for a vm_page_t. m = PHYS_TO_VM_PAGE(pa); returns the vm_page_t associated with a physical address. (try to avoid PHYS_TO_VM_PAGE -- it doesn't always work, because not every physical address has a page, and it usually implies a design flaw, or a quick work-around that needs to be corrected in the future.) PAGE_WAKEUP(m); (SUPPORTED) This is used to free the lock on a page as represented by the PG_BUSY bit. Other processes that are waiting on that page are waken up. In order to wait on a page the following could be done: s = splhigh(); while ((m->flags & PG_BUSY) || m->busy) { m->flags |= PG_WANTED; tsleep(m, PVM, "xxxxxx", 0); } splx(s); You would do that normally after a vm_page_lookup. VM_WAIT; (SUPPORTED) Use this if you have tried to do a vm_page_alloc in non-interrupt state, and vm_page_alloc did not return a vm_page_t pointer (vm_page_alloc returns NULL on failure.) VM_WAIT blocks your process and wakes up the pageout daemon. When this returns, there likely will have some memory, so vm_page_alloc can be retried. Likely return values from most of the vm routines : KERN_SUCCESS, KERN_INVALID_ADDRESS, KERN_PROTECTION_FAILURE, KERN_NO_SPACE, KERN_INVALID_ARGUMENT, KERN_FAILURE, KERN_RESOURCE_SHORTAGE, KERN_NOT_RECEIVER?, KERN_NO_ACCESS? Important X86 tidbit: The kernel_pmap is always effectively mapped into the user's pmap. When referring to kernel space, one should use the kernel_pmap, and all processes will see the change in the kernel. Memory queues: vm_page_queue_free -- free pages vm_page_queue_zero -- free pages that are zero vm_page_queue_cache -- free pages that still have info may NOT be BUSY or mapped. vm_page_queue_active -- active pages vm_page_queue_inactive -- inactive pages Commonly needed VM system routines: int vm_map_find(map, object, offset, addr, length, find_space, prot, max, cow); (SUPPORTED) This finds AND allocates virtual space from the specified map (Address space). The user can optionally specify a vm object to map into the space (e.g. mapped file.) The parameters associated with the address space include: map -- The specific vm_map_t involved with the op addr -- Ptr to the address in the vm_map length -- Length of the mapping in bytes Note that the address (addr) above is equivalent to the address in a process or in the kernel. If the address is >= VM_MIN_KERNEL_ADDRESS you MUST use kernel_map, and not &curproc->p_vmspace->vm_map!!! Secondary note, unless you *really* know what you are doing, do not do a vm_map_find in the kernel map. Please use kmem_alloc instead. If you specify an initial value for addr, and find_space is zero, then the allocation request will succeed only if there is enough virtual address space available at the specified address. The parameters associated with the vm object: object -- Optional VM object -- if NULL, a default pager object will be created as needed when a fault happens thereby making the object necessary (an container for the page.) offset -- Offset into the object (long long, vm_ooffset_t) Additional parameters modifying the operation of the routine: find_space -- If there is no space at 'addr', space is found after that place. prot,max -- R/W permissions to address space: VM_PROT_READ, VM_PROT_WRITE, VM_PROT_EXEC cow -- Copy-on-write, original obj is NOT modified. Error returns: KERN_SUCCESS -- Operation completed KERN_INVALID_ADDRESS -- Address specified is invalid KERN_NO_SPACE -- No space in the map int vm_map_remove(map, start, end); (SUPPORTED) This routine deallocates the virtual space between start and end. All objects that are backing this space are deallocated as appropriate. This is sort-of inverse of vm_map_find above. Always returns KERN_SUCCESS. int vm_map_protect(map, start, end, new_prot, set_max); (SUPPORTED) Changes the access permissions for a virtual address range in the specified map. This routine makes all necessary modfications to the pmap associated with the map also. int vm_map_pageable(map, start, end, new_pageable); (SUPPORTED) Allows sections of a map to be wired or unwired into memory. int vm_map_check_protection(map, start, end, protection); (SUPPORTED) Allows an address range to be checked for specified protection attributes. int vm_map_lookup(map, addr, fault_type, out_entry, object, pindex, out_prot, wired, single_use); (SUPPORTED) This is a routine that provides functionality more than the name implies. The routine does return the map entry associated with (map, addr) pair. But, vm_map_lookup also does much of the work necessary to create an object for the map entry (in much of the VM code, objects are created in a lazy fashion -- only when needed), and also performs much of the work for COW. If the fault_type is a write fault, a new object might be created to support the local copy of a COW map entry (e.g. .data segment of an executable.) vm_page_t vm_page_alloc(object, pindex, flags); (SUPPORTED) flags -- VM_ALLOC_NORMAL normal process allocation VM_ALLOC_SYSTEM preferential allocation VM_ALLOC_INTERRUPT allocate interrupt-safely VM_ALLOC_ZERO normal process with priority to zero pages NON-BLOCKING. This is the lowest level page allocation routine. A NULL is returned if the allocation cannot be currently satisified. The pages are returned to the user with the PG_BUSY bit set and are not on any queue. After allocating the page, it is a good idea to issue a PAGE_WAKEUP(m) on the page, and at least wire the page. vm_page_alloc has support for page coloring built-in so that the system will choose pages more selectively than the usual ad-hoc schemes previously used. void vm_page_free(object, pindex); (SUPPORTED) This is the lowest level page free routine. This routine does NOT remove ANY mappings associated with the page. Chaos will ensue if the page is not properly removed from all pmap's. A normally used page can be removed from all pmap's by a vm_page_protect(m,VM_PROT_NONE); However, kernel mappings must be removed one-by-one, and must be manually tracked. void vm_page_activate(m); void vm_page_deactivate(m); void vm_page_cache(m); void vm_page_wire(m); (SUPPORTED) NON-BLOCKING. These are the queue manipulation routines. These are used to affect the policy of the paging and allocation system. If a page is activated, it is not likely to be freed soon. If it is deactivated, it will more likely be used. Cached pages are similar to freed pages, available for allocation, but still have their identity for quick reuse. If a page is not in one of the other states for a long time, it is best to wire it so the system can at least account for it. A page that is wired is "hidden" from the pageout daemon. vm_object_t vm_object_allocate(type, size); type -- OBJT_DEFAULT, default -- converts to swap OBJT_VNODE, vnode object OBJT_SWAP, swap object OBJT_DEVICE, device object This is the routine that creates an object. The user should only normally be used create objects of type OBJT_DEFAULT. Note that the size is in units of pages. vm_object_t vm_pager_allocate(type, handle, size, prot, foff); (SUPPORTED) type -- OBJT_DEFAULT, default -- converts to swap OBJT_VNODE, vnode object OBJT_SWAP, swap object OBJT_DEVICE, device object This is the routine that creates an object and associates the object with a file. If the object already exists, the reference count for the object will be incremented. In the case of a vnode object, the handle is the vnode pointer, and the foff and prot are both ignored. In the case of a swap object the handle is a unique 32bit number (probably address), and the foff and prot are both ignored. The handle for a device object is likely the device vnode, the prot is the protection that the memory device can support, and the foff is the offset into the device. vm_object_deallocate(object); (SUPPORTED) This routine decrements the reference bit for the object, potentially freeing it. vm_page_protect(m, prot); (SUPPORTED) Used to turn off permissions for pages mapped into processes. vm_page_protect(m, VM_PROT_READ) helps implement COW, and vm_page_protect(m, VM_PROT_NONE) is an important step in freeing pages. vm_fault(map, vaddr, fault_type, change_wiring); (SUPPORTED) Does the things necessary to bring a page into a processes address space. The most common use of this routine is in the trap code to implement demand-paging. Most normal driver or system use would be as follows: vm_fault(map, vaddr, VM_PROT_READ or (VM_PROT_READ|VM_PROT_WRITE), 0); KMEM series of operations (meant to be used on kernel_map or submaps of kernel_map), they always return page aligned addresses. kva = kmem_alloc(map, size); kva = kmem_alloc_pageable(map, size); (SUPPORTED) kmem_alloc and kmem_alloc_pageable each allocate space from the kernel_map (or any of it's submaps except kmem_map). kmem_alloc allocates both kva space and memory, while kmem_alloc_pageable allocates only kva space. If memory is being allocated (instead of just virtual space), you should generally use kmem_alloc. kmem_alloc_pageable does not do all of the correct things in all cases for the setup of the underlying kernel_object offset. It is best to use kmem_alloc_pageable when you plug the pages directly into the kernel address space. kmem_free(map,addr,size); (SUPPORTED) Use kmem_free to give back the kernel address space as allocated by kmem_alloc or kmem_malloc. Be careful to remove any mappings specifically created by pmap_enter before freeing the address range. It is especially important to be careful when using kmem_free after allocating kva space with kmem_alloc_pageable. kva = kmem_malloc(map, size, waitflag); Use this special form of kmem_alloc for kmem_map or mb_map. Except for current usage, it is best not to use kmem_malloc in new kernel extensions. It is best to use malloc/free for things that you CAN use kmem_malloc for. MALLOC/FREE (refer to /sys/sys/malloc.h for available types.) These return aligned memory, but not necessarily on 1 page boundaries. kva = malloc(size, type, flags); (SUPPORTED) flags = M_NOWAIT (call like this from interrupt level.) = M_KERNEL (preferential allocation of memory.) = M_WAITOK (normal call for non-interrupt level.) malloc is callable using M_NOWAIT from both splbio and splimp interrupt levels. (void) free(kva, type); (SUPPORTED) The kva specified to free must be identical to the one returned by malloc. The type likewise should be the same, otherwise malloc usage accounting will not work correctly (and the system will likely panic.) The kernel malloc/free routines do not deal well with partial frees of malloced entities. If that capability is needed, then the kmem_alloc/kmem_free routines would be better choices. PMAP routines. These routines are the lowest level defined interface to the processor memory management hardware. Given the virtual addresses have been set-up correctly, pmap can be kernel_pmap, the current processes' pmap or in some cases, another processes pmap. void pmap_enter(pmap, va, pa, prot, wired); (SUPPORTED) map a single page into the physical address space. void pmap_remove(pmap, sva, eva); (SUPPORTED) remove a range of pages from the physical address space. pa = pmap_extract(pmap, va); (SUPPORTED) get the physical address associated with the specified mapped page. pa = pmap_kextract(va); (SUPPORTED) same as pmap_extract, except is much more efficient and works only for the kernel_pmap (assuming the kernel space.) va = pmap_map(va, startp, endp, prot); (SUPPORTED) map a contiguous range of pages from physical address startp through endp at virtual address va. The returned address points to the next address that can be used for mapping. pmap_protect(pmap, sva, eva, prot); (SUPPORTED) Removes permissions from page protections on pages in the specified range. It does NOT remove protections for other pmaps on the pages. pmap_qenter(va, m, count); pmap_qremove(va, count); (PROBABLY SUPPORTED) pmap_qenter/pmap_qremove are used for fast kernel mappings of vm_page's allocated from the VM system. The implied pmap is kernel_pmap, and must refer to va's that are >= VM_MIN_KERNEL_ADDRESS. Usually one would use address that were returned by kmem_alloc_pageable. The second argument to pmap_qenter is a pointer to an array of pages. This is used often in the buffer cache code for quick mapping of vm_page_t's. pmap_kenter(va, pa); pmap_kremove(va); (PROBABLY SUPPORTED) pmap_kenter/pmap_kremove are used for fast kernel mappings. The implied pmap is kernel_pmap and must refer to va's that are >= VM_MIN_KERNEL_ADDRESS. Usually one would use address that were returned by kmem_alloc_pageable. pmap_growkernel(topaddr); This routine supports the creation of additional pagetable pages to encompass the address "topaddr". Kind-of the equiv of sbrk for the kernel. FreeBSD does not need to preallocate all of the needed kernel pagetables up-front because of this routine. pmap_destroy(pmap); Decrements pmap ref-count, and if zero, destroy's it. pmap_reference(pmap); Increments pmap ref-count. pmap_pinit(pmap) Creates a pmap. pmap_object_init_pt(pmap, addr, object, pindex, size); Prefaults pages into a processes pmap. If the pages are in memory, they are placed directly into a processes address space. This is called at mmap time. pmap_prefault(pmap, addra, entry, object); Prefaults pages into a processes pmap. This only places pages that are in a region around the specified address. This is called at vm_fault time. pmap_change_wiring(pmap, va, wired); This notates the page as being wired. This DOES NOT actually wire the page. pmap_copy(dst_pmap, src_pmap, dst_addr, len, src_addr); This is a routine that might be used to short-circuit faulting pages into an address space from another. It is currently NOT used. pmap_zero_page(dstpa); (SUPPORTED) This is the routine that is used to zero a page for demand zero. pmap_copy_page(srcpa,dstpa); (SUPPORTED) This is the routine that is used to copy a page for COW. pmap_pageable(pmap, sva, eva, pageable); This notates a range of pages as being pageable and is information. It is currently NOT used. pmap_page_protect(dstpa, prot); Decreases (and now increases) the protection for a given page. It is used to remove a page from all address spaces (for example, prior to being freed), or to write-protect (for example, for setting up an address space for COW.) This routine should not normally be used, vm_page_protect is vastly superior. The pte bit routines below are much more complicated than they appear, because they have to check the pte's for each page in every pmap that the page is mapped. pmap_is_referenced(srcpa); (SUPPORTED) Senses the reference bit on a given page. pmap_is_modified(srcpa); (SUPPORTED) Senses the modified bit on a given page. pmap_clear_modify(dstpa); (SUPPORTED) Clears the modified bit for a given page. pmap_clear_reference(dstpa); (SUPPORTED) Clears the reference bit for a given page. kva = pmap_mapdev(pa, size); (SUPPORTED) Maps device memory into the kernel. kva space is allocated, and the physical device is mapped directly into the kernel_pmap ptes. This allows full memory access to the device from the kernel. Additional miscellaneous routines that are useful to kernel developers, but refer to them in the source. They most likely will be around for a "long time." vmspace_alloc(min, max, pageable); vmspace_free(vm); vm_map_reference(map); vm_map_deallocate(map); vm_map_insert(map, object, offset, start, end, prot, max, cow); vm_map_findspace(map, start, length, addr); vm_map_lookup(map, address, entry); vm_map_inherit(map, start, end, new_inheritance); vm_map_clean(map, start, end, syncio, invalidate); ------- End of forwarded message ------- -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 15:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05026 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 15:01:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04999 for ; Wed, 8 Jul 1998 15:01:17 -0700 (PDT) (envelope-from sysadmin@greeves.mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id RAA00489; Wed, 8 Jul 1998 17:00:54 -0500 (CDT) (envelope-from sysadmin@mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDAABB.E0597FD0@noc.mfn.org>; Wed, 8 Jul 1998 22:00:53 -0500 Message-ID: <01BDAABB.E0597FD0@noc.mfn.org> From: NOC-IPAD To: NOC-IPAD , "'Archie Cobbs'" Cc: "freebsd-hackers@FreeBSD.ORG" Subject: RE: Specifying ICMP Subtypes to IPFW Date: Wed, 8 Jul 1998 22:00:52 -0500 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 Hrmmm... OK. I may do that. I am surprised however, since IPFW *does* support subtypes in it's reporting: i.e., we routinely log packets such as "3.1" or "3.3". I am assuming of course that IPFW's use of the tag "3.1" is a reference to icmptype3, subtype 1; am I incorrect? Yours, J.A. Terranson sysadmin@mfn.org ---------- From: Archie Cobbs Sent: Wednesday, July 08, 1998 12:37 PM To: NOC-IPAD Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Specifying ICMP Subtypes to IPFW NOC-IPAD writes: > There has been a recent thread (mine) on "questions" which has > not been resolved - the last comment in this thread was from Doug White, > "No Idea...". > > I need to know how to specify an ICMP subtype to IPFW, for > instance, rather than killing *all* ICMPtype 3 messages using > > ipfw add 1 deny icmp from any to 123.123.123.0/24 icmptype 3 > > I need to kill only icmptype 3, subtype 11. How would I specify this? > > I have tried using icmptype 3.11, 3/11, 311, 3-11, etc... You must create a patch to add this functionality and apply it :-) :-) That is, ipfw doesn't currently support ICMP subtypes. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 16:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14643 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 16:20:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14635 for ; Wed, 8 Jul 1998 16:20:23 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA01525; Wed, 8 Jul 1998 16:20:21 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd001461; Wed Jul 8 16:20:17 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA27772; Wed, 8 Jul 1998 16:20:10 -0700 (MST) From: Terry Lambert Message-Id: <199807082320.QAA27772@usr02.primenet.com> Subject: Re: Y2K compliance To: finrod@niobe.ewox.org (Dag-Erling Coidan Sm?rgrav) Date: Wed, 8 Jul 1998 23:20:09 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <86yau4b0hp.fsf@niobe.ewox.org> from "Dag-Erling Coidan Sm?rgrav" at Jul 8, 98 09:34:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Niobe is running make release with that patch right now, but I don't > think I'll encounter any trouble. The only thing I can think of that > it might break is ordering, i.e. if anybody is relying on collating > order to sort snapshots, since 1998 is lexically less than 98. > > Comments? Yes. If they are using "sort" instead of "sort -n", they are a loon. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 16:47:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18084 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 16:47:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pandora.lovett.com (root@pandora.eng.demon.net [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18079 for ; Wed, 8 Jul 1998 16:47:15 -0700 (PDT) (envelope-from ade@demon.net) Received: from pandora.eng.demon.net ([38.155.241.3] helo=pandora.lovett.com ident=ade) by pandora.lovett.com with esmtp (Exim 1.92 #1) for hackers@freebsd.org id 0yu3vd-00028W-00; Wed, 8 Jul 1998 18:47:13 -0500 To: hackers@FreeBSD.ORG Subject: Internal modem on Fujitsu Lifebook 280DX Organization: Demon Internet Reply-To: ade@demon.net Date: Wed, 08 Jul 1998 18:47:13 -0500 From: Ade Lovett Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Anyone had any experiences of getting the internal modem on a Fujitsu Lifebook 200-series to identify itself to FreeBSD -- I've done a couple of searches through the mail archives, but nothing obvious turned up On booting (with 2.2.6-stable), it appears as some kind of PCI device: pci0:16: vendor=0x11c1, device=0x0440, class=comms, subclass=0x80 int a irq 9 [no driver assigned] and pciconf -l reports similar information: pci0:16:0: class=0x078000 card=0x044011c1 chip=0x44011c1 rev=0x00 hdr=0x00 Making matters slightly more complicated is that there also appear to be a number of other internal devices hooked to irq 9, namely the two PCI<->Cardbus bridges (one on int a, the other on int b), and a USB controller (on int d) Any suggestions for getting this beastie working, or am I doomed to go get a PC-Card modem? -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 17:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20869 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 17:06:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20864 for ; Wed, 8 Jul 1998 17:06:40 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA06774; Wed, 8 Jul 1998 17:06:09 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma006770; Wed Jul 8 17:05:59 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA04794; Wed, 8 Jul 1998 17:05:49 -0700 (PDT) From: Archie Cobbs Message-Id: <199807090005.RAA04794@bubba.whistle.com> Subject: Re: Specifying ICMP Subtypes to IPFW In-Reply-To: <01BDAABB.E0597FD0@noc.mfn.org> from NOC-IPAD at "Jul 8, 98 10:00:52 pm" To: sysadmin@greeves.mfn.org (NOC-IPAD) Date: Wed, 8 Jul 1998 17:05:49 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 NOC-IPAD writes: > Hrmmm... OK. I may do that. I am surprised however, since > IPFW *does* support subtypes in it's reporting: i.e., we routinely > log packets such as "3.1" or "3.3". I am assuming of course that > IPFW's use of the tag "3.1" is a reference to icmptype3, subtype 1; > am I incorrect? You are correct. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 18:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01796 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 18:44:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aaka.3skel.com (aaka.3skel.com [207.240.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01790 for ; Wed, 8 Jul 1998 18:44:06 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by aaka.3skel.com (8.8.5/8.8.2) with ESMTP id VAA20621; Wed, 8 Jul 1998 21:44:03 -0400 (EDT) Received: from 3skel.com (localhost.3skel.com [127.0.0.1]) by fnur.3skel.com (8.8.8/8.8.2) with ESMTP id VAA24758; Wed, 8 Jul 1998 21:44:03 -0400 (EDT) Message-ID: <35A42062.D658B154@3skel.com> Date: Wed, 08 Jul 1998 21:44:02 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: jack CC: hackers@FreeBSD.ORG Subject: Re: manually using procmail References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is quite correct, or your mail can end up like an asphalt frog in Austrailia. Dan jack wrote: > On Wed, 8 Jul 1998, David O'Brien wrote: > > Haven't read man procmail(1), have we? :) > > exit 0 > -- danj@3skel.com Dan Janowski Triskelion Systems, Inc. Bronx, NY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 19:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08181 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 19:39:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08174 for ; Wed, 8 Jul 1998 19:38:58 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id WAA15990; Wed, 8 Jul 1998 22:36:02 -0400 (EDT) Date: Wed, 8 Jul 1998 22:36:02 -0400 (EDT) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: Network driver question 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 Okay, I'm confused. I have got the tokenring driver passing packets up to the higher network layers but to no avail. If I receive and arp packet it should be fed to the arp layer and result in an arp packet begin generated and sent back, but the output routine is never being called. The same for IP packets. I am pretty sure things are working correctly up to that point because tcpdump is printing the incoming packets on the interface (well trying to anyway, it can't decode them yet). Also my iso88025_input (hacked version of ether_input) is printing debug information that make me think everything is working ok up to that point. Here is what I have: (full sources at http://anarchy.stdio.com) void iso88025_input(ifp, th, m) struct ifnet *ifp; register struct iso88025_header *th; struct mbuf *m; { register struct ifqueue *inq; u_short ether_type; int s; register struct llc *l = mtod(m, struct llc *); printf("iso88025_input: entered.\n"); printf("iso88025_input: adjusting mbuf.\n"); m->m_pkthdr.len = m->m_len = m->m_len - 8; /* Length of LLC header in our case */ m->m_data += 8; /* Length of LLC header in our case */ if ((ifp->if_flags & IFF_UP) == 0) { m_freem(m); return; } ifp->if_ibytes += m->m_pkthdr.len + sizeof (*th); if (th->iso88025_dhost[0] & 1) { if (bcmp((caddr_t)etherbroadcastaddr, (caddr_t)th->iso88025_dhost, sizeof(etherbroadcastaddr)) == 0) m->m_flags |= M_BCAST; else m->m_flags |= M_MCAST; } if (m->m_flags & (M_BCAST|M_MCAST)) ifp->if_imcasts++; ether_type = ntohs(l->llc_un.type_snap.ether_type); switch (ether_type) { #ifdef INET case ETHERTYPE_IP: printf("iso88025_input: IP Packet\n"); if (ipflow_fastforward(m)) return; schednetisr(NETISR_IP); inq = &ipintrq; break; case ETHERTYPE_ARP: printf("iso88025_input: ARP Packet\n"); schednetisr(NETISR_ARP); inq = &arpintrq; break; #endif [SNIP] s = splimp(); if (IF_QFULL(inq)) { IF_DROP(inq); m_freem(m); printf("iso88025_input: Packet dropped (Queue full).\n"); } else IF_ENQUEUE(inq, m); printf("iso88025_input: Packet queued.\n"); splx(s); } And the dmesg info is: tok0: Receive interrupt called. tok: isrp e[2] o[8] isra e[7] o[0] (tok_rx_intr 1). tok0: Packet received data: cmd[81] station_id[100] bptr[1c2e] lhdr[10] dhdr[3] len[70] ncb[6] tok0: copying packet into mbuf. tok0: adjusting mbuf. tok0:Packet data: aa aa 3 0 0 0 8 0 45 0 0 58 33 6d 0 0 1e 11 54 28 a 0 0 2 a 0 0 ff 2 1 2 1 0 44 37 10 1 1 0 0 35 a4 26 54 0 0 0 0 63 79 6e 69 63 69 73 6d 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 35 9d 74 3 tok0: calling iso88025 input routine. iso88025_input: entered. iso88025_input: adjusting mbuf. iso88025_input: IP Packet iso88025_input: Packet queued. tok0: ack'ing packet to adapter (rc=0). tok: isrp e[2] o[8] isra e[3] o[10] (tok_rx_intr 2). tok0: asb->bptr [1c2e] arb->bptr [1c2e]. tcpdump for that interface is putting out things like: 22:06:24.254811 ff:ff:90:0:5a:b1 18:40:ff:ff:ff:ff c5ec 112: 8220 aaaa 0300 0000 0800 4500 0058 3368 0000 1e11 542d 0a00 0002 0a00 00ff 0201 0201 0044 37c4 0101 0000 35a4 25a0 0000 0000 6379 6e69 Which is correct if not somewhat shifted a bit (or several :) (Note: these packets are not neccesarily the same) So what is going wrong? Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 20:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15752 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 20:38:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15689; Wed, 8 Jul 1998 20:37:47 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) id 0yu7Wa-0005QX-00; Thu, 9 Jul 1998 05:37:36 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id XAA00255; Wed, 8 Jul 1998 23:57:37 +0200 (SAT) Date: Wed, 8 Jul 1998 23:57:37 +0200 (SAT) From: Peter van Heusden To: Stefan Esser cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: SCSI drive not remapping bad block: Any solution (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 [message cc'ed to freebsd-questions because that's where I asked the question initially] With help from freebsd-hackers I've got my SCSI disk going fine (I did a make buildworld on it, and it held up). A wipe with 'dd if=/dev/zero of=/dev/rsd2s1 bs=64k' cleaned it up (I then read the disk using dd and there were no problems. Thanks in particular to Stefan Esser and Julian Elischer. Peter -- Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 21:16:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21452 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 21:16:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21444 for ; Wed, 8 Jul 1998 21:16:13 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt4-180.HiWAAY.net [208.166.127.180]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id XAA26839; Wed, 8 Jul 1998 23:16:10 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id RAA02989; Wed, 8 Jul 1998 17:59:51 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807082259.RAA02989@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: freebsd-hackers@FreeBSD.ORG, David Kelly From: David Kelly Subject: Re: Someone working on swapoff? In-reply-to: Message from Stefan Eggers of "Wed, 08 Jul 1998 08:31:38 +0200." <199807080631.IAA01081@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Jul 1998 17:59:51 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Eggers writes: > > system, but would it be breaking sacred tradition to merge swapon and > > the future swapoff into one "swap" management utility? The unified > > utility could do swapon tasks if linked to the name "swapon" and > > swapoff tasks if its named "swapoff". > > I think deciding on the name how to behave is not that good an idea > in the first place. Besides this: How long would the swapoff in user > land be? About 50 lines or less I'd guess. Merging is not worth > any effort as it does save nothing in C code lines but adds more code > to do the check the program name and call the corresponding code. > > What would then be worth talking about is replacing swapon with a new > command for swap management. But that can wait till there is any need > for this i.e. the kernel support for swapoff or priorities or something > like that is at least nearly finished! For that such a merger might be > worthwhile as the swapon functionalty would be in the new command > already and one would have to support swapon for compatibility at least > for a while. That's like pstat and swapinfo. That's the other one to merge into swap(1), swapinfo/pstat(1). Agree that its too early to decide on a name, the functionality is needed first. But didn't think it was too early to start thinking about the name. But mostly I'm thinking about how it gets used. Bouncing between SGI Irix, Sun Solaris, and FreeBSD, swap, swapon, and swapinfo are commands residing in the cobweb corners of my brain as they are generally not used until there is a problem. Often the wrong one comes to the top when needed, resulting in a session of, "man -k swap", hunting for the right one. In the advent of a functioning swapoff, we should consider bringing the highest level of swap management into conformity with the other Un*x's. pstat is moderatly complex: n4hhe: {801} wc -l /usr/src/usr.sbin/pstat/pstat.c 1191 /usr/src/usr.sbin/pstat/pstat.c n4hhe: {802} -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 22:06:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26638 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 22:06:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26633 for ; Wed, 8 Jul 1998 22:06:10 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id WAA02982; Wed, 8 Jul 1998 22:06:06 -0700 (PDT) (envelope-from jdp) Message-Id: <199807090506.WAA02982@austin.polstra.com> To: rminnich@Sarnoff.COM Subject: Re: .palign 2 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 08 Jul 1998 22:06:06 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Ron G. Minnich wrote: > I tried -questions but no dice. So here I am: > > On the latest tree, at some point in the gnu side, I get an error due to > an op in read.S, > .palign 2 > > Any ideas? It appears to be hidden in one of the gnu standard Macros From > Hell, since read.S itself is just two lines, an include and a macro > invocation. This isn't really an answer, but ... I'm aware of a ".p2align" directive, but I've never heard of ".palign". ".p2align" aligns to 2**n, where n is the argument. I added support for it quite some time ago. It's handy because it means the same thing for a.out as for ELF. Whereas the old ".align n" aligned to a multiple of n for a.out, but a multiple of 2**n for ELF. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 22:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26994 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 22:08:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26988 for ; Wed, 8 Jul 1998 22:08:52 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id WAA03001; Wed, 8 Jul 1998 22:08:49 -0700 (PDT) (envelope-from jdp) Message-Id: <199807090508.WAA03001@austin.polstra.com> To: rminnich@Sarnoff.COM Subject: Re: p2align In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 08 Jul 1998 22:08:49 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Ron G. Minnich wrote: > it's in contrib/gcc/config/i386/freebsd.h if that rings any bells. > There appears to be no such op in gas? Yes, it's supported in the assembler: vashon# cd /usr/src/gnu/usr.bin/as vashon# grep -3 p2align read.c #endif /* NO_LISTING */ { "octa", big_cons, 16 }, { "org", s_org, 0 }, { "p2align", s_align_ptwo, 0 }, #ifdef NO_LISTING { "psize", s_ignore, 0 }, /* set paper size */ #else -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 22:25:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29442 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 22:25:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29437 for ; Wed, 8 Jul 1998 22:25:14 -0700 (PDT) (envelope-from CAROLCARTR@aol.com) From: CAROLCARTR@aol.com Received: from imo15.mx.aol.com (imo15.mx.aol.com [198.81.17.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id WAA03727 for ; Wed, 8 Jul 1998 22:25:08 -0700 (PDT) Received: from CAROLCARTR@aol.com by imo15.mx.aol.com (IMOv14_b1.1) id 9WHZa20768 for ; Thu, 9 Jul 1998 01:24:26 -0400 (EDT) Message-ID: Date: Thu, 9 Jul 1998 01:24:26 EDT To: freebsd-hackers@freefall.cdrom.com Mime-Version: 1.0 Subject: Training Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: AOL 3.0 for Windows 95 sub 64 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like information on how to learn Unix. I've got a PC with no network connections, except the INternet. Is it possible? And if so, how? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 8 23:38:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06768 for freebsd-hackers-outgoing; Wed, 8 Jul 1998 23:38:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06763 for ; Wed, 8 Jul 1998 23:38:27 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id IAA09238; Thu, 9 Jul 1998 08:38:14 +0200 (MET DST) Date: Thu, 9 Jul 1998 08:38:12 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Ade Lovett cc: FreeBSD hackers mailing list Subject: Re: Internal modem on Fujitsu Lifebook 280DX 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 > Anyone had any experiences of getting the internal modem on a Fujitsu > Lifebook 200-series to identify itself to FreeBSD -- I've done a couple > of searches through the mail archives, but nothing obvious turned up I have a Lifebook 735 and it contains a so called DSVD modem. PCI thingie. According to the Linux FAQ of februari, there is no support for that type of device in Linux, so I bet the challenge to write the driver for it is yours. Let the list know though if you find something. > Making matters slightly more complicated is that there also appear to > be a number of other internal devices hooked to irq 9, namely the > two PCI<->Cardbus bridges (one on int a, the other on int b), and a > USB controller (on int d) Don't worry about that. If Windows can use it all at the same time, than FreeBSD certainly can. An Windows is able to do it: Handling a USB camera and a modem at the same time, that is. > Any suggestions for getting this beastie working, or am I doomed to > go get a PC-Card modem? That is the simple way to go. Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 00:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10463 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 00:16:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10458 for ; Thu, 9 Jul 1998 00:16:40 -0700 (PDT) (envelope-from fschan@capgemini.com.sg) Received: from mail.capgemini.com.sg ([203.116.11.115]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id AAA12557 for ; Thu, 9 Jul 1998 00:16:29 -0700 (PDT) Received: from 123.capgemini.com.sg (MIS_FSCHAN.capgemini.com.sg [10.64.0.177]) by mail.capgemini.com.sg (post.office MTA v2.0 0813 ID# 0-16936) with SMTP id AAA226; Thu, 9 Jul 1998 15:12:30 +0800 Received: by localhost with Microsoft MAPI; Thu, 9 Jul 1998 15:17:41 +0800 Message-ID: <01BDAB4C.B6F33BE0.fschan@capgemini.com.sg> From: fschan@capgemini.com.sg (Chan, Fook Sheng) To: "'CAROLCARTR@aol.com'" , "freebsd-hackers@freefall.cdrom.com" Subject: RE: Training Date: Thu, 9 Jul 1998 15:17:39 +0800 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG go to www.unixworld.com www.freebsd.org read some books on unix Best Regards, Fook Sheng -----Original Message----- From: CAROLCARTR@aol.com [SMTP:CAROLCARTR@aol.com] Sent: Thursday, July 09, 1998 1:24 PM To: freebsd-hackers@freefall.cdrom.com Subject: Training I'd like information on how to learn Unix. I've got a PC with no network connections, except the INternet. Is it possible? And if so, how? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 01:26:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16833 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 01:26:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16815 for ; Thu, 9 Jul 1998 01:25:58 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA07037 ; Thu, 9 Jul 1998 10:24:51 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA08963; Thu, 9 Jul 1998 10:24:50 +0200 To: Terry Lambert Cc: finrod@niobe.ewox.org (Dag-Erling Coidan Sm?rgrav), hackers@FreeBSD.ORG Subject: Re: Y2K compliance References: <199807082320.QAA27772@usr02.primenet.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 10:24:49 +0200 In-Reply-To: Terry Lambert's message of Wed, 8 Jul 1998 23:20:09 +0000 (GMT) Message-ID: Lines: 12 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > Niobe is running make release with that patch right now, but I don't > > think I'll encounter any trouble. The only thing I can think of that > > it might break is ordering, i.e. if anybody is relying on collating > > order to sort snapshots, since 1998 is lexically less than 98. > Yes. If they are using "sort" instead of "sort -n", they are a loon. Okiedokie, it's going into -current right now then. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 03:00:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23560 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 03:00:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from inet.prbank.msk.su (root@prbank.msk.su [195.54.219.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23521 for ; Thu, 9 Jul 1998 03:00:36 -0700 (PDT) (envelope-from fav@prbank.msk.su) Received: from pegasus.prbank.msk.su (root@pegasus [172.16.26.0]) by inet.prbank.msk.su (8.8.8/vak/1.9) with ESMTP id OAA20657 for ; Thu, 9 Jul 1998 14:05:41 +0400 Received: from prbank.msk.su by pegasus.prbank.msk.su with ESMTP id OAA14541; (8.8.7/vak/1.9) Thu, 9 Jul 1998 14:04:43 +0400 Message-ID: <35A494AB.7B143EA8@prbank.msk.su> Date: Thu, 09 Jul 1998 14:00:12 +0400 From: "Andrew V. Fomenkov" Organization: ProgramBank Ltd. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: TCPMUX problems Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As specified in RFC1078, there are 2 types of TCPMUX replies: 1. If service available, it sends '+',then message,then CRLF 2. if not available, '-' etc. If I'm trying to query not-existent service, all OK. But service available, TCPMUX doesn't send '+', and connects to my server. I've tried to connect using telnet to port 1, and the same result... Why TCPMUX doesn't send positive reply? How can I check for success if my program must be portable? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 03:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24613 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 03:11:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24605 for ; Thu, 9 Jul 1998 03:11:46 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA13063 for ; Thu, 9 Jul 1998 12:11:14 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA10249; Thu, 9 Jul 1998 12:11:13 +0200 To: hackers@FreeBSD.ORG Subject: kern/7201 Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 12:11:13 +0200 Message-ID: Lines: 95 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you who follow -bugs, I have the following patch for kern/7201 lying in my freefall account waiting to be committed. It compiles cleanly on my laptop, but I don't have a PII or PPro box handy for testing right now, so if any of you have time to test it for me I'd be very grateful. If not, I can get my hands on both kinds of boxes by the end of the week, so it's not life or death. For the uninitiated, it fixes CPU initialization and some other stuff I broke when I added identification of Pentium II processors, since the old code didn't anticipate the appearance of additional models in the 686 family. A small change to LINT is also necessary for documentation purposes, but it doesn't affect the code so I left it out. Index: initcpu.c =================================================================== RCS file: /c/ncvs/src/sys/i386/i386/initcpu.c,v retrieving revision 1.13 diff -u -r1.13 initcpu.c --- initcpu.c 1998/05/16 14:38:10 1.13 +++ initcpu.c 1998/07/09 09:53:38 @@ -483,6 +483,8 @@ init_6x86MX(); break; case CPU_686: + case CPU_PII: + /* The PPro and PII are two submodels of the 686 class. */ if (strcmp(cpu_vendor, "GenuineIntel") == 0 && (cpu_id & 0xff0) == 0x610) init_ppro(); Index: pmap.c =================================================================== RCS file: /c/ncvs/src/sys/i386/i386/pmap.c,v retrieving revision 1.202 diff -u -r1.202 pmap.c --- pmap.c 1998/05/21 07:47:34 1.202 +++ pmap.c 1998/07/09 09:59:20 @@ -458,7 +458,7 @@ { int i; - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { for(i = 0; i < NPPROVMTRR; i++) { PPro_vmtrr[i].base = rdmsr(PPRO_VMTRRphysBase0 + i * 2); PPro_vmtrr[i].mask = rdmsr(PPRO_VMTRRphysMask0 + i * 2); @@ -471,7 +471,7 @@ { int i; - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { wbinvd(); for(i = 0; i < NPPROVMTRR; i++) { wrmsr(PPRO_VMTRRphysBase0 + i * 2, PPro_vmtrr[i].base); @@ -483,7 +483,7 @@ void pmap_setvidram(void) { - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { wbinvd(); /* * Set memory between 0-640K to be WB @@ -506,7 +506,7 @@ unsigned long long mask; return; - if (cpu != CPU_686) + if (cpu_class != CPUCLASS_686) return; free = -1; @@ -2799,7 +2799,7 @@ cpu_invlpg(&prv_CPAGE3); #if defined(I686_CPU) - if (cpu == CPU_686) + if (cpu_class == CPUCLASS_686) i686_pagezero(&prv_CPAGE3); else #endif @@ -2820,7 +2820,7 @@ } #if defined(I686_CPU) - if (cpu == CPU_686) + if (cpu_class == CPUCLASS_686) i686_pagezero(CADDR2); else #endif -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 04:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03760 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 04:47:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thorin.hway.ru (thorin.hway.ru [195.170.38.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03755 for ; Thu, 9 Jul 1998 04:47:13 -0700 (PDT) (envelope-from flash@intech.hway.ru) Received: from balin.intech.hway.ru (balin.intech.hway.ru [192.168.1.25]) by thorin.hway.ru (8.8.8/8.8.8) with ESMTP id PAA03173; Thu, 9 Jul 1998 15:44:49 +0400 (MSD) Received: from localhost (flash@localhost) by balin.intech.hway.ru (8.8.8/8.8.8) with SMTP id PAA06848; Thu, 9 Jul 1998 15:44:37 +0400 (MSD) Date: Thu, 9 Jul 1998 15:44:37 +0400 (MSD) From: "Alexander V. Tischenko" To: "Andrew V. Fomenkov" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: TCPMUX problems In-Reply-To: <35A494AB.7B143EA8@prbank.msk.su> 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 For this result coding you have to define tcpmux as tcpmux+ in inetd.conf. Otherwise no + will be sent in reply. On Thu, 9 Jul 1998, Andrew V. Fomenkov wrote: > As specified in RFC1078, there are 2 types of TCPMUX replies: > 1. If service available, it sends '+',then message,then CRLF > 2. if not available, '-' etc. > If I'm trying to query not-existent service, all OK. > But service available, TCPMUX doesn't send '+', and connects to my > server. > I've tried to connect using telnet to port 1, and the same result... > Why TCPMUX doesn't send positive reply? > How can I check for success if my program must be portable? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Alexander V. Tischenko ------------------------------------------------------------------------------ Integrated Network Technologies | Tel: +7 095 978-47-37 7, Miusskaya sq., Moscow, 125047 Russia | Fax: +7 095 978-47-37 Internet: flash@hway.ru | NIC: AT55-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 06:56:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15536 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 06:56:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA15530 for ; Thu, 9 Jul 1998 06:56:46 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw2.att.com; Thu Jul 9 08:37 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id IAA09305 for ; Thu, 9 Jul 1998 08:56:39 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9HSWZ>; Thu, 9 Jul 1998 09:56:38 -0400 Message-ID: To: mike@smith.net.au Cc: hackers@FreeBSD.ORG Subject: RE: NIC drivers Date: Thu, 9 Jul 1998 09:56:36 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > > > >> Just curious, how do one find the neccesary info to write a > driver of > > >> say 3c509 fro FreeBSD? > > > You mean like, eg. /sys/i386/isa/if_ep.c? (The 3c509 driver.) > > > > Last I heard, the 509 driver was buggy. (According to LINT, it > still > > is.) When I last tried it about eight months ago, it was still > buggy. > > Cursory tests now (I've got one in this box, on the same LAN as an > > NE2000) indicate that it may still be broken. > > Yes; the driver is not spectacular, and neither is the card. > It worked fine for me in '95-'97 in my machine at work. Yes, it occasionally loses packets under high load but it's still faster than NE2000 (although I agree that the card is somewhat pathological). It can easily handle FTP at full Ethernet speed (1.1MB/s) in an old 486. Although I don't know about the current state of the driver. There was a period (early '95) when packet loss led to the hang of the card and that's the reason why it was marked as "buggy" in LINT at that time. This was fixed but this comment just was not cleaned up. There was the same problem somewhere in '96 when David Greenman had changed the way the watchdog routines are called for network drivers, but after this driver was changed according to the new way it worked again. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:06:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16603 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:06:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1 (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA16598 for ; Thu, 9 Jul 1998 07:06:21 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1 (SMI-8.6/8.6.9) with SMTP id KAA17897 for ; Thu, 9 Jul 1998 10:06:18 -0400 Date: Thu, 9 Jul 1998 10:06:17 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 Reply-To: zhihuizhang To: hackers Subject: Multi-threaded and TCP/IP window size Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got two general questions here: (1) I know for sure that FreeBSD does not supported multi-threaded. I am considering the possibility of constructing a clustered file system using a good NIC. I am just wondering if the fact that FreeBSD does not support multi-threaded programming will affect the performance or implementation of a clustered file system and how. (2) A friend has a special application requirement in which two machines are communicating with each other with TCP/IP. If the receiver send a packet with window size of *zero*, it expects the sender to send one byte a time immediately. He tested other Unix systems (Linux, SunOS, AIX) and found that in these Unix systems, the sender keeps sending a lot of data *for a while* before sending one byte a time (kind of probing). What he wants is an instantanous response form the sender. Later when the receiver sends a packet saying the window size is now, say, 3000 bytes, the sender should be able to come to data rate *immediately*. Can this be (or already have been) done by FreeBSD? Any help is appreciated. ------------------------------------------------- Zhihui Zhang Department of Computer Science State University of New York at Binghamton Web Site: http://cs.binghamton.edu/~zzhang ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18522 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:20:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18511 for ; Thu, 9 Jul 1998 07:20:47 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA21756; Thu, 9 Jul 1998 16:18:44 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA07892; Thu, 9 Jul 1998 11:29:08 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807090929.LAA07892@semyam.dinoco.de> To: Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Someone working on swapoff? In-reply-to: Your message of "Wed, 08 Jul 1998 15:43:09 CDT." <199807082043.PAA00578@detlev.UUCP> Date: Thu, 09 Jul 1998 11:29:03 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Remember that this doc was old when I got it in April. Thanks! That's exactly the type of information I was looking for. It should help in understanding the VM subsystem of FreeBSD in less time. Maybe we could include such a document in an updated version in the system. Don't ask me to do that. I first have to understand it my- self before I can think about updating it. ;-) Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18581 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:21:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18567 for ; Thu, 9 Jul 1998 07:21:03 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA21757; Thu, 9 Jul 1998 16:18:46 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA07918; Thu, 9 Jul 1998 11:35:34 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807090935.LAA07918@semyam.dinoco.de> Cc: David Kelly , Stefan Eggers To: freebsd-hackers@FreeBSD.ORG Subject: Re: Someone working on swapoff? In-reply-to: Your message of "Wed, 08 Jul 1998 17:59:51 CDT." <199807082259.RAA02989@nospam.hiwaay.net> Date: Thu, 09 Jul 1998 11:35:33 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > already and one would have to support swapon for compatibility at least > > for a while. That's like pstat and swapinfo. > > That's the other one to merge into swap(1), swapinfo/pstat(1). What do the open file table, the terminal state and the like to do with swapping? One can talk about moving swapinfo functionality fro pstat(1) to a new swap management command but the rest has to stay. > needed first. But didn't think it was too early to start thinking about > the name. But mostly I'm thinking about how it gets used. Bouncing I think swapctl as we already have manctl, pppctl and sysctl in /usr/sbin. Once one gets the idea it's simple to remember. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:33:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19680 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:33:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19645 for ; Thu, 9 Jul 1998 07:33:13 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA25231 ; Thu, 9 Jul 1998 16:31:42 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA13592; Thu, 9 Jul 1998 16:31:40 +0200 To: sbabkin@dcn.att.com Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 16:31:39 +0200 In-Reply-To: sbabkin@dcn.att.com's message of Thu, 9 Jul 1998 09:56:36 -0400 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sbabkin@dcn.att.com writes: > Although I don't know about the current state of the driver. There > was a period (early '95) when packet loss led to the hang of the > card and that's the reason why it was marked as "buggy" in LINT at > that time. This was fixed but this comment just was not cleaned up. Believe me, it still sucks. Search the archives (both the mailing list archives and the PR database) for "no buffer space", and/or "ep0". Basically, the driver is fine for telnet and mail, but wedges under sustained load. I can get it to hang without ever going above 20 kBps (160 kbps). Gimme an Intel EtherExpress. DES (not very proud owner of three 3c509) -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:33:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19714 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:33:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19649 for ; Thu, 9 Jul 1998 07:33:15 -0700 (PDT) (envelope-from tiger1@eythan.com) From: tiger1@eythan.com Received: from eythan.com (client-151-196-207-63.covesoft.com [151.196.207.63] (may be forged)) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA24634 for ; Thu, 9 Jul 1998 07:33:00 -0700 (PDT) Received: from fac (d01a866d.dip.cdsnet.net [208.26.134.109]) by eythan.com (8.8.5/8.6.12) with SMTP id QAA21692 for ; Thu, 9 Jul 1998 16:27:37 +0100 (WET DST) Date: Thu, 9 Jul 1998 16:27:37 +0100 (WET DST) Message-Id: <199807091527.QAA21692@eythan.com> To: freebsd-hackers@freefall.cdrom.com; Subject: INTERNET MAKES MILLIONIARES! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am sure you are aware by now that the Internet and advanced telecommunications are changing the ways that many are making their living. A growing number of people are abandoning the traditional workplace to enjoy the freedom of working from their own homes and making more money than they ever dreamed possible. If you are one of those who desires to get out of the rat race and reap the rewards of your own Internet based business just follow the link below, we'll show you how to get started. After all you might as well let that expensive computer of yours make some money for you! ****************************************************************************** The addresses for this mailing were extracted from a publicly available database. If you would like to be removed from this list just reply to the message with the word REMOVE in the subject line. ****************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20757 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:36:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20734 for ; Thu, 9 Jul 1998 07:36:36 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA25434 ; Thu, 9 Jul 1998 16:35:44 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA13644; Thu, 9 Jul 1998 16:35:43 +0200 To: zhihuizhang Cc: hackers Subject: Re: Multi-threaded and TCP/IP window size References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 16:35:41 +0200 In-Reply-To: zhihuizhang's message of Thu, 9 Jul 1998 10:06:17 -0400 (EDT) Message-ID: Lines: 29 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG zhihuizhang writes: > (1) I know for sure that FreeBSD does not supported multi-threaded. I am I beg your pardon? What's this then: des@freefall ~$ uname -a FreeBSD freefall.freebsd.org 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Fri May 29 01:56:28 PDT 1998 jkh@freefall.freebsd.org:/d/src/sys/compile/FREEFALL i386 des@freefall ~$ apropos thread pthread(3) - POSIX thread functions pthread_create(3) - create a new thread pthread_detach(3) - detach a thread pthread_equal(3) - compare thread IDs pthread_exit(3) - terminate the calling thread pthread_getspecific(3) - get a thread-specific data value pthread_join(3) - wait for thread termination pthread_key_create(3) - thread-specific data key creation pthread_key_delete(3) - delete a thread-specific data key pthread_once(3) - dynamic package initialization pthread_self(3) - get the calling thread's ID pthread_setspecific(3) - set a thread-specific data value XInitThreads(3), XLockDisplay(3), XUnlockDisplay(3) - multi-threading support XtAppSetExitFlag(3), XtAppGetExitFlag(3) - thread support functions XtToolkitThreadInitialize(3) - initialize the toolkit for multiple threads There's no kernel support, but that doesn't mean it doesn't work. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22729 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:48:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22723 for ; Thu, 9 Jul 1998 07:48:18 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Thu Jul 9 09:48 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id JAA05963 for ; Thu, 9 Jul 1998 09:47:44 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9HTCY>; Thu, 9 Jul 1998 10:47:43 -0400 Message-ID: To: smoergrd@oslo.geco-prakla.slb.com Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: RE: NIC drivers Date: Thu, 9 Jul 1998 10:47:40 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: smoergrd@oslo.geco-prakla.slb.com > [SMTP:smoergrd@oslo.geco-prakla.slb.com] > > sbabkin@dcn.att.com writes: > > Although I don't know about the current state of the driver. There > > was a period (early '95) when packet loss led to the hang of the > > card and that's the reason why it was marked as "buggy" in LINT at > > that time. This was fixed but this comment just was not cleaned up. > > Believe me, it still sucks. Search the archives (both the mailing list > archives and the PR database) for "no buffer space", and/or "ep0". > Basically, the driver is fine for telnet and mail, but wedges under > sustained load. I can get it to hang without ever going above 20 kBps > Do you have heavy disk load ? This card has small buffer size so it's sensitive to interrupt delays. Another problem is that in case of buffer overflow it has to be reset. But when the watchdog routine discovers this, it restores just fine and the problem generally occurs not that often. Of course, if it was not broken again (I've fixed it twice but I don't have these cards any more so I have no interest in doing that once more :-). A good solution would be to have high-frequency watchdog routine (say, 5 times a second), it would reduce the delays in case of overflow considerably and still bring less CPU load than the solution used in BSDI when the interrupt is delivered at beginning of receiving of a packet and the CPU idles in a loop until it gets the whole packet. > (160 kbps). Gimme an Intel EtherExpress. > Sure, _now_, when you can get 100Mbps EtherExpress for the same money, nobody would buy 3c509. But a few years ago it was a good enough solution. -Serge Babkin whose old e-mail address was babkin@hq.icb.chel.su To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 07:57:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24420 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:57:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24415 for ; Thu, 9 Jul 1998 07:57:34 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA26281 ; Thu, 9 Jul 1998 16:56:09 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA13910; Thu, 9 Jul 1998 16:56:08 +0200 To: sbabkin@dcn.att.com Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 16:56:07 +0200 In-Reply-To: sbabkin@dcn.att.com's message of Thu, 9 Jul 1998 10:47:40 -0400 Message-ID: Lines: 37 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sbabkin@dcn.att.com writes: > > sbabkin@dcn.att.com writes: > > > Although I don't know about the current state of the driver. There > > > was a period (early '95) when packet loss led to the hang of the > > > card and that's the reason why it was marked as "buggy" in LINT at > > > that time. This was fixed but this comment just was not cleaned up. > > Believe me, it still sucks. Search the archives (both the mailing list > > archives and the PR database) for "no buffer space", and/or "ep0". > > Basically, the driver is fine for telnet and mail, but wedges under > > sustained load. I can get it to hang without ever going above 20 kBps > Do you have heavy disk load ? This card has small buffer size No. I experience these problems mostly while playing MP3 audio files which reside on an NFS file system. It is invariably the server that gets wedged. The disk load is practically identical to the network load in that case (~130 kbps) > so it's sensitive to interrupt delays. Another problem is that in > case of buffer overflow it has to be reset. But when the watchdog > routine discovers this, it restores just fine and the problem > generally occurs not that often. Of course, if it was Nope. Once it's wedged it stays wedged until I do ifconfig ep0 up. > not broken again (I've fixed it twice but I don't have these cards > any more so I have no interest in doing that once more :-). > > (160 kbps). Gimme an Intel EtherExpress. > Sure, _now_, when you can get 100Mbps EtherExpress for > the same money, nobody would buy 3c509. But a few years ago -------------- Half the money, if the reports I've heard of EtherExpress cards retailing at $50 are reliable. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 08:51:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01895 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 08:51:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01876 for ; Thu, 9 Jul 1998 08:51:16 -0700 (PDT) (envelope-from msanders@shell.aros.net) Received: from shell.aros.net (root@shell.aros.net [207.173.16.19]) by mars.aros.net (8.8.7/8.8.4) with ESMTP id JAA23182; Thu, 9 Jul 1998 09:50:43 -0600 (MDT) Received: from shell.aros.net (msanders@localhost.aros.net [127.0.0.1]) by shell.aros.net (8.8.7/8.8.5) with ESMTP id JAA18853; Thu, 9 Jul 1998 09:51:00 -0600 (MDT) Message-Id: <199807091551.JAA18853@shell.aros.net> X-Attribution: msanders To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) cc: sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "09 Jul 1998 16:56:07 +0200." X-Mailer: MH 6.8.3 Date: Thu, 09 Jul 1998 09:51:00 -0600 From: "Michael K. Sanders" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Coidan Sm rgr av writes: >sbabkin@dcn.att.com writes: >> > (160 kbps). Gimme an Intel EtherExpress. >> Sure, _now_, when you can get 100Mbps EtherExpress for >> the same money, nobody would buy 3c509. But a few years ago > -------------- >Half the money, if the reports I've heard of EtherExpress cards >retailing at $50 are reliable. You've always[1] been able to get EtherExpress 100 cards for $50-- you could get two 100B cards directly from Intel for $49 ea. through their "evaluation program"[2], and numerous mail order companies currently have the 100B and 100+ for < $50. 1: or at least for a very long time, now. 2: http://www.intel.com/network/ee100/eval/index.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06773 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:30:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06762 for ; Thu, 9 Jul 1998 09:30:20 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA25435; Thu, 9 Jul 1998 11:30:42 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA04740; Thu, 9 Jul 1998 11:29:59 -0500 (CDT) (envelope-from joelh) Date: Thu, 9 Jul 1998 11:29:59 -0500 (CDT) Message-Id: <199807091629.LAA04740@detlev.UUCP> To: sbabkin@dcn.att.com CC: mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: (sbabkin@dcn.att.com) Subject: Re: NIC drivers From: Joel Ray Holveck References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Last I heard, the 509 driver was buggy. (According to LINT, it >>> still is.) When I last tried it about eight months ago, it was >>> still buggy. Cursory tests now (I've got one in this box, on the >>> same LAN as an NE2000) indicate that it may still be broken. >> Yes; the driver is not spectacular, and neither is the card. > It worked fine for me in '95-'97 in my machine at work. Yes, it > occasionally loses packets under high load but it's still faster > than NE2000 (although I agree that the card is somewhat > pathological). It can easily handle FTP at full Ethernet speed > (1.1MB/s) in an old 486. Although I don't know about the current > state of the driver. There was a period (early '95) when packet loss > led to the hang of the card and that's the reason why it was marked > as "buggy" in LINT at that time. This was fixed but this comment > just was not cleaned up. There was the same problem somewhere in '96 > when David Greenman had changed the way the watchdog routines are > called for network drivers, but after this driver was changed > according to the new way it worked again. Hmmm... What version of FreeBSD are you using? I'd like to get mine working; you appear to know what's going on. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:36:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08357 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:36:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08351 for ; Thu, 9 Jul 1998 09:36:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA25727; Thu, 9 Jul 1998 11:36:46 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA04767; Thu, 9 Jul 1998 11:35:57 -0500 (CDT) (envelope-from joelh) Date: Thu, 9 Jul 1998 11:35:57 -0500 (CDT) Message-Id: <199807091635.LAA04767@detlev.UUCP> To: msanders@aros.net CC: smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: <199807091551.JAA18853@shell.aros.net> (msanders@aros.net) Subject: Re: NIC drivers From: Joel Ray Holveck References: <199807091551.JAA18853@shell.aros.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> (160 kbps). Gimme an Intel EtherExpress. >>> Sure, _now_, when you can get 100Mbps EtherExpress for >>> the same money, nobody would buy 3c509. But a few years ago >> Half the money, if the reports I've heard of EtherExpress cards >> retailing at $50 are reliable. > You've always[1] been able to get EtherExpress 100 cards for $50-- you > could get two 100B cards directly from Intel for $49 ea. through their > "evaluation program"[2], and numerous mail order companies currently > have the 100B and 100+ for < $50. > 1: or at least for a very long time, now. > 2: http://www.intel.com/network/ee100/eval/index.htm Evidently we've got different definitions of 'very long time'. The reason I have a 509 is because I built the system in '93, and I am *quite* certain there were no 100Mbit cards for < $50... even any that fell off the back of a lorry. Heppy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08665 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:38:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1 (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08656 for ; Thu, 9 Jul 1998 09:38:18 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1 (SMI-8.6/8.6.9) with SMTP id MAA25245 for ; Thu, 9 Jul 1998 12:38:12 -0400 Date: Thu, 9 Jul 1998 12:38:11 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: default_pager_convert_to_swap() 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 maybe trivial. But default_pager_convert_to_swap() calls swap_pager_swp_alloc() with a flag M_KERNEL which is never checked directly. malloc() and kern_malloc() do check M_WAITOK and M_NOWAIT, but in DIFFERENT ways: & and ==. So you can not tell whether M_KERNEL is effectively M_WAITOK or M_NOWAIT. Besides, default_pager_convert_to_swap() has no return value, will not call panic() if it fails. So who knows if it does fail? Or we do not care about the results? For example, vm_map_insert() calls default_pager_convert_to_swapq() which in turn calls default_pager_convert_to_swap() (no "q" here), but vm_map_insert() does not check for possible failure in the conversion. BTW, I am reading stable-FreeBSD. Maybe current-FreeBSD has already corrected these. Maybe I am simply wrong. ------------------------------------------------- Zhihui Zhang Department of Computer Science State University of New York at Binghamton Web Site: http://cs.binghamton.edu/~zzhang ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08819 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:39:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08808 for ; Thu, 9 Jul 1998 09:38:58 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA05779; Thu, 9 Jul 1998 09:41:02 -0700 (PDT) Date: Thu, 9 Jul 1998 09:41:02 -0700 (PDT) From: Jim Shankland Message-Id: <199807091641.JAA05779@biggusdiskus.flyingfox.com> To: sbabkin@dcn.att.com, smoergrd@oslo.geco-prakla.slb.com Subject: Re: NIC drivers Cc: hackers@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) writes: > Believe me, [the ep driver] still sucks. Search the archives (both the > mailing list archives and the PR database) for "no buffer space", > and/or "ep0". Basically, the driver is fine for telnet and mail, but > wedges under sustained load. I can get it to hang without ever going > above 20 kBps (160 kbps). Gimme an Intel EtherExpress. That was not my experience. We ran 4 3C509's in 1 box a few years ago (FreeBSD 2.1.?), and hammered them pretty hard, and it all just worked. Granted, we did retire the cards, and the 486 box they were in, some time ago. The Intel cards and the fxp driver are great. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09449 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:42:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09441 for ; Thu, 9 Jul 1998 09:42:19 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw2.att.com; Thu Jul 9 11:22 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id LAA06482 for ; Thu, 9 Jul 1998 11:42:09 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9HTV8>; Thu, 9 Jul 1998 12:42:08 -0400 Message-ID: To: joelh@gnu.org Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: RE: NIC drivers Date: Thu, 9 Jul 1998 12:42:05 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Joel Ray Holveck [SMTP:joelh@gnu.org] > > >>> Last I heard, the 509 driver was buggy. (According to LINT, it > >>> still is.) When I last tried it about eight months ago, it was > >>> still buggy. Cursory tests now (I've got one in this box, on the > >>> same LAN as an NE2000) indicate that it may still be broken. > >> Yes; the driver is not spectacular, and neither is the card. > > It worked fine for me in '95-'97 in my machine at work. Yes, it > > occasionally loses packets under high load but it's still faster > > than NE2000 (although I agree that the card is somewhat > > pathological). It can easily handle FTP at full Ethernet speed > > (1.1MB/s) in an old 486. Although I don't know about the current > > state of the driver. There was a period (early '95) when packet loss > > led to the hang of the card and that's the reason why it was marked > > as "buggy" in LINT at that time. This was fixed but this comment > > just was not cleaned up. There was the same problem somewhere in '96 > > when David Greenman had changed the way the watchdog routines are > > called for network drivers, but after this driver was changed > > according to the new way it worked again. > > Hmmm... What version of FreeBSD are you using? I'd like to get mine > working; you appear to know what's going on. > I was using 2.0.5 at that time (and 2.0 before 2.0.5 was released), but 3c509 driver was for some period of time ahead of FreeBSD releases, I have transplanted it from later version to support Plug-n-Play mode and some other minor changes (actually, some of the changes were going in reverse direction, transplanted into -current from my 2.0.5 development machine). They key words to fix it are "use the watchdog routine, Luke" :-) The biggest problem with this driver seems to be that nobody from the core team is actively using it so when something in the network system gets changed, this driver gets broken until someone else who is actively using it notices and fixes that. -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 09:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09714 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:43:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09699 for ; Thu, 9 Jul 1998 09:43:24 -0700 (PDT) (envelope-from msanders@shell.aros.net) Received: from shell.aros.net (root@shell.aros.net [207.173.16.19]) by mars.aros.net (8.8.7/8.8.4) with ESMTP id KAA00299; Thu, 9 Jul 1998 10:43:01 -0600 (MDT) Received: from shell.aros.net (msanders@localhost.aros.net [127.0.0.1]) by shell.aros.net (8.8.7/8.8.5) with ESMTP id KAA00749; Thu, 9 Jul 1998 10:43:18 -0600 (MDT) Message-Id: <199807091643.KAA00749@shell.aros.net> X-Attribution: msanders To: Joel Ray Holveck cc: msanders@aros.net, smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "Thu, 09 Jul 1998 11:35:57 CDT." <199807091635.LAA04767@detlev.UUCP> X-Mailer: MH 6.8.3 Date: Thu, 09 Jul 1998 10:43:17 -0600 From: "Michael K. Sanders" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807091635.LAA04767@detlev.UUCP>, Joel Ray Holveck writes: > >Evidently we've got different definitions of 'very long time'. The >reason I have a 509 is because I built the system in '93, and I am >*quite* certain there were no 100Mbit cards for < $50... even any that >fell off the back of a lorry. You have a good point. I should have stated 'for nearly as long as the EtherExpress 100 cards have been in existance, you've been able to get them for $50'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 10:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14123 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 10:12:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from enterprise.dfacades.com (aria.dfacades.com [207.155.93.3] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14104; Thu, 9 Jul 1998 10:12:09 -0700 (PDT) (envelope-from dleeds@dfacades.com) Received: from bukowski.hepcat.org (cosmos@bukowski.hepcat.org [207.155.93.198]) by enterprise.dfacades.com (8.8.7/8.8.7) with ESMTP id KAA04819; Thu, 9 Jul 1998 10:05:31 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on Solaris X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 09 Jul 1998 10:13:44 -0700 (PDT) Reply-To: dleeds@dfacades.com Organization: DigitalFacades From: Daniel Leeds To: questions@FreeBSD.ORG, mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: us robotics pcmcia modem, CC1336 supported? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a megahertz/usrobotics pcmcia 33.6 modem, model CC1336 and cannot get it to work :( i looked around for a HCL, but couldnt find it. it has an entry in /etc/pccard.conf on 3.0-SNAP which i am running. but i cannot get it to work. i can connect to it via cu, and get it to dial, but i get no output. i can connect to /dev/cuaa0 and get output, but no dialtone, etc. i can connect to /dev/cuaa1 and get no output, but dial numbers and connect. i can connect to /dev/cuaa2 and get no output, but dial numbers and connect. can anyone help me? anyone running freebsd on a laptop with this modem? id appreciate ALL pointers/help/suggestions. i need to get this running ppp eventually... thanks ---------------------------------- E-Mail: Daniel Leeds Date: 09-Jul-98 Time: 10:09:45 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 10:17:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15041 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 10:17:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15028 for ; Thu, 9 Jul 1998 10:16:59 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA03679; Thu, 9 Jul 1998 12:16:57 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id MAA12023; Thu, 9 Jul 1998 12:16:26 -0500 Message-ID: <19980709121625.29898@right.PCS> Date: Thu, 9 Jul 1998 12:16:25 -0500 From: Jonathan Lemon To: zhihuizhang Cc: hackers Subject: Re: Multi-threaded and TCP/IP window size References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from zhihuizhang on Jul 07, 1998 at 10:06:17AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1998 at 10:06:17AM -0400, zhihuizhang wrote: > (2) A friend has a special application requirement in which two machines > are communicating with each other with TCP/IP. If the receiver send a > packet with window size of *zero*, it expects the sender to send one byte > a time immediately. He tested other Unix systems (Linux, SunOS, AIX) and > found that in these Unix systems, the sender keeps sending a lot of data > *for a while* before sending one byte a time (kind of probing). What he > wants is an instantanous response form the sender. Later when the receiver > sends a packet saying the window size is now, say, 3000 bytes, the sender > should be able to come to data rate *immediately*. Can this be (or > already have been) done by FreeBSD? This wouldn't be a mobile-tcpip link, would it, now? I don't know if it has been done specifically for FBSD, but it sounds suspiciously like some of the experimental mobile TCP/IP stack modifications, to get around the normal congestion control mechanisms. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 10:37:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17842 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 10:37:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17834 for ; Thu, 9 Jul 1998 10:37:52 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id NAA26549 for ; Thu, 9 Jul 1998 13:30:57 -0400 (EDT) Date: Thu, 9 Jul 1998 13:37:44 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-hackers@FreeBSD.ORG Subject: Questions on WaveLan networking... 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 this "friend" whos in a bind. This town we're in really blows for connectivity. It's either long haul dedicated connectivity from a town 30 miles away, or use crappy cable modem services which really blows. So I got to thinking about the wavelan stuff in freebsd and looking around. The distance between the offices of this "friend" are almost 5 miles. Am I correct in assuming you need the following items to make this work: 2 x wavelan isa cards in 2 freebsd boxen. one at each end. 2 x wavepoint II MAC bridges for the servers to connect to the hub on each end. and 2 x outdoor antenna's to extend the range to 5 miles using the 915Mhz model? Any other software, hardware? You just configure the WL cards on the server with wlconfig to set its parameters, and then configure it as a normal NIC card? Thanks for the info... Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:10:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24006 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:10:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA23923; Thu, 9 Jul 1998 11:10:00 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id NAA00769; Thu, 9 Jul 1998 13:07:45 -0500 Received: from stlabcexg004.anheuser-busch.com(unknown 151.145.101.160) by gatewayb via smap (V2.1) id xma029793; Thu, 9 Jul 98 13:07:17 -0500 Received: by stlabcexg004.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3QYWQC10>; Thu, 9 Jul 1998 19:10:12 +0100 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776608@STLABCEXG011> From: "Alton, Matthew" To: "'FreeBSD-fs@FreeBSD.ORG'" , "'Hackers@FreeBSD.ORG'" Subject: lfs b_blkno diddling Date: Thu, 9 Jul 1998 19:10:13 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having some difficulty determining where the physical disk block allocation algorithm is located. Does the lfs code (or ufs for that matter) just use the vnodes provided by the vm system without regard to the placement on disk (i.e. the value of (buf)->b_blkno) or does it somehow control these things. I thought that the ffs im- provements from 4.3BSD involved strategic physical locality of data placement on disk and assumed that this was implemented in the ffs code. I can see where doing a big nasty write to disk beats doing a lot of little writes in lfs - I also assumed that lfs writes tried to en- force contiguity if possible, I just can't see where. The word "strat- egy" crops up all over the place in the code. I'll look into that. The section 9 man pages are really sparse. I'll fix the VOP_* ones when I get this all sorted out :-) Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:10:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24111 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:10:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24076 for ; Thu, 9 Jul 1998 11:10:38 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA27454; Thu, 9 Jul 1998 11:10:36 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd027424; Thu Jul 9 11:10:32 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA19691; Thu, 9 Jul 1998 11:10:31 -0700 (MST) From: Terry Lambert Message-Id: <199807091810.LAA19691@usr04.primenet.com> Subject: Re: Multi-threaded and TCP/IP window size To: bf20761@binghamton.edu Date: Thu, 9 Jul 1998 18:10:30 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "zhihuizhang" at Jul 9, 98 10:06:17 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (1) I know for sure that FreeBSD does not supported multi-threaded. I am > considering the possibility of constructing a clustered file system using > a good NIC. I am just wondering if the fact that FreeBSD does not support > multi-threaded programming will affect the performance or implementation > of a clustered file system and how. FreeBSD supports multithreading. It does not support kernel threading without patches. If you need contexts within the kernel, it is possible to get them three ways: A) The way init, update/syncd, and the page daemon get them, by creating process contexts in the kernel. Since I was the person who generalized this mechanism in init_main.c, I know that you can start arbitrary processes using the same method by providing a "thread" entrypoint. B) The way nfsiod, et. al. do it, which is to create a process in user space, and make a call to kernel space that never returns to user space. This effectively creates the same situation, with the difference that you get a choice as to how many process contexts you provide the kernel. C) Contact Elvind and get a copy of John Dyson's patches in support of kernel threading. There is also primitive support for important things like SMP CPU affinity. > (2) A friend has a special application requirement in which two machines > are communicating with each other with TCP/IP. If the receiver send a > packet with window size of *zero*, it expects the sender to send one byte > a time immediately. He tested other Unix systems (Linux, SunOS, AIX) and > found that in these Unix systems, the sender keeps sending a lot of data > *for a while* before sending one byte a time (kind of probing). What he > wants is an instantanous response form the sender. Later when the receiver > sends a packet saying the window size is now, say, 3000 bytes, the sender > should be able to come to data rate *immediately*. Can this be (or > already have been) done by FreeBSD? You may want to contact Julian Elisher, julian@freebsd.org; he has done work in dynamic window size adjustment. I believe that the advertised window size would have to be one byte (not zero) for this to work, and if you dynamically adjusted it, then you would still have a short period until it took effect. One possible approach would be to synchronize by sending bytes of a particular value back and forth, and changing value when the one byte level has been reached. This would require a correlation delay, but the resulting channel will be one byte. Because TCP is reliable stream delivery, both ends will know when this situation has occurred, and can start up whatever protocol on top of this that they need. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25927 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:18:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25918 for ; Thu, 9 Jul 1998 11:18:11 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id OAA05431; Thu, 9 Jul 1998 14:16:35 -0400 (EDT) From: "Allen Smith" Message-Id: <9807091416.ZM5429@beatrice.rutgers.edu> Date: Thu, 9 Jul 1998 14:16:34 -0400 In-Reply-To: Snob Art Genre "Re: Someone working on swapoff?" (Jul 8, 11:55am) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: ben@rosengart.com Subject: Re: Someone working on swapoff? Cc: Stefan Eggers , 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 On Jul 8, 11:55am, Snob Art Genre (possibly) wrote: > On Wed, 8 Jul 1998, Allen Smith wrote: > > > > As I am at it: Any hints on good books, papers, whatever about paging > > > and swapping internals in BSD - especially FreeBSD? > > > > I'd be curious about this also; the existing information that I've > > found (in the 4.4 BSD book) is not exactly copious, and is somewhat > > outdated. > > How about /usr/share/doc/papers/newvm.ascii.gz? Thanks, but it doesn't really have much on the internals. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:18:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26111 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:18:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sol22.cs.wisc.edu (sol22.cs.wisc.edu [128.105.41.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26102 for ; Thu, 9 Jul 1998 11:18:52 -0700 (PDT) (envelope-from heyer@cs.wisc.edu) Received: from localhost (heyer@localhost) by sol22.cs.wisc.edu (8.8.6/8.8.6) with SMTP id NAA11083 for ; Thu, 9 Jul 1998 13:18:50 -0500 (CDT) Date: Thu, 9 Jul 1998 13:18:50 -0500 (CDT) From: John Heyer To: freebsd-hackers@FreeBSD.ORG Subject: swap_pager and vm_faults 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 Any idea what exactly would cause this? Jul 5 08:30:24 rancor /kernel: swap_pager: I/O error - pagein failed; blkno 708776, size 4096, error 22 Jul 5 08:30:24 rancor /kernel: vm_fault: pager input (probably hardware) error, PID 197 failure Jul 5 08:30:24 rancor /kernel: pid 197 (innd), uid 8: exited on signal 11 As you can tell from innd, this machine is a news Server with 96 Megs of RAM and 256 Megs of Swap. While the CPU and Disk Drives are kept pretty busy, it usually has plenty of memory to spare. The time it occured (8:30 AM on a Sunday) and the fact the machine stayed up seems very strange to me. This machine has been rebooting about once a day on average for no obvious reason, so I'm trying to investigate everything possible. -- John Heyer :: University of Wisconsin - Madison :: http://heyer.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:32:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28716 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:32:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sol22.cs.wisc.edu (sol22.cs.wisc.edu [128.105.41.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28682 for ; Thu, 9 Jul 1998 11:31:59 -0700 (PDT) (envelope-from heyer@cs.wisc.edu) Received: from localhost (heyer@localhost) by sol22.cs.wisc.edu (8.8.6/8.8.6) with SMTP id NAA11130 for ; Thu, 9 Jul 1998 13:31:58 -0500 (CDT) Date: Thu, 9 Jul 1998 13:31:58 -0500 (CDT) From: John Heyer To: freebsd-hackers@FreeBSD.ORG Subject: Innd Question 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 Here's another oddity about my troubled news server. It's happenend a few times where innd is using 0% CPU, doesn't show up in ps -aux, but is still runinng and can't be killed. Here's the output from "top": PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 28266 news -18 0 21868K 8516K objtrm 88:51 0.00% 0.00% innd 3431 news -6 4 232K 188K piperd 10:08 0.00% 0.00% crosspost 202 root 10 0 524K 192K wait 1:40 0.00% 0.00% sh This is a Pentium 200 system running 2.2.6 BTW. The only way I could think to end this problem is to just reboot. I hope I'm talking on the right list...I didn't notice one for News or innd. -- John Heyer :: University of Wisconsin - Madison :: http://heyer.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01075 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:41:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01043; Thu, 9 Jul 1998 11:41:17 -0700 (PDT) (envelope-from rafareta@mexcom.net.mx) Received: from mexcom.net.mx (rafa.nix.mexcom.net [206.103.64.101]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id NAA13088; Thu, 9 Jul 1998 13:39:57 -0500 (CDT) Message-ID: <35A50E84.FF61A50F@mexcom.net.mx> Date: Thu, 09 Jul 1998 13:40:04 -0500 From: "Rafael A. Reta Rodriguez" Organization: MexCom.Net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD sunix3.0.1 i386) MIME-Version: 1.0 To: dleeds@dfacades.com CC: questions@FreeBSD.ORG, mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: us robotics pcmcia modem, CC1336 supported? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Leeds wrote: > > Hi, > > I have a megahertz/usrobotics pcmcia 33.6 modem, model CC1336 and cannot get it > to work :( i looked around for a HCL, but couldnt find it. > > it has an entry in /etc/pccard.conf on 3.0-SNAP which i am running. but i > cannot get it to work. i can connect to it via cu, and get it to dial, but i > get no output. > > i can connect to /dev/cuaa0 and get output, but no dialtone, etc. > i can connect to /dev/cuaa1 and get no output, but dial numbers and connect. > i can connect to /dev/cuaa2 and get no output, but dial numbers and connect. > > can anyone help me? anyone running freebsd on a laptop with this modem? > > id appreciate ALL pointers/help/suggestions. > > i need to get this running ppp eventually... > > thanks > Are you in a PBX? I've been having problems to dial with a PCMCI USR from a PBX extension. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 11:45:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02036 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 11:45:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from enterprise.dfacades.com (aria.dfacades.com [207.155.93.3] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01997; Thu, 9 Jul 1998 11:44:56 -0700 (PDT) (envelope-from dleeds@dfacades.com) Received: from bukowski.hepcat.org (cosmos@bukowski.hepcat.org [207.155.93.198]) by enterprise.dfacades.com (8.8.7/8.8.7) with ESMTP id LAA06012; Thu, 9 Jul 1998 11:38:02 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on Solaris X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <35A50E84.FF61A50F@mexcom.net.mx> Date: Thu, 09 Jul 1998 11:46:15 -0700 (PDT) Reply-To: dleeds@dfacades.com Organization: DigitalFacades From: Daniel Leeds To: "Rafael A. Reta Rodriguez" Subject: Re: us robotics pcmcia modem, CC1336 supported? Cc: hackers@FreeBSD.ORG, mobile@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Are you in a PBX? I've been having problems to dial with a PCMCI USR > from a PBX extension. no. just a standard analog phone line. it seems to work somewhat...im at a loss :( ---------------------------------- E-Mail: Daniel Leeds Date: 09-Jul-98 Time: 11:44:28 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 12:15:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07442 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 12:15:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07425; Thu, 9 Jul 1998 12:15:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00486; Thu, 9 Jul 1998 21:13:33 +0200 (CEST) To: "Alton, Matthew" cc: "'FreeBSD-fs@FreeBSD.ORG'" , "'Hackers@FreeBSD.ORG'" Subject: Re: lfs b_blkno diddling In-reply-to: Your message of "Thu, 09 Jul 1998 19:10:13 BST." <31B3F0BF1C40D11192A700805FD48BF901776608@STLABCEXG011> Date: Thu, 09 Jul 1998 21:13:33 +0200 Message-ID: <484.900011613@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <31B3F0BF1C40D11192A700805FD48BF901776608@STLABCEXG011>, "Alton, Mat thew" writes: >I'm having some difficulty determining where the physical disk block >allocation algorithm is located. This is located in ffs respectively lfs start looking at ffs_balloc() -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 12:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08897 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 12:21:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08880; Thu, 9 Jul 1998 12:21:44 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id OAA02304; Thu, 9 Jul 1998 14:19:42 -0500 Received: from stlabcexg006.anheuser-busch.com(unknown 151.145.101.161) by gatewayb via smap (V2.1) id xma001094; Thu, 9 Jul 98 14:19:32 -0500 Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id <3QY72MRV>; Thu, 9 Jul 1998 14:22:01 -0500 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776609@STLABCEXG011> From: "Alton, Matthew" To: "'Poul-Henning Kamp'" Cc: "'FreeBSD-fs@FreeBSD.ORG'" , "'Hackers@FreeBSD.ORG'" Subject: RE: lfs b_blkno diddling Date: Thu, 9 Jul 1998 14:22:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And there it is 8) Thank you. > -----Original Message----- > From: Poul-Henning Kamp [SMTP:phk@critter.freebsd.dk] > Sent: Thursday, July 09, 1998 2:14 PM > To: Alton, Matthew > Cc: 'FreeBSD-fs@FreeBSD.ORG'; 'Hackers@FreeBSD.ORG' > Subject: Re: lfs b_blkno diddling > > In message <31B3F0BF1C40D11192A700805FD48BF901776608@STLABCEXG011>, > "Alton, Mat > thew" writes: > >I'm having some difficulty determining where the physical disk block > >allocation algorithm is located. > > This is located in ffs respectively lfs > > start looking at ffs_balloc() > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their > laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color > terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 13:02:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16612 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 13:02:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16547 for ; Thu, 9 Jul 1998 13:02:00 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id QAA20275 for ; Thu, 9 Jul 1998 16:01:59 -0400 (EDT) Date: Thu, 9 Jul 1998 16:01:58 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: hackers@FreeBSD.ORG Subject: Maybe time to configure Front Page Extensions... (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 Well, this thoroughly sucks. (apologies if this is a repost -- apparently my subscriptions were zapped for two days?) Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ ---------- Forwarded message ---------- Date: Thu, 09 Jul 1998 11:18:44 -0600 From: Kurt Raymond To: bsdi-users@bsdi.com Subject: Maybe time to configure Front Page Extensions... A news story about this is available at: http://dailynews.yahoo.com/headlines/technology/wired/story.html?s=z/reuters /980707/wired/stories/microsoft_1.html Front Page Extensions for BSDI are available at: http://www.rtr.com/fpsupport/SERK/default.htm -kurtray >> From: nev@bostic.com >> Date: Thu, 9 Jul 1998 10:05:00 -0400 (EDT) >> Subject: Advanced marketing. >> To: nev@bostic.com (/dev/null) >> >> Forwarded-by: Joe Ilacqua >> >> http://www.mdi.ca/sysadmin/fpexpress/ >> >> Front Page Express comes built-in to Windows 98. >> >> If you hand out "free user homepages", chances are, your users are >> going to want "Front Page Extensions" installed on your server. >> >> If you do not give Front Page Extensions to every one of your "free" >> homepage users and they try and use FRONT PAGE EXPRESS, then... >> >> Microsoft will spit out an error telling your customer to go find >> another ISP. -- To unsubscribe, send 'unsubscribe' to bsdi-users-request@mailinglists.org Archives of this list can be found at: http://www.nexial.nl/cgi-bin/bsdi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 14:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01610 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 14:44:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01605; Thu, 9 Jul 1998 14:44:04 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id OAA14480; Thu, 9 Jul 1998 14:37:32 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id OAA17187; Thu, 9 Jul 1998 14:37:31 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id OAA03663; Thu, 9 Jul 1998 14:37:30 -0700 (PDT) From: Don Lewis Message-Id: <199807092137.OAA03663@salsa.gv.tsc.tdk.com> Date: Thu, 9 Jul 1998 14:37:30 -0700 In-Reply-To: Poul-Henning Kamp "Re: lfs b_blkno diddling" (Jul 9, 9:13pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Poul-Henning Kamp , "Alton, Matthew" Subject: Re: lfs b_blkno diddling Cc: "'FreeBSD-fs@FreeBSD.ORG'" , "'Hackers@FreeBSD.ORG'" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 9, 9:13pm, Poul-Henning Kamp wrote: } Subject: Re: lfs b_blkno diddling } In message <31B3F0BF1C40D11192A700805FD48BF901776608@STLABCEXG011>, "Alton, Mat } thew" writes: } >I'm having some difficulty determining where the physical disk block } >allocation algorithm is located. } } This is located in ffs respectively lfs } } start looking at ffs_balloc() For a description, see /usr/share/doc/smm/05.fastfs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 17:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19229 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 17:02:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19221 for ; Thu, 9 Jul 1998 17:02:09 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA12460; Thu, 9 Jul 1998 20:01:37 -0400 (EDT) (envelope-from luoqi) Date: Thu, 9 Jul 1998 20:01:37 -0400 (EDT) From: Luoqi Chen Message-Id: <199807100001.UAA12460@lor.watermarkgroup.com> To: freebsd-hackers@FreeBSD.ORG, heyer@cs.wisc.edu Subject: Re: swap_pager and vm_faults Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any idea what exactly would cause this? > > Jul 5 08:30:24 rancor /kernel: swap_pager: I/O error - pagein failed; > blkno 708776, size 4096, error 22 You have a bad sector on your swap partition. I presume this is an IDE disk, you may try using bad144 to map the bad sector out. > Jul 5 08:30:24 rancor /kernel: vm_fault: pager input (probably hardware) > error, PID 197 failure > Jul 5 08:30:24 rancor /kernel: pid 197 (innd), uid 8: exited on signal 11 > > As you can tell from innd, this machine is a news Server with 96 Megs of > RAM and 256 Megs of Swap. While the CPU and Disk Drives are kept pretty > busy, it usually has plenty of memory to spare. The time it occured (8:30 > AM on a Sunday) and the fact the machine stayed up seems very strange to > me. This machine has been rebooting about once a day on average for no > obvious reason, so I'm trying to investigate everything possible. > > -- > John Heyer :: University of Wisconsin - Madison :: http://heyer.ml.org > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 18:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29803 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 18:26:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA29798 for ; Thu, 9 Jul 1998 18:26:01 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 28738 invoked from network); 10 Jul 1998 01:26:01 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 10 Jul 1998 01:26:01 -0000 Date: Thu, 9 Jul 1998 18:26:01 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@FreeBSD.ORG Subject: Any work going on NFS client in 2.2.x-stable series? 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 Or is everybody's efforts in -current? I've noticed a few anomalies on a 2.2.5 box, and was thinking of upgrading, but since it's fairly critical that it work just peachy, and it generally does, I'd hate to mess with a good thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 22:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22174 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 22:22:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from linux.cca.usart.ru (max@linux.cca.usart.ru [194.226.230.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22007 for ; Thu, 9 Jul 1998 22:22:00 -0700 (PDT) (envelope-from max@cca.usart.ru) Received: from localhost (max@localhost) by linux.cca.usart.ru (8.8.6/8.8.4) with SMTP id LAA32235; Fri, 10 Jul 1998 11:24:14 +0600 Date: Fri, 10 Jul 1998 11:24:13 +0600 (ESD) From: Max Gotlib To: Open Systems Networking cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions on WaveLan networking... 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 Hi OSN! We have a wavelan-powered channel between our academy and our provider that is situated in 2 miles to the west from us :) This channel is constructed from: (our point) ISA WaveLAN AT/2.4G board in i486DX2-66/8M machine outdoor antenna kit with unidirectional ant. FreeBSD 2.2.6 patched with INRIA (IPv6) staff and several (my) patches to the WaveLAN driver. (their point) some kind of WavePOINT radio-hub, directly connected to the backbone network, outdoor omnidirectional antenna kit (i'm not very shure abouth "their" configuration they change it every month :) We istablished this channel more than 3 year ago. First time it was Linux(out) <-> NetWare(their) connection. About half a year we change OS to FreeBSD and they moved to WavePOINT... As I have figured out, there is the nessessity to patch WaveLAN driver (FreeBSD-2.2.5 ... 3.0 current) to let it correctly drive an old full-length isa boards (the one we have)... If you have any q's - I can try to help you, and as for the q's you've asked: > Am I correct in assuming you need the following items to make this > work: > > 2 x wavelan isa cards in 2 freebsd boxen. one at each end. Yes. > 2 x wavepoint II MAC bridges for the servers to connect to the hub on > each end. No (or you can replace wavelan boards with wavepoints) > and 2 x outdoor antenna's to extend the range to 5 miles using the > 915Mhz model? We use 2.4G staff and according to the documantation it is sutable to handle up to 5 miles connections (we have 2 miles and it is "trusted" interval). > You just configure the WL cards on the server with wlconfig to set its > parameters, and then configure it as a normal NIC card? As for wlconfig, you have to use it once to configure NET ID's. But this can be done (and better done, because wlconfig is not fully functional yet) with the configuration utility the boards are shipped with (there is not bad diagnistic utility in their packageas well) ... With best regards, Max. On Thu, 9 Jul 1998, Open Systems Networking wrote: > I have this "friend" whos in a bind. This town we're in really blows for > connectivity. It's either long haul dedicated connectivity from a town 30 > miles away, or use crappy cable modem services which really blows. > So I got to thinking about the wavelan stuff in freebsd and looking > around. The distance between the offices of this "friend" are almost 5 > miles. Am I correct in assuming you need the following items to make this > work: > > 2 x wavelan isa cards in 2 freebsd boxen. one at each end. > 2 x wavepoint II MAC bridges for the servers to connect to the hub on each > end. > and 2 x outdoor antenna's to extend the range to 5 miles using the 915Mhz > model? > > Any other software, hardware? > > You just configure the WL cards on the server with wlconfig to set its > parameters, and then configure it as a normal NIC card? > > Thanks for the info... > > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 9 23:30:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28287 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 23:30:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outreach.wolfnet.org (root@outreach.wolfnet.org [207.173.133.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28281 for ; Thu, 9 Jul 1998 23:30:14 -0700 (PDT) (envelope-from jkf@wolfnet.org) Received: from outreach.wolfnet.org (jkf@outreach.wolfnet.org [207.173.133.202]) by outreach.wolfnet.org (8.8.8/8.8.8) with SMTP id XAA14661 for ; Thu, 9 Jul 1998 23:31:04 -0700 (PDT) (envelope-from jkf@wolfnet.org) Date: Thu, 9 Jul 1998 23:31:04 -0700 (PDT) From: "Jason K. Fritcher" To: hackers@FreeBSD.ORG Subject: Raw sockets & ICMP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I've been working on an icmp logger today, and ran across an interesting problem. It seems the kernel in 2.2.6-stable does not pass all icmp packets to the raw sockets. I looked through the code in icmp_input, and from what I can see, echo, timestamp, and mask request packets don't make it to the rip_input call. Was this intentional, or were those packets simply overlooked because of the processing in the reflect block? -- Jason K. Fritcher jkf@wolfnet.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 01:39:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08959 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 01:39:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08954 for ; Fri, 10 Jul 1998 01:39:33 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id BAA23365; Fri, 10 Jul 1998 01:39:34 -0700 (PDT) Message-ID: <19980710013934.B17377@Alameda.net> Date: Fri, 10 Jul 1998 01:39:34 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: freefall down ? Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is not pingable from hub. Neither the home dirs seem to be mounted. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 02:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11204 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 02:08:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shaman.lycaeum.org (shaman.lycaeum.org [207.66.171.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11199; Fri, 10 Jul 1998 02:08:49 -0700 (PDT) (envelope-from edmond@shaman.lycaeum.org) Received: from localhost (edmond@localhost) by shaman.lycaeum.org (Partyon/dude!) with SMTP id CAA22992; Fri, 10 Jul 1998 02:08:46 -0700 (PDT) Date: Fri, 10 Jul 1998 02:08:46 -0700 (PDT) From: "Andrew N. Edmond (Nero)" To: questions@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: optimizing with a heavy load... 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 four Dual Pentium II 333mhz computers (DK440LX motherboards), 512MB of memory each, all running on 100Mb switched ethernet, 9 gig SCSI-2 Cheetahs, and everything is running great, until I experience heavy load. Two of the computers are running MySQL databases (one processing more than 2,000,000 transactions per day, the other processing more than 4,000,000 transactions per day). The other two computers are running Apache 1.2.5 + FastCGI, and processing upwards of 7 million hits per day combined. Obviously, I'm using a lot of file handles and sockets, and as I experience super heavy load (anything more than it is now), I start seeing a rash of errors due to, what I think, is an improperly configured kernel. FreeBSD 052098-SNAP, some of the kernel configuration: maxusers 512 options NMBCLUSTERS=4096 options "CHILD_MAX=512" options "OPEN_MAX=512" options SYSVSHM options SYSVSEM options SYSVMSG also, I do this is /etc/rc.local: /sbin/sysctl -w kern.ipc.somaxconn=4096 /sbin/sysctl -w kern.maxfiles=16384 ------------------------------------------------------------------------------ Questions: How else do I optimize this machine for more load? What the heck is an NMBCLUSTER anyhow? ------------------------------------------------------------------------------ Thanks so much for any help you can give! Andy Edmond +-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ || Andrew N. Edmond | Lycaeum Director | Nymserver Administrator || || edmond@lycaeum.org | http://www.lycaeum.org/ | http://www.nymserver.com/ || >---------------------+-------------------------+----------------------------< || Children of a future age, reading this indignant page, know that in a || || former time, a path to love was thought a crime - William Blake || +-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 02:42:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15174 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 02:42:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15169 for ; Fri, 10 Jul 1998 02:42:33 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id LAA27615 ; Fri, 10 Jul 1998 11:41:14 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id LAA28397; Fri, 10 Jul 1998 11:41:14 +0200 To: "Michael K. Sanders" Cc: sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: <199807091551.JAA18853@shell.aros.net> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 10 Jul 1998 11:41:13 +0200 In-Reply-To: "Michael K. Sanders"'s message of Thu, 09 Jul 1998 09:51:00 -0600 Message-ID: Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael K. Sanders" writes: > In message , Dag-Erling Coidan Sm rgr > av writes: > >sbabkin@dcn.att.com writes: > > > > (160 kbps). Gimme an Intel EtherExpress. > > > Sure, _now_, when you can get 100Mbps EtherExpress for > > > the same money, nobody would buy 3c509. But a few years ago > > -------------- > > Half the money, if the reports I've heard of EtherExpress cards > > retailing at $50 are reliable. > You've always[1] been able to get EtherExpress 100 cards for $50-- you > could get two 100B cards directly from Intel for $49 ea. through their > "evaluation program"[2], and numerous mail order companies currently > have the 100B and 100+ for < $50. Sounds good to me :) Last time I checked, retail prices for Etherlink III NICs in Norway were closer to $100 than $50. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 02:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15595 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 02:49:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15589; Fri, 10 Jul 1998 02:49:26 -0700 (PDT) (envelope-from jkoshy@FreeBSD.org) From: Joseph Koshy Received: (from jkoshy@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id CAA01481; Fri, 10 Jul 1998 02:49:26 -0700 (PDT) Date: Fri, 10 Jul 1998 02:49:26 -0700 (PDT) Message-Id: <199807100949.CAA01481@freefall.freebsd.org> To: freebsd-hackers@FreeBSD.ORG Subject: Do you rely on "dump"s (currently incorrect) exit codes? Cc: jkoshy@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm planning a straight-forward change to "dump" to make its exit codes confirm to the man page. Currently "dump" returns "3" (i.e. non-recoverable error) in a number of places where it should return "1" (startup error). No big deal. My concern however, is that people may be using the `wrong' return values in their backup scripts. If you feel you are going to be badly affected by such a change and if you feel this change shouldn't take place, please speak up now! (PR: 5346) Koshy (who would rather not pull the rug from under some hapless sysadmin relying on the incorrect exit codes :-)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 04:18:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25636 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 04:18:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25631 for ; Fri, 10 Jul 1998 04:18:54 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id NAA02066 ; Fri, 10 Jul 1998 13:18:21 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id NAA29627; Fri, 10 Jul 1998 13:18:20 +0200 To: ulf@alameda.net Cc: hackers@FreeBSD.ORG Subject: Re: freefall down ? References: <19980710013934.B17377@Alameda.net> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 10 Jul 1998 13:18:19 +0200 In-Reply-To: Ulf Zimmermann's message of Fri, 10 Jul 1998 01:39:34 -0700 Message-ID: Lines: 18 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann writes: > Is not pingable from hub. Neither the home dirs seem to be mounted. Looks good to me. smoergrd@sunw132 ~$ ping -s freefall.freebsd.org PING freefall.freebsd.org: 56 data bytes 64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=0. time=581. ms 64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=1. time=398. ms 64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=2. time=439. ms ^C ----freefall.freebsd.org PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 398/472/581 DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 06:14:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07354 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 06:14:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07346; Fri, 10 Jul 1998 06:13:55 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id PAA07767 ; Fri, 10 Jul 1998 15:13:16 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id PAA01130; Fri, 10 Jul 1998 15:13:15 +0200 To: "Andrew N. Edmond (Nero)" Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: optimizing with a heavy load... References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 10 Jul 1998 15:13:13 +0200 In-Reply-To: "Andrew N. Edmond's message of Fri, 10 Jul 1998 02:08:46 -0700 (PDT) Message-ID: Lines: 27 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrew N. Edmond (Nero)" writes: > FreeBSD 052098-SNAP, some of the kernel configuration: > > maxusers 512 > options NMBCLUSTERS=4096 > options "CHILD_MAX=512" > options "OPEN_MAX=512" > options SYSVSHM > options SYSVSEM > options SYSVMSG Your maxusers is so high that setting NMBCLUSTERS to 4096 actually *reduces* the number of mbuf clusters instead of increasing it. Leave that line out, or raise the value above 8704 (which is the default computed value for maxusers=512) > also, I do this is /etc/rc.local: > > /sbin/sysctl -w kern.ipc.somaxconn=4096 > /sbin/sysctl -w kern.maxfiles=16384 The default value for maxfiles with maxusers=512 is 16424, which again is higher (though not by much) than your arbitrarily tweaked value. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 06:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11170 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 06:41:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA10792; Fri, 10 Jul 1998 06:38:59 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id JAA01264; Fri, 10 Jul 1998 09:38:13 -0400 Date: Fri, 10 Jul 1998 09:38:12 -0400 (EDT) From: Jamie Bowden To: "Jonathan M. Bresler" cc: Terry Lambert , joelh@gnu.org, mike@smith.net.au, dmm125@bellatlantic.net, questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: FreeBSD equiv. of /proc/loadavg In-Reply-To: <199807030027.RAA05728@hub.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 Thu, 2 Jul 1998, Jonathan M. Bresler wrote: > Terry Lambert wrote: > > > >> I realize now though that if you want to port some apps with > > > >> low-level details, you gotta do a little reworking. > > > > Yup. Particularly when you're dealing with code written for Linux > > > > (where NIH is considered a virtue...). > > > > > > What's NIH? > > > > We can't tell you; the use of the term was Not Invented Herei, and > > thus, like SysV rc.d, we fear and mistrust it... 8-). > > Oh Terry! i dont like rc.d because i am left which > "which of these scripts in which directory did what!" > why? grr.... > > with our current strcuture, we have some separation without > reaching the level of cookiness that sunos 5.5.1 provides: > 70 shell scripts scattered across 5 directories. Eevery last one of those shell scripts in /etc/rcX.d points back to a file in /etc/init.d. There's nothing wrong with the SysV init. I tend to prefer it personally. Guarantees proper startup and shutdown of important services, like, oh, oracle, which really just hates not be sent a dbshut and given the proper time to dismount the database. I also like being able to use those scripts to shutdown and restart processes individually on a running system in the exact fashion that init does at startup/change of runlevel. There is a reason for the change of rc in SysV, and it's not a bad thing, just different. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 07:08:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14873 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 07:08:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA14866 for ; Fri, 10 Jul 1998 07:08:36 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id HAA29382 for hackers@freebsd.org; Fri, 10 Jul 1998 07:07:24 -0700 Date: Fri, 10 Jul 1998 07:07:24 -0700 From: Joe McGuckin Message-Id: <199807101407.HAA29382@monk.via.net> To: hackers@FreeBSD.ORG Subject: interface address spontaenously disappearing ? X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have a couple of web servers running 2.2.6-RELEASE. We're seeing what appears to be aliased interface addresses randomly disappearing Has anyone else seen this happening? How difficult would it be to have the kernel generate a syslog message when an IP address is added or deleted for debugging purposes? Thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 08:06:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22129 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 08:06:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22124 for ; Fri, 10 Jul 1998 08:06:16 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id RAA00085; Fri, 10 Jul 1998 17:03:33 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id QAA12935; Fri, 10 Jul 1998 16:57:31 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807101457.QAA12935@semyam.dinoco.de> To: John Heyer Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Innd Question In-reply-to: Your message of "Thu, 09 Jul 1998 13:31:58 CDT." Date: Fri, 10 Jul 1998 16:57:30 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's another oddity about my troubled news server. It's happenend a few > times where innd is using 0% CPU, doesn't show up in ps -aux, but is still > runinng and can't be killed. > 28266 news -18 0 21868K 8516K objtrm 88:51 0.00% 0.00% innd Note the state it is in. "objtrm" is in the VM subsystem and you sent a message about trouble with the swap partition to the list. It is waiting there for a paging operation to terminate. If this is the same machine a quick guess (w/o having read all the source) from me is that the swap in failed due to an I/O error. You then tried to kill it (or the system did that) which was successful so far. Now the system has to free the processes memory and that's what I think it was doing when you discovered this state. It was waiting for a paging operation to terminate in order to free memory but this termination never happened due to the previous I/O error. I hope I'm not too wrong with my theory. At least it sounds plausible to me. ;-) > This is a Pentium 200 system running 2.2.6 BTW. The only way I could > think to end this problem is to just reboot. I hope I'm talking on the > right list...I didn't notice one for News or innd. This is the right one as it your problem is related to kernel inter- nals. If I'm right I think the propper solution is really to reboot as w/o this page innd won't do anything anymore. After rebooting into single user mode check the swap partition to find out why it failed. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 10:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11314 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 10:33:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@hobbes.saturn-tech.com [207.229.19.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11294 for ; Fri, 10 Jul 1998 10:33:45 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id LAA22889; Fri, 10 Jul 1998 11:32:50 -0600 (MDT) Date: Fri, 10 Jul 1998 11:32:50 -0600 (MDT) From: Doug Russell To: Dag-Erling Coidan Smørgrav cc: sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA11295 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > Believe me, it still sucks. Search the archives (both the mailing list > archives and the PR database) for "no buffer space", and/or "ep0". > Basically, the driver is fine for telnet and mail, but wedges under > sustained load. I can get it to hang without ever going above 20 kBps > (160 kbps). Gimme an Intel EtherExpress. They are definitely funky. I have one (thank goodness it was given to me, I didn't buy it. :) ) It usually sits on the shelf, but when I have tried to use it, it will do all kinds of strange things. In some machines, the probe fails to detect it. Drop it straight into another machine, and it will be detected fine. If you can get it detected, sometimes it will basically work, and sometimes it will go at about 5 K/sec. Drop it into another machine, and it'll do 800 K/sec. Don't ask me... I don't know. That's why it sits on the shelf. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 10:38:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12026 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 10:38:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12014 for ; Fri, 10 Jul 1998 10:38:37 -0700 (PDT) (envelope-from shigio@wafu.netgate.net) Message-Id: <199807101738.KAA12014@hub.freebsd.org> Received: (qmail 24502 invoked from network); 10 Jul 1998 09:38:22 -0000 Received: from ins11.tama-ap3.dti.ne.jp (HELO choota.signet.or.jp) (203.181.67.11) by wafu.netgate.net with SMTP; 10 Jul 1998 09:38:22 -0000 Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.7/) with ESMTP id CAA00918; Sat, 11 Jul 1998 02:39:37 +0900 (JST) To: hackers@FreeBSD.ORG Cc: shigio@wafu.netgate.net Subject: Improvemnet of ln(1). Date: Sat, 11 Jul 1998 02:39:37 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all I'm thinking about improvement of ln(1). [Problem] Ln(1) with -s option makes illegal symbolic link in some case. For example, (Both '/usr/src/sys' and '/tmp' are real directories.) % cd /usr % ln -s src/sys /tmp % ls -l /tmp/sys lrwxrwxrwx 1 shigio wheel 7 Jul 11 02:03 /tmp/sys -> src/sys % cd /tmp/sys /tmp/sys: No such file or directory. Symbolic link '/tmp/sys' has illegal value, so we cannot move there. Above behavior is not desireble in almost case, I think. [Solution] It would be more useful if ln(1) works like follows. Two options are added. Both of them is valid only with -s option. -r option: make right and relative symbolic link -a option: make right and absolute symbolic link (-r and -a cannot be used at a same time.) % cd /usr % ln -sr src/sys /tmp % ls -l /tmp/sys lrwxrwxrwx 1 shigio wheel 14 Jul 11 02:00 /tmp/sys -> ../usr/src/sys % cd /tmp/sys % pwd /usr/src/sys % cd /usr % ln -sa src/sys /tmp % ls -l /tmp/sys lrwxrwxrwx 1 shigio wheel 12 Jul 11 02:02 /tmp/sys -> /usr/src/sys % cd /tmp/sys % pwd /usr/src/sys New version of ln(1) makes right symbolic link. [Question] Is it improvement? Is it useful? Is it the right way to do it? Is there any problem made by this solution? Comment appreciated. Thank you in advance. -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 12:09:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24061 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 12:09:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dsi1.dsi.com.mx (dsi1.dsi.com.mx [200.33.196.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24050 for ; Fri, 10 Jul 1998 12:09:50 -0700 (PDT) (envelope-from szapata@creatos.com.mx) Received: from [200.33.165.133] by dsi1.dsi.com.mx (Post.Office MTA v3.5 release 214 ID# 0-49601U5000L500S0V35) with ESMTP id mx for ; Fri, 10 Jul 1998 14:08:54 -0500 X-Sender: sz@dns.cabonet.net.mx Message-Id: In-Reply-To: References: Ulf Zimmermann's message of Fri, 10 Jul 1998 01:39:34 -0700 <19980710013934.B17377@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 10 Jul 1998 14:11:41 -0600 To: hackers@FreeBSD.ORG From: Santiago Zapata Sauceda Subject: Re: freefall down ? Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA24057 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Ulf Zimmermann writes: >> Is not pingable from hub. Neither the home dirs seem to be mounted. > >Looks good to me. > >smoergrd@sunw132 ~$ ping -s freefall.freebsd.org >PING freefall.freebsd.org: 56 data bytes >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=0. time=581. ms >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=1. time=398. ms >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=2. time=439. ms >^C >----freefall.freebsd.org PING Statistics---- >3 packets transmitted, 3 packets received, 0% packet loss >round-trip (ms) min/avg/max = 398/472/581 > >DES >-- >Dag-Erling Sm¯rgrav - smoergrd@oslo.geco-prakla.slb.com > It is not reachable from some points. Do a traceroute from your site Ulf. It stucks at a NAP point in NY or NJ. Santiago --------------------------------------------------------------------------- Santiago Zapata Sauceda METCOM, S.A. de C.V. szapata@creatos.com.mx Tetitla No 9, Col Toriello Guerra 14050 Mexico, D.F. tel. 528 3113 fax 606 7074 From the U.S. phone 011 52 5 528 3113 fax 011 52 5 606 7074 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 12:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27925 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 12:44:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27915; Fri, 10 Jul 1998 12:44:16 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA26731; Fri, 10 Jul 1998 12:43:45 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma026729; Fri Jul 10 12:43:39 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA27189; Fri, 10 Jul 1998 12:43:39 -0700 (PDT) From: Archie Cobbs Message-Id: <199807101943.MAA27189@bubba.whistle.com> Subject: Re: Do you rely on "dump"s (currently incorrect) exit codes? In-Reply-To: <199807100949.CAA01481@freefall.freebsd.org> from Joseph Koshy at "Jul 10, 98 02:49:26 am" To: jkoshy@FreeBSD.ORG (Joseph Koshy) Date: Fri, 10 Jul 1998 12:43:39 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Joseph Koshy writes: > I'm planning a straight-forward change to "dump" to make its exit codes > confirm to the man page. Currently "dump" returns "3" (i.e. non-recoverable > error) in a number of places where it should return "1" (startup error). Do these values jive OK with man sysexits(3) ? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 13:26:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04813 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 13:26:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA04780 for ; Fri, 10 Jul 1998 13:26:08 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id QAA27244; Fri, 10 Jul 1998 16:24:53 -0400 Date: Fri, 10 Jul 1998 16:24:52 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Shigio Yamaguchi cc: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807101738.KAA12014@hub.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 Sat, 11 Jul 1998, Shigio Yamaguchi wrote: > Ln(1) with -s option makes illegal symbolic link in some case. > Two options are added. Both of them is valid only with -s option. > -r option: make right and relative symbolic link > -a option: make right and absolute symbolic link >Is it improvement I think so. > Is it useful? It would save people some trouble. Actually, why not just have ln warn of questionable links in any case. > Is there any problem made by this solution? Added features are always a concern, but something like this does seem reasonable. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 13:27:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05247 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 13:27:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05214 for ; Fri, 10 Jul 1998 13:27:33 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA24586; Fri, 10 Jul 1998 09:46:05 -0400 Date: Fri, 10 Jul 1998 09:46:04 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: p2align In-Reply-To: <199807090508.WAA03001@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks john, I found the same thing too. What basically happened was my -current from a few months back was just too old to be updated via cvsup and 'make world'. So I just reloaded the machine with the new -current. Things are fine now. For those of you who have thought about fxtv: it's quite amazing. Esp. since i'm currently not even running with DIRECT mode on, i.e. screen updates are done in software. You can run programs that hammer the disk and the video still runs at a seeming 30 fps. Absolutely amazing (this is on a P2/300 though). One thing for the fxtv guys to think about, or maybe you have done it: a -lcapture, i.e. a library that could run the video capture with no X stuff intermingled would be quite useful. thanks ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 13:41:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08531 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 13:41:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08481; Fri, 10 Jul 1998 13:41:34 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id QAA19648; Fri, 10 Jul 1998 16:34:29 -0400 (EDT) Date: Fri, 10 Jul 1998 16:41:23 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: "Andrew N. Edmond (Nero)" cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: optimizing with a heavy load... 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, 10 Jul 1998, Andrew N. Edmond (Nero) wrote: > options NMBCLUSTERS=4096 Raise this number to a higher value, double it. Im not sure what size the app is either but if its over 128MB's try looking at lint at the following two options: options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" A couple of ideas anyway. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 13:51:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12214 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 13:51:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12116 for ; Fri, 10 Jul 1998 13:50:57 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id BAA26242; Fri, 10 Jul 1998 01:56:19 -0400 (EDT) Date: Fri, 10 Jul 1998 02:03:14 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Max Gotlib cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions on WaveLan networking... 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 Max, THANKS for the info! I'll pass this along to the person interested. And ill be sure to mail should anymore questions arise. Thanks again for all the info!! Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 14:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16673 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 14:11:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from merlin.darkmage.net (mwsmith@[207.238.141.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16667 for ; Fri, 10 Jul 1998 14:11:09 -0700 (PDT) (envelope-from mwsmith@merlin.darkmage.net) Received: from localhost (mwsmith@localhost) by merlin.darkmage.net (8.8.8/8.8.8) with SMTP id OAA00378 for ; Fri, 10 Jul 1998 14:08:41 -0700 (PDT) (envelope-from mwsmith@merlin.darkmage.net) Date: Fri, 10 Jul 1998 14:08:41 -0700 (PDT) From: "Michael W. Smith" To: freebsd-hackers@FreeBSD.ORG Subject: Too many files open? 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 keep getting a too many files open error on the system and it's hosing it all to hell. A friend of mine who's more familiar with FreeBSD told me I need to rebuild the kernel but he wasn't sure which directive I need to change to fix it. I've got the Complete FreeBSD book, and know how to rebuild the kernel, but it's not entirely clear what I need to change to stop that error from happening. Any help would be greatly appreciated. -Mike ------------------------------------------------------------------------------- "Why make history if you fail to learn from it?" - Vir, "Knives" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 14:28:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19557 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 14:28:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19552 for ; Fri, 10 Jul 1998 14:28:30 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: by kcgw1.att.com; Fri Jul 10 15:18 CDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id PAA02156 for ; Fri, 10 Jul 1998 15:18:28 -0500 (CDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id <32C9HX77>; Fri, 10 Jul 1998 16:18:27 -0400 Message-ID: To: shigio@wafu.netgate.net, hackers@FreeBSD.ORG Subject: RE: Improvemnet of ln(1). Date: Fri, 10 Jul 1998 16:18:26 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Shigio Yamaguchi [SMTP:shigio@wafu.netgate.net] > > I'm thinking about improvement of ln(1). > > [Problem] > > Ln(1) with -s option makes illegal symbolic link in some case. > For example, > > (Both '/usr/src/sys' and '/tmp' are real directories.) > > % cd /usr > % ln -s src/sys /tmp > % ls -l /tmp/sys > lrwxrwxrwx 1 shigio wheel 7 Jul 11 02:03 /tmp/sys -> src/sys > % cd /tmp/sys > /tmp/sys: No such file or directory. > > Symbolic link '/tmp/sys' has illegal value, so we cannot move there. > Above behavior is not desireble in almost case, I think. > > [Solution] > ln -s `pwd`/src/sys /tmp Isn't it simpler ? -Serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 15:12:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28050 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 15:12:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (qmailr@mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28003 for ; Fri, 10 Jul 1998 15:12:12 -0700 (PDT) (envelope-from peter@taronga.com) Received: (qmail 2592 invoked from network); 10 Jul 1998 11:05:25 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 10 Jul 1998 11:05:25 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA16976 for hackers@freebsd.org; Fri, 10 Jul 1998 06:04:21 -0500 Date: Fri, 10 Jul 1998 06:04:21 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199807101104.GAA16976@bonkers.taronga.com> To: hackers@FreeBSD.ORG Subject: Is this list still live? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't seen anything in this list since Ron Minnich's message on Sunday about his hoopy distributed /proc code. Message-ID: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 15:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02536 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 15:35:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02518 for ; Fri, 10 Jul 1998 15:35:05 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id SAA12067; Fri, 10 Jul 1998 18:26:49 -0400 (EDT) Date: Fri, 10 Jul 1998 18:33:43 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Peter da Silva cc: hackers@FreeBSD.ORG Subject: Re: Is this list still live? In-Reply-To: <199807101104.GAA16976@bonkers.taronga.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, 10 Jul 1998, Peter da Silva wrote: > I haven't seen anything in this list since Ron Minnich's message on > Sunday about his hoopy distributed /proc code. Its alive, just quiet. Maybe tooo quiet.. hrmmm :-) Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 15:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05128 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 15:48:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05076 for ; Fri, 10 Jul 1998 15:47:55 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id PAA09522; Fri, 10 Jul 1998 15:48:17 -0700 (PDT) Date: Fri, 10 Jul 1998 15:48:16 -0700 (PDT) From: Dan Busarow To: "Michael W. Smith" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Too many files open? 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, 10 Jul 1998, Michael W. Smith wrote: > I keep getting a too many files open error on the system and it's hosing > it all to hell. A friend of mine who's more familiar with FreeBSD told me > I need to rebuild the kernel but he wasn't sure which directive I need to > change to fix it. I've got the Complete FreeBSD book, and know how to > rebuild the kernel, but it's not entirely clear what I need to change to > stop that error from happening. Any help would be greatly appreciated. Usually the easiest way to fix this is just to increase the value of maxusers in your kernel config file. maxusers controls quite a few system limits. You made need to do more, depending on what this box is doing but this is a good start. Dan -- Dan Busarow 949 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 15:55:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06380 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 15:55:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06342 for ; Fri, 10 Jul 1998 15:55:09 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA08125; Fri, 10 Jul 1998 15:55:42 -0700 (PDT) Message-Id: <199807102255.PAA08125@implode.root.com> To: Santiago Zapata Sauceda cc: hackers@FreeBSD.ORG Subject: Re: freefall down ? In-reply-to: Your message of "Fri, 10 Jul 1998 14:11:41 MDT." From: David Greenman Reply-To: dg@root.com Date: Fri, 10 Jul 1998 15:55:42 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It is not reachable from some points. > >Do a traceroute from your site Ulf. It stucks at a NAP point in NY or NJ. There were some network problems in Philadelphia that cause connectivity problems with most east coast sites. This should be resolved now. There is also a major fiber cut in Philadelphia that is causing other connectivity problems, but these should be more isolated. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 17:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00265 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 17:53:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.alcatel.com.au (gatekeeper.alcatel.com.au [203.17.66.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00237 for ; Fri, 10 Jul 1998 17:53:21 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from mfg1.cim.alcatel.com.au ("port 2195"@[139.188.23.1]) by gatekeeper.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IZ9SM56WKW00097W@gatekeeper.alcatel.com.au> for hackers@freebsd.org; Sat, 11 Jul 1998 10:52:43 +1000 Received: from gsms01.alcatel.com.au by cim.alcatel.com.au (PMDF V5.1-10 #U2695) with ESMTP id <01IZ9SM2J4GW8X1UH7@cim.alcatel.com.au> for hackers@freebsd.org; Sat, 11 Jul 1998 10:52:40 +1000 Received: (from jeremyp@localhost) by gsms01.alcatel.com.au (8.8.8/8.7.3) id KAA07523 for hackers@freebsd.org; Sat, 11 Jul 1998 10:52:38 +1000 (EST) Date: Sat, 11 Jul 1998 10:52:38 +1000 (EST) From: Peter Jeremy Subject: PPS device To: hackers@FreeBSD.ORG Message-id: <199807110052.KAA07523@gsms01.alcatel.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone using a PPS device with FreeBSD? I notice that -current includes support for a PPS source attached via a parallel port. For some time, I have been using a PPS source via DCD on a serial port (if anyone wants the patches to sio.c, let me know). One problem with this approach is jitter - firstly, there's the general interrupt latency (I'm not sure how to measure this, but I'd assume it's in the 10's of usec on a 486) and secondly interrupt masking via spl(). One approach I have been considering is to have a hardware counter counting the number of (eg) usec from the 1pps transition time and read it as an 8-bit number via the parallel port. This would reduce the unfiltered jitter to <1usec. Based on a quick read of draft-mogul-pps-api-02.txt, this either hasn't been considered, or has been discarded. Does anyone have any comments on this idea. BTW: Anyone looking for a good stand-alone reference might like to look at the master reference oscillators in digital cellular base stations - the GSM standard (which also covers DCS-1800 and DCS-1900) requires a 0.05ppm or better reference in the base station. I suspect DAMPS and CMDA also have similarly tight tolerances. Whilst these references are expensive new, if you know someone in the industry, you might be able to acquire one from a junked board. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 18:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07587 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 18:48:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07579 for ; Fri, 10 Jul 1998 18:48:11 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA05767; Fri, 10 Jul 1998 18:48:12 -0700 (PDT) Message-ID: <19980710184811.A4936@Alameda.net> Date: Fri, 10 Jul 1998 18:48:11 -0700 From: Ulf Zimmermann To: Santiago Zapata Sauceda , hackers@FreeBSD.ORG Subject: Re: freefall down ? Reply-To: ulf@Alameda.net References: <19980710013934.B17377@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Santiago Zapata Sauceda on Fri, Jul 10, 1998 at 02:11:41PM -0600 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Turned out it was in ddb with a NMI interupt. Message from jkh. On Fri, Jul 10, 1998 at 02:11:41PM -0600, Santiago Zapata Sauceda wrote: > >Ulf Zimmermann writes: > >> Is not pingable from hub. Neither the home dirs seem to be mounted. > > > >Looks good to me. > > > >smoergrd@sunw132 ~$ ping -s freefall.freebsd.org > >PING freefall.freebsd.org: 56 data bytes > >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=0. time=581. ms > >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=1. time=398. ms > >64 bytes from freefall.FreeBSD.ORG (204.216.27.21): icmp_seq=2. time=439. ms > >^C > >----freefall.freebsd.org PING Statistics---- > >3 packets transmitted, 3 packets received, 0% packet loss > >round-trip (ms) min/avg/max = 398/472/581 > > > >DES > >-- > >Dag-Erling Sm¯rgrav - smoergrd@oslo.geco-prakla.slb.com > > > It is not reachable from some points. > > Do a traceroute from your site Ulf. It stucks at a NAP point in NY or NJ. > > Santiago > > --------------------------------------------------------------------------- > Santiago Zapata Sauceda METCOM, S.A. de C.V. > szapata@creatos.com.mx Tetitla No 9, Col Toriello Guerra > 14050 Mexico, D.F. > > tel. 528 3113 > fax 606 7074 > > From the U.S. > phone 011 52 5 528 3113 > fax 011 52 5 606 7074 > --------------------------------------------------------------------------- > > > > 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 Fri Jul 10 19:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11023 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 19:19:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11016 for ; Fri, 10 Jul 1998 19:19:51 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt4-31.HiWAAY.net [208.166.127.31]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id VAA12214; Fri, 10 Jul 1998 21:19:48 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id VAA00332; Fri, 10 Jul 1998 21:12:05 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807110212.VAA00332@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Michael W. Smith" , freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: Too many files open? In-reply-to: Message from Dan Busarow of "Fri, 10 Jul 1998 15:48:16 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Jul 1998 21:12:05 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Busarow writes: > On Fri, 10 Jul 1998, Michael W. Smith wrote: > > I keep getting a too many files open error on the system and it's hosing > > it all to hell. A friend of mine who's more familiar with FreeBSD told me > > I need to rebuild the kernel but he wasn't sure which directive I need to > > change to fix it. I've got the Complete FreeBSD book, and know how to > > rebuild the kernel, but it's not entirely clear what I need to change to > > stop that error from happening. Any help would be greatly appreciated. > > Usually the easiest way to fix this is just to increase the value > of maxusers in your kernel config file. maxusers controls quite > a few system limits. You made need to do more, depending on what > this box is doing but this is a good start. What about the various limits in /etc/login.conf such as "openfiles". These may be kicking in before the kernel exhausts its resources. See limits(1) and login.conf(5) for more ideas. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 20:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18932 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 20:31:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ranma.nectar.com (nectar.communique.net [204.27.67.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18925 for ; Fri, 10 Jul 1998 20:31:28 -0700 (PDT) (envelope-from nectar@ranma.nectar.com) Received: from localhost (localhost [127.0.0.1]) by ranma.nectar.com (8.8.8/8.8.8) with ESMTP id WAA04308; Fri, 10 Jul 1998 22:18:51 -0500 (CDT) Message-Id: <199807110318.WAA04308@ranma.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199807102255.PAA08125@implode.root.com> References: <199807102255.PAA08125@implode.root.com> Subject: Re: freefall down ? To: dg@root.com cc: Santiago Zapata Sauceda , hackers@FreeBSD.ORG Date: Fri, 10 Jul 1998 22:18:50 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- There were some 700 DS3s gone between DC and Philadelphia. They were restored about 4:45pm central time. Jacques Vidrine On 10 July 1998 at 15:55, David Greenman wrote: > >It is not reachable from some points. > > > >Do a traceroute from your site Ulf. It stucks at a NAP point in NY or NJ. > > There were some network problems in Philadelphia that cause connectivity > problems with most east coast sites. This should be resolved now. There is > also a major fiber cut in Philadelphia that is causing other connectivity > problems, but these should be more isolated. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNabZmjeRhT8JRySpAQGbzAQAswXGXseahkcEb8Iy/F6xIuxGhUehV4Ch WXF7yZdfx3623V2Kwh9aCl0k9GNNuvRFuKhLyU8V48C33/zPKfNNooINNfMbtf7t T3Iy4cxC1qp9ZnWOuDmwJE3z2cYwyAtoDoZlaQgxh+OPddB+Rby1RebYGTW2VT+i MV8vqiW/Po0= =4jia -----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 Fri Jul 10 21:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24752 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 21:39:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24728; Fri, 10 Jul 1998 21:39:22 -0700 (PDT) (envelope-from dcarmich@Mars.mcs.net) Received: from Mars.mcs.net (dcarmich@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA19858; Fri, 10 Jul 1998 23:39:22 -0500 (CDT) Received: (from dcarmich@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA29567; Fri, 10 Jul 1998 23:39:21 -0500 (CDT) From: Douglas Carmichael Message-Id: <199807110439.XAA29567@Mars.mcs.net> Subject: Region of horizontal lines on right region of screen (duplib err -d uplication of leftr region) To: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Fri, 10 Jul 1998 23:39:21 -0500 (CDT) Action: urgent Reply-To: dcarmich@mcs.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the subject. My backspace seems to be messed up. I have a problem with XFree86 3.3.2 on a NEC Versa LX with an ATI 3D RAGE PRO LT video chip. (I'm using FreeBSD 2.2.6 with the pcvt console driver). When I start X with startx -- -bpp 32, X starts up fine and I can see the screen but on the right of the screen, there are horizontal lines going down to the bottom of the screen (not on the whole screen, but on about 1/4th of it) and anything dragged in that area cannot be seen. (Also, when I have my X cursor near that region, I see a mirror immage of it with a little white box before it in that region). Here's my XF86Config: # File generated by xf86config. # # Copyright (c) 1995 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # For OSs that support Dynamically loaded modules, ModulePath can be # used to set a search path for the modules. This is currently supported # for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown # here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Module section -- this is an optional section which is used to specify # which dynamically loadable modules to load. Dynamically loadable # modules are currently supported only for Linux ELF, FreeBSD 2.x # and NetBSD 1.x. Currently, dynamically loadable modules are used # only for some extended input (XInput) device drivers. # ********************************************************************** # # Section "Module" # # This loads the module for the Joystick driver # # Load "xf86Jstk.so" # # EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # DontZoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. # AllowNonLocalXvidtune # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # DisableModInDev # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # AllowNonLocalModInDev EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Keyboard section # ********************************************************************** Section "Keyboard" Protocol "Standard" # when using XQUEUE, comment out the above line, and uncomment the # following line # Protocol "Xqueue" AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be required # when using pre-R6 clients # ServerNumLock # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Xleds 1 2 3 # To set the LeftAlt to Meta, RightAlt key to ModeShift, # RightCtl key to Compose, and ScrollLock key to ModeLock: # LeftAlt Meta # RightAlt ModeShift # RightCtl Compose # ScrollLock ModeLock # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel "pc102" # If you have a US Microsoft Natural keyboard, you can use: # XkbModel "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout "de" # or: # XkbLayout "de" # XkbVariant "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions "ctrl:swapcaps" # These are the default XKB settings for XFree86 # XkbRules "xfree86" # XkbModel "pc101" # XkbLayout "us" # XkbVariant "" # XkbOptions "" XkbKeymap "xfree86(us)" EndSection # ********************************************************************** # Pointer section # ********************************************************************** Section "Pointer" Protocol "PS/2" Device "/dev/mouse" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Protocol "Xqueue" # Baudrate and SampleRate are only for some Logitech mice # BaudRate 9600 # SampleRate 150 # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Emulate3Buttons Emulate3Timeout 50 # ChordMiddle is an option for some 3-button Logitech mice # ChordMiddle EndSection # ********************************************************************** # Xinput section -- this is optional and is required only if you # are using extended input devices. This is for example only. Refer # to the XF86Config man page for a description of the options. # ********************************************************************** # # Section "Xinput" # SubSection "WacomStylus" # Port "/dev/ttyS1" # DeviceName "Wacom" # EndSubSection # SubSection "WacomCursor" # Port "/dev/ttyS1" # EndSubSection # SubSection "WacomEraser" # Port "/dev/ttyS1" # EndSubSection # # SubSection "Elographics" # Port "/dev/ttyS1" # DeviceName "Elo" # MinimumXPosition 300 # MaximumXPosition 3500 # MinimumYPosition 300 # MaximumYPosition 3500 # Screen 0 # UntouchDelay 10 # ReportDelay 10 # EndSubSection # # SubSection "Joystick" # Port "/dev/joy0" # DeviceName "Joystick" # TimeOut 10 # MinimumXPosition 100 # MaximumXPosition 1300 # MinimumYPosition 100 # MaximumYPosition 1100 # # CenterX 700 # # CenterY 600 # Delta 20 # EndSubSection # # The Mouse Subsection contains the same type of entries as the # standard Pointer Section (see above), with the addition of the # DeviceName entry. # # SubSection "Mouse" # Port "/dev/mouse2" # DeviceName "Second Mouse" # Protocol "Logitech" # EndSubSection # EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "NEC Internal LCD" VendorName "NEC" ModelName "NEC" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 24.18 - 56.48 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 30-120 # Modes can be specified in two formats. A compact one-line format, or # a multi-line format. # These two are equivalent # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace # Mode "1024x768i" # DotClock 45 # HTimings 1024 1048 1208 1264 # VTimings 768 776 784 817 # Flags "Interlace" # EndMode # This is a set of standard mode timings. Modes that are out of monitor spec # are automatically deleted by the server (provided the HorizSync and # VertRefresh lines are correct), so there's no immediate need to # delete mode timings (unless particular mode timings don't work on your # monitor). With these modes, the best standard mode that your monitor # and video card can support for a given resolution is automatically # used. # 640x480 @ 60 Hz, 31.5 kHz hsync Modeline "640x480" 24 640 664 760 800 480 491 493 525 # 800x600 @ 56 Hz, 35.15 kHz hsync ModeLine "800x600" 36 800 824 896 1024 600 601 603 625 #ModeLine "1024x768" 62 1024 1064 1240 1280 768 774 776 808 ModeLine "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Generic VGA" VendorName "Unknown" BoardName "Unknown" Chipset "generic" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Sample Device for accelerated server: # Section "Device" # Identifier "Actix GE32+ 2MB" # VendorName "Actix" # BoardName "GE32+" # Ramdac "ATT20C490" # Dacspeed 110 # Option "dac_8_bit" # Clocks 25.0 28.0 40.0 0.0 50.0 77.0 36.0 45.0 # Clocks 130.0 120.0 80.0 31.0 110.0 65.0 75.0 94.0 # EndSection # Sample Device for Hercules mono card: # Section "Device" # Identifier "Hercules mono" # EndSection # Device configured by xf86config: Section "Device" Identifier "NEC Internal" VendorName "NEC Internal" BoardName "NEC" #MemBase 0xfd000000 #IOBase 0xec00 #VideoRam 4096 #DacSpeed 135 ChipID 0x4754 ChipRev 0x7 EndSection # ********************************************************************** # Screen sections # ********************************************************************** # The Colour SVGA server Section "Screen" Driver "svga" Device "Generic VGA" #Device "NEC Internal" Monitor "NEC Internal LCD" Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection EndSection # The 16-color VGA server Section "Screen" Driver "vga16" Device "Generic VGA" Monitor "NEC Internal LCD" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The Mono server Section "Screen" Driver "vga2" Device "Generic VGA" Monitor "NEC Internal LCD" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64) Section "Screen" Driver "accel" Device "NEC Internal" Monitor "NEC Internal LCD" Subsection "Display" Depth 8 Modes "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection EndSection And the output from startx -- -bpp 32: XFree86 Version 3.3.2 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: February 28 1998 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 2.2.5-STABLE i386 Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) Using pcvt driver (version 3.20) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: "xfree86(us)" (overrides other XKB settings) (**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3 (**) Mouse: 3 button emulation (timeout: 50ms) (**) Mach64: Graphics device ID: "NEC Internal" (**) Mach64: Monitor ID: "NEC Internal LCD" (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fon ts/100dpi/" (--) Mach64: PCI: unknown ATI (0x4c50) rev 220, Aperture @ 0xfd000000, Block I/O @ 0xec00 (**) Mach64: Mach64 chipset override, using ChipID 0x4754 instead of 0x4c50 (**) Mach64: Mach64 chipset override, using ChipRev 0x07 instead of 0xdc (--) Mach64: Card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 170.000 MHz (**) Mach64: Mode "1024x768": mode clock = 75.000 (**) Mach64: Mode "800x600": mode clock = 36.000 (**) Mach64: Mode "640x480": mode clock = 24.000 (--) Mach64: Virtual resolution: 1024x768 (--) Mach64: Video RAM: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xfd000000 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 170 MHz (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots (--) Mach64: Font cache: 0 fonts System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m us -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" keymap/xfree86 /var/tmp/xfree86.xkm' waiting for X server to shut down X connection to :0.0 broken (explicit kill or server shutdown). xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" And the output from FreeBSD's dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-RELEASE #0: Sat Jul 11 02:00:02 CDT 1998 dcarmich@dcarmich.pr.mcs.net:/usr/src/sys/compile/VERSALX CPU: Pentium Pro (233.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff,,MMX,> real memory = 33554432 (32768K bytes) avail memory = 31055872 (30328K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 vga0 rev 220 int a irq 10 on pci0:2:0 chip1 rev 2 int a irq ?? on pci0:3:0 chip2 rev 2 int b irq ?? on pci0:3:1 pci0:4: vendor=0x125d, device=0x1978, class=multimedia (audio) int a irq 5 [no driver assigned] chip3 rev 2 on pci0:7:0 chip4 rev 1 on pci0:7:1 chip5 rev 1 int d irq ?? on pci0:7:2 chip6 rev 2 on pci0:7:3 Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 4134Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface What could be the problem? (I've tried fussing with xvidtune, but no change.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 22:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28528 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 22:35:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28523; Fri, 10 Jul 1998 22:35:43 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id PAA24585; Sat, 11 Jul 1998 15:05:11 +0930 (CST) Message-ID: <19980711150510.D23241@freebie.lemis.com> Date: Sat, 11 Jul 1998 15:05:10 +0930 From: Greg Lehey To: dcarmich@mcs.com Cc: FreeBSD Questions Subject: Re: Region of horizontal lines on right region of screen (duplib err -d uplication of leftr region) References: <199807110439.XAA29567@Mars.mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807110439.XAA29567@Mars.mcs.net>; from Douglas Carmichael on Fri, Jul 10, 1998 at 11:39:21PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 10 July 1998 at 23:39:21 -0500, Douglas Carmichael wrote (to -mobile and -hackers) This isn't a -hackers topic, and I suspect it's not really a -mobile topic either: it's a question, so I'm following up there. > Sorry for the subject. My backspace seems to be messed up. Try stty erase ^H > I have a problem with XFree86 3.3.2 on a NEC Versa LX with an ATI 3D RAGE > PRO LT video chip. (I'm using FreeBSD 2.2.6 with the pcvt console driver). > When I start X with startx -- -bpp 32, X starts up fine and I can see the > screen but on the right of the screen, there are horizontal lines going > down to the bottom of the screen (not on the whole screen, but on about > 1/4th of it) and anything dragged in that area cannot be seen. > (Also, when I have my X cursor near that region, I see a mirror immage of > it with a little white box before it in that region). This looks like a disagreement between the display and your XF86config as to the correct scan timing. There are a number of things you can do: 1. Check whether it happens in other resolutions. You don't say, but I suppose you were doing this at 1024x768. Does it still happen at 800x600 and 640x480? 2. Check whether it happens in other colour depths. If it doesn't, check the dot clocks. Your current ones are: > (**) Mach64: Mode "1024x768": mode clock = 75.000 > (**) Mach64: Mode "800x600": mode clock = 36.000 > (**) Mach64: Mode "640x480": mode clock = 24.000 3. I note that for 1024x768 you have the following mode line: ModeLine "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync I don't know if this is some decision by xf86setup that you need negative sync just for this speed, but I suspect it's bogus. You could try removing the -hsync -vsync and see if that improves things, though at the moment I can't see how. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 22:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29657 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 22:49:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ymris.ddm.on.ca (p.neon.sentex.ca [207.245.212.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29646 for ; Fri, 10 Jul 1998 22:49:09 -0700 (PDT) (envelope-from dchapes@ddm.on.ca) Received: from squigy.ddm.on.ca (squigy.ddm.on.ca [209.47.139.138]) by ymris.ddm.on.ca (8.8.8/8.8.8) with ESMTP id BAA21927; Sat, 11 Jul 1998 01:48:53 -0400 (EDT) (envelope-from dchapes@ymris.ddm.on.ca) From: Dave Chapeskie Received: (from dchapes@localhost) by squigy.ddm.on.ca (8.8.8/8.8.7) id BAA04648; Sat, 11 Jul 1998 01:48:52 -0400 (EDT) Message-ID: <19980711014852.14739@ddm.on.ca> Date: Sat, 11 Jul 1998 01:48:52 -0400 To: "Ron G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). Mail-Followup-To: "Ron G. Minnich" , hackers@FreeBSD.ORG References: <199807101738.KAA12014@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Ron G. Minnich on Fri, Jul 10, 1998 at 04:24:52PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 04:24:52PM -0400, Ron G. Minnich wrote: > Actually, why not just have ln warn of questionable links in any case. Please NO! I like that most standard unix commands do what I tell them even if I tell them the wrong thing. It puts the onus on me to think about the commands I give. (Unlike in m$. How many people do you know that habitually close editor windows before saving expecting the system to notice and remind them to first save the file? I know quite a few). I've many times used ln(1) to create what you call 'questionable links' on purpose and I'd _hate_ warnings. If someone insists on adding such warnings then do it like mv(1) and cp(1) by adding an option to ln(1) turn it on. -- Dave Chapeskie , DDM Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 10 23:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01884 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 23:17:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pacfc.fleet.navy.mil (pacfc.fleet.navy.mil [205.56.145.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01879 for ; Fri, 10 Jul 1998 23:17:58 -0700 (PDT) (envelope-from circuit@vinson.navy.mil) Received: by pacfc.fleet.navy.mil; id GAA20656; Sat, 11 Jul 1998 06:13:58 GMT Received: from unknown(205.58.1.31) by pacfc.fleet.navy.mil via smop (4.1) id xma020636; Sat, 11 Jul 98 06:13:21 GMT Received: by intruder.vinson.navy.mil with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BDAC3F.442D0480@intruder.vinson.navy.mil>; Fri, 10 Jul 1998 20:13:56 -1000 Message-ID: From: "CA01 Jewell Christopher G. RM3" To: "'Dave Chapeskie'" , "'Ron G. Minnich'" Cc: "'hackers@FreeBSD.ORG'" Subject: makeinf an executable command in Unix Date: Fri, 10 Jul 1998 20:13:54 -1000 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to make a cleanup routine for my hp-ux system. I made a file with the simple command find / -name core -print I saved it as .cleanup everytime i execut it with . .cleanup command it gives me Permission denied on several directories. Can anyon ehelp me out here? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 00:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06562 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 00:15:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from merlin.camalott.com (root@merlin.camalott.com [208.229.74.19] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06554 for ; Sat, 11 Jul 1998 00:15:32 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-94.camalott.com [208.229.74.94]) by merlin.camalott.com (8.8.7/8.8.7) with ESMTP id CAA10001; Sat, 11 Jul 1998 02:10:24 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id CAA10210; Sat, 11 Jul 1998 02:08:46 -0500 (CDT) (envelope-from joelh) Date: Sat, 11 Jul 1998 02:08:46 -0500 (CDT) Message-Id: <199807110708.CAA10210@detlev.UUCP> To: dchapes@ddm.on.ca CC: rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <19980711014852.14739@ddm.on.ca> (message from Dave Chapeskie on Sat, 11 Jul 1998 01:48:52 -0400) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807101738.KAA12014@hub.freebsd.org> <19980711014852.14739@ddm.on.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Actually, why not just have ln warn of questionable links in any case. > Please NO! I like that most standard unix commands do what I tell them > even if I tell them the wrong thing. It puts the onus on me to think > about the commands I give. Nobody's talking about making Unix not letting you do either stupid or clever things anymore. We're not even talking about making it harder. See below. > (Unlike in m$. How many people do you know that habitually close > editor windows before saving expecting the system to notice and > remind them to first save the file? I know quite a few). Unlike Unix, where we have thrived for years on ex, everybody's favorite text editor: if (F_ISSET(ep, F_MODIFIED) && ep->refcnt <= 1 && !force) { msgq(sp, M_ERR, "264|File modified since last complete write; write or use ! to override"); return (1); } Although in these enlightened days, we use the more refined and sophisticated vi: /* Call the ex parser. */ (void)ex_cmd(sp); Or, maybe you prefer Emacs: (save-some-buffers arg t) (and (or (not (memq t (mapcar (function (lambda (buf) (and (buffer-file-name buf) (buffer-modified-p buf)))) (buffer-list)))) (yes-or-no-p "Modified buffers exist; exit anyway? ")) But naturally, we Real Unix Hackers don't use these utilities. Real Unix Hackers use cat for all our manual file creation needs... or would you consider the difference between SIGINT (^C) and EOF (^D) to be a type of confirmation? How about file modification? We'll use ed, the standard text editor. But wait... what's this bit of ed code? gflag = (modified && !scripted && c == 'q') ? EMOD : EOF; Interactive user interfaces for interactive programs are a Good Thing. I for one would rather let my computer remember whether or not I've saved all my buffers than me have to. Humans are fallible, and at 4:00 AM after a long night of hacking, I'm bound to forget to save something. And we all know whether it will be the buffer with 2 changes, 5 changes, or 328 scattered three-character painfully researched and discovered changes. (A related side note: Emacs users who jot useful notes in *scratch* may want to investigate the emacs-lock package in Emacs 20.) But, putting sarcasm aside for a moment (yes, I can if I try), this isn't relevant to our present case. We're not talking about a prompt in an interactive program. If I read our discussion right, we're talking about adding a warning. # cd /usr # ln -s src/sys /sys ln: warning: src/sys does not exist relative to /. # rm /sys # ln -s usr/src/sys /sys # ^D, with the satisfaction that you have averted another needless help desk call. Unix will still let you shoot yourself in the foot if you want to, and quite gladly let you script the shooting. What we're proposing is a mechanism by which you'll know that you did so immediately instead of first feeling a strange pain in your foot a week later, at the same time as you wonder where your kernel source went. > I've many times used ln(1) to create what you call 'questionable links' > on purpose and I'd _hate_ warnings. You frequently link to files that don't exist? I generally consider that to be putting the cart before the cat(1), er, horse. But it's your system. > If someone insists on adding such warnings then do it like mv(1) and > cp(1) by adding an option to ln(1) turn it on. You mean, in the style of the cp and mv which both sport -f, and one of which features the -R flag? Bottom line: Warnings are good program design. Requiring extra work to issue them-- particularly when they're most frequently required in interactive use-- is not. One of my very favorite badges says, "Unix doesn't keep you from doing stupid things because that would keep you from doing clever things." That's still true. But I still like to know that I'm doing something stupid, just in case I'm not particularly clever at the moment. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 00:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06843 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 00:18:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06838 for ; Sat, 11 Jul 1998 00:18:22 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-94.camalott.com [208.229.74.94]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id CAA11682; Sat, 11 Jul 1998 02:18:19 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id CAA10297; Sat, 11 Jul 1998 02:17:33 -0500 (CDT) (envelope-from joelh) Date: Sat, 11 Jul 1998 02:17:33 -0500 (CDT) Message-Id: <199807110717.CAA10297@detlev.UUCP> To: circuit@vinson.navy.mil CC: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: (circuit@vinson.navy.mil) Subject: Re: makeinf an executable command in Unix From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am trying to make a cleanup routine for my hp-ux system. I made a file > with the simple command > find / -name core -print > I saved it as .cleanup > everytime i execut it with > . .cleanup > command it gives me Permission denied on several directories. Can anyon > ehelp me out here? This belongs in -questions, not in -hackers. Execute it as root if you want it to be able to search every directory. Execute it as a mortal if you only want it to be able to search directories only mortals can read. (The main difference is directories that may have sensitive information, like /var/crash.) Better yet, add it to /etc/daily.local and let it run automatically and mail root the results. (root generally should be forwarded to the sysadmin in /etc/aliases anyway; don't forget to run newaliases!) Don't use find ... -exec rm -f {} ; as this is a security hole. The command may need to be find / -name "*.core" -print instead, since FreeBSD currently stores corefiles under progname.core rather than just core. (I don't know what all versions this applies to.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 01:14:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10328 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 01:14:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10321 for ; Sat, 11 Jul 1998 01:14:11 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id RAA27850; Sat, 11 Jul 1998 17:44:07 +0930 (CST) Message-ID: <19980711174401.F23241@freebie.lemis.com> Date: Sat, 11 Jul 1998 17:44:01 +0930 From: Greg Lehey To: FreeBSD Hackers Subject: New Vinum alpha release available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fourth alpha version of vinum is now available for download at ftp://ftp.lemis.com/pub/vinum/vinumdist-11Jul.tar.gz ABOUT VINUM =========== Vinum is a logical volume manager modeled after the Veritas(R) volume manager. It is not a clone of Veritas, however, and attempts to solve a number of problems more elegantly than Veritas. It also offers features that Veritas does not have. See http://www.lemis.com/vinum.html for more details. Concepts ________ As used in this document, a volume manager is a software component which isolates file systems from the underlying disk hardware. Instead of building file systems on disk partitions, they are built on volumes. This has a number of advantages: o Volumes may span disk drives. o Volumes may be larger than any drive. o By spreading the disk load over multiple volumes, it is possible to improve performance. o By dynamically increasing the size of a volume, it is possible to solve space problems without repartitioning. o By replicating data within the volume, it is possible to improve availability. o By changing the volume configuration on-line, it is possible to reorganize disk storage on-line. WHAT YOU CAN DO =============== The purpose of this release is to ensure that bugs and misfeatures in the product are found and rectified as quickly as possible. If you download this software, please use it and inform me of any problems you have. It will help to have a kernel debugger and a debug kernel installed so that I can pinpoint problems more easily. If the system panics, please keep the dump. If at all possible, I would prefer to examine it on your machine. FIXES IN THE 11 JULY VERSION ============================ - Numerous panics and hangs fixed. - Rewrote configuration. - Implement the 'rm' and 'read' commands. Vinum now saves its configuration on disk. The 'read' command will read in the configuration as it was when the system shut down. CAVEATS IN THE CURRENT VERSION ============================== A couple of things to observe: - The configuration now much better, but it hasn't been thoroughly tested, and it's possible to shoot yourself in the foot with it. If this happens to you, please let me know: it's one of the few ways I have to ensure that holes are patched. - The partitions used for vinum *must* be of type "unused". This helps avoid shooting yourself in the foot by building a vinum on top of a file system partition. If you try, you will get the message "Drive has invalid partition type". Release versions of vinum will use their own special partition type. - Volume recovery is still not complete, though enough code is present to give you the opportunity for a variety of panics. - The code contains a lot of debug aids, and it's compiled without optimization in order to make debugging easier. Don't worry about the size *too* much: it'll shrink by approximately 30% when it's compiled with optimization. The performance will also improve. - This version of vinum is a stripped-down version without RAID-5 code, and I haven't tested it in this form beyond confirming that it will compile. PREVIOUS ANNOUNCEMENTS ====================== Vinum is available under a Berkeley-style copyright. It is implemented as a loadable kernel module (LKM). This version of vinum contains a subset of the final functionality, roughly equivalent to the ccd driver. In particular, the following restrictions apply: Automatic startup is not yet complete. It is currently necessary to re-configure the volumes every time the subsystem is started. This operation does not change the data on the disks. Detection of differences between the version of the kernel and the LKM is not yet implemented. Detaching plexes and subdisks has not yet been implemented. Reintegration of failed disks has not yet been implemented. vinum requires a special version of newfs, which has not yet been committed. The current version places some restrictions on volume names. See the documentation for further information. This version of vinum will run (hopefully) on FreeBSD 2.2.6 and recent versions of 3.0-CURRENT. It may also run on 2.2.5, but I haven't tested it. Due to changes in -CURRENT, it will not compile on versions older than about mid-March 1998. Due to licensing restrictions, this version does not contain the RAID5 functionality. If you are interested in testing this, please contact me privately. Don't use this version for performance testing. I have a lot of debug code in there, some of which is quite slow. At the moment, my main concern is stability. Documentation for this version includes man pages (vinum(4) and vinum(8)) and a user's guide, currently (for my convenience) in /usr/src/sbin/vinum/doc. You can build PostScript versions of any of these by building the appropriate file (vinum4.ps, vinum8.ps or userguide.ps) in this directory. For convenience' sake, the distribution includes the PostScript file /usr/src/sbin/vinum/doc/userguide.ps. This document is intended to be formatted with troff; you can format it with nroff, but it will look funny. I don't intend to fix this. The documentations Makefile also refers to a file notes.*, which will contain technical notes when it is finished. All documents refer to the RAID5 functionality. Please ignore them for the time being. If you use this version, *PLEASE* give me some feedback, even if things work fine. In particular, of course, I'd like to hear of any problems you have either with the software or the documentation. I'll also accept requests for enhancement, but don't expect to see them in the near future: there's still a lot of code to be written. Greg Lehey -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 01:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12955 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 01:48:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12949 for ; Sat, 11 Jul 1998 01:48:37 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA19821; Sat, 11 Jul 1998 01:48:34 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd019801; Sat Jul 11 01:48:24 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA16020; Sat, 11 Jul 1998 01:48:16 -0700 (MST) From: Terry Lambert Message-Id: <199807110848.BAA16020@usr08.primenet.com> Subject: Re: Improvemnet of ln(1). To: joelh@gnu.org Date: Sat, 11 Jul 1998 08:48:16 +0000 (GMT) Cc: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-Reply-To: <199807110708.CAA10210@detlev.UUCP> from "Joel Ray Holveck" at Jul 11, 98 02:08:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've many times used ln(1) to create what you call 'questionable links' > > on purpose and I'd _hate_ warnings. > > You frequently link to files that don't exist? I generally consider > that to be putting the cart before the cat(1), er, horse. But it's > your system. I don't do it frequently, but yes, I do this occasionally. In a number of cases, I do this in makefiles, and I do this to create links into a non-existant object tree. > > If someone insists on adding such warnings then do it like mv(1) and > > cp(1) by adding an option to ln(1) turn it on. > > You mean, in the style of the cp and mv which both sport -f, and one > of which features the -R flag? The "-f" flag to "ln" unlinks an existing file of the link name; in other words, it's already taken as "force". It would be a mistake to issue a warning without some way to disable it, akain to the "rm -f" behaviour of "-f". One problem here is that it is likely that you waould want to *not* get the "ln -f" behaviour, yet you would want to suppress warnings. > Bottom line: Warnings are good program design. Requiring extra work > to issue them-- particularly when they're most frequently required in > interactive use-- is not. Clearly, you could wrap this with a script that uses test(1) to ensure the link target exists, and put your script in your path ahead of the ln command. Whereas in order to get the existing non-"-f" behaviour, I'd have to modify existing code. Note that "-f" is already taken on "ln", according to POSIX semantics, so it's not like you could overload it reasonably. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 02:02:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14068 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 02:02:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14063 for ; Sat, 11 Jul 1998 02:02:34 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id KAA28118; Sat, 11 Jul 1998 10:59:07 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id KAA01112; Sat, 11 Jul 1998 10:46:49 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807110846.KAA01112@semyam.dinoco.de> Cc: Greg Lehey , seggers@semyam.dinoco.de To: freebsd-hackers@FreeBSD.ORG Subject: Re: odd problems with AMD K6 In-reply-to: Your message of "Sat, 27 Jun 1998 11:54:50 +0930." <19980627115450.O16259@freebie.lemis.com> Date: Sat, 11 Jul 1998 10:46:49 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Old but still unanswered as far as I saw.] > > graphics that just came in. The system froze, and rebooted. The system > > did dump core, however, and this is the result (using kgdb): > > > > IdlePTD 279000 > > current pcb at 25325c > > panic: vref used where vget required > > #0 0xf0116c5e in boot () > > (kgdb) bt > > #0 0xf0116c5e in boot () > > #1 0xf0116f4a in panic () > > #2 0xf013cc07 in vref () > > #3 0xf01043d0 in iso_iget () > > #4 0xf010686a in cd9660_root () [...] > > Again, I have not been able to reproduce this. I've run the system > > ragged since then, and it hasn't crashed a single time. > > Doesn't look like hardware. There have been some software problems in > this area. Do you still have the dump? It is software. See my PR kern/6981 on how to reproduce this with a certain operations at the CD drive. I got it all the time I did what I describe there. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 04:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26483 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 04:27:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA26475 for ; Sat, 11 Jul 1998 04:27:04 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from (ragnet.demon.co.uk) [158.152.46.40] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0yuxny-000014-00; Sat, 11 Jul 1998 11:27:02 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0yuwOo-0005QQ-00; Sat, 11 Jul 1998 10:56:58 +0100 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199807110052.KAA07523@gsms01.alcatel.com.au> Date: Sat, 11 Jul 1998 10:56:58 +0100 (BST) From: Duncan Barclay To: Peter Jeremy Subject: RE: PPS device Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jul-98 Peter Jeremy wrote: > Is anyone using a PPS device with FreeBSD? I notice that -current > includes support for a PPS source attached via a parallel port. > [snip] > BTW: Anyone looking for a good stand-alone reference might like to look > at the master reference oscillators in digital cellular base stations - > the GSM standard (which also covers DCS-1800 and DCS-1900) requires > a 0.05ppm or better reference in the base station. I suspect DAMPS and > CMDA also have similarly tight tolerances. Whilst these references are > expensive new, if you know someone in the industry, you might be able > to acquire one from a junked board. That's a neat idea! If you can cope with a slightly relaxed tolerance of 1ppm get a 13MHz TVCXO (temperate/voltage controlled crystal oscillator) for handset use. These will be cheap, a couple of dollars I guesss (I only ever know prices by the millions:-)). There're probably smaller than the base station version too. The handset TCXOs have a voltage control function too, so if you got clever you could do a hardware trim of them too. Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 06:39:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03106 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 06:39:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.nternet.net (ns.nternet.net [206.154.20.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03101 for ; Sat, 11 Jul 1998 06:39:25 -0700 (PDT) (envelope-from jvz@ns.nternet.net) Received: from localhost (jvz@localhost) by ns.nternet.net (8.8.8/8.8.7) with SMTP id JAA04575 for ; Sat, 11 Jul 1998 09:48:09 -0400 (EDT) Date: Sat, 11 Jul 1998 09:48:09 -0400 (EDT) From: Jonny To: hackers@FreeBSD.ORG Subject: Assembly.. 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, im having a bit of a problem understanding the way freebsd does its syscalls in asm.. ive searched, and read the as info pages numerous times, and looked over kernel src, along with compiling simple C code with -S -o blah.s i was told fbsd uses 'call gates' so that where linux would do movl $1,%eax // exit() syscall in linux movl $0,%ebx // exit code int $0x80 // do the syscall i was told fbsd is similar only where linux does the interrupt it would do a call ie; call 0x7,0x0 which gives me errors from as (no known i386 instructions) i understand i could do the 'call syscallName' but i want a thorough understanding on how these ' call gates' work.. if someone could explain a bit how they work and are called.. and provide me a sample standalone asm code .. heck 'hello world' for that matter.. i would greatly appreciate it. thanx in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 06:48:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03462 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 06:48:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bsdsrvr.viasoft.com (bsdsrvr.viasoft.com [208.192.53.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03455 for ; Sat, 11 Jul 1998 06:48:23 -0700 (PDT) (envelope-from dlr@davids.org) Received: from bsdsrvr.viasoft.com (root@localhost) by bsdsrvr.viasoft.com with ESMTP id GAA01646 for ; Sat, 11 Jul 1998 06:57:50 -0700 (MST) Received: from ntwork ([10.10.20.245]) by bsdsrvr.viasoft.com with SMTP id GAA01642 for ; Sat, 11 Jul 1998 06:57:44 -0700 (MST) Message-Id: <3.0.5.32.19980711065416.009108d0@www.davids.org> X-Sender: dlr@www.davids.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 11 Jul 1998 06:54:16 To: FreeBSD-hackers@FreeBSD.ORG From: David Richardson Subject: Q: RAID Controllers In-Reply-To: <199807110535.WAA28570@hub.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 All, I have been trying to determine which, or if any RAID controllers are supported. Or if there is any way to setup RAID-1 through FreeBSD. I did see a new boot disk for the DPT RAID controller 2.2.6 CD-ROM. Is this the only RAID controller that is supported? Thanks, Dave dlr@davids.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 07:42:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07132 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 07:42:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07127 for ; Sat, 11 Jul 1998 07:42:05 -0700 (PDT) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id KAA19245; Sat, 11 Jul 1998 10:42:04 -0400 (EDT) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id KAA19474; Sat, 11 Jul 1998 10:42:04 -0400 (EDT) Message-Id: <199807111442.KAA19474@chai.torrentnet.com> To: joelh@gnu.org Cc: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Your message of "Sat, 11 Jul 1998 02:08:46 CDT." <199807110708.CAA10210@detlev.UUCP> Date: Sat, 11 Jul 1998 10:42:03 -0400 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bottom line: Warnings are good program design. Requiring extra work > to issue them-- particularly when they're most frequently required in > interactive use-- is not. For interactive use, alias ln to `ln -w' to warn you. If you change the default behavior of ln, you *will* break scripts. Unlike editors, ln is more likely to be used in scripts than interactively (well, it is so for most people). Bottom line: backward compatibility is a good program design. > One of my very favorite badges says, "Unix doesn't keep you from doing > stupid things because that would keep you from doing clever things." > That's still true. But I still like to know that I'm doing something > stupid, just in case I'm not particularly clever at the moment. Adding such band-aids and making them the default *does* make it harder to do clever things (such as write scripts). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 07:48:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07605 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 07:48:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA07600 for ; Sat, 11 Jul 1998 07:48:26 -0700 (PDT) (envelope-from shigio@wafu.netgate.net) Message-Id: <199807111448.HAA07600@hub.freebsd.org> Received: (qmail 10585 invoked from network); 11 Jul 1998 06:48:15 -0000 Received: from ins19.tama-ap3.dti.ne.jp (HELO choota.signet.or.jp) (203.181.67.19) by wafu.netgate.net with SMTP; 11 Jul 1998 06:48:15 -0000 Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.7/) with ESMTP id XAA00557; Sat, 11 Jul 1998 23:49:22 +0900 (JST) To: sbabkin@dcn.att.com cc: shigio@wafu.netgate.net, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Message from sbabkin@dcn.att.com of "Fri, 10 Jul 1998 16:18:26 -0400." Date: Sat, 11 Jul 1998 23:49:22 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > [Problem] > > > > Ln(1) with -s option makes illegal symbolic link in some case. > > For example, > > > > (Both '/usr/src/sys' and '/tmp' are real directories.) > > > > % cd /usr > > % ln -s src/sys /tmp > > % ls -l /tmp/sys > > lrwxrwxrwx 1 shigio wheel 7 Jul 11 02:03 /tmp/sys -> src/sys > > % cd /tmp/sys > > /tmp/sys: No such file or directory. > > > > Symbolic link '/tmp/sys' has illegal value, so we cannot move there. > > Above behavior is not desireble in almost case, I think. > > > > [Solution] > > > ln -s `pwd`/src/sys /tmp > > Isn't it simpler ? But it forces user to use absolute symbolic link. There are two important issue, I think. o Is it right symbolic link? o Can we make a choice whether absolute or relative symbolic link? -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10052 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:23:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparky8 (sparky8.cc.binghamton.edu [128.226.4.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA10047 for ; Sat, 11 Jul 1998 08:23:13 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by sparky8 (SMI-8.6/8.6.9) with SMTP id LAA00770 for ; Sat, 11 Jul 1998 11:23:07 -0400 Date: Sat, 11 Jul 1998 11:23:06 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@sparky8 To: hackers Subject: Question about shadow object collapse 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 According to the Mach paper "Machine-Independent Virtual Memory Management for Paged Uniprocessor and Multiprocessor Architectures", a shadow object still relies on the original object (i.e., backing object) that it shadows for all unmodified data. If this is true in FreeBSD, can anyone explain the following comments found in the routine vm_object_collapse() (see source file vm/vm_object.c): (1) Pages that have been paged out will be overwirteen by any of the parent's pages that shadow them. (why so and how to know if a page has been paged out?) (2) If the page falls outside the parent, dispose of it. (why so?) Any help is appreciated. ------------------------------------------------- Zhihui Zhang Department of Computer Science State University of New York at Binghamton Web Site: http://cs.binghamton.edu/~zzhang ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10506 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:26:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10500 for ; Sat, 11 Jul 1998 08:26:05 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-33.camalott.com [208.229.74.33]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id KAA23588; Sat, 11 Jul 1998 10:26:18 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id KAA13574; Sat, 11 Jul 1998 10:25:34 -0500 (CDT) (envelope-from joelh) Date: Sat, 11 Jul 1998 10:25:34 -0500 (CDT) Message-Id: <199807111525.KAA13574@detlev.UUCP> To: tlambert@primenet.com CC: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <199807110848.BAA16020@usr08.primenet.com> (message from Terry Lambert on Sat, 11 Jul 1998 08:48:16 +0000 (GMT)) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807110848.BAA16020@usr08.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I've many times used ln(1) to create what you call 'questionable links' >>> on purpose and I'd _hate_ warnings. >> You frequently link to files that don't exist? I generally consider >> that to be putting the cart before the cat(1), er, horse. But it's >> your system. > I don't do it frequently, but yes, I do this occasionally. Then occasionally getting a warning wouldn't be a bad thing. >>> If someone insists on adding such warnings then do it like mv(1) and >>> cp(1) by adding an option to ln(1) turn it on. >> You mean, in the style of the cp and mv which both sport -f, and one >> of which features the -R flag? > The "-f" flag to "ln" unlinks an existing file of the link name; > in other words, it's already taken as "force". > It would be a mistake to issue a warning without some way to disable > it, akain to the "rm -f" behaviour of "-f". > One problem here is that it is likely that you waould want to *not* > get the "ln -f" behaviour, yet you would want to suppress warnings. I agree. So choose a different flag than -f. >> Bottom line: Warnings are good program design. Requiring extra work >> to issue them-- particularly when they're most frequently required in >> interactive use-- is not. > Clearly, you could wrap this with a script that uses test(1) to ensure > the link target exists, and put your script in your path ahead of the > ln command. Yes, you could. I do that quite frequently. (You can imagine my ~/hp9000-hpux/bin directory, full of compatibility scripts.) But is this a problem that only exists for a few users and would annoy many (which would mean that we few should use the scripts), or does it exist for many and would annoy few (which would mean we should modify ln)? > Whereas in order to get the existing non-"-f" behaviour, I'd have to > modify existing code. A warning message wouldn't break your existing code. Again, we're not proposing a prompt here, just a diagnostic that you can ignore if you're intentionally linking to a non-existant file. > Note that "-f" is already taken on "ln", according to POSIX semantics, > so it's not like you could overload it reasonably. Okay, let's choose a different flag. How about '-q' (quiet)? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:37:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11560 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:37:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11555 for ; Sat, 11 Jul 1998 08:37:37 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id KAA05739; Sat, 11 Jul 1998 10:37:37 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id KAA06114; Sat, 11 Jul 1998 10:37:36 -0500 (CDT) Message-ID: <19980711103736.15200@mcs.net> Date: Sat, 11 Jul 1998 10:37:36 -0500 From: Karl Denninger To: David Richardson Cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: Q: RAID Controllers References: <199807110535.WAA28570@hub.freebsd.org> <3.0.5.32.19980711065416.009108d0@www.davids.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <3.0.5.32.19980711065416.009108d0@www.davids.org>; from David Richardson on Sat, Jul 11, 1998 at 01:58:29PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 11, 1998 at 01:58:29PM +0000, David Richardson wrote: > All, > > I have been trying to determine which, or if any RAID controllers are > supported. Or if there is any way to setup RAID-1 through FreeBSD. I did > see a new boot disk for the DPT RAID controller 2.2.6 CD-ROM. Is this the > only RAID controller that is supported? > > Thanks, Dave > dlr@davids.org I like the external, SCSI-connected CMD controllers. They work great with FreeBSD. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11681 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:38:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparky8 (sparky8.cc.binghamton.edu [128.226.4.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11674 for ; Sat, 11 Jul 1998 08:38:20 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by sparky8 (SMI-8.6/8.6.9) with SMTP id LAA00784; Sat, 11 Jul 1998 11:38:16 -0400 Date: Sat, 11 Jul 1998 11:38:12 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@sparky8 To: Jonny cc: hackers@FreeBSD.ORG Subject: Re: Assembly.. 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 myself do not fully understand the details of the system call mechanism. But I think the following two sources might be of help: (1) Dr. Dobb's Journal March 1998 - Benchmarking and Software Testing, Tracing BSD System Calls, by Sean Eric Fagan (2) http://www.x86.org/intel.doc/P2Manuals.html, Intel Architecture Software Developer's Manual, Volume 3: System Programming Guide -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- On Sat, 11 Jul 1998, Jonny wrote: > > Hi, im having a bit of a problem understanding the way > freebsd does its syscalls in asm.. ive searched, and > read the as info pages numerous times, and looked over > kernel src, along with compiling simple C code with -S -o blah.s > i was told fbsd uses 'call gates' so that where linux would do > > movl $1,%eax // exit() syscall in linux > movl $0,%ebx // exit code > int $0x80 // do the syscall > > i was told fbsd is similar > only where linux does the interrupt it would do a call ie; > > call 0x7,0x0 > > which gives me errors from as (no known i386 instructions) > > i understand i could do the 'call syscallName' but i want > a thorough understanding on how these ' call gates' work.. > if someone could explain a bit how they work and are called.. > and provide me a sample standalone asm code .. heck 'hello world' > for that matter.. i would greatly appreciate it. > > thanx in advance. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:39:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11910 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:39:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11894 for ; Sat, 11 Jul 1998 08:39:38 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id LAA07461; Sat, 11 Jul 1998 11:46:54 -0400 (EDT) Date: Sat, 11 Jul 1998 11:46:54 -0400 (EDT) From: Charles Youse To: Bakul Shah cc: joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807111442.KAA19474@chai.torrentnet.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, 11 Jul 1998, Bakul Shah wrote: > For interactive use, alias ln to `ln -w' to warn you. If you > change the default behavior of ln, you *will* break scripts. > Unlike editors, ln is more likely to be used in scripts than > interactively (well, it is so for most people). I fail to see how. An extra line output to stderr is going to break scripts? Can you provide an example? > Bottom line: backward compatibility is a good program design. Well, not always. Compare Windows/DOS. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 08:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12494 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 08:45:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12489 for ; Sat, 11 Jul 1998 08:45:42 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-33.camalott.com [208.229.74.33]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id KAA24308; Sat, 11 Jul 1998 10:46:14 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id KAA13645; Sat, 11 Jul 1998 10:45:31 -0500 (CDT) (envelope-from joelh) Date: Sat, 11 Jul 1998 10:45:31 -0500 (CDT) Message-Id: <199807111545.KAA13645@detlev.UUCP> To: bakul@torrentnet.com CC: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <199807111442.KAA19474@chai.torrentnet.com> (message from Bakul Shah on Sat, 11 Jul 1998 10:42:03 -0400) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807111442.KAA19474@chai.torrentnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Bottom line: Warnings are good program design. Requiring extra work >> to issue them-- particularly when they're most frequently required in >> interactive use-- is not. > For interactive use, alias ln to `ln -w' to warn you. If you > change the default behavior of ln, you *will* break scripts. > Unlike editors, ln is more likely to be used in scripts than > interactively (well, it is so for most people). > Bottom line: backward compatibility is a good program design. How on earth will issuing a diagnostic break scripts? >> One of my very favorite badges says, "Unix doesn't keep you from doing >> stupid things because that would keep you from doing clever things." >> That's still true. But I still like to know that I'm doing something >> stupid, just in case I'm not particularly clever at the moment. > Adding such band-aids and making them the default *does* make > it harder to do clever things (such as write scripts). How on earth will issuing a diagnostic make it harder to write scripts? I have no descire whatsoever to break existing scripts, and I especially have no desire to break scripts written to go between several Unixes. But I don't see how adding a diagnostic will break anything. There seems to be a perception that I am proposing (actually, I believe rminnich proposed; I'm just arguing for) changing the practical behavior of ln. That would be a considerable lose. The only behavior I am proposing changing is what is output to stderr. I'm *not* talking about a prompt a la cp -i. I'm *not* talking about a failure a la trying to symlink over an existing file. I'm talking about a diagnostic. >From my first post: > # cd /usr > # ln -s src/sys /sys > ln: warning: src/sys does not exist relative to /. > # rm /sys > # ln -s usr/src/sys /sys Note that ln made the symlink anyway, without asking for confirmation. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 09:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18564 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 09:57:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18471; Sat, 11 Jul 1998 09:57:18 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sat, 11 Jul 1998 12:56:44 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA13121; Sat, 11 Jul 98 12:56:41 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id MAA14446; Sat, 11 Jul 1998 12:56:03 -0400 Message-Id: <19980711125602.A14345@ct.picker.com> Date: Sat, 11 Jul 1998 12:56:02 -0400 From: Randall Hopper To: Roger Hardiman , Mark Handley , Mark Tinguely , Amancio Hasty , Greg Lehey , "Jonathan M. Bresler" , Sue Blake , Eivind Eklund Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: list closed to non subscribers Mail-Followup-To: Roger Hardiman , Mark Handley , Mark Tinguely , Amancio Hasty , Greg Lehey , "Jonathan M. Bresler" , Sue Blake , Eivind Eklund , multimedia@freebsd.org, hackers@freebsd.org References: <199807011757.MAA19802@plains.NoDak.edu> <4458.899321082@north.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <4458.899321082@north.lcs.mit.edu>; from Mark Handley on Wed, Jul 01, 1998 at 03:24:42PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The "consensus building" messages: Mark Handley: |The technological solution to this problem would be to only allow |postings from members of the list. Amancio Hasty: |I like that idea a lot . Amancio Hasty: |I see however what we are asking to have the multimedia mailing list |accept mail *only* from members. Can you do that? Amancio Hasty: |The list is now closed and it is time to go back to our multimedia |related topics. Roger Hardiman: |Is -muiltimedia still closed so you need to subscribe before you |can post? | |I'd like it open again, as it used to be. I agree (for your reasons, and a few others which I posted 7/2). At the very least, I'd expect opinions/votes to be solicited and discussion to be held on this topic by list members (and FreeBSD folks in general) before we decide on a policy for all of us based on the expressed desires of only one person. I'd come to expect more from the FreeBSD community. I didn't think this is how we did things here (sounds like Li*ux). |I'd like the group back open again. Seconded. And if some still want it closed, we should "discuss" this and solicit positions/votes first. |Perhaps those that reply with abusive comments about Microsoft |operating systems could just ignore Windows posts. Ditto that. I also have been perturbed by the rudeness of some folks responding to MSW posters. If one of those had been my first exposure to FreeBSD years ago, I for one would have gone elsewhere. All we need is a little tact and a desire to help--who knows who is on the verge of kicking the MSW habit. Randall Randall Hopper: |Amancio Hasty: | |Only members are allowed to post to the multimedia mailing list. | |This is a bad idea IMO. | |Some newer folks that pick up the Bt848 driver or some FreeBSD util and |have trouble with it want to mail a question without signing up for a |mailing list, waiting until they know they're getting the messages, post |the question, accumulate a bunch of irrelevent list mail, get their answer, |and then unsubscribe. | |They'll more likely just drop the driver/utility, forget the problem, and |go onto something else. That's what we'll be encouraging. | |Don't forget that not everyone has an ISP that let's them accumulate the |mail traffic some mailing lists produce, even if they're willing to put up |with the inconvenience of subscribe/wait/post/wait/unsubscribe/clean house. | |I do this same thing with various S/W I use. | |Do the few Windoze posts we get here from time to time annoy you that much? |Hey man, relax and take a vacation. ;-) | |Randall | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-multimedia" in the body of the message Randall Roger Hardiman : |Hi, | |Is -muiltimedia still closed so you need to subscribe before you |can post? | |I'd like it open again, as it used to be. | |Few reasons. |1) We only ever have one or two Windows 95/98/NT questions a month. | And I usually reply direct to the author with the answer anyway. | | (I reply with a friendly comment about a) what FreeBSD is, b) where | the correct place to post/search is and c) I often know the | answer anyway as I have Win95/98/NT 4 boxes with Bt848's based | grabbers and do some Video for Windows API development. | |2) In Europe, local calls (to your ISP) are not free. email costs me |money. | freebsd-muiltimedia is low traffic, but subscribing increases the | amount of mail you need to download, when usually the reply you | wanted is CC'ed to the original author anyway. | |I'd like the group back open again. | |This time, we could generate some stats on Windows posts and just see |how |frequently they occur. |Perhaps those that reply with abusive comments about Microsoft |operating systems could just ignore Windows posts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 10:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21319 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 10:29:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21309; Sat, 11 Jul 1998 10:29:25 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA06795; Sat, 11 Jul 1998 10:29:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807111729.KAA06795@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: Roger Hardiman , Mark Handley , Mark Tinguely , Greg Lehey , "Jonathan M. Bresler" , Sue Blake , Eivind Eklund , multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: list closed to non subscribers In-reply-to: Your message of "Sat, 11 Jul 1998 12:56:02 EDT." <19980711125602.A14345@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Jul 1998 10:29:02 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jonathan, Care to open the list again? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 10:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24719 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 10:59:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24713 for ; Sat, 11 Jul 1998 10:59:36 -0700 (PDT) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id NAA29741; Sat, 11 Jul 1998 13:59:35 -0400 (EDT) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id NAA20011; Sat, 11 Jul 1998 13:59:35 -0400 (EDT) Message-Id: <199807111759.NAA20011@chai.torrentnet.com> To: joelh@gnu.org CC: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Your message of "Sat, 11 Jul 1998 10:45:31 CDT." <199807111545.KAA13645@detlev.UUCP> Date: Sat, 11 Jul 1998 13:59:35 -0400 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How on earth will issuing a diagnostic break scripts? Consider a script that uses output of another script. A typical shell script that just does its job normally does not chatter away on stderr. If dmr & ken had wanted warnings they would have added stdwarn [warning: that is a joke] > How on earth will issuing a diagnostic make it harder to write > scripts? Because now you have to filter out (additional) noise. > I'm *not* talking about a prompt a la cp -i. I'm *not* talking about > a failure a la trying to symlink over an existing file. I'm talking > about a diagnostic. Understood. I am just pointing out that *any* deviation from existing practice can break things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 11:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26668 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 11:19:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ccs.sogang.ac.kr (root@ccs.sogang.ac.kr [163.239.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26661 for ; Sat, 11 Jul 1998 11:18:57 -0700 (PDT) (envelope-from kylee@oslab0.sogang.ac.kr) Received: from oslab0.sogang.ac.kr by ccs.sogang.ac.kr (8.8.8/Sogang) id DAA09774; Sun, 12 Jul 1998 03:10:31 +0900 (KST) Received: from oslab0.sogang.ac.kr by oslab0.sogang.ac.kr (8.8.8/SMI-SVR4) id DAA05957; Sun, 12 Jul 1998 03:10:02 +0900 (KST) Message-ID: <35A7AB93.AE27345@oslab0.sogang.ac.kr> Date: Sun, 12 Jul 1998 03:14:44 +0900 From: Lee Ki Young Organization: Sogang University X-Mailer: Mozilla 4.03 [ko] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Disk Scheduling for Multimedia IN BSD..?? Content-Type: text/plain; charset=iso-2022-kr Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HI!! Well. I want to know about disk scheduling for Multimedia data (,stream) in BSD. I hope someone teach me followings. 1. Which kind of scheduling is truly used in BSD for continuous and non-continuous data? 2. How can I the scheduling code, where I can find it? 3. If you have some answers, please introduce some useful contents or related sites. Thanks for your reading. I will wait your reply. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 11:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00263 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 11:39:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00258 for ; Sat, 11 Jul 1998 11:39:27 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA04241; Sat, 11 Jul 1998 14:38:55 -0400 (EDT) (envelope-from luoqi) Date: Sat, 11 Jul 1998 14:38:55 -0400 (EDT) From: Luoqi Chen Message-Id: <199807111838.OAA04241@lor.watermarkgroup.com> To: hackers@FreeBSD.ORG, jvz@ns.nternet.net Subject: Re: Assembly.. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, im having a bit of a problem understanding the way > freebsd does its syscalls in asm.. ive searched, and > read the as info pages numerous times, and looked over > kernel src, along with compiling simple C code with -S -o blah.s > i was told fbsd uses 'call gates' so that where linux would do > > movl $1,%eax // exit() syscall in linux > movl $0,%ebx // exit code > int $0x80 // do the syscall > > i was told fbsd is similar > only where linux does the interrupt it would do a call ie; > > call 0x7,0x0 It should be a `far' call: lcall 0x7,0x0. -lq > > which gives me errors from as (no known i386 instructions) > > i understand i could do the 'call syscallName' but i want > a thorough understanding on how these ' call gates' work.. > if someone could explain a bit how they work and are called.. > and provide me a sample standalone asm code .. heck 'hello world' > for that matter.. i would greatly appreciate it. > > thanx in advance. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 11:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02329 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 11:59:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.nternet.net (ns.nternet.net [206.154.20.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02324 for ; Sat, 11 Jul 1998 11:59:49 -0700 (PDT) (envelope-from jvz@ns.nternet.net) Received: from localhost (jvz@localhost) by ns.nternet.net (8.8.8/8.8.7) with SMTP id PAA16085; Sat, 11 Jul 1998 15:08:34 -0400 (EDT) Date: Sat, 11 Jul 1998 15:08:34 -0400 (EDT) From: Jonny To: Luoqi Chen cc: hackers@FreeBSD.ORG Subject: Re: Assembly.. In-Reply-To: <199807111838.OAA04241@lor.watermarkgroup.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 > > call 0x7,0x0 > > It should be a `far' call: lcall 0x7,0x0. > > -lq right, my bust. even so i continue to get operands dont match any known 386 instruction. -> going out of my head =) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 12:06:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03379 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 12:06:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03370 for ; Sat, 11 Jul 1998 12:06:48 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id VAA12713; Sat, 11 Jul 1998 21:04:18 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id RAA16359; Sat, 11 Jul 1998 17:22:13 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807111522.RAA16359@semyam.dinoco.de> To: "Michael W. Smith" Cc: freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Too many files open? In-reply-to: Your message of "Fri, 10 Jul 1998 14:08:41 PDT." Date: Sat, 11 Jul 1998 17:22:11 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I keep getting a too many files open error on the system and it's hosing > it all to hell. A friend of mine who's more familiar with FreeBSD told me > I need to rebuild the kernel but he wasn't sure which directive I need to No, you don't have to. You can increase the maximum number of files opened at the same time on the system at will with sysctl. Just look at the list it gives with "sysctl -A" and you will soon find the variable which does this. Put a script in /usr/local/etc/rc.d which does the appropriate sysctl call and on startup the system sets their number to the new count automatically. That's how I did it on my 2.2-stable system. If it is that a program can't open enough files at the same time there is a limit setable with sysctl which is used systemwide for processes. Additionally a process has its own soft and hard limits that one sets with limit (csh/tcsh) and ulimit (sh/ksh/bash). Their initial values depend on the settings in /etc/login.conf. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 12:07:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03491 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 12:07:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03485 for ; Sat, 11 Jul 1998 12:07:26 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id PAA08412; Sat, 11 Jul 1998 15:15:07 -0400 (EDT) Date: Sat, 11 Jul 1998 15:15:07 -0400 (EDT) From: Charles Youse To: Bakul Shah cc: joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: <199807111759.NAA20011@chai.torrentnet.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 Obviously this guy is on crack. "Adding a warning to stderr is gonna break things! Why can't we just leave it alone instead of effecting massive change?!?" I'd hate to see what FreeBSD would be like if everybody had that mentality. Chuck On Sat, 11 Jul 1998, Bakul Shah wrote: > > How on earth will issuing a diagnostic break scripts? > > Consider a script that uses output of another script. A > typical shell script that just does its job normally does not > chatter away on stderr. If dmr & ken had wanted warnings > they would have added stdwarn [warning: that is a joke] > > > How on earth will issuing a diagnostic make it harder to write > > scripts? > > Because now you have to filter out (additional) noise. > > > I'm *not* talking about a prompt a la cp -i. I'm *not* talking about > > a failure a la trying to symlink over an existing file. I'm talking > > about a diagnostic. > > Understood. I am just pointing out that *any* deviation from > existing practice can break things. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 12:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00632 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 12:50:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00616; Sat, 11 Jul 1998 12:50:19 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) id PAA24148; Sat, 11 Jul 1998 15:47:07 -0400 (EDT) Date: Sat, 11 Jul 1998 15:47:07 -0400 (EDT) From: "Larry S. Lile" To: hackers@FreeBSD.ORG, tokenring@FreeBSD.ORG cc: David Greenman Subject: Still having problems with my driver :( Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1461733264-1779487855-900186427=:23884" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1461733264-1779487855-900186427=:23884 Content-Type: TEXT/PLAIN; charset=US-ASCII I still cannot get the upper network layers to respond to incoming packets. I even hacked tcpdump to make sure that I was no wrecking the packets as I took them off the wire. 15:29:58.698564 arp who-has anatok tell blastok (0:0:83:2d:9f:35) hardware #6 15:29:59.588735 cyntok > anatok: icmp: echo request 15:30:00.590438 cyntok > anatok: icmp: echo request tcpdump: WARNING: compensating for unaligned libpcap packets (^- anybody know how to fix this?) 15:30:03.499586 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) win 16384 15:30:09.271262 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) win 16384 15:30:09.702343 arp who-has anatok tell blastok (0:0:83:2d:9f:35) hardware #6 The only messages I got indicating anything at all is wrong were these when I ifconfig the card up for the first time after a reboot. Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, 10.0.0.255.520): No buffer space available Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 --> 10.0.0.1: File exists Any ideas what might be wrong, or could someone please look at my code and help me figure this out. I have attached the tcpdump patches if someone would like to commit them to the source tree, I also sent them to the tcpdump maintainers. The source for my driver is at http://anarchy.stdio.com. I really need some help here, It is undoubtedly something small and simple that I am overlooking. Larry Lile lile@stdio.com --1461733264-1779487855-900186427=:23884 Content-Type: APPLICATION/octet-stream; name="tcpdump-tr.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: tcpdump token-ring patches H4sIAL+8pzUAA+0aa3PaSDJf4Vd0nL0YvLKNMH7HqZVBNrrF4EMij8qlWCEN oIuQdNJgx5X1f7/ukYQEBnv3Ko+7WqZcWJrp6fd092iGW4E9nQS7z75hg1rl cH8fngG1ysL/5AUO9vflw739SqUKIFcOapVnsP8tmUrbNOJmCPAs9H3+GNzt mDH3ezD0fRtP7J/837F2ApNb469KQ66gPWsr7S9XDmf2rx3uH2DP3sEh2r/y VblY0f7i9t/a2oLdaRTuRqG1a/keD53B7kOn8ENnVNBNDn+fuiDLIO+fyPJJ tQby8fFRcXt7G2awC2CV4xP5MAbbmm/0DsdV6fgIxCsA/qE1uGPhv3BqcQhC x+MsTP9HHz7CGXxBsMIXYHzMwr4z7ItBqdBoGX21LVeuzuFeKj5fBaKpqnqE QQZhBJrIzQEICL2lXc+GgyBYHL++zoaHtu0sELhoNDQaJ6XE0uHT9jeQjvuf mPejpPvRfrtuX6elS12YeFu41I71lWk8Hv9luVaV0/h/UK0cUvyvVarr+P89 2i7G3S2o+8EdRvgxh5JVxmB9dCTR7zH9HlfEryx+q+J3T/zWxO+++D1ALAVj zKDLRszjEfhDwAgGPc+5wcjm8DvqqZuuM/RDzzF3ABTXBUEzgpBFLLxh9g5i IXa6zHYiykRT7vgemJ4N04iB40HkT0OLiZ6B45nhHSC+SSTBrcPH4Ifivz/l hGXi287QsUzCIYEZMghYOHE4ZzaGXP/GsfGBj01+AiW5nKK2fJtBnnxEuELG TSRPIpkD/4bAUo15Pob0mCU+diIIzNAchWYwJn4dlA714eD8OwlK1TIhm8OO UJY7tR1vlEokOIh72RMUCdvjRCHh2vat6QQ7hTZIUT4lGJiYmHgc0xVCzpQi lClm5TiVhIilvTKYaDnTRrtyJyK+Z0iAKCAodhK+ITP5FG1L5Mh+wieQ2cgf 8luyB6IPXPNOkBr6ruvfEjrT+uT5ty6zR4zwnRCq334zhJihb1PmTLSTR8Vu mOsHyPzg7lHPkwhdy7wNmYc6PGfhJ+ayO+wZ+KHJfdQ/iUkqTKqhKXZGO5ub 0GaO0Blh98wJyRPrf46Y52cQYhksokJ13cGAkUbQY3y0lI29jFD5VAv4E5+z VNIIBQsRtw1DHFhQX+LrEAXMIk+nQsIPCdFtSG7uxQ4fRWgSWlpgNDUd9M6F 8VbpqoDP193OG62hNlC/io4dKKXSbsBbzWh2egY+vwf13XVX1XXodEG7um5p aoMwIYKu0jY0VZdAa9dbvYbWvpRmE1valWYohtZpS0hUTWfmpkHngvBcqd16 E3uUc62lGe8F9QvNaBPFCySpwLXSNbR6r6V04brXve7oaholmugoqBihePLp YVxIbYvSaccCtGmI5mw5LoNXLv7+EnHb8Xcsf/Ia5+8WXzhDz2ZDcHFWMSnN 0FIRB2uMOSG0IsemmqxIaWrjl9KLMvzUZCZa5KeN0+ILNJwzLCKWZKm+iu6i XVqIk53x64Vu7kzYw97IRwk49RMv0O/rRqPe7xeT+nAymA5P05cQ7cnDuxnd DJPH+K4zTLAknRtxJh9vFOcBHQHszbNCfUJpXszMshl95JdPVowGq/r7N2a4 fGxqr5iEA6tnYbWyciDmIq9hYe058MAyF6A2ROk9NC1Gysq6TdsOuU+LeL5f 6InfBQvdrmsJZcfuM+0LB9oKyEN5cLrQHXlmgEY8LaZO53joggxufMcuxlW9 8ORSyEYYgDHkzM8fBBI+IwC4zBvxcbn4pVhYgE28JsY2Fk4LW8RK+sllOTzK AVtuDmzaj8Z+yJP9CAmObKeDPMANS+kRguVBDpUroPOEyqVBAD+D0flVbfeb jW6/pbbL2QRcEiVN7+udXreu9rsYWNRGGWbDfw4vvne1C3q6NJrlnBC7WzmU W6CmBgaMKemqAAy7JghNSIBhHGZuQPnV9IjsNpkVxmaUxzZgGIUxxqB5bTAj qCZGjLAAEhktRsyngWNjHOIcY9UYvYYSw9D5nEclYj/mMMwwt4KHyJ8gG6Jw YJwsifxNXZtyi+17lGBozOP+OCqV85jevXuXe93NnjMjk0ZLie3LbrD9eibw B/kjvHoF8kEZfof5kcpHVGuBrPbvoWuOysVCoUQ+XRbePCxt/C0C+rNPYEPC wUJGlJZbn2oNb1RS9W69xINy+TGYhm4swCRr4bRYYC6m0xW0vxl5AYNZm/sp UKbNZVzeF4tx7Z26ARUN3A8QAisZCDGxU0xI6ujkEwF6zWawmUIHPnaKyg29 hToERUgWXzpTxCAJNvlNNpPSEcaeSSCqoc2Yqdlo/DqPAN/i11ssK+NScBOD KYJuEopkpjedDGLSgzuO5Y9p8SlWi1jTmgGVgqLC3y3mAl36daGUBjcsi0Jp PihR1O4Hn/jYxvGxtBANAxH+4ngYc4TOO95+HT+fpkOJUGIo7l8ZIgvLgl6B fUYDeFlA/MxDFI/Z/dkCyEdNIkk2ZP2YoUo2uBhqF8Lp8kBKcAUeJcp6iULw qJwut0TsVwuRFFAvhdT/P/wuMG6Ta37coGVSGKGzAvKIz/cJJpYu3HwawnQz c9tiAb22gBbXMfrMvlzBrekRyzBCTxlQ/DJ55pEUQGn1sChikSRmo//sYiiz xoxi3TiGvtvEohY3N4jN/USxK/U5TJbz3rgjkHTNpB7HAByYkXDBididCEfF Mtv2b3HfcssgYoICbkJGrj/ArYrAsIsqfULnuSyh2P+aot9RCE72ivEiHWEO oF1ovLVK9ltXSj1diLkIuzyjfXmQ0vKek0tbmQ/dz3Gmo3QiGJA2fOFZMW1c qIJp2j8g28v4zXG3LJEuy6Mz7vJpNKl1EAOtoKTEoTeckC7FOZ4/OQHgvjaM tQ7klwtaKyRrdvtsNQtIK/H+J6CQj0cBcIHns1+cNkuo0/n0J5bAkrUfL3Fc HGDgngONIJaGcIVWq76Nu9wsMr+EMe7j8UH0RkJU8gxU+eKKkxLdSZCmJXxK kw+cIdF4lSPdHPu0hmgPjdNiNkLzNo3jRExQez5b63OLfRaIyzy/7uM5SwSP 6c/CTAmlxSxbjlNsvq6Yy41jrK2jpejKgth9yuRnYhJevoTns5qigPWUOXV5 pqtYR2URx8S0zynsalAKfCfoFlNO4pY2/+ltiqz8oz/IfeeWfv/NbYO++gng U+d/sry/cP5Xkw/k9fff79EePf/LO8WyE8DqiVzJTgBz0A+PCmt7q88A5cMD ST6S41NAwhR37KUHZ0nlRVUjsFGQLOb5KjDZES8Wh2I3OTd/7lytlE1fXXGK w7AHaH+eQ7uimH0c7c9L0M5zO3cA98ewPqWAUcgeU+ADeMearNL4A0o/2pnX 7U+3dKlfmZ/Y0HHZN7j+8VT835Or1cX7H/vy+v7Hd2lz8R//70QDx1u8AJJ5 x7IssDeXBVLQxWsgRye1g9UpoCYhjuQWSP2ipVzqP59tN5rKG7V/UW8brX7z TIako63GtxiSPkO7Uvt08NDX3+t9esPuf1LMTuBVo6l2+22jo2Q4dNVoaW31 vHch+sR396aqNNSuns3uqoauXRrvr9UzEQrTnjdK62yGqFP/VWnghkJXaE8h Jj+fkTau+pdXRuciptI6b/WVlnbZFm900SIVsdHQkOSV0pbPCulFGhl7sObX 4ayQHHHsWNktm5jH+MDDDKkjeea4d869TWbPw3D2OEBfj3GQxYTuk1T719Q9 bI9+jPqXVkM1qTpbCwkJOl5IZ3vDKHvmGWlv6rqzFz8KhvNcBk7GSxBk00In e44yBJG3KGY09cIgY4OOYmbPwxwfdLKTPt8OBA40Su48xYJBMOwnepyY1thm YoYZRgyFG47xZcod5IUcsqUq7QutpaJTZobAgcY1mh77fvrS0s5b9yD+X9eV 63scbDXiQVQcbLtUIMV1pVBt4up/bdWm6OMLP19T0T86o63bn2mzTB+fF38T Gk/Vf7W9Wf13UKlR/Vet1tb7/+/Slt//Oj6ScrcnCOJ/57bWwm0h3ITazuye Fs2bsPjOkLyzwJq4jpO/5jWh7/mrr3YREmzJdaupF7PIbCk+i3URNWHMOJCS W2A5/hIcyIblms6EheIiTvUha8hCTkcpa/E1oKXXwOa4W8nSQ45yvCSHFSmP c1fEkhOahWtiT9wRS11i9UWj8/fiQpDSM5p0vafdgHqnbXS1857R6erz95CE 3y29grTq/hFigXYnuX+EYEZH3D8iREuvIP1X948EWyhWQ9PrLQVr3sYOIBNI GNQ3atsAvam0Wnkx8W9OynMVOVTOWwKVIINSNrSuWjdInOypjjpD5loS6Ndq XaMH9Z2Kkijd91KCVlf/0UMgHCRsDeVKuUTZSk9oBQ1S73XVK+IX9aD3znVD M3qGCpedTkMnVIheV7tvtLqqn0KrowuF9XRVQiKGIsgjFtQWDuPzeU/XhN60 tqF2u71ruv4l7js2O29RMcisgrMbQsedtpAZddTpvie8pA9hAgneNsWugVQq tKaQLnTUXt0Qd/cySKSK+jRywkJbvcQqX23XVRrtEKK3mq6W0WKaTgBaTPmt 8l7I2BPik62Qt/gx57qSsChoF6A03mjEfAKMfqBric/EN9n0Xr2ZaD9ZBbvF 4ov46sfCuVPy2bs2G148EqThEk+PnejAOeIfKh/hJVQ+H1XKs3nZyWB2dFgq xUdXND20hmUxSR5WKmV4/RqOygs8dVEn/SulHjN2kKFGRmhIVy/JRxDkHcgH xeKyk9Ls/DL5FghgWqcPO4fLOmMRbSHiQ5Y+rpwR/ZEZ8VE9oB6W9UZs9GGJ nIjh/rS4rmPXbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3W7f+0 /QdYFh4+AFAAAA== --1461733264-1779487855-900186427=:23884-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00440 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:06:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00400 for ; Sat, 11 Jul 1998 19:06:23 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA05896; Sat, 11 Jul 1998 18:14:39 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd005830; Sat Jul 11 18:14:33 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA17113; Sat, 11 Jul 1998 18:14:27 -0700 (MST) From: Terry Lambert Message-Id: <199807120114.SAA17113@usr08.primenet.com> Subject: Re: Improvemnet of ln(1). To: cyouse@artemis.syncom.net (Charles Youse) Date: Sun, 12 Jul 1998 01:14:27 +0000 (GMT) Cc: bakul@torrentnet.com, joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-Reply-To: from "Charles Youse" at Jul 11, 98 11:46:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For interactive use, alias ln to `ln -w' to warn you. If you > > change the default behavior of ln, you *will* break scripts. > > Unlike editors, ln is more likely to be used in scripts than > > interactively (well, it is so for most people). > > I fail to see how. An extra line output to stderr is going to break > scripts? Can you provide an example? ... # call subscript, save all output... a successful subscript will produce # no output... OUT=/tmp/out.$$ subscript > $(OUT} 2>&1 # postprocess output to look for errors, warnings... ... echo "The following failures occurred while processing subscript:" echo "-----------------------------------------------------------" cat ${OUT} echo "-----------------------------------------------------------" rm ${OUT} exit 1 fi > > Bottom line: backward compatibility is a good program design. > > Well, not always. Compare Windows/DOS. That's OS design, not program design. Most code can be compiled on Windows/DOS, if only because, by definition, good program design means the code is portable to diverse platfroms, including Windows/DOS. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:06:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00526 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:06:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA00502 for ; Sat, 11 Jul 1998 19:06:55 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40827(1)>; Sat, 11 Jul 1998 14:01:19 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id OAA21311; Sat, 11 Jul 1998 14:01:17 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199807112101.OAA21311@mango.parc.xerox.com> To: "Jason K. Fritcher" cc: hackers@FreeBSD.ORG Subject: Re: Raw sockets & ICMP In-reply-to: Your message of "Thu, 09 Jul 1998 23:31:04 PDT." Date: Sat, 11 Jul 1998 14:01:16 PDT From: Bill Fenner Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As far as I can tell, the design of raw sockets was kind of ad-hoc, so I wouldn't necessarily call it "intentional". The idea is that you would use a raw socket to provide services that the kernel doesn't, so there's no need to send the messages that the kernel has already handled to a raw socket. The easiest solution is to use bpf instead of raw sockets, since its interface is cleaner. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00591 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:07:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (root@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00569 for ; Sat, 11 Jul 1998 19:07:05 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA19201; Sat, 11 Jul 1998 18:23:35 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd019159; Sat Jul 11 18:23:25 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA17458; Sat, 11 Jul 1998 18:23:19 -0700 (MST) From: Terry Lambert Message-Id: <199807120123.SAA17458@usr08.primenet.com> Subject: Re: Improvemnet of ln(1). To: bakul@torrentnet.com (Bakul Shah) Date: Sun, 12 Jul 1998 01:23:19 +0000 (GMT) Cc: joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-Reply-To: <199807111759.NAA20011@chai.torrentnet.com> from "Bakul Shah" at Jul 11, 98 01:59:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How on earth will issuing a diagnostic make it harder to write > > scripts? > > Because now you have to filter out (additional) noise. Consider the "improvement" to the dump(8) command about a year ago... > > I'm *not* talking about a prompt a la cp -i. I'm *not* talking about > > a failure a la trying to symlink over an existing file. I'm talking > > about a diagnostic. > > Understood. I am just pointing out that *any* deviation from > existing practice can break things. Especially if it is a deviation in order to protect the kind of people who type "DIR" in DOS after "DELETE FILE.DAT" to reassure themselves that the system, indeed, did what they told it to do, and deleted the file. Protecting people who don't believe a file is really gone until they get a directory listing without the file in it is pretty low on the ladder of UNIX priorities. I wouldn't object too strongly to a "-w", as has been suggested elsewhere, so long as the alias was not there by default. I would still object a little, on the principle that a future version of POSIX might define a "-w" argument, causing a namespace collision with the FreeBSD version of the command (and thus breaking scripts, .login's, .cshrc's, etc.). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00638 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:07:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (root@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00616 for ; Sat, 11 Jul 1998 19:07:11 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA11446; Sat, 11 Jul 1998 17:56:15 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd011404; Sat Jul 11 17:56:05 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA16154; Sat, 11 Jul 1998 17:56:00 -0700 (MST) From: Terry Lambert Message-Id: <199807120056.RAA16154@usr08.primenet.com> Subject: Re: Improvemnet of ln(1). To: joelh@gnu.org Date: Sun, 12 Jul 1998 00:56:00 +0000 (GMT) Cc: tlambert@primenet.com, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-Reply-To: <199807111525.KAA13574@detlev.UUCP> from "Joel Ray Holveck" at Jul 11, 98 10:25:34 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> I've many times used ln(1) to create what you call 'questionable links' > >>> on purpose and I'd _hate_ warnings. > >> You frequently link to files that don't exist? I generally consider > >> that to be putting the cart before the cat(1), er, horse. But it's > >> your system. > > I don't do it frequently, but yes, I do this occasionally. > > Then occasionally getting a warning wouldn't be a bad thing. Except I like "make world" to complete without issuing any warnings. The most fundamental thing you can do with a system, building itself, should not be fraught with warnings, IMO. > Yes, you could. I do that quite frequently. (You can imagine my > ~/hp9000-hpux/bin directory, full of compatibility scripts.) But is > this a problem that only exists for a few users and would annoy many > (which would mean that we few should use the scripts), or does it > exist for many and would annoy few (which would mean we should modify > ln)? A better place to put this would be a "ln" shell built-in. > > Whereas in order to get the existing non-"-f" behaviour, I'd have to > > modify existing code. > > A warning message wouldn't break your existing code. Again, we're not > proposing a prompt here, just a diagnostic that you can ignore if > you're intentionally linking to a non-existant file. A warning implies a seperate exit code, which I can check for, so I can see if the program completed with no errors or warnings before proceeding onto the next operation. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01589 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:11:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01572 for ; Sat, 11 Jul 1998 19:11:46 -0700 (PDT) (envelope-from tfuruya@ppp142104.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142104.asahi-net.or.jp [202.213.142.104]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id FAA23924; Sun, 12 Jul 1998 05:32:29 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id FAA12708; Sun, 12 Jul 1998 05:26:25 +0900 (JST) Message-Id: <199807112026.FAA12708@galois.tf.or.jp> To: luoqi@watermarkgroup.com Cc: freebsd-hackers@FreeBSD.ORG, heyer@cs.wisc.edu, Tetsuro Furuya Subject: Re: swap_pager and vm_faults From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Thu, 9 Jul 1998 20:01:37 -0400 (EDT)" References: <199807100001.UAA12460@lor.watermarkgroup.com> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 12 Jul 1998 05:26:24 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <199807100001.UAA12460@lor.watermarkgroup.com> Luoqi Chen wrote: > > Any idea what exactly would cause this? > > > > Jul 5 08:30:24 rancor /kernel: swap_pager: I/O error - pagein failed; > > blkno 708776, size 4096, error 22 > > You have a bad sector on your swap partition. I presume this is an IDE disk, > you may try using bad144 to map the bad sector out. > > > Jul 5 08:30:24 rancor /kernel: vm_fault: pager input (probably hardware) > > error, PID 197 failure > > Jul 5 08:30:24 rancor /kernel: pid 197 (innd), uid 8: exited on signal 11 > > > > As you can tell from innd, this machine is a news Server with 96 Megs of > > RAM and 256 Megs of Swap. While the CPU and Disk Drives are kept pretty > > busy, it usually has plenty of memory to spare. The time it occured (8:30 > > AM on a Sunday) and the fact the machine stayed up seems very strange to > > me. This machine has been rebooting about once a day on average for no > > obvious reason, so I'm trying to investigate everything possible. > > > > -- > > John Heyer :: University of Wisconsin - Madison :: http://heyer.ml.org > > Please take a glance at my posted mail, 07/09 Re: Disk problem. Message-Id: <199807082149.GAA01464@galois.tf.or.jp> ======================================================================== FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:14:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02353 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:14:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02231; Sat, 11 Jul 1998 19:13:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id JAA29530; Sun, 12 Jul 1998 09:58:47 +0930 (CST) Message-ID: <19980712095847.M23241@freebie.lemis.com> Date: Sun, 12 Jul 1998 09:58:47 +0930 From: Greg Lehey To: David Richardson , FreeBSD Questions Subject: Re: Q: RAID Controllers References: <199807110535.WAA28570@hub.freebsd.org> <3.0.5.32.19980711065416.009108d0@www.davids.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3.0.5.32.19980711065416.009108d0@www.davids.org>; from David Richardson on Sat, Jul 11, 1998 at 06:54:16AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 11 July 1998 at 6:54:16 +0000, David Richardson wrote: > All, > > I have been trying to determine which, or if any RAID controllers are > supported. Or if there is any way to setup RAID-1 through FreeBSD. I did > see a new boot disk for the DPT RAID controller 2.2.6 CD-ROM. Is this the > only RAID controller that is supported? Why are we getting so many questions sent to -hackers lateley? This must be at least the third I have answered in the last 24 hours. Please send questions to FreeBSD-questions. Hackers is for in-depth discussion. Yes, the DPT is currently the only controller supported. You can get software RAID-1 with the ccd driver or vinum. Vinum is still in development--see http://www.lemis.com/vinum.html for more details. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:26:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06443 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:26:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (root@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06427 for ; Sat, 11 Jul 1998 19:26:16 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id VAA20881; Sat, 11 Jul 1998 21:18:03 -0400 (EDT) Date: Sat, 11 Jul 1998 21:18:03 -0400 (EDT) From: "Matthew N. Dodd" To: Charles Youse cc: Bakul Shah , joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Jul 1998, Charles Youse wrote: > Obviously this guy is on crack. "Adding a warning to stderr is gonna > break things! Why can't we just leave it alone instead of effecting > massive change?!?" You -will- break things if you alter the default behavior. As you are not able to prove for -all- cases that this change will not break things it should be only enabled by a new switch. (-w as someone suggested) Besides, creating a link to a non existent directory is not cause for an error condition; you get the error when you attempt to reference the link. This is the correct unix behavior, to assume that you know what you're talking about. If you want to have unix perform sanity checks, there are flags for that as well. Add this as a new flag please. > I'd hate to see what FreeBSD would be like if everybody had that > mentality. Linux /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08347 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 19:33:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08284 for ; Sat, 11 Jul 1998 19:32:51 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-105.camalott.com [208.229.74.106] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA01292; Sat, 11 Jul 1998 14:26:57 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id OAA14413; Sat, 11 Jul 1998 14:26:12 -0500 (CDT) (envelope-from joelh) Date: Sat, 11 Jul 1998 14:26:12 -0500 (CDT) Message-Id: <199807111926.OAA14413@detlev.UUCP> To: bakul@torrentnet.com CC: dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG In-reply-to: <199807111759.NAA20011@chai.torrentnet.com> (message from Bakul Shah on Sat, 11 Jul 1998 13:59:35 -0400) Subject: Re: Improvemnet of ln(1). From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807111759.NAA20011@chai.torrentnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> How on earth will issuing a diagnostic break scripts? > Consider a script that uses output of another script. A > typical shell script that just does its job normally does not > chatter away on stderr. Most scripts that I have seen that rely on output use stdout, not stderr. > If dmr & ken had wanted warnings they would have added stdwarn > [warning: that is a joke] :-) >> How on earth will issuing a diagnostic make it harder to write >> scripts? > Because now you have to filter out (additional) noise. So, we've now got a script that relies on the stderr of another script, the latter of which makes symlinks to non-existant files, and the former of which will break if a line is added. Have I got you right? I will personally buy a beer (so long as it's not an American beer) for the first five people who can show me current existance of such a script. (In other words, a script written during or after this discussion doesn't count.) That said, I sincerely doubt I'll have to buy a single beer. >> I'm *not* talking about a prompt a la cp -i. I'm *not* talking about >> a failure a la trying to symlink over an existing file. I'm talking >> about a diagnostic. > Understood. I am just pointing out that *any* deviation from > existing practice can break things. If you want every utility and library call to behave the same forever, then stay at the same OS revision forever. If you don't want change... don't change. I realize that it is possibly feasable for such a script to exist. I also believe that it is practically unreasonable, and arguably (though I won't argue it in this thread, and hope that none of you do) deserves to lose. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 19:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00632 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 12:50:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00616; Sat, 11 Jul 1998 12:50:19 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) id PAA24148; Sat, 11 Jul 1998 15:47:07 -0400 (EDT) Date: Sat, 11 Jul 1998 15:47:07 -0400 (EDT) From: "Larry S. Lile" To: hackers@FreeBSD.ORG, tokenring@FreeBSD.ORG cc: David Greenman Subject: Still having problems with my driver :( Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1461733264-1779487855-900186427=:23884" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1461733264-1779487855-900186427=:23884 Content-Type: TEXT/PLAIN; charset=US-ASCII I still cannot get the upper network layers to respond to incoming packets. I even hacked tcpdump to make sure that I was no wrecking the packets as I took them off the wire. 15:29:58.698564 arp who-has anatok tell blastok (0:0:83:2d:9f:35) hardware #6 15:29:59.588735 cyntok > anatok: icmp: echo request 15:30:00.590438 cyntok > anatok: icmp: echo request tcpdump: WARNING: compensating for unaligned libpcap packets (^- anybody know how to fix this?) 15:30:03.499586 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) win 16384 15:30:09.271262 cyntok.1054 > anatok.telnet: S 3037285377:3037285377(0) win 16384 15:30:09.702343 arp who-has anatok tell blastok (0:0:83:2d:9f:35) hardware #6 The only messages I got indicating anything at all is wrong were these when I ifconfig the card up for the first time after a reboot. Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, 10.0.0.255.520): No buffer space available Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 --> 10.0.0.1: File exists Any ideas what might be wrong, or could someone please look at my code and help me figure this out. I have attached the tcpdump patches if someone would like to commit them to the source tree, I also sent them to the tcpdump maintainers. The source for my driver is at http://anarchy.stdio.com. I really need some help here, It is undoubtedly something small and simple that I am overlooking. Larry Lile lile@stdio.com --1461733264-1779487855-900186427=:23884 Content-Type: APPLICATION/octet-stream; name="tcpdump-tr.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: tcpdump token-ring patches H4sIAL+8pzUAA+0aa3PaSDJf4Vd0nL0YvLKNMH7HqZVBNrrF4EMij8qlWCEN oIuQdNJgx5X1f7/ukYQEBnv3Ko+7WqZcWJrp6fd092iGW4E9nQS7z75hg1rl cH8fngG1ysL/5AUO9vflw739SqUKIFcOapVnsP8tmUrbNOJmCPAs9H3+GNzt mDH3ezD0fRtP7J/837F2ApNb469KQ66gPWsr7S9XDmf2rx3uH2DP3sEh2r/y VblY0f7i9t/a2oLdaRTuRqG1a/keD53B7kOn8ENnVNBNDn+fuiDLIO+fyPJJ tQby8fFRcXt7G2awC2CV4xP5MAbbmm/0DsdV6fgIxCsA/qE1uGPhv3BqcQhC x+MsTP9HHz7CGXxBsMIXYHzMwr4z7ItBqdBoGX21LVeuzuFeKj5fBaKpqnqE QQZhBJrIzQEICL2lXc+GgyBYHL++zoaHtu0sELhoNDQaJ6XE0uHT9jeQjvuf mPejpPvRfrtuX6elS12YeFu41I71lWk8Hv9luVaV0/h/UK0cUvyvVarr+P89 2i7G3S2o+8EdRvgxh5JVxmB9dCTR7zH9HlfEryx+q+J3T/zWxO+++D1ALAVj zKDLRszjEfhDwAgGPc+5wcjm8DvqqZuuM/RDzzF3ABTXBUEzgpBFLLxh9g5i IXa6zHYiykRT7vgemJ4N04iB40HkT0OLiZ6B45nhHSC+SSTBrcPH4Ifivz/l hGXi287QsUzCIYEZMghYOHE4ZzaGXP/GsfGBj01+AiW5nKK2fJtBnnxEuELG TSRPIpkD/4bAUo15Pob0mCU+diIIzNAchWYwJn4dlA714eD8OwlK1TIhm8OO UJY7tR1vlEokOIh72RMUCdvjRCHh2vat6QQ7hTZIUT4lGJiYmHgc0xVCzpQi lClm5TiVhIilvTKYaDnTRrtyJyK+Z0iAKCAodhK+ITP5FG1L5Mh+wieQ2cgf 8luyB6IPXPNOkBr6ruvfEjrT+uT5ty6zR4zwnRCq334zhJihb1PmTLSTR8Vu mOsHyPzg7lHPkwhdy7wNmYc6PGfhJ+ayO+wZ+KHJfdQ/iUkqTKqhKXZGO5ub 0GaO0Blh98wJyRPrf46Y52cQYhksokJ13cGAkUbQY3y0lI29jFD5VAv4E5+z VNIIBQsRtw1DHFhQX+LrEAXMIk+nQsIPCdFtSG7uxQ4fRWgSWlpgNDUd9M6F 8VbpqoDP193OG62hNlC/io4dKKXSbsBbzWh2egY+vwf13XVX1XXodEG7um5p aoMwIYKu0jY0VZdAa9dbvYbWvpRmE1valWYohtZpS0hUTWfmpkHngvBcqd16 E3uUc62lGe8F9QvNaBPFCySpwLXSNbR6r6V04brXve7oaholmugoqBihePLp YVxIbYvSaccCtGmI5mw5LoNXLv7+EnHb8Xcsf/Ia5+8WXzhDz2ZDcHFWMSnN 0FIRB2uMOSG0IsemmqxIaWrjl9KLMvzUZCZa5KeN0+ILNJwzLCKWZKm+iu6i XVqIk53x64Vu7kzYw97IRwk49RMv0O/rRqPe7xeT+nAymA5P05cQ7cnDuxnd DJPH+K4zTLAknRtxJh9vFOcBHQHszbNCfUJpXszMshl95JdPVowGq/r7N2a4 fGxqr5iEA6tnYbWyciDmIq9hYe058MAyF6A2ROk9NC1Gysq6TdsOuU+LeL5f 6InfBQvdrmsJZcfuM+0LB9oKyEN5cLrQHXlmgEY8LaZO53joggxufMcuxlW9 8ORSyEYYgDHkzM8fBBI+IwC4zBvxcbn4pVhYgE28JsY2Fk4LW8RK+sllOTzK AVtuDmzaj8Z+yJP9CAmObKeDPMANS+kRguVBDpUroPOEyqVBAD+D0flVbfeb jW6/pbbL2QRcEiVN7+udXreu9rsYWNRGGWbDfw4vvne1C3q6NJrlnBC7WzmU W6CmBgaMKemqAAy7JghNSIBhHGZuQPnV9IjsNpkVxmaUxzZgGIUxxqB5bTAj qCZGjLAAEhktRsyngWNjHOIcY9UYvYYSw9D5nEclYj/mMMwwt4KHyJ8gG6Jw YJwsifxNXZtyi+17lGBozOP+OCqV85jevXuXe93NnjMjk0ZLie3LbrD9eibw B/kjvHoF8kEZfof5kcpHVGuBrPbvoWuOysVCoUQ+XRbePCxt/C0C+rNPYEPC wUJGlJZbn2oNb1RS9W69xINy+TGYhm4swCRr4bRYYC6m0xW0vxl5AYNZm/sp UKbNZVzeF4tx7Z26ARUN3A8QAisZCDGxU0xI6ujkEwF6zWawmUIHPnaKyg29 hToERUgWXzpTxCAJNvlNNpPSEcaeSSCqoc2Yqdlo/DqPAN/i11ssK+NScBOD KYJuEopkpjedDGLSgzuO5Y9p8SlWi1jTmgGVgqLC3y3mAl36daGUBjcsi0Jp PihR1O4Hn/jYxvGxtBANAxH+4ngYc4TOO95+HT+fpkOJUGIo7l8ZIgvLgl6B fUYDeFlA/MxDFI/Z/dkCyEdNIkk2ZP2YoUo2uBhqF8Lp8kBKcAUeJcp6iULw qJwut0TsVwuRFFAvhdT/P/wuMG6Ta37coGVSGKGzAvKIz/cJJpYu3HwawnQz c9tiAb22gBbXMfrMvlzBrekRyzBCTxlQ/DJ55pEUQGn1sChikSRmo//sYiiz xoxi3TiGvtvEohY3N4jN/USxK/U5TJbz3rgjkHTNpB7HAByYkXDBididCEfF Mtv2b3HfcssgYoICbkJGrj/ArYrAsIsqfULnuSyh2P+aot9RCE72ivEiHWEO oF1ovLVK9ltXSj1diLkIuzyjfXmQ0vKek0tbmQ/dz3Gmo3QiGJA2fOFZMW1c qIJp2j8g28v4zXG3LJEuy6Mz7vJpNKl1EAOtoKTEoTeckC7FOZ4/OQHgvjaM tQ7klwtaKyRrdvtsNQtIK/H+J6CQj0cBcIHns1+cNkuo0/n0J5bAkrUfL3Fc HGDgngONIJaGcIVWq76Nu9wsMr+EMe7j8UH0RkJU8gxU+eKKkxLdSZCmJXxK kw+cIdF4lSPdHPu0hmgPjdNiNkLzNo3jRExQez5b63OLfRaIyzy/7uM5SwSP 6c/CTAmlxSxbjlNsvq6Yy41jrK2jpejKgth9yuRnYhJevoTns5qigPWUOXV5 pqtYR2URx8S0zynsalAKfCfoFlNO4pY2/+ltiqz8oz/IfeeWfv/NbYO++gng U+d/sry/cP5Xkw/k9fff79EePf/LO8WyE8DqiVzJTgBz0A+PCmt7q88A5cMD ST6S41NAwhR37KUHZ0nlRVUjsFGQLOb5KjDZES8Wh2I3OTd/7lytlE1fXXGK w7AHaH+eQ7uimH0c7c9L0M5zO3cA98ewPqWAUcgeU+ADeMearNL4A0o/2pnX 7U+3dKlfmZ/Y0HHZN7j+8VT835Or1cX7H/vy+v7Hd2lz8R//70QDx1u8AJJ5 x7IssDeXBVLQxWsgRye1g9UpoCYhjuQWSP2ipVzqP59tN5rKG7V/UW8brX7z TIako63GtxiSPkO7Uvt08NDX3+t9esPuf1LMTuBVo6l2+22jo2Q4dNVoaW31 vHch+sR396aqNNSuns3uqoauXRrvr9UzEQrTnjdK62yGqFP/VWnghkJXaE8h Jj+fkTau+pdXRuciptI6b/WVlnbZFm900SIVsdHQkOSV0pbPCulFGhl7sObX 4ayQHHHsWNktm5jH+MDDDKkjeea4d869TWbPw3D2OEBfj3GQxYTuk1T719Q9 bI9+jPqXVkM1qTpbCwkJOl5IZ3vDKHvmGWlv6rqzFz8KhvNcBk7GSxBk00In e44yBJG3KGY09cIgY4OOYmbPwxwfdLKTPt8OBA40Su48xYJBMOwnepyY1thm YoYZRgyFG47xZcod5IUcsqUq7QutpaJTZobAgcY1mh77fvrS0s5b9yD+X9eV 63scbDXiQVQcbLtUIMV1pVBt4up/bdWm6OMLP19T0T86o63bn2mzTB+fF38T Gk/Vf7W9Wf13UKlR/Vet1tb7/+/Slt//Oj6ScrcnCOJ/57bWwm0h3ITazuye Fs2bsPjOkLyzwJq4jpO/5jWh7/mrr3YREmzJdaupF7PIbCk+i3URNWHMOJCS W2A5/hIcyIblms6EheIiTvUha8hCTkcpa/E1oKXXwOa4W8nSQ45yvCSHFSmP c1fEkhOahWtiT9wRS11i9UWj8/fiQpDSM5p0vafdgHqnbXS1857R6erz95CE 3y29grTq/hFigXYnuX+EYEZH3D8iREuvIP1X948EWyhWQ9PrLQVr3sYOIBNI GNQ3atsAvam0Wnkx8W9OynMVOVTOWwKVIINSNrSuWjdInOypjjpD5loS6Ndq XaMH9Z2Kkijd91KCVlf/0UMgHCRsDeVKuUTZSk9oBQ1S73XVK+IX9aD3znVD M3qGCpedTkMnVIheV7tvtLqqn0KrowuF9XRVQiKGIsgjFtQWDuPzeU/XhN60 tqF2u71ruv4l7js2O29RMcisgrMbQsedtpAZddTpvie8pA9hAgneNsWugVQq tKaQLnTUXt0Qd/cySKSK+jRywkJbvcQqX23XVRrtEKK3mq6W0WKaTgBaTPmt 8l7I2BPik62Qt/gx57qSsChoF6A03mjEfAKMfqBric/EN9n0Xr2ZaD9ZBbvF 4ov46sfCuVPy2bs2G148EqThEk+PnejAOeIfKh/hJVQ+H1XKs3nZyWB2dFgq xUdXND20hmUxSR5WKmV4/RqOygs8dVEn/SulHjN2kKFGRmhIVy/JRxDkHcgH xeKyk9Ls/DL5FghgWqcPO4fLOmMRbSHiQ5Y+rpwR/ZEZ8VE9oB6W9UZs9GGJ nIjh/rS4rmPXbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3Wbd3W7f+0 /QdYFh4+AFAAAA== --1461733264-1779487855-900186427=:23884-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 21:39:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01553 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 21:39:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01542 for ; Sat, 11 Jul 1998 21:39:01 -0700 (PDT) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by torrentnet.com (8.8.5/8.8.5) with ESMTP id AAA03769; Sun, 12 Jul 1998 00:38:59 -0400 (EDT) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id AAA03097; Sun, 12 Jul 1998 00:38:58 -0400 (EDT) Message-Id: <199807120438.AAA03097@chai.torrentnet.com> To: joelh@gnu.org CC: hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). In-reply-to: Your message of "Sat, 11 Jul 1998 14:26:12 CDT." <199807111926.OAA14413@detlev.UUCP> Date: Sun, 12 Jul 1998 00:38:58 -0400 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> How on earth will issuing a diagnostic break scripts? > > Consider a script that uses output of another script. A > > typical shell script that just does its job normally does not > > chatter away on stderr. > Most scripts that I have seen that rely on output use stdout, not > stderr. Most. Not all. Regression test scripts e.g. would want to capture all output. An expect(1) script may want to try different things depending on the kind of error message it gets. > >> How on earth will issuing a diagnostic make it harder to write > >> scripts? > > Because now you have to filter out (additional) noise. > So, we've now got a script that relies on the stderr of another > script, the latter of which makes symlinks to non-existant files, and > the former of which will break if a line is added. Have I got you > right? Nope! I am arguing on general principles, not about a specific one line warning. Consider: - The same script may behave differently on FreeBSD from other Unix compatible OSes. - In ln -s you can warn and do a reasonable thing. Not so for other commands. For instance the following sort of warning is not very helpful (even if you did not intend to overwrite target). $ cp source target cp: warning: you just overwrote `target' In general, fat fingers at 4AM can cause all sorts of mistakes you can't easily warn against/prevent. - There is nothing to prevent one from removing a symlink target file later (causing the same problem you are trying to warn about) and warning about *that* is not going to be cheap! > >> I'm *not* talking about a prompt a la cp -i. I'm *not* talking about > >> a failure a la trying to symlink over an existing file. I'm talking > >> about a diagnostic. > > Understood. I am just pointing out that *any* deviation from > > existing practice can break things. > > If you want every utility and library call to behave the same forever, > then stay at the same OS revision forever. If you don't want > change... don't change. The issue is to not make a silent change. Principle of Least Astonishment and all that. As a rule one would want to break compatibility with existing practice _only if_ a) there is a *significant* improvement and b) there is *no* other way. > I realize that it is possibly feasable for such a script to exist. Amen! -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 22:58:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11947 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 22:58:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11939; Sat, 11 Jul 1998 22:58:40 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id WAA18710; Sat, 11 Jul 1998 22:58:32 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd018663; Sat Jul 11 22:58:26 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA28581; Sat, 11 Jul 1998 22:58:22 -0700 (MST) From: Terry Lambert Message-Id: <199807120558.WAA28581@usr07.primenet.com> Subject: Re: Still having problems with my driver :( To: lile@stdio.com (Larry S. Lile) Date: Sun, 12 Jul 1998 05:58:22 +0000 (GMT) Cc: hackers@FreeBSD.ORG, tokenring@FreeBSD.ORG, dg@root.com In-Reply-To: from "Larry S. Lile" at Jul 11, 98 03:47:07 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I still cannot get the upper network layers to respond to incoming > packets. I even hacked tcpdump to make sure that I was no wrecking > the packets as I took them off the wire. [ ... ] What about the kernel printf's? > The only messages I got indicating anything at all is wrong were > these when I ifconfig the card up for the first time after a > reboot. > > Jul 10 22:21:33 anarchy routed[69]: ignore RTM_ADD without gateway > Jul 10 22:21:33 anarchy routed[69]: Send bcast sendto(tok0, > 10.0.0.255.520): No buffer space available > Jul 10 22:21:33 anarchy routed[69]: write(rt_sock) RTM_ADD 10.0.0.0/24 > --> 10.0.0.1: File exists > > Any ideas what might be wrong, or could someone please look at my > code and help me figure this out. This happens to me on my ppp link if I start pinging, but turn my modem off (yes, I do bizarre things to see what would happen on border cases) so the link can't come up. Typically, it means that outbound packets haven't been sent, and the output queue has filled up. Have you tested this unidirectionally, ie: from some other system to FreeBSD, or vice versa, where you don't need an echo? This would let you test the input and output seperately. You should also probably put a fprintf in the soft interrupt handler. > I have attached the tcpdump patches if someone would like to commit > them to the source tree, I also sent them to the tcpdump maintainers. > The source for my driver is at http://anarchy.stdio.com. I went looking. I see you put the LLC code in the driver itself? I didn't see where you registered it with the system, or the driver itself, for that matter (ie: no DATA_SET). I couldn't see where you were calling ether_input()??? One thing you might want to consider is seting up the LLC in such a way that you can ifconfig up a loopback interface through the LLC and back for testing the upper layers down and back up. Unfortunately, TR hardware wants a hub. If I were still hanging out at Weber State University, I'd take advantage of their networking lab; as it is, I have no hardware to play with, and no known working other end to talk to in any case. The only thing I can recommend is that you try and divide the problem into smaller pieces (per my suggestions, above). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 11 23:13:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13969 for freebsd-hackers-outgoing; Sat, 11 Jul 1998 23:13:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA13964 for ; Sat, 11 Jul 1998 23:13:50 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id XAA20809 for hackers@freebsd.org; Sat, 11 Jul 1998 23:12:34 -0700 Date: Sat, 11 Jul 1998 23:12:34 -0700 From: Joe McGuckin Message-Id: <199807120612.XAA20809@monk.via.net> To: hackers@FreeBSD.ORG Subject: Changes to login.conf X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After shooting myself in the foot a couple of times, I'd like to propose that the login.conf values cannot be set below values that would render the machine inoperable. It's all too easy to type 20 instead of 20M when setting datasize or stack size. Unfortunately this causes the machine to go into a coma at the next reboot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message