From owner-freebsd-hackers Sun Jan 10 02:04:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26657 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 02:04:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26643; Sun, 10 Jan 1999 02:04:03 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id CAA28628; Sun, 10 Jan 1999 02:02:55 -0800 Date: Sun, 10 Jan 1999 02:02:55 -0800 (PST) From: Neal Westfall To: Mike Smith cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Support for Netgear ethernet cards In-Reply-To: <199901100539.VAA03464@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 And if I recall that particular card is supported by the if_pn.c driver. The older Netgear cards had the DEC chip, which can still be found here and there, but *any* cards using DEC chip are dissappearing rapidly.. -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ On Sat, 9 Jan 1999, Mike Smith wrote: > > Does anyone know if the Netgear series of ethernet cards (PCI, 10/100Mb/s) > > is supported by the current bunch of drivers? I had a look at the > > card and couldn't see any familiar names silk-screened on the chips, > > with main chip having NetGear splattered all over it. > > Yes; as Bill recently posted, we now have support either in the tree or > available as addons from Bill's page (www.freebsd.org/~wpaul) for > prettymuch all of the 100Mbps chipsets. > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 04:17:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14429 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 04:17:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14424 for ; Sun, 10 Jan 1999 04:17:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA51747; Sun, 10 Jan 1999 04:16:48 -0800 (PST) To: "Daniel C. Sobral" cc: Duncan Barclay , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-reply-to: Your message of "Sun, 10 Jan 1999 13:20:50 +0900." <36982AA2.3F0FBE1B@newsguy.com> Date: Sun, 10 Jan 1999 04:16:48 -0800 Message-ID: <51744.915970608@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is being worked on. Well, it would be being worked on if I had > got a single second opinion on how to proceed, but... Really? You're waiting for this? I thought we'd already just agreed on whatever the last round of discussions produced and were waiting to move on. :-) > * Right now, all builtins return 1 if no error happened, 0 > otherwise (btw, Jordan, ANS specifies all bits 1 as the "true" value > :). It is my intention to change this behavior. In fact, I have > already submitted the patches. If I have it my way, errors will use > THROW instead. I can live with all that - we're not tied to the builtin return values being anything specific, they were chosen arbitrarily. > * Right now, you can't set a variable to the name of another > variable. For instance, the default value of prompt is "${currdev}". Looks like Mike just fixed that. > * Right now (yeah, I'm emphasizing it :), EVALUATE doesn't work > according to specs. It will silently ignore the count passed, and Aye! > say, I hope :-), I intend to fix this too. Alas, I haven't submitted > this patch yet. Anyway, if you want to create strings to be Aye! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 06:00:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23230 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 06:00:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23225 for ; Sun, 10 Jan 1999 06:00:49 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id OAA13899; Sun, 10 Jan 1999 14:00:16 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id OAA00892; Sun, 10 Jan 1999 14:01:27 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901101401.OAA00892@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Dru Nelson" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Tunneling GRE through NAT? In-reply-to: Your message of "19 Dec 1998 02:58:37 GMT." <19981219025837.1592.qmail@findmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Jan 1999 14:01:27 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I wrote a patch to natd to allow it pass GRE/ ie > PPTP. Check with the maintainers of natd on the > latest version. So you've mentioned before. Neither Charles or Ari (cc'd) seem to have mentioned it since.... > > I'm writing here because of what I found via the mailing list search at > > www.freebsd.org: > > > > -- > > On Wed, 1 Apr 1998, M.C Wong wrote: > > > > > I wonder if there is any implementation, user-land or kernel, of > > > tunneling protocol based on GRE (rfc1701, rfc1702) ? > > > > I remember some rumblings in -hackers about someone implementing a generic > > tunnelling system. I think a GRE tunnel was part of the inspiration for > > the project. Check the mail archives for info. > > > > Doug White | University of Oregon > > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > -- > > > > Did this go anywhere? > > > > I have a number of Windows users who'd like to be able to access some > > WindowsNT based services using Microsoft's PPTP. > > > > As it stands, the WindowsNT machine is behind a FreeBSD machine running > > natd which is in turn behind a Cisco which acts as a firewall. > > > > I can pass PPTP packets (port 1723) through to the FreeBSD machine and I > > can pass the GRE packets associated with PPTP through to the FreeBSD > > machine. > > > > I can then tunnel the PPTP packets through natd to the NT box, but I > > haven't found any way to tunnel GRE through the NAT. > > > > Did this discussion of tunneling GRE through NAT ever go anywhere? Has > > anyone written any software that does this? Is there any reason why this > > would not be possible? (i.e., any reason why I shouldn't just pick up my > > network programming book and write it myself?) > > > > Any help is much appreciated. > > > > > > James Snow > > > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > * We live in the short term | sno at teardrop dot org * > > * and hope for the best. | I am Geek. Hear me ^G * > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 09:20:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13565 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 09:20:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from galileo.physics.purdue.edu (galileo.physics.purdue.edu [128.210.67.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13560 for ; Sun, 10 Jan 1999 09:20:26 -0800 (PST) (envelope-from csg@physics.purdue.edu) Received: (from csg@localhost) by galileo.physics.purdue.edu (8.9.1/8.8.8) id MAA03447; Sun, 10 Jan 1999 12:19:50 -0500 (EST) Message-ID: <19990110121950.A2810@physics.purdue.edu> Date: Sun, 10 Jan 1999 12:19:50 -0500 From: "C. Stephen Gunn" To: freebsd-hackers@FreeBSD.ORG Cc: Terry Lambert Subject: Re: NFS problems under 3.0-RELEASE References: <199901062142.QAA13257@galileo.physics.purdue.edu> <199901070207.TAA07487@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901070207.TAA07487@usr09.primenet.com>; from Terry Lambert on Thu, Jan 07, 1999 at 02:07:47AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 07, 1999 at 02:07:47AM +0000, Terry Lambert wrote: > Dump from 32 bytes before the problem to 64 bytes after as hex. > > See if the corruption, in fact, contains the ethernet address of one > or both machines. I didn't notice the Ethernet Addresses in there, but they may have slipped by me un-noticed. I also haven't had the time to reproduce the problem since it was the show-stopper for deploying 5 machines in our department. (yes, in the department of physics, you can have the clerical staff run FreeBSD) . If Terry, or someone else wants a look at a kernel dump from this problem, I'll see if I can't get one. - Steve -- C. Stephen Gunn, Computer Systems Engineer Physics Computer Network, Purdue University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 10:05:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19300 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 10:05:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles240.castles.com [208.214.165.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19295 for ; Sun, 10 Jan 1999 10:05:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA07274; Sun, 10 Jan 1999 10:01:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901101801.KAA07274@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: "Daniel C. Sobral" , Duncan Barclay , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-reply-to: Your message of "Sun, 10 Jan 1999 04:16:48 PST." <51744.915970608@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Jan 1999 10:01:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > * Right now, you can't set a variable to the name of another > > variable. For instance, the default value of prompt is "${currdev}". > > Looks like Mike just fixed that. Actually, I forgot both to credit Daniel for the patch and to reference the PR. Oops. -- \\ 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 Jan 10 11:51:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05663 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 11:51:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mtu.ru (ns.mtu.ru [195.34.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05639 for ; Sun, 10 Jan 1999 11:51:06 -0800 (PST) (envelope-from daktaklakpak@mtu-net.ru) Received: from dan (dial57039.mtu-net.ru [195.34.57.39]) by ns.mtu.ru (8.9.1/8.8.8) with SMTP id WAA22192 for ; Sun, 10 Jan 1999 22:54:02 +0300 (MSK) Message-ID: <014201be3cd2$128cd210$0100a8c0@dan.space_net> From: "Dan Shebunin" To: Subject: Re: Problems with IDE CD-ROM under FreeBSD Date: Sun, 10 Jan 1999 22:11:26 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Mark Kobussen To: Dan Shebunin Cc: freebsd-hackers@FreeBSD.ORG ; freebsd-questions@FreeBSD.ORG Date: 9 Jan 1999. 21:36 Subject: Re: Problems with IDE CD-ROM under FreeBSD >I'm just a newbie - so it's a possibility that I could be horrendously >wrong. But to try: > >#mount_cd9660 /dev/wdc1 /cdrom > >Notice the sys message during boot: wdc1. Looks like you're trying to >mount the CD drive on the primary IDE controller. > >There is probably a way to fix it so that it recognizes wdc1 by using >#mount /cdrom, but the only way I can think of is by adding an alias. > >Oh, and don't worry about the unknown phase message. My CD-ROM reports >that at boot-up as well, although I have no problems mounting it using >#mount /cdrom. It's also an IDE drive, except mounted on the primary >EIDE controller as a slave. If I'm not blunder, wdc1 is a secondary IDE controller, but not a drive. Drives have numbers wd0, wd1, e.t.c. And wcd0c is not CD on 1'st IDE, but 1'st CD. Maybe I wrong. Nevertheless, I've tried as you say '/dev/wdc1' and many other combinations of letters 'w' 'c' 'd' and numbers, but it do not work. Worse, sysinstall work fine with wcd0c (it writes wcd0c in info box during copy operations). Have a nice CONNECT! Dan. (daktaklakpak@public.mtu.ru) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 11:51:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05675 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 11:51:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mtu.ru (ns.mtu.ru [195.34.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05644 for ; Sun, 10 Jan 1999 11:51:07 -0800 (PST) (envelope-from daktaklakpak@mtu-net.ru) Received: from dan (dial57039.mtu-net.ru [195.34.57.39]) by ns.mtu.ru (8.9.1/8.8.8) with SMTP id WAA22198 for ; Sun, 10 Jan 1999 22:54:03 +0300 (MSK) Message-ID: <014301be3cd2$13750f30$0100a8c0@dan.space_net> From: "Dan Shebunin" To: Subject: Re: Problems with IDE CD-ROM under FreeBSD Date: Sun, 10 Jan 1999 22:36:30 +0300 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.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Iani Brankov To: Dan Shebunin Cc: freebsd-hackers Date: 10 Jan 1999. 2:23 Subject: Re: Problems with IDE CD-ROM under FreeBSD > >It seems you don't have iso9660 FS in the kernel or as lkm. >check for option "CD9660" in your current kernel configuretion file. > >By the way Mark makes a mistake: wdc != wcd at all. > I have "CD9660" option in kernel config file. Maybe the reason is in my old CD drive. I do not remember, how old it its. (4x, maybe ACER CD-drive) >> >> The worse is SYSINSTALL can mount my CD, and even read packages from it. >> So, why can't I use mount? >> > >If the reason is absence of cdrom fs emulation, yes - it's possible. > >good luck :) > SYSINSTALL uses mount(2) system call. And mount_cd9660 uses the same system call. But one work where other did not. Have a nice CONNECT! Dan. (daktaklakpak@public.mtu.ru) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 12:13:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08580 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 12:13:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.enter.net (mail.enter.net [204.170.70.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08572 for ; Sun, 10 Jan 1999 12:13:53 -0800 (PST) (envelope-from dh@enter.net) Received: from freebsd.athome.net (m40atwn-1-39.enter.net [204.170.16.49]) by mail.enter.net (8.8.8/8.8.8) with ESMTP id PAA08023 for ; Sun, 10 Jan 1999 15:13:19 -0500 (EST) 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 Date: Sun, 10 Jan 1999 15:09:28 -0500 (EST) Reply-To: dh@enter.net From: Daniel Hauer To: hackers@FreeBSD.ORG Subject: X question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Quick question., I'm no "X" expert. When I open an xterm, and then su to root in it to run an app as root, (cvsup for example) I get an "unable to open display localhost:0" error message. What have I missed? System info: Pentium 166 90MB ram ATI graphics card Xfree 3.3.3 2.2.8-RELEASE Windowmaker 0.23 Regards, Daniel Hauer. http://www.enter.net "The Road To The Internet Starts There!" *************************************************************************** Windoze is for GAMES, UNIX is for the rest of us. UNIX is like the sights on a loaded gun. If you aim the gun at your foot and pull the trigger, it is the basic function of UNIX to accurately deliver the bullet from the gun to the target. In this case, it's your foot. *************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 12:20:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09318 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 12:20:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09313 for ; Sun, 10 Jan 1999 12:20:54 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA25195 for freebsd-hackers@freebsd.org; Sun, 10 Jan 1999 14:20:21 -0600 (CST) From: Mohit Aron Message-Id: <199901102020.OAA25195@cs.rice.edu> Subject: Intel performance counters To: freebsd-hackers@FreeBSD.ORG Date: Sun, 10 Jan 1999 14:20:21 -0600 (CST) 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 Hi, can someone please tell me how I can read the performance counters in a Pentium II running FreeBSD-2.2.6. I'm particularly interested in the data and instruction cache misses over periods of time. Thanks, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 12:54:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12148 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 12:54:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12108 for ; Sun, 10 Jan 1999 12:54:10 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id OAA99984; Sun, 10 Jan 1999 14:53:35 -0600 (CST) Date: Sun, 10 Jan 1999 14:53:34 -0600 From: Dan Nelson To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel performance counters Message-ID: <19990110145334.A99814@dan.emsphone.com> References: <199901102020.OAA25195@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901102020.OAA25195@cs.rice.edu>; from "Mohit Aron" on Sun Jan 10 14:20:21 GMT 1999 X-OS: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 10), Mohit Aron said: > Hi, > can someone please tell me how I can read the performance counters > in a Pentium II running FreeBSD-2.2.6. I'm particularly interested in the > data and instruction cache misses over periods of time. Thanks, man perfmon, and go from there. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 13:44:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17430 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 13:43:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17424 for ; Sun, 10 Jan 1999 13:43:24 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id OAA01712; Sun, 10 Jan 1999 14:42:19 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36991EBB.28BEF843@softweyr.com> Date: Sun, 10 Jan 1999 14:42:19 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Shebunin CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with IDE CD-ROM under FreeBSD References: <014301be3cd2$13750f30$0100a8c0@dan.space_net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Shebunin wrote: > > I have "CD9660" option in kernel config file. Maybe the reason is in my old > CD drive. I do not remember, how old it its. (4x, maybe ACER CD-drive) Ugh. ATAPI drives of that era were generally pretty bad. Chuck it and get a new one; they're not that expensive anymore. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 14:32:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23079 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 14:32:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23074 for ; Sun, 10 Jan 1999 14:32:57 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id RAA13486 for ; Sun, 10 Jan 1999 17:32:17 -0500 (EST) Date: Sun, 10 Jan 1999 17:32:17 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Where is _swi_vm defined? 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, can anyone tell me where the routine _swi_vm is defined? It appears in the table of interrupt handler addresses (ihandlers) in file vector.s. Thanks for any help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 15:28:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28507 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 15:28:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28492 for ; Sun, 10 Jan 1999 15:28:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA07514; Mon, 11 Jan 1999 08:28:03 +0900 (JST) Message-ID: <36992A01.1ACB2134@newsguy.com> Date: Mon, 11 Jan 1999 07:30:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: "Jordan K. Hubbard" , Duncan Barclay , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables References: <199901101801.KAA07274@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Actually, I forgot both to credit Daniel for the patch and to reference > the PR. Oops. You'll get other chances, I promise... :-) (Just don't do it as a way to make me keep submitting patches! :) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 15:32:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28501 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 15:28:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28489 for ; Sun, 10 Jan 1999 15:28:48 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA07504; Mon, 11 Jan 1999 08:27:59 +0900 (JST) Message-ID: <369929B0.7ACC2DED@newsguy.com> Date: Mon, 11 Jan 1999 07:29:04 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Duncan Barclay , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables References: <51744.915970608@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > This is being worked on. Well, it would be being worked on if I had > > got a single second opinion on how to proceed, but... > > Really? You're waiting for this? I thought we'd already just agreed > on whatever the last round of discussions produced and were waiting to > move on. :-) Really. :-) I proposed an unified flag registering macro, like the one been used to register the builtins, so that such flags can be allocated numbers instead of passed as strings at compile-time use of builtins. I'm not even sure myself if I still want to do this. Presently (as you know, of course), all builtins are called just passing it's parameter string, and they do their own parameter processing. If you want a new builtin, you can simply plug in another C file. My change would end up in a big switch() for a parameter processing for all builtins, which would have to be changed for each new builtin written (unless a sensible "default:" is used). Using numeric parameters where possible in ficl seems a great improvement imho, but I don't know if the change required wouldn't offset the gains. That's why I really want to hear the opinion of at least one more person. > > * Right now, all builtins return 1 if no error happened, 0 > > otherwise (btw, Jordan, ANS specifies all bits 1 as the "true" value > > :). It is my intention to change this behavior. In fact, I have > > already submitted the patches. If I have it my way, errors will use > > THROW instead. > > I can live with all that - we're not tied to the builtin return values > being anything specific, they were chosen arbitrarily. Well, kern/9412, if you want. :-) > > > * Right now, you can't set a variable to the name of another > > variable. For instance, the default value of prompt is "${currdev}". > > Looks like Mike just fixed that. Yup. So he did. (Do I need to mention I do have other PRs open concerning the loader? kern/9371, misc/9373 (these two go together), kern/9398 (this one requires making a choice, I realize), and kern/9406 (well, this one can easily go ages ignored :), just in case you were waiting for the numbers :). > > * Right now (yeah, I'm emphasizing it :), EVALUATE doesn't work > > according to specs. It will silently ignore the count passed, and > > say, I hope :-), I intend to fix this too. Alas, I haven't submitted > > this patch yet. Anyway, if you want to create strings to be > > Aye! :) Yeah, this one won't live another night. At least in *my* tree. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 16:06:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04766 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 16:06:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04417 for ; Sun, 10 Jan 1999 16:06:25 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA10230; Mon, 11 Jan 1999 10:35:24 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA18433; Mon, 11 Jan 1999 10:35:24 +1030 (CST) Date: Mon, 11 Jan 1999 10:35:24 +1030 From: Greg Lehey To: zhihuizhang Cc: hackers Subject: Re: Where is _swi_vm defined? Message-ID: <19990111103524.B8886@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from zhihuizhang on Sun, Jan 10, 1999 at 05:32:17PM -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 Sunday, 10 January 1999 at 17:32:17 -0500, zhihuizhang wrote: > > Hi, can anyone tell me where the routine _swi_vm is defined? It appears > in the table of interrupt handler addresses (ihandlers) in file vector.s. /usr/src/sys/i386/i386/vm_machdep.c, about line 654. Use ctags or etags to find things like this. Greg -- See complete headers for address, home page 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 Jan 10 16:18:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05593 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 16:18:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (support [140.186.40.192] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05585 for ; Sun, 10 Jan 1999 16:18:32 -0800 (PST) (envelope-from kaleb@ics.com) Received: from kaleb.keithley.belmont.ma.us (support [140.186.40.192]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with SMTP id TAA15728; Sun, 10 Jan 1999 19:17:50 -0500 (EST) Message-ID: <3699577A.2D857063@ics.com> Date: Sun, 10 Jan 1999 20:44:26 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: dh@enter.net CC: hackers@FreeBSD.ORG Subject: Re: X question 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 Hauer wrote: > > Hi, > Quick question., I'm no "X" expert. When I open an xterm, and then su to > root in it to run an app as root, (cvsup for example) I get an "unable to open > display localhost:0" error message. What have I missed? Rather off-topic for FreeBSD-hackers--- Did you log in through xdm? If so, the server only knows the xdm-auth credentials for you. When you su to root, Xlib looks in root's ~root/.Xauthority file to find credentials and one of three things happens: 1) there's no ~root/.Xauthority at all, 2) there is a ~root/.Xauthority but there isn't no credential for your $DISPLAY, or 3) there is a ~root/.Xauthority file, and there is a credential for your $DISPLAY, but it isn't valid. The way around this is: as you: %xauth list ... my.host:0 MIT-MAGIC-COOKIE-1 a823117ea138ef897e39ced196d9cb03 my.host/unix:0 MIT-MAGIC-COOKIE-1 a823117ea138ef897e39ced196d9cb03 ... as root: %xauth add my.host:0 MIT-MAGIC-COOKIE-1 a823117ea138ef897e39ced196d9cb0 %xaut add my.host/unix:0 MIT-MAGIC-COOKIE-1 a823117ea138ef897e39ced196d9cb03 If there are XDM-AUTHORIZATION-1 credentials copy those as well. Now root will be able to run X programs in your session. Once you log out and log back in you'll get new credentials and you'll need to repeat the above steps again. -- Kaleb S. KEITHLEY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 20:24:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29079 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 20:24:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29074 for ; Sun, 10 Jan 1999 20:24:31 -0800 (PST) (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 XAA12630; Sun, 10 Jan 1999 23:23:36 -0500 (EST) Date: Sun, 10 Jan 1999 23:23:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Dag-Erling Smorgrav cc: hackers@FreeBSD.ORG Subject: Re: proposed mod to ps(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 7 Jan 1999, Dag-Erling Smorgrav wrote: > Wouldn't it make sense to add an option to ps(1) to display the login > class of each process? I was under the impression that 'login class' was really a property of the class database in userland, and that the kernel didn't know what class you were in, just the current process properties (resource limits, etc). Programs such as 'login' set their resource limitations based on these class entries. As such, ps would not know the 'class' on a per-process basis. On the other hand, modifying ps to display current resource limits (possibly with authorization checking?) would be *extremely* useful for debugging problems on large server machines :). Instead of having processes fail to start because for some reason or another they end up with the wrong resource limits (such as sshd not correctly setting the class) I could ps and see which processes end up with which properties. It might be something to add to procfs as a 'limits' entry containing formatted limit data that could be interpretted as appropriate. It's not clear whether the ability to modify limits for other processes is desirable, and if so, whether procfs is an appropriate venue for this behavior (it certainly would be cool :). If it were, the permissions on the file could be used to restrict who could do it in a general way--presumably existing restrictions on soft/hard limits, etc, would be observed (normal uid's could lower hard, and bump soft up to hard or not; root could modify hard and soft limits). This might be beyond the scope of procfs, or just plain undesirable. Either way, having the data readable there with appropriate permissions would be useful for debugging a variety of resource-related problems, and probably clarify the behavior of resource limits for a lot of people. Also, it would make it far easier to track down setuid programs that do not correctly impose limits when switching to a uid for a login-style session. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 22:23:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13573 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 22:23:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13556 for ; Sun, 10 Jan 1999 22:23:16 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id AAA00358 for freebsd-hackers@freebsd.org; Mon, 11 Jan 1999 00:22:43 -0600 (CST) From: Mohit Aron Message-Id: <199901110622.AAA00358@cs.rice.edu> Subject: TCP bug report for FreeBSD-2.2.6 To: freebsd-hackers@FreeBSD.ORG Date: Mon, 11 Jan 1999 00:22:43 -0600 (CST) 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 Hi, I'm using FreeBSD-2.2.6. I've discovered that the TCP implementation has a nasty bug that can cause problems in general for any TCP connection with respect to the end and receive buffer sizes used by a connection. The latter are important for fully utilizing the bandwidth (long fat pipes). I'll outline the problem below. RFC 1323 mandates that TCP only exchange the window scale option with the initial SYN segment. So to use larger windows for the length of the connection, the application needs to increase the send and receive buffer sizes using setsockopt() system call BEFORE the connection is established. This holds for both the client as well as the server. As soon as the connection gets established, the tcp_mss() function gets called that resets the send and receive buffer sizes by copying them over from the routing entry. Assuming that the routing entry already exists for the peer, and it contains the value of send and receive buffer sizes used by some other application earlier, then TCP would still (wrongly) reset the send and receive buffer sizes for the connection. To fix the above problem at the application level, setsockopt() needs to be called again AFTER the connection gets established. So in general, to use large windows in FreeBSD, the send and receive buffer sizes need to be set both before and after the connection establishment. Can this be fixed in future releases ? I do not know whether the problem exists in other BSD stacks. Can someone verify the existence of the problem in other stacks ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 23:01:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17241 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 23:01:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles351.castles.com [208.214.167.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17232 for ; Sun, 10 Jan 1999 23:01:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA87130; Sun, 10 Jan 1999 22:57:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901110657.WAA87130@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: "Jordan K. Hubbard" , Duncan Barclay , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-reply-to: Your message of "Mon, 11 Jan 1999 07:29:04 +0900." <369929B0.7ACC2DED@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Jan 1999 22:57:39 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > * Right now, all builtins return 1 if no error happened, 0 > > > otherwise (btw, Jordan, ANS specifies all bits 1 as the "true" value > > > :). It is my intention to change this behavior. In fact, I have > > > already submitted the patches. If I have it my way, errors will use > > > THROW instead. > > > > I can live with all that - we're not tied to the builtin return values > > being anything specific, they were chosen arbitrarily. > > Well, kern/9412, if you want. :-) This is something I think that you Forthies need to sort out; I'm happy with however you chose to bind Forth and C together, just as long as you pick a method and get to it. > Yup. So he did. (Do I need to mention I do have other PRs open > concerning the loader? kern/9371, misc/9373 (these two go together), > kern/9398 (this one requires making a choice, I realize), and > kern/9406 (well, this one can easily go ages ignored :), just in > case you were waiting for the numbers :). I'm not sure about the whole softwords/help text munging thing. Using Perl scripts is bad for various reasons, but I'm not sure that I want to go to having committed generated files (like the kernel uses) or the other way to compiled special-purpose tools. Anyone handy with awk want to try fixing these - both would probably succumb to the awesome power of awk. The other three are down, thanks. > > > * Right now (yeah, I'm emphasizing it :), EVALUATE doesn't work > > > according to specs. It will silently ignore the count passed, and > > > say, I hope :-), I intend to fix this too. Alas, I haven't submitted > > > this patch yet. Anyway, if you want to create strings to be > > > > Aye! :) > > Yeah, this one won't live another night. At least in *my* tree. :-) Remember to mail me the PR number. -- \\ 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 Jan 10 23:31:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21273 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 23:31:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21262 for ; Sun, 10 Jan 1999 23:31:45 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id IAA08140; Mon, 11 Jan 1999 08:36:55 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 11 Jan 1999 08:36:55 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Watson cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: proposed mod to ps(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 Sun, 10 Jan 1999, Robert Watson wrote: > On 7 Jan 1999, Dag-Erling Smorgrav wrote: > > > Wouldn't it make sense to add an option to ps(1) to display the login > > class of each process? > > I was under the impression that 'login class' was really a property of the > class database in userland, and that the kernel didn't know what class you > were in, just the current process properties (resource limits, etc). > Programs such as 'login' set their resource limitations based on these > class entries. As such, ps would not know the 'class' on a per-process while on the subject... Does any of you know how login time limits are enforced? I couldn't find any place where it is done, and the real-life evidence seems to support my view that currently they are being just ignored... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 10 23:36:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21743 for freebsd-hackers-outgoing; Sun, 10 Jan 1999 23:34:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21695 for ; Sun, 10 Jan 1999 23:34:00 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id BAA15813; Mon, 11 Jan 1999 01:33:00 -0600 (CST) From: Kevin Day Message-Id: <199901110733.BAA15813@home.dragondata.com> Subject: Re: proposed mod to ps(1) In-Reply-To: from Andrzej Bialecki at "Jan 11, 1999 8:36:55 am" To: abial@nask.pl (Andrzej Bialecki) Date: Mon, 11 Jan 1999 01:33:00 -0600 (CST) Cc: robert+freebsd@cyrus.watson.org, des@flood.ping.uio.no, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 10 Jan 1999, Robert Watson wrote: > > > On 7 Jan 1999, Dag-Erling Smorgrav wrote: > > > > > Wouldn't it make sense to add an option to ps(1) to display the login > > > class of each process? > > > > I was under the impression that 'login class' was really a property of the > > class database in userland, and that the kernel didn't know what class you > > were in, just the current process properties (resource limits, etc). > > Programs such as 'login' set their resource limitations based on these > > class entries. As such, ps would not know the 'class' on a per-process > > while on the subject... Does any of you know how login time limits are > enforced? I couldn't find any place where it is done, and the real-life > evidence seems to support my view that currently they are being just > ignored... > AFAIK, the only way to enforce login time limits is through idled, which is in ports. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 00:06:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26295 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 00:06:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26288 for ; Mon, 11 Jan 1999 00:06:38 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id VAA13259; Mon, 11 Jan 1999 21:06:02 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id VAA29499; Mon, 11 Jan 1999 21:05:58 +1300 (NZDT) (envelope-from jabley) Date: Mon, 11 Jan 1999 21:05:58 +1300 From: Joe Abley To: Mike Smith Cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , Duncan Barclay , freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990111210558.A29444@clear.co.nz> References: <369929B0.7ACC2DED@newsguy.com> <199901110657.WAA87130@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901110657.WAA87130@dingo.cdrom.com>; from Mike Smith on Sun, Jan 10, 1999 at 10:57:39PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 10, 1999 at 10:57:39PM -0800, Mike Smith wrote: > > > Yup. So he did. (Do I need to mention I do have other PRs open > > concerning the loader? kern/9371, misc/9373 (these two go together), > > kern/9398 (this one requires making a choice, I realize), and > > kern/9406 (well, this one can easily go ages ignored :), just in > > case you were waiting for the numbers :). > > I'm not sure about the whole softwords/help text munging thing. Using > Perl scripts is bad for various reasons, but I'm not sure that I want > to go to having committed generated files (like the kernel uses) or the > other way to compiled special-purpose tools. Anyone handy with awk > want to try fixing these - both would probably succumb to the awesome > power of awk. Eh? If someone needs some awk writing, and can describe clearly what needs doing, I'll do it. Mmm. Awk :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 00:44:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01566 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 00:44:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01413 for ; Mon, 11 Jan 1999 00:44:07 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id JAA19448; Mon, 11 Jan 1999 09:47:57 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 11 Jan 1999 09:47:56 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Kevin Day cc: robert+freebsd@cyrus.watson.org, des@flood.ping.uio.no, hackers@FreeBSD.ORG Subject: Re: proposed mod to ps(1) In-Reply-To: <199901110733.BAA15813@home.dragondata.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, 11 Jan 1999, Kevin Day wrote: > > while on the subject... Does any of you know how login time limits are > > enforced? I couldn't find any place where it is done, and the real-life > > evidence seems to support my view that currently they are being just > > ignored... > > > > AFAIK, the only way to enforce login time limits is through idled, which is > in ports. But then we should mark in the man page that these capabilities are not implemented... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 02:21:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11456 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 02:21:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11419 for ; Mon, 11 Jan 1999 02:20:49 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id TAA24683; Mon, 11 Jan 1999 19:20:07 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98122515) with ESMTP id TAA13847; Mon, 11 Jan 1999 19:20:06 +0900 (JST) Message-Id: <199901111020.TAA13847@hotaka.csl.sony.co.jp> To: Mohit Aron cc: freebsd-hackers@FreeBSD.ORG Subject: Re: TCP bug report for FreeBSD-2.2.6 In-reply-to: Your message of "Mon, 11 Jan 1999 00:22:43 CST." <199901110622.AAA00358@cs.rice.edu> Date: Mon, 11 Jan 1999 19:20:06 +0900 From: Kenjiro Cho Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mohit Aron said: >> I'm using FreeBSD-2.2.6. I've discovered that the TCP implementation has a >> nasty bug that can cause problems in general for any TCP connection with >> respect to the end and receive buffer sizes used by a connection. The latter >> are important for fully utilizing the bandwidth (long fat pipes). I'll outline >> the problem below. This is a well-known problem since 2.1. It was fixed in -current long time ago but the fix didn't go into -stable. I've been using the following patch to enable SO_SNDBUF/SO_RCVBUF. As a side-effect, it disables copying the pipesize in the route. --Kenjiro -------------------------------------------------------------------------- diff -urN ../sys/netinet/in_rmx.c ./netinet/in_rmx.c --- ../sys/netinet/in_rmx.c Fri Jun 21 00:41:23 1996 +++ ./netinet/in_rmx.c Tue Dec 8 18:59:00 1998 @@ -130,11 +130,13 @@ * as it sees fit. This will hopefully allow TCP more * opportunities to save its ssthresh value. */ +#if 0 /* commented out for the tcp window problem --kjc */ if (!rt->rt_rmx.rmx_sendpipe && !(rt->rt_rmx.rmx_locks & RTV_SPIPE)) rt->rt_rmx.rmx_sendpipe = tcp_sendspace; if (!rt->rt_rmx.rmx_recvpipe && !(rt->rt_rmx.rmx_locks & RTV_RPIPE)) rt->rt_rmx.rmx_recvpipe = tcp_recvspace; +#endif if (!rt->rt_rmx.rmx_mtu && !(rt->rt_rmx.rmx_locks & RTV_MTU) && rt->rt_ifp) -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 02:27:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11925 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 02:27:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles351.castles.com [208.214.167.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11920 for ; Mon, 11 Jan 1999 02:27:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id CAA88602; Mon, 11 Jan 1999 02:23:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901111023.CAA88602@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joe Abley cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-reply-to: Your message of "Mon, 11 Jan 1999 21:05:58 +1300." <19990111210558.A29444@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Jan 1999 02:23:45 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I'm not sure about the whole softwords/help text munging thing. Using > > Perl scripts is bad for various reasons, but I'm not sure that I want > > to go to having committed generated files (like the kernel uses) or the > > other way to compiled special-purpose tools. Anyone handy with awk > > want to try fixing these - both would probably succumb to the awesome > > power of awk. > > Eh? > > If someone needs some awk writing, and can describe clearly what needs > doing, I'll do it. There are two separate tasks, each with their own interesting requirements. The easiest way to understand them is probably to look at what the current perl scripts are doing. The first transforms the Forth softwords files into a large string array, stripping all the unnecessary bits; that's /sys/boot/ficl/softwords/softcore.pl. Run it as per the Makefile to see the output it produces; inferring the rules from that should be pretty straightforward. The second task is to construct a unified, sorted helpfile from two input files. The helpfiles consist of records delimited thus: ##... # T [S] D ...data # The records from each of the two files need to be sorted into topic order, with every subtopic record sorted in following its topic record, eg. Tfoo Tfoo Sbar Tfoo Sbaz Tfish ... The input files are /sys/boot/common/help.common and /sys/boot/i386/loader/i386.help (i386) or /sys/boot/alpha/boot2/alpha.help (alpha). I can help more with syntax, examples etc. if you're interested. -- \\ 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 Jan 11 02:32:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12412 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 02:32:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA12399 for ; Mon, 11 Jan 1999 02:32:51 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA19799; Mon, 11 Jan 1999 09:19:08 +0100 From: Luigi Rizzo Message-Id: <199901110819.JAA19799@labinfo.iet.unipi.it> Subject: Re: TCP bug report for FreeBSD-2.2.6 To: kjc@csl.sony.co.jp (Kenjiro Cho) Date: Mon, 11 Jan 1999 09:19:07 +0100 (MET) Cc: aron@cs.rice.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199901111020.TAA13847@hotaka.csl.sony.co.jp> from "Kenjiro Cho" at Jan 11, 99 07:19:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mohit Aron said: > >> I'm using FreeBSD-2.2.6. I've discovered that the TCP implementation has a > >> nasty bug that can cause problems in general for any TCP connection with > >> respect to the end and receive buffer sizes used by a connection. The latter > >> are important for fully utilizing the bandwidth (long fat pipes). I'll outline > >> the problem below. > > This is a well-known problem since 2.1. It was fixed in -current long > time ago but the fix didn't go into -stable. > I've been using the following patch to enable SO_SNDBUF/SO_RCVBUF. As > a side-effect, it disables copying the pipesize in the route. how about putting this in RELENG_2_2 ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 03:08:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16318 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 03:08:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16310 for ; Mon, 11 Jan 1999 03:08:32 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id UAA24977; Mon, 11 Jan 1999 20:07:41 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98122515) with ESMTP id UAA16256; Mon, 11 Jan 1999 20:07:40 +0900 (JST) Message-Id: <199901111107.UAA16256@hotaka.csl.sony.co.jp> To: Luigi Rizzo cc: aron@cs.rice.edu, freebsd-hackers@FreeBSD.ORG, wollman@lcs.mit.edu Subject: Re: TCP bug report for FreeBSD-2.2.6 In-reply-to: Your message of "Mon, 11 Jan 1999 09:19:07 +0100." <199901110819.JAA19799@labinfo.iet.unipi.it> Date: Mon, 11 Jan 1999 20:07:39 +0900 From: Kenjiro Cho Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo said: > This is a well-known problem since 2.1. It was fixed in -current long > time ago but the fix didn't go into -stable. > I've been using the following patch to enable SO_SNDBUF/SO_RCVBUF. As > a side-effect, it disables copying the pipesize in the route. >> how about putting this in RELENG_2_2 ? Garrett brought in_rmx.c into FreeBSD and also fixed that problem. He also made some modification to tcp_subr.c when he made the fix. So, I guess it's up to Garrett. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 04:12:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24373 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 04:12:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24368 for ; Mon, 11 Jan 1999 04:12:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA10941; Mon, 11 Jan 1999 21:11:39 +0900 (JST) Message-ID: <3699DED5.A622C57E@newsguy.com> Date: Mon, 11 Jan 1999 20:21:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Joe Abley CC: freebsd-hackers@FreeBSD.ORG, Mike Smith Subject: Re: FICL and setting BTX variables References: <369929B0.7ACC2DED@newsguy.com> <199901110657.WAA87130@dingo.cdrom.com> <19990111210558.A29444@clear.co.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > > > I'm not sure about the whole softwords/help text munging thing. Using > > Perl scripts is bad for various reasons, but I'm not sure that I want > > to go to having committed generated files (like the kernel uses) or the > > other way to compiled special-purpose tools. Anyone handy with awk > > want to try fixing these - both would probably succumb to the awesome > > power of awk. > > Eh? > > If someone needs some awk writing, and can describe clearly what needs > doing, I'll do it. Roger. I thought the problem could be easily solved by awk, but I do not qualify as "handy with awk" by any standards. :-) I don't know what are the perl scripts making the help file, so I'll describe just the script I converted. It is /sys/boot/ficl/softwords/softcore.pl. It basic function is dealing with assorted variations of this basic regexp pattern: ".*\\ .*" (the \\ is an escaped backslash, not two of them). We process three variations of this pattern. 1) If the pattern is "^\\ \*\*" (^ meaning it is at the beginning of the line), translate the bugger into a C comment. The translation should spam multiple lines and look like this: \ ** This is \ ** an example \ ** of this pattern becomes /* This is * an example * of this pattern */ 2) If the pattern is "^\\ #", you just cut out "\\ ". Example: \ #ifdef LOCAL_WORDSET becomes #ifdef LOCAL_WORDSET 3) If the pattern is "^\\ .*" or " \\ .*", then cut it out. Example: : definition \ This is a comment becomes : definition All these patterns apply to everything up to the end of the line. Empty lines and lines that become empty after the rule number 3 was applied must be ignored. Aside from that, cut trailing spaces if the line has more than one. You can run the perl script in /sys/boot/ficl/softwords against the .fr files in that directory, to compare your results against the original program. But, mind you, we'll be asking you to remove the following pattern later: " ( [^)]*)" (not to the end of the line). (This has been asked, and ought to work, but I'd prefer having a perfect translation of the perl script in the repository first.) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 04:18:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25229 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 04:18:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA25222 for ; Mon, 11 Jan 1999 04:18:53 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 20483 invoked by uid 1001); 11 Jan 1999 12:18:06 -0000 To: daktaklakpak@mtu-net.ru (Dan Shebunin) Cc: hackers@FreeBSD.ORG Subject: Re: Problems with IDE CD-ROM under FreeBSD References: <014301be3cd2$13750f30$0100a8c0@dan.space_net> From: Ville-Pertti Keinonen Date: 11 Jan 1999 14:17:20 +0200 In-Reply-To: daktaklakpak@mtu-net.ru's message of "10 Jan 1999 21:51:22 +0200" Message-ID: <86g19i80mm.fsf@not.oeno.com> Lines: 11 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG daktaklakpak@mtu-net.ru (Dan Shebunin) writes: > I have "CD9660" option in kernel config file. Maybe the reason is in my old > CD drive. I do not remember, how old it its. (4x, maybe ACER CD-drive) I had a similar problem (with an ACER 747, IIRC), the multi-session support code in the old ATAPI driver decided it wanted to mount the partition at a strange offset. Using "-s 0" as a mount option helped (although I didn't discover this until after creating a modified cd9660 lkm). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 04:57:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29376 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 04:57:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29370 for ; Mon, 11 Jan 1999 04:57:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA15998; Mon, 11 Jan 1999 21:56:30 +0900 (JST) Message-ID: <3699F402.565DB9B9@newsguy.com> Date: Mon, 11 Jan 1999 21:52:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: Joe Abley , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables References: <199901111023.CAA88602@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > There are two separate tasks, each with their own interesting > requirements. The easiest way to understand them is probably to look > at what the current perl scripts are doing. The first transforms the > Forth softwords files into a large string array, stripping all the > unnecessary bits; that's /sys/boot/ficl/softwords/softcore.pl. Yeah, I forgot two bits. The perl script also does cat < > Run it as per the Makefile to see the output it produces; inferring the > rules from that should be pretty straightforward. Actually, reading the perl script should also be quite straightforward. It is commented, and one of the cleanests perl scripts I ever saw. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 05:16:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01265 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 05:16:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from magc.cd.2573.savbank.ru (h26.216.elnet.msk.ru [194.190.216.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01254 for ; Mon, 11 Jan 1999 05:16:05 -0800 (PST) (envelope-from mag@h26.216.elnet.msk.ru) From: mag@h26.216.elnet.msk.ru Received: (from mag@localhost) by magc.cd.2573.savbank.ru (8.8.5/8.8.5) id QAA04638; Mon, 11 Jan 1999 16:18:34 +0300 Date: Mon, 11 Jan 1999 16:18:34 +0300 Message-Id: <199901111318.QAA04638@magc.cd.2573.savbank.ru> To: hackers@FreeBSD.ORG, mag@h26.216.elnet.msk.ru, xbugs@x.org Subject: Xlib: faulty cyrillic keymap in xterm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG VERSION: R6.3, public-patch-3 (X11R6_333) Intel/FreeBSD 2.2.8 DISPLAY TYPE: S3 Trio64V2 WINDOW MANAGER: twm COMPILER: gcc 2.7.2.1 AREA: Xlib SYNOPSIS: faulty cyrillic keymap in xterm DESCRIPTION: I have built XFree86, contrib and russian fonts from ports: $ cd /usr/ports/x11 $ cd XFree86 $ make # making with VGA16, S3 (default), without Kerberos, # with everything else $ make install $ cd ../XFree86-contrib $ make; make install $ cd /usr/ports/russian/X.language $ make; make install # see REPEAT BY for problem description REPEAT BY: simple test: ># partial contents of /etc/XF86Config >... >Section "ServerFlags" > DontZap >EndSection >Section "Keyboard" > Protocol "Standard" > XkbRules "xfree86" > XkbModel "pc104" > XkbLayout "ru" > XkbOptions "grp:toggle" > AutoRepeat 250 30 >EndSection >Section "Pointer" > Protocol "PS/2" > Device "/dev/psm0" > Emulate3Timeout 50 > Emulate3Buttons >EndSection >Section "Monitor" > Identifier "Primary Monitor" > VendorName "Unknown" > ModelName "Unknown" > HorizSync 31.5-48.5 > VertRefresh 55-90 > Modeline "1024x768" 65.00 1024 1040 1184 1340 768 771 777 802 -hsync -vsync > Modeline "800x600" 50.00 800 804 924 1060 600 601 607 638 +hsync +vsync > Modeline "640x480" 36.00 640 680 736 792 480 481 484 517 -hsync -vsync > Modeline "640x400" 31.50 640 648 712 808 400 405 408 437 -hsync +vsync >EndSection >Section "Device" > Identifier "Primary Card" > VendorName "Unknown" > BoardName "None" >EndSection >Section "Screen" > Driver "Accel" > Device "Primary Card" > Monitor "Primary Monitor" > SubSection "Display" > Depth 8 > Modes "1024x768" "800x600" "640x480" "640x400" > EndSubSection > SubSection "Display" > Depth 16 > Modes "1024x768" "800x600" "640x480" "640x400" > EndSubSection > SubSection "Display" > Depth 24 > Modes "800x600" "640x480" "640x400" > EndSubSection > SubSection "Display" > Depth 32 > Modes "800x600" "640x480" "640x400" > EndSubSection >EndSection ># -- $ startx # press in xterm window # if you press in xterm window you see # <<>> (it is wrong) # but not <<>> SAMPLE FIX: replacing libX11.so.6.1 from X11R6_332 (with patches 1, 2 and 3) fixes described problem :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 05:43:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04240 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 05:43:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04235 for ; Mon, 11 Jan 1999 05:43:16 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.37]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id SAA18015; Mon, 11 Jan 1999 18:41:30 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <3699FF89.C4E389DC@urc.ac.ru> Date: Mon, 11 Jan 1999 18:41:29 +0500 From: Konstantin Chuguev Organization: Southern Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: mag@h26.216.elnet.msk.ru CC: hackers@FreeBSD.ORG, xbugs@x.org Subject: Re: Xlib: faulty cyrillic keymap in xterm References: <199901111318.QAA04638@magc.cd.2573.savbank.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mag@h26.216.elnet.msk.ru wrote: > > VERSION: R6.3, public-patch-3 (X11R6_333) > Intel/FreeBSD 2.2.8 > DISPLAY TYPE: S3 Trio64V2 > WINDOW MANAGER: twm > COMPILER: gcc 2.7.2.1 > AREA: Xlib > SYNOPSIS: faulty cyrillic keymap in xterm > DESCRIPTION: I have built XFree86, contrib and russian fonts from ports: > $ cd /usr/ports/x11 ... skipped > REPEAT BY: simple test: > > ># partial contents of /etc/XF86Config > >... > >Section "ServerFlags" > > DontZap > >EndSection > >Section "Keyboard" > > Protocol "Standard" > > XkbRules "xfree86" > > XkbModel "pc104" > > XkbLayout "ru" > > XkbOptions "grp:toggle" > > AutoRepeat 250 30 > >EndSection ... skipped > > SAMPLE FIX: replacing libX11.so.6.1 from X11R6_332 (with patches 1, 2 and 3) > fixes described problem :-( > I use 3.3.3 with XkbLayout "ru" and XkbOptions "grp:toggle" during several weeks on two different machines (PC and notebook), xterm and all other applications work fine. The only difference is that I have XkbModel "pc101". I think the problem is caused by wrong xkb scheme (though I never tried "pc104" myself), not by libX11. Could you try "pc101" just to test? IMO, the best tool for testing keyboard mappings is xev (from XFree86-contrib). You just have to localize it: insert #include in the header section and setlocale(LC_ALL, ""); somewhere before initializing X application in main(), then recompile it. Unfortunately, I have this patch only at home, now I am off. -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 05:51:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05371 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 05:51:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05184 for ; Mon, 11 Jan 1999 05:51:15 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id AAA12714; Tue, 12 Jan 1999 00:27:10 +1100 (EST) Message-ID: <19990112002710.N10679@rf900.physics.usyd.edu.au> Date: Tue, 12 Jan 1999 00:27:10 +1100 From: David Dawes To: mag@h26.216.elnet.msk.ru, hackers@FreeBSD.ORG Subject: Re: Xlib: faulty cyrillic keymap in xterm References: <199901111318.QAA04638@magc.cd.2573.savbank.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901111318.QAA04638@magc.cd.2573.savbank.ru>; from mag@h26.216.elnet.msk.ru on Mon, Jan 11, 1999 at 04:18:34PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 11, 1999 at 04:18:34PM +0300, mag@h26.216.elnet.msk.ru wrote: > VERSION: R6.3, public-patch-3 (X11R6_333) > Intel/FreeBSD 2.2.8 > DISPLAY TYPE: S3 Trio64V2 > WINDOW MANAGER: twm > COMPILER: gcc 2.7.2.1 > AREA: Xlib > SYNOPSIS: faulty cyrillic keymap in xterm This should be fixed in XFree86 3.3.3.1, which is now available. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 06:59:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12618 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 06:59:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12612 for ; Mon, 11 Jan 1999 06:59:58 -0800 (PST) (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 JAA15004; Mon, 11 Jan 1999 09:59:06 -0500 (EST) Date: Mon, 11 Jan 1999 09:59:05 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Andrzej Bialecki cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: proposed mod to ps(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 Mon, 11 Jan 1999, Andrzej Bialecki wrote: > On Sun, 10 Jan 1999, Robert Watson wrote: > > > On 7 Jan 1999, Dag-Erling Smorgrav wrote: > > > > > Wouldn't it make sense to add an option to ps(1) to display the login > > > class of each process? > > > > I was under the impression that 'login class' was really a property of the > > class database in userland, and that the kernel didn't know what class you > > were in, just the current process properties (resource limits, etc). > > Programs such as 'login' set their resource limitations based on these > > class entries. As such, ps would not know the 'class' on a per-process > > while on the subject... Does any of you know how login time limits are > enforced? I couldn't find any place where it is done, and the real-life > evidence seems to support my view that currently they are being just > ignored... I don't believe they are. As someone points out, idled is one way to implement them. Presumably also the time of day/etc limits would be appropriate for implementation via a PAM authorization module to catch people at login. (and a bunch of the other weird stuff like advance warning for password expiry, etc). login classes have always seemed to me to be a kitchen sink for strange information :-) The implementation of various features have always seemed a little questionable to me. The names of the fields (having to do with 'login') are accurate but potentially misleading for newer users of UNIX who might not understand the distinction between being able to 'login' and being able to run a process. There exist many ways to run a process under UNIX without actually being logged in, and I am uncertain as to how many of them even inflict resource limits, let alone determine if there is some way to authorize the uid to run a process. For example, cron, .forward in sendmail, at (when enabled), CGI programs if web access is not adequately disabled, etc. An administrator should not feel confident (currently) that if they put the user in a class with no login capabilities and no CPU time allowed that the user will be unable to effectively login, run processes, access files, etc. A lot of this is presumably because of the presence of many 3rd party applications, of course... Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 07:30:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18550 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 07:30:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18542 for ; Mon, 11 Jan 1999 07:30:43 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id KAA06921; Mon, 11 Jan 1999 10:29:54 -0500 (EST) Date: Mon, 11 Jan 1999 10:29:53 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: Greg Lehey cc: hackers Subject: Re: Where is _swi_vm defined? In-Reply-To: <19990111103524.B8886@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, 11 Jan 1999, Greg Lehey wrote: > On Sunday, 10 January 1999 at 17:32:17 -0500, zhihuizhang wrote: > > > > Hi, can anyone tell me where the routine _swi_vm is defined? It appears > > in the table of interrupt handler addresses (ihandlers) in file vector.s. > > /usr/src/sys/i386/i386/vm_machdep.c, about line 654. Use ctags or > etags to find things like this. > > Greg > -- Thanks. The reason I did not find it is that the Stable code was updated in May, 1998. My vm_machdep.c was downloaded earlier than that time. I also guess that the hyperlinked source code tree at http://minnie.cs.adfa.oz.au/FreeBSD-srctree/FreeBSD.html should be updated. It can not find a normal C routine like swi_vm(). Zhihui Zhang ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 09:49:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04219 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 09:49:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04201; Mon, 11 Jan 1999 09:49:14 -0800 (PST) (envelope-from bs@adimus.de) Received: (from admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id SAA18311; Mon, 11 Jan 1999 18:02:36 +0100 (MET) Received: from mail by mx.adimus.de with local (Exim 1.92 #1) id 0zzjel-0000nB-00; Mon, 11 Jan 1999 16:53:31 +0100 Received: from det.adimus.de(192.168.0.1) via SMTP by adimus.de, id smtpdaM3039; Mon Jan 11 16:53:24 1999 Received: from bs by det.adimus.de with local (Exim 1.92 #1) id 0zzjdn-0000F4-00; Mon, 11 Jan 1999 16:52:31 +0100 To: "Dan Shebunin" Cc: , Subject: Re: Problems with DEC PCI Ethernet undef FreeBSD References: <01e401be3bf4$1ae88e60$0100a8c0@dan.space_net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit From: Benedikt Stockebrand Date: 11 Jan 1999 16:52:30 +0100 In-Reply-To: "Dan Shebunin"'s message of "Sat, 9 Jan 1999 20:17:07 +0300" Message-ID: Lines: 21 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dan Shebunin" writes: > Description: > I have DEC PCI Ethernet card installed in my computer. During system boot > phase this card is deteced by de0 device driver. But after loggin' in I > can't use PING, TRACEROUTE, e.t.c. We've had similar problems on a 10baseT network. Putting "media 10baseT/UTP" in /etc/rc.conf for interface options solved the problem. So long, Ben -- Benedikt Stockebrand Adimus Beratungsgesellschaft für System- System Administration & Design, und Netzwerkadministration mbH & Co KG IT Security, Remote System Mgmt Universitätsstr. 142, 44799 Bochum Opinions presented are my own. Tel. (02 34) 971 971 -2, Fax -9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 09:50:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04390 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 09:50:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04379 for ; Mon, 11 Jan 1999 09:50:21 -0800 (PST) (envelope-from bs@adimus.de) Received: (from admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id SAA18364; Mon, 11 Jan 1999 18:02:42 +0100 (MET) Received: from mail by mx.adimus.de with local (Exim 1.92 #1) id 0zzjHr-0000m4-00; Mon, 11 Jan 1999 16:29:51 +0100 Received: from det.adimus.de(192.168.0.1) via SMTP by adimus.de, id smtpdlc2872; Mon Jan 11 16:29:42 1999 Received: from bs by det.adimus.de with local (Exim 1.92 #1) id 0zzjGp-000094-00; Mon, 11 Jan 1999 16:28:47 +0100 To: Joe Abley Cc: Benedikt Stockebrand , Yani Brankov , "Stephen J. Roznowski" , hackers@FreeBSD.ORG Subject: Re: Why is root's crontab different? References: <199901032313.SAA04829@istari.home.net> <368FFD42.F849603C@bulinfo.net> <19990106002259.B6168@clear.co.nz> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit From: Benedikt Stockebrand Date: 11 Jan 1999 16:28:44 +0100 In-Reply-To: Joe Abley's message of "Wed, 6 Jan 1999 00:22:59 +1300" Message-ID: Lines: 52 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley writes: > On Tue, Jan 05, 1999 at 11:45:28AM +0100, Benedikt Stockebrand wrote: > > > Aside from that it's a Good Thing[TM] to keep all configuration files > > in /etc --- putting them in /var will bite you as soon as you have to > > recover from a disk crash and find out you've never bothered to dump > > /var (including assorted spools and log files). And /var has a way > > stronger tendency to get messed up on a system crash than / has. > > If you've lost /var, isn't it probably a good thing that cron isn't > running? You probably have more important things to worry about :) Cron shouldn't be running because your system should be coming up in single user mode then. > Turning your argument around, if it _is_ desirable to have crontabs available > with a minimal number of filesystems mounted, why not move /var/cron to > /etc/cron and dispense with /etc/crontab? Yes, that's an option. Or put the user crontabs into ~/.crontab (with ~root being on the root FS that'd work reasonably well). The downside is that people expect certain things in certain directories. If they don't find things where they expect them they get mighty annoyed (try SuSe-Linux if you don't believe me---I've learned to hate it at my former job). > We seem to have taken the same approach with /etc/namedb, which I have > seen more often located in /var/named... But maybe that's just me. I don't > know the history of this one. The standards for named aren't as thoroughly established and with a secondary server one could argue that the zone files should go to /var because they aren't configuration. Personally I keep the boot and primary zone files in /etc and the rest in /var/named. Since the location of the zone files is configured in the zone file and the zone file is (usually) given as a boot-time argument it's way easier to track down than the compiled-in paths in crond. So long, Ben -- Benedikt Stockebrand Adimus Beratungsgesellschaft für System- System Administration & Design, und Netzwerkadministration mbH & Co KG IT Security, Remote System Mgmt Universitätsstr. 142, 44799 Bochum Opinions presented are my own. Tel. (02 34) 971 971 -2, Fax -9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 11:26:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15959 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 11:26:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zoe.iserve.net (zoe.iserve.net [207.250.219.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15952 for ; Mon, 11 Jan 1999 11:26:22 -0800 (PST) (envelope-from rch@iserve.net) Received: from blackacid_nt (acidic.iserve.net [207.250.219.40]) by zoe.iserve.net (8.9.1/8.9.1) with SMTP id OAA23936 for ; Mon, 11 Jan 1999 14:25:49 -0500 (EST) Date: Mon, 11 Jan 1999 14:25:49 -0500 (EST) Message-Id: <3.0.32.19990111142616.00c64e20@iserve.net> X-Sender: rch@iserve.net X-Mailer: Windows Eudora Pro Version 3.0 (32) To: freebsd-hackers@FreeBSD.ORG From: Robert Hough Subject: Problems with 3.0 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 been currently having problems with FreeBSD 3.0-RELEASE, and was hoping someone here might have an idea of what is causing this. Here's what is happening. /kernel: pid 22761 (httpd), uid 65534: exited on signal 11 This error will repeat itself over and over, untill I stop the process, and restart it. I'm not sure if it's a problem with apache though, as it has happened to inetd, and cron as well. At first I thought maybe it was a problem with the ram, so I've replaced that twice, still no luck. I'm getting ready to swap the CPU as well. Any ideas would be appeciated. __ _______ |__| __|.-----.----.--.--.-----. .-------------------------------. | |__ || -__| _| | | -__| | Robert Hough (rch@iserve.net) | |__|_______||_____|__| \___/|_____| | 317-802-3036 / 317-876-0846 | _____________________________________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 11:35:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17110 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 11:35:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17102 for ; Mon, 11 Jan 1999 11:35:22 -0800 (PST) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.1/8.9.1) id OAA13336 for hackers@freebsd.org; Mon, 11 Jan 1999 14:33:32 -0500 (EST) (envelope-from dervish) Message-ID: <19990111143332.B10918@bantu.cl.msu.edu> Date: Mon, 11 Jan 1999 14:33:32 -0500 From: bush doctor To: hackers@FreeBSD.ORG Subject: What are the advantages of ELF kernels? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just asked this question by my boss, so can someone tell me what are the advantages of elf kernels as opposed to aout kernels? thanxs ... -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 11:44:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18710 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 11:44:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18701 for ; Mon, 11 Jan 1999 11:44:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA96896; Mon, 11 Jan 1999 11:44:21 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 11:44:21 -0800 (PST) From: Matthew Dillon Message-Id: <199901111944.LAA96896@apollo.backplane.com> To: bush doctor Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I was just asked this question by my boss, so can someone tell me :what are the advantages of elf kernels as opposed to aout kernels? : :thanxs ... God, I'm going to sound like one of those IBM web server commercials. (long pause) Better compatibility with and portability to/from linux. Of course, there are lots of reasons for going with ELF - ELF has a much more consistent shared library scheme, for one. But describing them in terms that a non-computer-geek would understand is like walkinging off a cliff blindfolded. -Matt :-- :So ya want ta here da roots? :Dem that feels it knows it ... :bush doctor Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 12:59:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29357 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 12:59:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29345 for ; Mon, 11 Jan 1999 12:59:07 -0800 (PST) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.1/8.9.1) id PAA13548; Mon, 11 Jan 1999 15:57:16 -0500 (EST) (envelope-from dervish) Message-ID: <19990111155716.E10918@bantu.cl.msu.edu> Date: Mon, 11 Jan 1999 15:57:16 -0500 From: bush doctor To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? References: <199901111944.LAA96896@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901111944.LAA96896@apollo.backplane.com>; from Matthew Dillon on Mon, Jan 11, 1999 at 11:44:21AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Matthew Dillon (dillon@apollo.backplane.com): > > :I was just asked this question by my boss, so can someone tell me > :what are the advantages of elf kernels as opposed to aout kernels? > : > :thanxs ... > > God, I'm going to sound like one of those IBM web server commercials. > > (long pause) > > Better compatibility with and portability to/from linux. > > Of course, there are lots of reasons for going with ELF - ELF has a much > more consistent shared library scheme, for one. But describing them in > terms that a non-computer-geek would understand is like walkinging off a > cliff blindfolded. That's ok, My boss, my coworker and myself make up the systems programming staff, so we're not afraid of tech talk. So does having an ELF kernel provide better support for elf shared libraries and elf binaries because it's elf also? > > -Matt > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 13:23:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02553 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 13:23:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (gw.sparks.net [209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA02539 for ; Mon, 11 Jan 1999 13:23:33 -0800 (PST) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0zzonI-0001c4-00; Mon, 11 Jan 1999 16:22:40 -0500 Date: Mon, 11 Jan 1999 16:22:40 -0500 (EST) From: To: hackers@FreeBSD.ORG Subject: 2.2.8/450 P-II/2940 problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any likely "gotcha's" with 2.2.8 from the dist CD, a 450 P-II (Tyan 1832DL), and Adaptec 2940UW controllers? The motherboard woks fine with an IDE drive and 2.2.7. The system can backup from the IDE drive to a DLT7000. It appears to finish normally, but would not access the tape to verify it afterwards. 2.2.8 will install on the disk (ST34520W) on my home system. With the same drive, controller, and cable the P-II will not finish a boot. Installs of 2.2.8 onto a scsi drive always randomly fail, somewhere between "cant stat /mnt" and actually reading some of the install tarballs. I've tried two 2940UW's, three cables, and three disk drives. Termination is set properly. I've tried failing hardware on a K6/350 system and it worked fine. Any guesses? Thanks, --- David Miller ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 13:24:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02688 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 13:24:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02680 for ; Mon, 11 Jan 1999 13:24:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA97427; Mon, 11 Jan 1999 13:24:01 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 13:24:01 -0800 (PST) From: Matthew Dillon Message-Id: <199901112124.NAA97427@apollo.backplane.com> To: bush doctor Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Better compatibility with and portability to/from linux. :> :> Of course, there are lots of reasons for going with ELF - ELF has a much :> more consistent shared library scheme, for one. But describing them in :> terms that a non-computer-geek would understand is like walkinging off a :> cliff blindfolded. :That's ok, My boss, my coworker and myself make up the systems programming staff, :so we're not afraid of tech talk. So does having an ELF kernel provide better :support for elf shared libraries and elf binaries because it's elf also? Not really. An ELF kernel should make kernel modules easier ( the new KLD stuff verses the old modload stuff ), but it has nothing to do with being able to run ELF binaries. ELF has been around for a long time. It has slightly more run-time overhead then a.out ( but this can be optimized ). ELF is designed to more directly support shared libraries and dynamic loading where as a.out was hacked to support shared libraries and dynamic loading. ELF also has core features useful to object oriented languages such as C++. For example, initialization domains. I always like to say: ELF is on par with the Amiga's object/link/binary format. It's nice to see UNIX finally catch up. ! But, most importantly, there has been a general trend towards ELF in the last decade and getting on that bandwagon is important, especially if we want to maintain native compatibility with Linux and other operating systems. The importance of maintaining compatibility cannot be underestimated. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 13:38:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04457 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 13:38:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04441 for ; Mon, 11 Jan 1999 13:38:07 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA042909555; Mon, 11 Jan 1999 10:45:55 -0500 Date: Mon, 11 Jan 1999 10:45:55 -0500 (EST) From: Bill Fumerola To: Robert Hough Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with 3.0 In-Reply-To: <3.0.32.19990111142616.00c64e20@iserve.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 Mon, 11 Jan 1999, Robert Hough wrote: > I have been currently having problems with FreeBSD 3.0-RELEASE, and was > hoping someone here might have an idea of what is causing this. Here's what > is happening. > > /kernel: pid 22761 (httpd), uid 65534: exited on signal 11 At the risk of sending a "me too!" message (this is, though), I've had this same problem as well, and have been trying to trace it. I think it may be related to the proxy module, though. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 13:46:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05556 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 13:46:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05551 for ; Mon, 11 Jan 1999 13:46:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id NAA25190; Mon, 11 Jan 1999 13:52:24 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901112152.NAA25190@troutmask.apl.washington.edu> Subject: Re: What are the advantages of ELF kernels? In-Reply-To: <199901112124.NAA97427@apollo.backplane.com> from Matthew Dillon at "Jan 11, 1999 1:24: 1 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Mon, 11 Jan 1999 13:52:24 -0800 (PST) Cc: dervish@bantu.cl.msu.edu, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Dillon: > > But, most importantly, there has been a general trend towards ELF in the > last decade and getting on that bandwagon is important, especially if we > want to maintain native compatibility with Linux and other operating > systems. The importance of maintaining compatibility cannot be > underestimated. Actually, hasn't FSF dropped support/development of a.out tools. So, if FreeBSD wants to continue to use FSF compiler technology, then we are compelled to move forward to ELF. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 14:30:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11106 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 14:30:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.barmentlo.net (gateway.barmentlo.net [194.158.173.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11099 for ; Mon, 11 Jan 1999 14:30:43 -0800 (PST) (envelope-from pbm@gateway.barmentlo.net) Received: from localhost (pbm@localhost) by mail.barmentlo.net (8.9.1a/8.9.1) with ESMTP id XAA00307 for ; Mon, 11 Jan 1999 23:30:00 +0100 (CET) Date: Mon, 11 Jan 1999 23:30:00 +0100 (CET) From: Patrick Barmentlo To: hackers@FreeBSD.ORG Subject: examples rules ipfw 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 Hai... Can someone please point me out to some good examples for the rc.firewall file (ipfw )?? (with most variant of opties/features...) i have to set up some filtering, but still having some difficulties with it after checking freebsd.org.... thanks patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 14:35:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11623 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 14:35:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11613 for ; Mon, 11 Jan 1999 14:35:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA20001 for ; Mon, 11 Jan 1999 14:34:43 -0800 Date: Mon, 11 Jan 1999 14:34:43 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-hackers@FreeBSD.ORG Subject: what is the meaning of this useless code? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in kern_physio.c: struct buf * phygetvpbuf(dev_t dev, int resid) { struct cdevsw *bdsw; int maxio; bdsw = cdevsw[major(dev)]; if ((bdsw == NULL) || (bdsw->d_bmaj == -1)) return getpbuf(); maxio = bdsw->d_maxio; if (resid > maxio) resid = maxio; return getpbuf(); } why is resid being truyncaated and maxio being set when this has no effect? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 14:57:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14194 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 14:57:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smarter.than.nu (thought.calbbs.com [207.71.213.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14188 for ; Mon, 11 Jan 1999 14:57:31 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.9.1) with ESMTP id OAA00933; Mon, 11 Jan 1999 14:56:44 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Mon, 11 Jan 1999 14:56:44 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Patrick Barmentlo cc: hackers@FreeBSD.ORG Subject: Re: examples rules ipfw 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, 11 Jan 1999, Patrick Barmentlo wrote: > Can someone please point me out to some good examples for the rc.firewall > file (ipfw )?? > (with most variant of opties/features...) > > i have to set up some filtering, but still having some difficulties with > it after checking freebsd.org.... What kind of filtering? For a single machine, or on a gateway for a LAN? Here are my firewall rules and a brief explanation of them: add 00002 allow ip from smarter to any This allows any IP traffic from the local host (its hostname is "smarter") to any host. add 00003 allow tcp from any to smarter established This allows any TCP traffic into the local host that does not have the SYN flag set. That is, it allows TCP connections that have already been established to continute to send us data. add 00050 allow ip from localhost to localhost via lo0 This allows all IP traffic from/to localhost over the loopback interface. add 00051 deny ip from localhost to any This denies any IP traffic claiming to be from the loopback address coming in from any interface. (Legitimate loopback traffic will be allowed by the rule above, and therefore won't get filtered out here) add 00101 deny log udp from any to smarter printer,nfsd,sunrpc This denies and logs any UDP packets sent to smarter's printer, nfsd, and sunrpc ports. add 00102 deny udp from any to smarter 137,138 This denies any UDP packets sent to netbios-ns and netbios-dgm. add 00199 allow udp from any to any This allows any UDP packets not previously filtered out. add 00201 allow icmp from any to smarter This allows all ICMP traffic destined for the local host. add 00301 allow tcp from any to smarter ftp This allows all traffic to the ftp daemon. add 00401 allow tcp from any to smarter ssh This allows all traffic to the ssh daemon. add 00450 deny tcp from any to smarter 3306 This denies all traffic to port 3306 (mysqld) add 00501 allow tcp from any to smarter 1024-65535 This allows all traffic to ports 1024 through 65535 (to let FTP work correctly) add 00601 allow tcp from 169.229.99.90 to smarter 25,139 add 00602 allow tcp from 169.229.99.92 to smarter 25,139 These rules allow my roommates' Windows computers to relay mail via my sendmail daemon (port 25) and to access my SAMBA daemon for filesharing/printing (port 139) add 60000 deny igmp from any to any This drops all IGMP packets. add 60001 reset tcp from any to smarter ident This sends a TCP RST in response to any attempt to connect to identd. (Initiator gets "Connection Refused") add 64000 reset tcp from any to smarter 139 This sends a TCP RST in response to any attempt to connect to SAMBA. add 65000 deny log ip from any to any This denies any packets not already accepted or denied, and logs them. Hope that helped. IPFW can do many more things which I don't currently use, but that should serve to give you a general idea of what you can do with IPFW. -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 15:08:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15848 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 15:08:14 -0800 (PST) (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 PAA15828 for ; Mon, 11 Jan 1999 15:08:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA10182; Mon, 11 Jan 1999 14:57:34 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdx10175; Mon Jan 11 22:57:30 1999 Date: Mon, 11 Jan 1999 14:57:25 -0800 (PST) From: Julian Elischer Reply-To: Julian Elischer To: Matthew Jacob cc: freebsd-hackers@FreeBSD.ORG Subject: Re: what is the meaning of this useless code? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Jan 1999, Matthew Jacob wrote: > > if (resid > maxio) > resid = maxio; > > return getpbuf(); > } > > > why is resid being truyncaated and maxio being set when this has no > effect? I think resid was originally an agument to getpbuf but mechanical edits have turned it all into a NOP. Good catch.. However there is a related problem.. the maximum IO size allowed for a device is kept in the cdevsw entry, which is the WRONG place, because it cannot correctly reflect the case when there are two differnt devices with different limits on the same controller (e.g. two different drives or even two differend controllers on one driver). julian > > > 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 Jan 11 15:09:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15926 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 15:09:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.barmentlo.net (gateway.barmentlo.net [194.158.173.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15916 for ; Mon, 11 Jan 1999 15:09:13 -0800 (PST) (envelope-from pbm@barmentlo.net) Received: from localhost (pbm@localhost) by mail.barmentlo.net (8.9.1a/8.9.1) with ESMTP id AAA00379; Tue, 12 Jan 1999 00:08:04 +0100 (CET) Date: Tue, 12 Jan 1999 00:08:03 +0100 (CET) From: Patrick Barmentlo To: "Brian W. Buchanan" cc: hackers@FreeBSD.ORG Subject: Re: examples rules ipfw 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, 11 Jan 1999, Brian W. Buchanan wrote: > On Mon, 11 Jan 1999, Patrick Barmentlo wrote: > > > Can someone please point me out to some good examples for the rc.firewall > > file (ipfw )?? > > (with most variant of opties/features...) > > > > i have to set up some filtering, but still having some difficulties with > > it after checking freebsd.org.... > > What kind of filtering? For a single machine, or on a gateway for a LAN? This what it is about, i have a bsd host with ep0 and ppp0 interfaces (the ppp0 is connected to the Internet, of course ;-)) i have a small subnet, so i don't need to do any 'nat' I want to allow all traffic out of my 'lan' to the internet, but only want to allow mail (smtp) and dns from the internet in.. (and eventualy other services) I also want to allow from a certain host traffic into my 'lan' If you can help me with something like this , the it would help me on the right way.. ;-) thanks.. > > Here are my firewall rules and a brief explanation of them: > > add 00002 allow ip from smarter to any > > This allows any IP traffic from the local host (its hostname is "smarter") > to any host. > > add 00003 allow tcp from any to smarter established > > This allows any TCP traffic into the local host that does not have the > SYN flag set. That is, it allows TCP connections that have already been > established to continute to send us data. > > add 00050 allow ip from localhost to localhost via lo0 > > This allows all IP traffic from/to localhost over the loopback interface. > > add 00051 deny ip from localhost to any > > This denies any IP traffic claiming to be from the loopback address > coming in from any interface. (Legitimate loopback traffic will be allowed > by the rule above, and therefore won't get filtered out here) > > add 00101 deny log udp from any to smarter printer,nfsd,sunrpc > > This denies and logs any UDP packets sent to smarter's printer, nfsd, > and sunrpc ports. > > add 00102 deny udp from any to smarter 137,138 > > This denies any UDP packets sent to netbios-ns and netbios-dgm. > > add 00199 allow udp from any to any > > This allows any UDP packets not previously filtered out. > > add 00201 allow icmp from any to smarter > > This allows all ICMP traffic destined for the local host. > > add 00301 allow tcp from any to smarter ftp > > This allows all traffic to the ftp daemon. > > add 00401 allow tcp from any to smarter ssh > > This allows all traffic to the ssh daemon. > > add 00450 deny tcp from any to smarter 3306 > > This denies all traffic to port 3306 (mysqld) > > add 00501 allow tcp from any to smarter 1024-65535 > > This allows all traffic to ports 1024 through 65535 (to let FTP work > correctly) > > add 00601 allow tcp from 169.229.99.90 to smarter 25,139 > add 00602 allow tcp from 169.229.99.92 to smarter 25,139 > > These rules allow my roommates' Windows computers to relay mail via my > sendmail daemon (port 25) and to access my SAMBA daemon for > filesharing/printing (port 139) > > add 60000 deny igmp from any to any > > This drops all IGMP packets. > > add 60001 reset tcp from any to smarter ident > > This sends a TCP RST in response to any attempt to connect to identd. > (Initiator gets "Connection Refused") > > add 64000 reset tcp from any to smarter 139 > > This sends a TCP RST in response to any attempt to connect to SAMBA. > > add 65000 deny log ip from any to any > > This denies any packets not already accepted or denied, and logs them. > > > Hope that helped. IPFW can do many more things which I don't currently > use, but that should serve to give you a general idea of what you can do > with IPFW. > > -- > Brian Buchanan brian@smarter.than.nu > brian@CSUA.Berkeley.EDU > > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > -- Benjamin Franklin, 1759 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 15:10:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16267 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 15:10:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16262 for ; Mon, 11 Jan 1999 15:10:53 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id PAA20161; Mon, 11 Jan 1999 15:10:14 -0800 Date: Mon, 11 Jan 1999 15:10:14 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Julian Elischer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: what is the meaning of this useless code? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Jan 1999, Julian Elischer wrote: > > > On Mon, 11 Jan 1999, Matthew Jacob wrote: > > > > > if (resid > maxio) > > resid = maxio; > > > > return getpbuf(); > > } > > > > > > why is resid being truyncaated and maxio being set when this has no > > effect? > > I think resid was originally an agument to getpbuf > but mechanical edits have turned it all into a NOP. > Good catch.. Okay. > > However there is a related problem.. > > the maximum IO size allowed for a device is kept in the > cdevsw entry, which is the WRONG place, because > it cannot correctly reflect the case when there are two differnt devices > with different limits on the same controller (e.g. two different drives > or even two differend controllers on one driver). > Well, there are a number of limits- some are device specific, some are bus specific and some are VM/OS specific. It's a bit confusing which applies here. I'm going to ponder this as time permits. I'm trying to track down a hang on alpha with larget I/Os and this led me to try and follow the raw I/O path which led to this... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 15:13:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16565 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 15:13:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA16558 for ; Mon, 11 Jan 1999 15:13:40 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 4114 invoked by uid 1000); 11 Jan 1999 23:11:56 -0000 Date: Tue, 12 Jan 1999 00:11:56 +0100 From: Andreas Braukmann To: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Message-ID: <19990112001155.D2889@paert.tse-online.de> References: <199901112124.NAA97427@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901112124.NAA97427@apollo.backplane.com>; from Matthew Dillon on Mon, Jan 11, 1999 at 01:24:01PM -0800 Organization: TSE TeleService GmbH Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Matt, (slightly off-topic ...) On Mon, Jan 11, 1999 at 01:24:01PM -0800, Matthew Dillon wrote: > I always like to say: ELF is on par with the Amiga's object/link/binary > format. It's nice to see UNIX finally catch up. ! I've been wondering all the time, if you might really be _that_ Matt Dillon, who gave this awesome kick-ass editor to the amiga-community in the late eighties? -Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 16:02:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21598 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 16:02:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21538 for ; Mon, 11 Jan 1999 16:02:02 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA24101; Mon, 11 Jan 1999 15:59:46 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA05104; Mon, 11 Jan 1999 15:59:45 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id QAA07210; Mon, 11 Jan 1999 16:59:44 -0700 Message-ID: <369A9070.F9DCC718@softweyr.com> Date: Mon, 11 Jan 1999 16:59:44 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl CC: Matthew Dillon , dervish@bantu.cl.msu.edu, hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? References: <199901112152.NAA25190@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > > According to Matthew Dillon: > > > > But, most importantly, there has been a general trend towards ELF in the > > last decade and getting on that bandwagon is important, especially if we > > want to maintain native compatibility with Linux and other operating > > systems. The importance of maintaining compatibility cannot be > > underestimated. > > Actually, hasn't FSF dropped support/development of a.out tools. > So, if FreeBSD wants to continue to use FSF compiler technology, > then we are compelled to move forward to ELF. And that is the strongest reason to move to ELF: because everyone else did. Being able to keep up with other developments in the world of development tools, not becoming a backwater, is an important point. This will allow FreeBSD to be a first-class Ada development system, using GNATS. ;^) -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 16:15:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24481 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 16:15:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24472 for ; Mon, 11 Jan 1999 16:15:15 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA15153; Mon, 11 Jan 1999 19:14:08 -0500 (EST) Date: Mon, 11 Jan 1999 19:14:08 -0500 (EST) From: Daniel Eischen Message-Id: <199901120014.TAA15153@pcnet1.pcnet.com> To: sgk@troutmask.apl.washington.edu, wes@softweyr.com Subject: Re: What are the advantages of ELF kernels? Cc: dervish@bantu.cl.msu.edu, dillon@apollo.backplane.com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Being able to keep up with other developments in the world of development > tools, not becoming a backwater, is an important point. This will allow > FreeBSD to be a first-class Ada development system, using GNATS. ;^) s/GNATS/GNAT/ And that's also one of my pet projects (FreeBSD GNAT Ada self-hosted and VxWorks cross-compiler). Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 16:20:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25203 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 16:20:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25196 for ; Mon, 11 Jan 1999 16:20:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA98154; Mon, 11 Jan 1999 16:20:04 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 16:20:04 -0800 (PST) From: Matthew Dillon Message-Id: <199901120020.QAA98154@apollo.backplane.com> To: Andreas Braukmann Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi Matt, : :(slightly off-topic ...) : :On Mon, Jan 11, 1999 at 01:24:01PM -0800, Matthew Dillon wrote: :> I always like to say: ELF is on par with the Amiga's object/link/binary :> format. It's nice to see UNIX finally catch up. ! :I've been wondering all the time, if you might really be _that_ :Matt Dillon, who gave this awesome kick-ass editor to the amiga-community :in the late eighties? : :-Andreas One word! http://www.backplane.com/dice/ Which just points to www.obviously.com, which is hosted on one of my BEST accounts. Hmm.. speaking of which, I should probably shift that domain over to backplane, I don't know how long the account will last now that I'm leaving BEST. Er, BEST/Hiway. Er. Verio. Ugh. I haven't worked on DICE much for a couple of years, but as my last major act I did fix it up so it could be compiled up on a UNIX box (aka linux, FreeBSD) and used as 68K C cross compiler -- everything except the FP support. I still use it for embedded 68000 work. It won't generate op codes for higher-end cpus and can't handle huge structures due to the way the code generator works (it's in love with 68K 16 bit register relative instructions), but it is still a nice piece of work. The source is available free now too so if you ever wanted to know what the insides of DICE looked like, you can pop it off the site and look at it. It's some of the best code I had ever written. GCC would probably do a better job even for embedded stuff now-a-days, but DICE generated enough income in its shareware days for me to help get BEST.COM started 4 years ago. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 16:30:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26489 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 16:30:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26484 for ; Mon, 11 Jan 1999 16:30:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA98242; Mon, 11 Jan 1999 16:29:38 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 16:29:38 -0800 (PST) From: Matthew Dillon Message-Id: <199901120029.QAA98242@apollo.backplane.com> To: Matthew Jacob Cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: what is the meaning of this useless code? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> On Mon, 11 Jan 1999, Matthew Jacob wrote: :> > if (resid > maxio) :> > resid = maxio; :> > :> > return getpbuf(); :> > } :> > :> > why is resid being truyncaated and maxio being set when this has no :> > effect? :> :> I think resid was originally an agument to getpbuf :> but mechanical edits have turned it all into a NOP. :> Good catch.. : :Okay. This is definitely a junk assignment. :> However there is a related problem.. :> :> the maximum IO size allowed for a device is kept in the :> cdevsw entry, which is the WRONG place, because :> it cannot correctly reflect the case when there are two differnt devices :> with different limits on the same controller (e.g. two different drives :> or even two differend controllers on one driver). :> : :Well, there are a number of limits- some are device specific, some are bus :specific and some are VM/OS specific. It's a bit confusing which applies :here. : :I'm going to ponder this as time permits. I'm trying to track down a hang :on alpha with larget I/Os and this led me to try and follow the raw I/O :path which led to this... The (struct buf *)->b_pages[] array is limited to MAXPHYS bytes worth of pages, where MAXPHYS is typically 128 KBytes. If you try to stuff a struct buf with more then that, you will overrun the array and bad things will happen. Make sure the devices properly limit the size of the I/O operation they try to stuff into a struct buf. This is just one of several limits, as you know. d_maxio could probably be removed from the kernel entirely with a little work. I wouldn't worry about it too much, all that really matters is that the value is large enough such that the transaction rate does not overburden the device. For a hard disk, anything over 8KBytes tends to accomplish this. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 16:33:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26874 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 16:33:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wireless.net (wireless.net [207.137.156.159] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26860; Mon, 11 Jan 1999 16:33:29 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id QAA17557; Mon, 11 Jan 1999 16:48:36 -0800 (PST) Date: Mon, 11 Jan 1999 16:48:36 -0800 (PST) From: Bernie Doehner To: hackers@FreeBSD.ORG cc: questions@FreeBSD.ORG Subject: limiting per process swap space utilization like Solaris ulimit? 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: Due to a problem with qmail running away, I'd like to be able to limit the per process swap space utilization under FreeBSD. How does one do this? Under Solaris ulimit provides a good interface to setting this limit, but I could find no such limit (either setable via a program, or a system call). Thanks. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 17:00:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01014 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 17:00:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01009; Mon, 11 Jan 1999 17:00:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA98452; Mon, 11 Jan 1999 16:59:31 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 16:59:31 -0800 (PST) From: Matthew Dillon Message-Id: <199901120059.QAA98452@apollo.backplane.com> To: Bernie Doehner Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi: : :Due to a problem with qmail running away, I'd like to be able to limit the :per process swap space utilization under FreeBSD. : :How does one do this? : :Under Solaris ulimit provides a good interface to setting this limit, but :I could find no such limit (either setable via a program, or a system :call). : :Thanks. : :Bernie You can set the datasize resource limit apollo:/usr/src/sys# limit cputime unlimited filesize unlimited datasize 524288 kbytes <---------- stacksize 65536 kbytes coredumpsize unlimited memoryuse 32768 kbytes descriptors 1024 memorylocked unlimited maxproc 200 That's about as close as you can get. Try setting it to something like 20m. The real solution is to figure out why qmail is blowing up in the first place. If it's a matter of too many qmail processes running, that's a different problem that a per-process resource limit will not solve. I don't know what the solution under qmail is for that. Under sendmail it's relatively easy to limit the maximum number of running sendmail processes through the MaxDaemonChildren option. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 17:05:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01636 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 17:05:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01629 for ; Mon, 11 Jan 1999 17:05:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id RAA98523; Mon, 11 Jan 1999 17:05:17 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 17:05:17 -0800 (PST) From: Matthew Dillon Message-Id: <199901120105.RAA98523@apollo.backplane.com> To: Bill Fumerola Cc: Robert Hough , freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with 3.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 11 Jan 1999, Robert Hough wrote: : :> I have been currently having problems with FreeBSD 3.0-RELEASE, and was :> hoping someone here might have an idea of what is causing this. Here's what :> is happening. :> :> /kernel: pid 22761 (httpd), uid 65534: exited on signal 11 : :At the risk of sending a "me too!" message (this is, though), I've had :this same problem as well, and have been trying to trace it. I think it :may be related to the proxy module, though. : :- bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - :- ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - This could be the same dying-daemons problem that was due to a bug in the swap code that was trying to optimize for low swap-space situations. If you have lots of swap space free, that isn't it though. With apache it is particularly difficult to discern whether the crash is due to the kernel or due to a big in apache. Since apache setuid()'s itself, core dumps are disabled. The only way to catch it in the act is to attach a debugger to the running process and wait for it to segfault, but there are usually too many apache (httpd) processes running to be able to do that effectively. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 17:39:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05198 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 17:39:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05193 for ; Mon, 11 Jan 1999 17:39:03 -0800 (PST) (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 RAA01895; Mon, 11 Jan 1999 17:38:28 -0800 (PST) (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 QAA12769; Mon, 11 Jan 1999 16:34:27 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA17038; Mon, 11 Jan 1999 16:34:26 -0800 (PST) From: Don Lewis Message-Id: <199901120034.QAA17038@salsa.gv.tsc.tdk.com> Date: Mon, 11 Jan 1999 16:34:26 -0800 In-Reply-To: bush doctor "What are the advantages of ELF kernels?" (Jan 11, 2:33pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: bush doctor , hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 11, 2:33pm, bush doctor wrote: } Subject: What are the advantages of ELF kernels? } I was just asked this question by my boss, so can someone tell me } what are the advantages of elf kernels as opposed to aout kernels? They are compatible with the elf gdb that you installed with the rest of your elf userland, so you don't have to jump through hoops to build an a.out gdb just for debugging your kernel ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 18:54:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14139 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 18:54:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14132 for ; Mon, 11 Jan 1999 18:54:12 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id PAA13108; Tue, 12 Jan 1999 15:53:29 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id PAA32924; Tue, 12 Jan 1999 15:53:25 +1300 (NZDT) (envelope-from jabley) Date: Tue, 12 Jan 1999 15:53:25 +1300 From: Joe Abley To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990112155325.A32880@clear.co.nz> References: <19990111210558.A29444@clear.co.nz> <199901111023.CAA88602@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901111023.CAA88602@dingo.cdrom.com>; from Mike Smith on Mon, Jan 11, 1999 at 02:23:45AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 11, 1999 at 02:23:45AM -0800, Mike Smith wrote: > > > > > > I'm not sure about the whole softwords/help text munging thing. Using > > > Perl scripts is bad for various reasons, but I'm not sure that I want > > > to go to having committed generated files (like the kernel uses) or the > > > other way to compiled special-purpose tools. Anyone handy with awk > > > want to try fixing these - both would probably succumb to the awesome > > > power of awk. > > > > Eh? > > > > If someone needs some awk writing, and can describe clearly what needs > > doing, I'll do it. > > There are two separate tasks, each with their own interesting > requirements. The easiest way to understand them is probably to look > at what the current perl scripts are doing. The first transforms the > Forth softwords files into a large string array, stripping all the > unnecessary bits; that's /sys/boot/ficl/softwords/softcore.pl. > > Run it as per the Makefile to see the output it produces; inferring the > rules from that should be pretty straightforward. Have a look at softcore.awk (below) - I haven't run too much through it, but I think it should work ok. It uses two gawk-specific extensions: + a function, to aid readability, but it's not a biggie and the function calls could certainly be rolled out if they offend anybody + one call to strftime() to generate the "last updated" line in the resulting c fragment header. This could also be made to go away if we don't like gawk-isms. The use of "[[:space:]]" I think is more readable than " " - these character classes are defined in the POSIX standard, but may not exist in other traditional implementations. I like them because hard-coding what a space is on an arbitrary system seems like a bad thing (although I suspect most people agree what a space is, and I had to hard-code the tab handling anyway with \t...) I'll have a look at the second part in a little while. Meanwhile, please point out all the bugs in the first part :) Joe #!/usr/bin/awk -f # Convert forth source files to a giant C string # Joe Abley , 12 January 1999 BEGIN \ { printf "/***************************************************************\n"; printf "** s o f t c o r e . c\n"; printf "** Forth Inspired Command Language -\n"; printf "** Words from CORE set written in FICL\n"; printf "** Author: John Sadler (john_sadler@alum.mit.edu)\n"; printf "** Created: 27 December 1997\n"; printf "** Last update: %s\n", strftime(); printf "***************************************************************/\n"; printf "\n/*\n"; printf "** This file contains definitions that are compiled into the\n"; printf "** system dictionary by the first virtual machine to be created.\n"; printf "** Created automagically by ficl/softwords/softcore.awk\n"; printf "*/\n"; printf "\n#include \"ficl.h\"\n"; printf "\nstatic char softWords[] =\n"; commenting = 0; } # some general early substitutions { gsub("\t", " "); # replace each tab with 4 spaces gsub("\"", "\\\""); # escape quotes gsub("\\\\[[:space:]]+$", ""); # toss empty comments } # strip out empty lines /^ *$/ \ { next; } # emit / ** lines as multi-line C comments /^\\[[:space:]]\*\*/ && (commenting == 0) \ { sub("^\\\\[[:space:]]", ""); printf "/*\n%s\n", $0; commenting = 1; next; } /^\\[[:space:]]\*\*/ \ { sub("^\\\\[[:space:]]", ""); printf "%s\n", $0; next; } # function to close a comment, used later function end_comments() { commenting = 0; printf "*/\n"; } # pass commented preprocessor directives /^\\[[:space:]]#/ \ { if (commenting) end_comments(); sub("^\\\\[[:space:]]", ""); printf "%s\n", $0; next; } # toss all other full-line comments /^\\/ \ { if (commenting) end_comments(); next; } # emit all other lines as quoted string fragments { if (commenting) end_comments(); sub("\\\\[[:space:]]+.*$", ""); # lop off trailing \ comments sub("[[:space:]]+$", ""); # remove trailing spaces printf " \"%s \\n\"\n", $0; next; } END \ { if (commenting) end_comments(); printf " \"quit \";\n"; printf "\n\nvoid ficlCompileSoftCore(FICL_VM *pVM)\n"; printf "{\n"; printf " assert(ficlExec(pVM, softWords) != VM_ERREXIT);\n"; printf "}\n"; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 19:13:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16244 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 19:13:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16239 for ; Mon, 11 Jan 1999 19:13:46 -0800 (PST) (envelope-from ejc@bazzle.com) Received: (qmail 61868 invoked from network); 12 Jan 1999 03:13:11 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 12 Jan 1999 03:13:11 -0000 Date: Mon, 11 Jan 1999 22:13:10 -0500 (EST) From: "Eric J. Chet" To: Andreas Braukmann cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? In-Reply-To: <19990112001155.D2889@paert.tse-online.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Andreas Braukmann wrote: > Hi Matt, > > (slightly off-topic ...) > > On Mon, Jan 11, 1999 at 01:24:01PM -0800, Matthew Dillon wrote: > > I always like to say: ELF is on par with the Amiga's object/link/binary > > format. It's nice to see UNIX finally catch up. ! > I've been wondering all the time, if you might really be _that_ > Matt Dillon, who gave this awesome kick-ass editor to the amiga-community > in the late eighties? Don't forget the "C" compiler DICE. > > -Andreas > Eric Chet -> ejc@bazzle.com || ejc@FreeBSD.ORG || ejchet@lucent.com Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo Jiu-Jitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 19:30:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18147 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 19:30:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18142 for ; Mon, 11 Jan 1999 19:30:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA99415; Mon, 11 Jan 1999 19:30:08 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 19:30:08 -0800 (PST) From: Matthew Dillon Message-Id: <199901120330.TAA99415@apollo.backplane.com> To: "Eric J. Chet" Cc: Andreas Braukmann , hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> (slightly off-topic ...) :> :> On Mon, Jan 11, 1999 at 01:24:01PM -0800, Matthew Dillon wrote: :> > I always like to say: ELF is on par with the Amiga's object/link/binary :> > format. It's nice to see UNIX finally catch up. ! :> I've been wondering all the time, if you might really be _that_ :> Matt Dillon, who gave this awesome kick-ass editor to the amiga-community :> in the late eighties? : :Don't forget the "C" compiler DICE. Heh. I never ported DME to UNIX. I've considered it on and off, but it'd be about a week's worth of work due to all the direct intuition and graphics calls. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 19:35:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18740 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 19:35:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18732 for ; Mon, 11 Jan 1999 19:35:23 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA01007; Tue, 12 Jan 1999 14:04:29 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901120330.TAA99415@apollo.backplane.com> Date: Tue, 12 Jan 1999 14:04:34 +1030 (CST) From: "Daniel O'Connor" To: Matthew Dillon Subject: Re: What are the advantages of ELF kernels? Cc: hackers@FreeBSD.ORG, Andreas Braukmann , "Eric J. Chet" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-99 Matthew Dillon wrote: > :Don't forget the "C" compiler DICE. > > Heh. I never ported DME to UNIX. I've considered it on and off, but > it'd be about a week's worth of work due to all the direct intuition and > graphics calls. Hmmm.. LDFLAGS+= -lintuition -lgraphics ? =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 11 23:37:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11147 for freebsd-hackers-outgoing; Mon, 11 Jan 1999 23:37:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles165.castles.com [208.214.165.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11139 for ; Mon, 11 Jan 1999 23:37:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA01513; Mon, 11 Jan 1999 23:34:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901120734.XAA01513@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Hough cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with 3.0 In-reply-to: Your message of "Mon, 11 Jan 1999 14:25:49 EST." <3.0.32.19990111142616.00c64e20@iserve.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Jan 1999 23:34:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been currently having problems with FreeBSD 3.0-RELEASE, and was > hoping someone here might have an idea of what is causing this. Here's what > is happening. > > /kernel: pid 22761 (httpd), uid 65534: exited on signal 11 > > This error will repeat itself over and over, untill I stop the process, and > restart it. I'm not sure if it's a problem with apache though, as it has > happened to inetd, and cron as well. At first I thought maybe it was a > problem with the ram, so I've replaced that twice, still no luck. I'm > getting ready to swap the CPU as well. Any ideas would be appeciated. The fact that the error repeats indicates that the cached copy of the program's text has been corrupted. This typically requires bad RAM, CPU or motherboard. Are you overclocking? -- \\ 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 Jan 12 00:32:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15930 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 00:32:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15925 for ; Tue, 12 Jan 1999 00:32:04 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id VAA28354; Tue, 12 Jan 1999 21:31:27 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id VAA57361; Tue, 12 Jan 1999 21:31:22 +1300 (NZDT) (envelope-from jabley) Date: Tue, 12 Jan 1999 21:31:21 +1300 From: Joe Abley To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990112213121.B54045@clear.co.nz> References: <19990111210558.A29444@clear.co.nz> <199901111023.CAA88602@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901111023.CAA88602@dingo.cdrom.com>; from Mike Smith on Mon, Jan 11, 1999 at 02:23:45AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 11, 1999 at 02:23:45AM -0800, Mike Smith wrote: > > The second task is to construct a unified, sorted helpfile from two > input files. The helpfiles consist of records delimited thus: > > ##... > # T [S] D > ...data > # > > The records from each of the two files need to be sorted into topic > order, with every subtopic record sorted in following its topic record, > eg. > > Tfoo > Tfoo Sbar > Tfoo Sbaz > Tfish > ... > > The input files are /sys/boot/common/help.common and > /sys/boot/i386/loader/i386.help (i386) or > /sys/boot/alpha/boot2/alpha.help (alpha). Should the resulting helpfile be in the same format as the help.i386 and help.alpha files? I'm presuming the answer is "yes" and I am steaming ahead :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 00:35:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16536 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 00:35:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles165.castles.com [208.214.165.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16531 for ; Tue, 12 Jan 1999 00:35:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA01933; Tue, 12 Jan 1999 00:32:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901120832.AAA01933@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joe Abley cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-reply-to: Your message of "Tue, 12 Jan 1999 21:31:21 +1300." <19990112213121.B54045@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jan 1999 00:32:09 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The input files are /sys/boot/common/help.common and > > /sys/boot/i386/loader/i386.help (i386) or > > /sys/boot/alpha/boot2/alpha.help (alpha). > > Should the resulting helpfile be in the same format as the help.i386 and > help.alpha files? > > I'm presuming the answer is "yes" and I am steaming ahead :) Yup; the goal is a merge of the two. -- \\ 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 Jan 12 01:08:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20540 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 01:08:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20535 for ; Tue, 12 Jan 1999 01:08:53 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA18368; Tue, 12 Jan 1999 10:13:55 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 12 Jan 1999 10:13:55 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Joe Abley cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-Reply-To: <19990112155325.A32880@clear.co.nz> 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, 12 Jan 1999, Joe Abley wrote: > # some general early substitutions > { > gsub("\t", " "); # replace each tab with 4 spaces Mhm.. I'm not sure. One of the goals here is also to make the resulting string as short as possible, because it directly influences the size of /boot/loader later. The string doesn't have to be nicely formatted, it just has to compile. So, I'd suggest gsub("\t"," "); Otherwise, I like it. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 01:49:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24393 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 01:49:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA24388 for ; Tue, 12 Jan 1999 01:49:44 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 27268 invoked by uid 1001); 12 Jan 1999 09:49:09 -0000 To: dillon@apollo.backplane.com (Matthew Dillon) Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? References: <199901120020.QAA98154@apollo.backplane.com> From: Ville-Pertti Keinonen Date: 12 Jan 1999 11:48:19 +0200 In-Reply-To: dillon@apollo.backplane.com's message of "12 Jan 1999 02:21:38 +0200" Message-ID: <8667acg6u4.fsf@not.oeno.com> Lines: 23 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dillon@apollo.backplane.com (Matthew Dillon) writes: > relative instructions), but it is still a nice piece of work. The source > is available free now too so if you ever wanted to know what the insides > of DICE looked like, you can pop it off the site and look at it. When I found the source some months ago, I was almost surprised that it built an internal sequence of statements, years ago I thought DICE might actually be generating assembly-language (possibly excluding register allocations) straight out of the parser, judging from the output. > GCC would probably do a better job even for embedded stuff now-a-days, but > DICE generated enough income in its shareware days for me to help get > BEST.COM started 4 years ago. DICE is something like 5x as fast as the native gcc on my FreeBSD box (when artificially forced to use the same headers -- not that it makes comparing i386 vs. m68k code generation valid), even more on the Amiga. It still has its advantages. ;--) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 02:30:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28505 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 02:30:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28500 for ; Tue, 12 Jan 1999 02:30:52 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id XAA21988; Tue, 12 Jan 1999 23:30:14 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id XAA90830; Tue, 12 Jan 1999 23:30:09 +1300 (NZDT) (envelope-from jabley) Date: Tue, 12 Jan 1999 23:30:08 +1300 From: Joe Abley To: Andrzej Bialecki Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990112233008.A81635@clear.co.nz> References: <19990112155325.A32880@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Andrzej Bialecki on Tue, Jan 12, 1999 at 10:13:55AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 12, 1999 at 10:13:55AM +0100, Andrzej Bialecki wrote: > On Tue, 12 Jan 1999, Joe Abley wrote: > > > # some general early substitutions > > { > > gsub("\t", " "); # replace each tab with 4 spaces > > Mhm.. I'm not sure. One of the goals here is also to make the resulting > string as short as possible, because it directly influences the size of > /boot/loader later. The string doesn't have to be nicely formatted, it > just has to compile. So, I'd suggest gsub("\t"," "); I was just copying what the perl version did :) I'm not sure what the idea was either... .. also, why are we bothering to split the input file with \n's within the string? Does the FICL parser have a maximum line length? Or does it just deal in tokens, and not care about linefeeds at all? If the latter we could save more space by compressing every occurrance of [[:blank:]]+ to " ", and omitting the newlines. > Otherwise, I like it. Thanks :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 02:43:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29822 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 02:43:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29816 for ; Tue, 12 Jan 1999 02:43:46 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id XAA23869; Tue, 12 Jan 1999 23:43:11 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id XAA11318; Tue, 12 Jan 1999 23:43:06 +1300 (NZDT) (envelope-from jabley) Date: Tue, 12 Jan 1999 23:43:06 +1300 From: Joe Abley To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990112234306.A2738@clear.co.nz> References: <19990112213121.B54045@clear.co.nz> <199901120832.AAA01933@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901120832.AAA01933@dingo.cdrom.com>; from Mike Smith on Tue, Jan 12, 1999 at 12:32:09AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 12, 1999 at 12:32:09AM -0800, Mike Smith wrote: > > Should the resulting helpfile be in the same format as the help.i386 and > > help.alpha files? > > > > I'm presuming the answer is "yes" and I am steaming ahead :) > > Yup; the goal is a merge of the two. OK. Try this. It's a bit messy at the moment (and I'm not sure that my linked list implementation is as elegant as it could be), but take a look and see if it's doing the right kind of thing. Driving instructions: + cat help.i386 help.alpha help.sparc | mergehelp.awk >help.unified + keep to left + watch out for pedestrians #!/usr/bin/awk -f # # $Id: mergehelp.awk,v 1.1 1999/01/12 10:37:38 jabley Exp $ # # Merge two boot loader help files for FreeBSD 3.0 # Joe Abley BEGIN \ { state = 0; first = 0; ind = 0; } # beginning of first command /^###/ && (state == 0) \ { state = 1; next; } # entry header /^# T[[:graph:]]+ (S[[:graph:]]+ )*D[[:graph:]][[:print:]]*$/ && (state == 1) \ { match($0, " T[[:graph:]]+"); T = substr($0, RSTART + 2, RLENGTH - 2); match($0, " S[[:graph:]]+"); S = (RLENGTH == -1) ? "" : substr($0, RSTART + 2, RLENGTH - 2); match($0, " D[[:graph:]][[:print:]]*$"); D = substr($0, RSTART + 2); # find a suitable place to store this one... ind++; if (ind == 1) { first = ind; help[ind, "T"] = T; help[ind, "S"] = S; help[ind, "link"] = -1; } else { i = first; j = -1; while (help[i, "T"] help[i, "S"] < T S) { j = i; i = help[i, "link"]; if (i == -1) break; } if (i == -1) { help[j, "link"] = ind; help[ind, "link"] = -1; } else { help[ind, "link"] = i; if (j == -1) first = ind; else help[j, "link"] = ind; } } help[ind, "T"] = T; help[ind, "S"] = S; help[ind, "D"] = D; # set our state state = 2; next; } /^[[:blank:]]+[[:graph:]][[:print:]]*$/ && (state == 2) \ { sub("^[[:blank:]]+", ""); sub("[[:blank:]]+$", ""); help[ind, "synopsis"] = $0; help[ind, "text"] = 0; state = 3; next; } /^[[:blank:]][[:graph:]][[:print:]]*$/ && (state == 3) \ { sub("^[[:blank:]]+", ""); sub("[[:blank:]]+$", ""); help[ind, "text", help[ind, "text"]] = $0; help[ind, "text"]++; next; } # end of last command, beginning of next one /^###/ && (state == 3) \ { state = 1; } # show them what we have (it's already sorted in help[]) END \ { node = first; while (node != -1) { printf "################################################################################\n"; printf "# T%s ", help[node, "T"]; if (help[node, "S"] != "") printf "S%s ", help[node, "S"]; printf "D%s\n", help[node, "D"]; printf "\n\t%s\n\n", help[node, "synopsis"]; for (i = 0; i < help[node, "text"]; i++) printf "\t%s\n", help[node, "text", i]; printf "\n"; node = help[node, "link"]; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 02:49:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00642 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 02:49:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00637 for ; Tue, 12 Jan 1999 02:49:00 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA24703; Tue, 12 Jan 1999 19:48:08 +0900 (JST) Message-ID: <369B125D.F487B9@newsguy.com> Date: Tue, 12 Jan 1999 18:14:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: bush doctor CC: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? References: <199901111944.LAA96896@apollo.backplane.com> <19990111155716.E10918@bantu.cl.msu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bush doctor wrote: > > That's ok, My boss, my coworker and myself make up the systems programming staff, > so we're not afraid of tech talk. So does having an ELF kernel provide better > support for elf shared libraries and elf binaries because it's elf also? I might be misleading here, but I'd think the Number One reason for changing to Elf is the lack of availability of binutils for a.out. Support for a.out has been abandoned in binutils (gcc tools). So, it seriously impacted on FreeBSD's ability to upgrade the compiler toolchain. As for the specifics on how elf is so much better than a.out, I usually heard most arguments coming from Terry. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 03:02:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02060 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 03:02:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02054 for ; Tue, 12 Jan 1999 03:02:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA25717; Tue, 12 Jan 1999 20:01:19 +0900 (JST) Message-ID: <369B29E8.335B11E5@newsguy.com> Date: Tue, 12 Jan 1999 19:54:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki CC: Joe Abley , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > On Tue, 12 Jan 1999, Joe Abley wrote: > > > # some general early substitutions > > { > > gsub("\t", " "); # replace each tab with 4 spaces > > Mhm.. I'm not sure. One of the goals here is also to make the resulting > string as short as possible, because it directly influences the size of > /boot/loader later. The string doesn't have to be nicely formatted, it > just has to compile. So, I'd suggest gsub("\t"," "); Let me come in Joe's defense here. :-) I told him that we wanted this really stripped, but I also mentioned that when I first got to replace this script, I decided to first write a 100% compatible replacement, and *then* apply patches to it, so the 100% compatible replacement would be in the repo. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 05:23:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18015 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 05:23:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18005 for ; Tue, 12 Jan 1999 05:22:42 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id OAA20743; Tue, 12 Jan 1999 14:25:52 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 12 Jan 1999 14:25:52 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Daniel C. Sobral" cc: Joe Abley , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-Reply-To: <369B29E8.335B11E5@newsguy.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, 12 Jan 1999, Daniel C. Sobral wrote: > Andrzej Bialecki wrote: > > Mhm.. I'm not sure. One of the goals here is also to make the resulting > > string as short as possible, because it directly influences the size of > > /boot/loader later. The string doesn't have to be nicely formatted, it > > just has to compile. So, I'd suggest gsub("\t"," "); > > Let me come in Joe's defense here. :-) I told him that we wanted > this really stripped, but I also mentioned that when I first got to > replace this script, I decided to first write a 100% compatible > replacement, and *then* apply patches to it, so the 100% compatible > replacement would be in the repo. Ok, you're right - I forgot it. Then, I don't have any objections. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 06:05:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22506 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 06:05:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22499 for ; Tue, 12 Jan 1999 06:05:25 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id WAA66113; Tue, 12 Jan 1999 22:04:34 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901121404.WAA66113@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: Matthew Dillon , hackers@FreeBSD.ORG, Andreas Braukmann , "Eric J. Chet" Subject: Re: What are the advantages of ELF kernels? In-reply-to: Your message of "Tue, 12 Jan 1999 14:04:34 +1030." Date: Tue, 12 Jan 1999 22:04:33 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel O'Connor" wrote: > > On 12-Jan-99 Matthew Dillon wrote: > > > :Don't forget the "C" compiler DICE. > > > > Heh. I never ported DME to UNIX. I've considered it on and off, but > > it'd be about a week's worth of work due to all the direct intuition a nd > > graphics calls. > Hmmm.. > LDFLAGS+= -lintuition -lgraphics > ? =) AARGH!!!! This whole thread is making me break out in a cold sweat! :-) I don't know if Matt will take this as a compliment or an insult, but I learned most of my early C programming from his code...... And I learned a lot of my early server and/or systems programming from trying to backport dnet to run on a vax after Matt had switched to something Sun-like and was byte order problems started to slip into the code for exporting a unix tree to an Amiga mountable filesystem the packet serial link. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 07:04:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29569 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 07:04:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29560 for ; Tue, 12 Jan 1999 07:04:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA60265; Tue, 12 Jan 1999 00:35:07 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901120035.AAA60265@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Joseph Lee , freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-reply-to: Your message of "Tue, 29 Dec 1998 17:49:12 +0100." <19981229174912.U53810@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jan 1999 00:35:07 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Dec 29, 1998 at 07:19:17AM -0800, Joseph Lee wrote: > > I've been hacking around in libalias to attempt ident support, and > > have gotten stuck due to my limited knowledge of tcp connections. > > > > The basic premise of the code has been: > > (1) see if tcp packet in is destined for port 113, if so special code > > (2) in special code, do a sscanf() similar to a basic ident query > > and grab querying remote/local (fport/lport) port pair > > (3) with pair found, find corresponding in-link to find originating > > out-link that triggered the ident query, using the fport/lport pair > > (4) with in-link found, create out-link originating at original ip/auth > > port to remote ip, same remote port, using FindUdpTcpOut() > > (5) do a PunchFWHole() on the new out-link > > (6) change the original (destined) address on the tcp packet from (1) > > > Step 4 is wrong, if I understand what you write correctly. The ident > query has to be re-written with support for the relevant ports > changing - libalias is _not_ guaranteed to use the same ports as the > original machine did. AFAIK, the problem isn't solvable :-( Libalias needs to rewrite the ident query, changing the destination IP to that of the correct machine, and changing the embedded port number to the one originally sent. To do this, libalias needs to identify the link table entry for the original connection, but all it's given is the source port number and the destination IP and port. The source IP can only be guessed at; an educated guess could be made, but it wouldn't be 100% reliable. With PKT_ALIAS_SAME_PORTS set, the guess can be more educated, but it's still not going to be 100%. Having said all that, I think it's still worth investing the time in getting this working (time I haven't got at the moment I'm afraid). It should be made run-time configurable (PacketAliasSetMode()) and should default to disabled. I believe that a lot of the people that use libalias are people with a small number of internal machines and a small number of people using them. The ident module should get a good hit rate. > Eivind. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 08:42:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09807 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 08:42:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09775 for ; Tue, 12 Jan 1999 08:42:13 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with SMTP id RAA23905 for ; Tue, 12 Jan 1999 17:42:42 +0100 (MET) Date: Tue, 12 Jan 1999 17:42:42 +0100 (MET) From: Marcin Cieslak To: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-Reply-To: <199901120035.AAA60265@keep.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Brian Somers wrote: > Having said all that, I think it's still worth investing the time in > getting this working (time I haven't got at the moment I'm afraid). > It should be made run-time configurable (PacketAliasSetMode()) and > should default to disabled. I believe that a lot of the people that > use libalias are people with a small number of internal machines and > a small number of people using them. The ident module should get a > good hit rate. I would also be happy to see another kind of ident -> not just proxying ident to the machines behind the NAT, but reporting some string identifying the host being masqueraded. If an ident query comes for port SPORT, aliasing code looks up port SPORT and translates them onto the pair (DPORT, DHOST) where DHOST is the internal host name. Some users would like to see that ident daemon should query DHOST on the ident port and return it to the original sender. However, I would like also to see another way of handling ident queries (I guess it's much easier to implement) returning the predefined string (for example hostname but not neccesary) uniquely identifying the host behind NAT. This may be not what the security guys want, but this would be a handy way of identifying machine for LARTing purposes for example :) We can go further and report something like "user+host" in the ident response: giving "host" identifying the hidden machine and "user" resulting from the ident query on that machine. I think that all those modes should be configurable, at least at the compile time. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 09:44:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17068 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 09:44:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17063 for ; Tue, 12 Jan 1999 09:44:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA04999; Tue, 12 Jan 1999 09:43:13 -0800 (PST) (envelope-from dillon) Date: Tue, 12 Jan 1999 09:43:13 -0800 (PST) From: Matthew Dillon Message-Id: <199901121743.JAA04999@apollo.backplane.com> To: Peter Wemm Cc: "Daniel O'Connor" , hackers@FreeBSD.ORG, Andreas Braukmann , "Eric J. Chet" Subject: Re: What are the advantages of ELF kernels? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :AARGH!!!! This whole thread is making me break out in a cold sweat! :-) : :I don't know if Matt will take this as a compliment or an insult, but I :learned most of my early C programming from his code...... : :And I learned a lot of my early server and/or systems programming from :trying to backport dnet to run on a vax after Matt had switched to :something Sun-like and was byte order problems started to slip into the :code for exporting a unix tree to an Amiga mountable filesystem the packet :serial link. : :Cheers, :-Peter Ooohh... dnet. I remember dnet. Yah, there were a few byte ordering problems. There was also a bug somewhere in the protocol that I never was able to track down. That was also my first attempt at using SIGIO. What a disaster! A lot of people managed to get it to work, though, and I would occassionally get an email from some unix system administrator asking me what the frig was the little process his users were leaving running in the background! Heh heh. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 10:06:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19581 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 10:06:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19574 for ; Tue, 12 Jan 1999 10:06:43 -0800 (PST) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by samizdat.uucom.com (8.9.1/8.9.0) id NAA13759; Tue, 12 Jan 1999 13:05:55 -0500 To: hackers@FreeBSD.ORG Subject: 2.2.8 make world fails due to termcap from remote system From: Chris Shenton Date: 12 Jan 1999 13:05:55 -0500 Message-ID: <86u2xwfjss.fsf@samizdat.uucom.com> Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm at work on a Linux box ssh-ing home to my 2.2.8-STABLE box doing a make world. After three hours, it fails apparently due to trying to run "ex" and not recognizing my (remote) terminal type: [...] uudecode < /usr/src/share/tabset/xerox1730-lm.uu uudecode < /usr/src/share/tabset/zenith29.uu ===> share/termcap ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null ex: xterm-debian: unknown terminal type *** Error code 1 Debian Linux sets the terminal type to "xterm-debian" which noone else on the planet understands, but this shouldn't affect a non-terminal-based build of the world. Right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 11:12:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26996 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 11:12:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26961 for ; Tue, 12 Jan 1999 11:12:00 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA23402; Tue, 12 Jan 1999 19:11:24 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id SAA13888; Tue, 12 Jan 1999 18:21:26 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901121821.SAA13888@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Marcin Cieslak cc: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-reply-to: Your message of "Tue, 12 Jan 1999 17:42:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jan 1999 18:21:26 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > However, I would like also to see another way of handling > ident queries (I guess it's much easier to implement) > returning the predefined string (for example hostname but > not neccesary) uniquely identifying the host behind NAT. > This may be not what the security guys want, but this > would be a handy way of identifying machine for LARTing > purposes for example :) > > We can go further and report something like "user+host" > in the ident response: giving "host" identifying the hidden > machine and "user" resulting from the ident query on that > machine. > > I think that all those modes should be configurable, at > least at the compile time. This sounds nice, but it's more than just a packet translation mechanism. It requires the ability to create a new process on the fly and pass all the necessary information to it. It also requires libalias to create a channel to that process so that it can pick up the response and send it as a packet back to the ident requestor. This is non-trivial as it would require natd to select() at the top level rather than just reading from the divert socket. I don't think the functionality warrants the effort required, and I think the libalias code would be polluted too much as a result. > -- > << Marcin Cieslak // saper@system.pl >> > > ----------------------------------------------------------------- > SYSTEM Internet Provider http://www.system.pl -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 11:26:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28753 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 11:26:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28747 for ; Tue, 12 Jan 1999 11:26:53 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA25780 for ; Tue, 12 Jan 1999 11:26:14 -0800 (PST) Message-Id: <199901121926.LAA25780@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Problem with the lnc driver in 3.0-RELEASE X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Jan 1999 11:26:13 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Hitachi MX-133 laptop with the built-in lance ethernet, and the lnc driver under 3.0 won't properly initialize it. (I know, I'm late moving to 3.0 on this machine, but I had a hell of a semester when 3.0 came out.) The Hitachi has the Am79C970A PC/Net II chip in it, and works fine under 2.2.7 release with the lance driver patched with Robert Swindells patches. As far as I can tell from the mailing lists and CVS records and diffs, this patch was put into 3.0-RELEASE (and 2.2.8-RELEASE). Unfortunately the driver no longer runs my ethernet. Any ideas what changed in the driver that I missed, or elsewhere in the 3.0 system that would confuse the driver further? The error printed to the console and syslog is: lnc1: Initialisation failed It seems to come from the attach routine, but I don't know enough about the lance chips to be sure exactly what's failing. A somewhat clipped dmesg is attached (the buffer allocated in the GENERIC kernel doesnt seem to be big enough to hold the whole thing.) Any help would be appreciated. ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc [top fell out of the buffer] s=0 secondarybus=0 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x8086, dev=0x1234, revid=0x03 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip1: rev 0x03 on pci0.1.0 found-> vendor=0x100b, dev=0x0002, revid=0x01 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 000001f0, size 3 map[1]: type 4, range 32, base 000003f4, size 2 map[2]: type 4, range 32, base 00000170, size 3 map[3]: type 4, range 32, base 00000374, size 2 map[4]: type 4, range 32, base 0000fcd0, size 4 ide_pci0: rev 0x01 int a irq 14 on pci0.5.0 found-> vendor=0x1022, dev=0x2000, revid=0x16 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000fce0, size 5 map[1]: type 1, range 32, base fedffc00, size 5 lnc1: rev 0x16 int a irq 9 on pci0.18.0 lnc1: PCnet-PCI II address 00:c0:9f:00:51:45 found-> vendor=0x1013, dev=0x1110, revid=0xc1 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=255 chip2: rev 0xc1 int a irq 255 on pci0.19.0 found-> vendor=0x1013, dev=0x1110, revid=0xc1 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=0 chip3: rev 0xc1 int b irq 0 on pci0.19.1 found-> vendor=0x102c, dev=0x00e0, revid=0xc6 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base fd000000, size 24 vga0: rev 0xc6 on pci0.20.0 Probing for devices on the ISA bus: video: RTC equip. code:0x03, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c02e2, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 01 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 00 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 01 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 00 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0045 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: current command byte:0045 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 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): wd0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wcd0: 1377Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked wt0 not found at 0x300 mcd0: timeout getting status mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze: slot 0: no card in slot ze: slot 1: no card in slot ze0 not found at 0x300 zp: slot 0: no card in slot zp: slot 1: no card in slot zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 173761946 bytes/sec bzero() bandwidth = 653594771 bytes/sec apm0: disabled, not probed. imasks: bio c008c040, tty c007129a, net c007129a BIOS Geometries: 0:02b93f3f 0..697=698 cylinders, 0..63=64 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround new masks: bio c008c040, tty c007129a, net c007129a Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 63, end = 2818367, size 2818305 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 13:42:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14926 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 13:42:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14903 for ; Tue, 12 Jan 1999 13:42:32 -0800 (PST) (envelope-from dwhite@pond.net) Received: from localhost (dwhite@localhost) by guppy.pond.net (8.8.8/8.8.7) with SMTP id NAA23632 for ; Tue, 12 Jan 1999 13:38:20 -0800 (PST) Date: Tue, 12 Jan 1999 13:38:19 -0800 (PST) From: Doug White Reply-To: Doug White To: hackers@FreeBSD.ORG Subject: using raw sockets 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'd like some info on a more efficient way to talk to a raw Ethernet network. Right now I have an app that's using BPF for this. Transmissions works great but there's a ~1.8s lag between physical packet reception and when they appear on BPF, which is unacceptable for my purposes. And sending regular packets out (ie pings) will keep incoming packets from showing up until the output stream stops. Anyone know of a better way to handle this? Or is it time to hack on bpf? Also, BPF's select() needs work anyway, see kern/9355. Would that be a more productive target? Doug White | Pacific Crest Networks Internet: dwhite@pond.net | http://www.pond.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 13:54:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16152 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 13:54:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16127 for ; Tue, 12 Jan 1999 13:54:55 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: from localhost (nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) with ESMTP id NAA27048; Tue, 12 Jan 1999 13:53:46 -0800 (PST) Date: Tue, 12 Jan 1999 13:53:46 -0800 (PST) From: Joseph Lee To: Brian Somers cc: Eivind Eklund , freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-Reply-To: <199901120035.AAA60265@keep.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Brian Somers wrote: > AFAIK, the problem isn't solvable :-( Libalias needs to rewrite the > ident query, changing the destination IP to that of the correct > machine, and changing the embedded port number to the one originally > sent. To do this, libalias needs to identify the link table entry I've spent an amount of time on it and found it unsolvable due to the way sockets work, and the way ident verifies connections. There might be a way around, but I wouldn't know enough about it yet. Basically, given a query from some remote ip for a remote/local port pair, ident searches the kernel tables for a matching tcp connection out with the same remote ip, on the local port out. That's the crux. You can write something to catch the ident query, rewrite it, and then query the originating ip (bob) behind natd easily, but the tcp connection has to look like, to bob, in accept() that it originated from the remote ip (mary), or otherwise, there's no match in bob's kernel tables... So, the natd host (jack) can recreate the ident tcp connection to bob through a connect() call, as Eivind suggested, or using libident, by forking off libalias and doing so. However, then jack's packet's src ip, needs to be spoofed to look like it came from mary, otherwise bob couldn't match the connection's remote ip to anything in the kernel tables. Then, libalias would have to catch packets coming back without automatically forwarding it to mary first, and it all becomes some really complicated ball of wax for a solution. The other way is to extend bob's ident's PROXY query to support remote/local ip remote/local ip to be specified in query, but then it becomes insecure, and infeasible because all hosts behind jack would have to have their idents extended. So, the original tcp syn packet from mary needs to be directly forwarded to bob by jack, but can't be done because the port pairs are unknown until the connection gets accept()'d, which I think is too late by then... There probably is a solution, but it's beyond my current knowledge of tcp/ip. So, I basically paraphased Brian's comments, but with some extra details.. ^^ p.s. I've actually gotten queries to make it all the way to bob, from mary, by extracting the data from the query by mary, and making another ident query to bob through libident, but bob couldn't match the query because it originated from jack, not mary. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 14:00:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17061 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:00:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA17056 for ; Tue, 12 Jan 1999 14:00:14 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <60851(3)>; Tue, 12 Jan 1999 13:59:34 PST Received: by crevenia.parc.xerox.com id <177534>; Tue, 12 Jan 1999 13:59:25 -0800 From: Bill Fenner To: dwhite@pond.net, hackers@FreeBSD.ORG Subject: Re: using raw sockets Message-Id: <99Jan12.135925pst.177534@crevenia.parc.xerox.com> Date: Tue, 12 Jan 1999 13:59:18 PST Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What OS version, and what kind of ethernet card, are you using when you see the BPF symptoms that you mention? I've never seen either of the problems you describe. It seems to me that fixing bpf is a much better target than creating a whole new mechanism. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 14:19:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19535 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:19:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19530 for ; Tue, 12 Jan 1999 14:19:05 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA05830; Tue, 12 Jan 1999 15:18:30 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd005569; Tue Jan 12 15:18:14 1999 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA06290; Tue, 12 Jan 1999 15:18:07 -0700 (MST) From: Terry Lambert Message-Id: <199901122218.PAA06290@usr09.primenet.com> Subject: Re: Problems with 3.0 To: mike@smith.net.au (Mike Smith) Date: Tue, 12 Jan 1999 22:18:07 +0000 (GMT) Cc: rch@iserve.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199901120734.XAA01513@dingo.cdrom.com> from "Mike Smith" at Jan 11, 99 11:34:03 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 have been currently having problems with FreeBSD 3.0-RELEASE, and was > > hoping someone here might have an idea of what is causing this. Here's what > > is happening. > > > > /kernel: pid 22761 (httpd), uid 65534: exited on signal 11 > > > > This error will repeat itself over and over, untill I stop the process, and > > restart it. I'm not sure if it's a problem with apache though, as it has > > happened to inetd, and cron as well. At first I thought maybe it was a > > problem with the ram, so I've replaced that twice, still no luck. I'm > > getting ready to swap the CPU as well. Any ideas would be appeciated. > > The fact that the error repeats indicates that the cached copy of the > program's text has been corrupted. This typically requires bad RAM, > CPU or motherboard. Are you overclocking? Actually, no. All it requires is the VM system reclaiming a clean page from an in core object without telling the object about it. This can't happen for most things, but mmap seems immune from correct functioning in a lot of ways, and this happens to be one of them. The pages that get zapped are in the libc code section for the mmap'ed libc.so image. This probably has something to do with the fact that the same libc is mapped into multiple processes (e.g., here's some place where having aliases in your VM sucks out). Another one recently discovered is that it *appears* that you can map (read only) the same file twice letting the system decide where to put it (pass NULL as binding location), and the second time the system will return the same address as the first time, instead of doing the right thing and setting up the mapping at a different location. 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 Jan 12 14:23:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19882 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:23:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zoe.iserve.net (zoe.iserve.net [207.250.219.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19877 for ; Tue, 12 Jan 1999 14:23:37 -0800 (PST) (envelope-from rch@iserve.net) Received: from blackacid_nt (acidic.iserve.net [207.250.219.40]) by zoe.iserve.net (8.9.1/8.9.1) with SMTP id RAA09192 for ; Tue, 12 Jan 1999 17:23:03 -0500 (EST) Date: Tue, 12 Jan 1999 17:23:03 -0500 (EST) Message-Id: <3.0.32.19990112172331.00caac10@iserve.net> X-Sender: rch@iserve.net X-Mailer: Windows Eudora Pro Version 3.0 (32) To: hackers@FreeBSD.ORG From: Robert Hough Subject: More troubles... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a suggestion, I installed and ran cvsup, ran it, no problems... Ran make world, in hopes that it would aleviate some of my problems. However, when I tried a 'w' or 'who' I got an error. I figured, ok, maybe I need to update the kernel then. I recompile the generic kernel, and reboot. Now it's giving me 'Invalid Format' as it tries to boot up. I can type in kernel.JAN12 and it boots up just fine. Can someone tell me what I'm doing wrong here? I've compiled at least 15-20 kernels before, and have never gotten this error before. I've tried 4 times now, still no luck. :( (I'm starting to think a re-install is in order) __ _______ |__| __|.-----.----.--.--.-----. .-------------------------------. | |__ || -__| _| | | -__| | Robert Hough (rch@iserve.net) | |__|_______||_____|__| \___/|_____| | 317-802-3036 / 317-876-0846 | _____________________________________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 14:29:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20442 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:29:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20434 for ; Tue, 12 Jan 1999 14:29:23 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA12016; Tue, 12 Jan 1999 15:28:39 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd011978; Tue Jan 12 15:28:37 1999 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA06757; Tue, 12 Jan 1999 15:28:35 -0700 (MST) From: Terry Lambert Message-Id: <199901122228.PAA06757@usr09.primenet.com> Subject: Re: What are the advantages of ELF kernels? To: dcs@newsguy.com (Daniel C. Sobral) Date: Tue, 12 Jan 1999 22:28:35 +0000 (GMT) Cc: dervish@bantu.cl.msu.edu, dillon@apollo.backplane.com, hackers@FreeBSD.ORG In-Reply-To: <369B125D.F487B9@newsguy.com> from "Daniel C. Sobral" at Jan 12, 99 06:14:05 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 might be misleading here, but I'd think the Number One reason for > changing to Elf is the lack of availability of binutils for a.out. > Support for a.out has been abandoned in binutils (gcc tools). So, it > seriously impacted on FreeBSD's ability to upgrade the compiler > toolchain. > > As for the specifics on how elf is so much better than a.out, I > usually heard most arguments coming from Terry. :-) It's better because it enables future work which would otherwise be impossible. I don't buy the shared library arguments, since mmap is mmap, and the semantics of an executable page aren't determined by the file name the thing is mapped from. The one good thing about the shared library semantic changes is that it should be possible to use a Motif distribution for Solaris or Linux on FreeBSD, assuming that you fix FreeBSD to conform to the Solaris libc or Linux libc calling conventions, such that a Motif depending on one or the other can actually link against a FreeBSD libc (the Solaris one fails because they changed function names instead of introducing binary incompatabilities to support 64bit off_t, etc.). It's also a pity that ELF objects generated on a 3.0 system won't be usable on a 3.1 (or later, if things go as slow as they have been, lately) system, since binutils 2.9.1 made a gratuitous change in the object file layout. Too bad FreeBSD didn't go to 2.9.1 and skip over the bad format entirely, but whatever. For the most part, ELF buys you multiple sections. Multiple sections buy you the ability to apply semantics to sections based on their names, or on associate attribute bits. One of many examples is that you could put all of the device probe code into a specific section name, and once you probed the devices at boot time, discard and reclaim that memory which is currently lost. Another example is that you could attribute the code in the paging path as "non-pageable", and allow the entire rest of the kernel to be paged in and out. This would let you do what "eBSD" (BSDI's "embedded BSD") does: run in 2M or less of real memory. 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 Jan 12 14:31:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20987 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:31:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20936 for ; Tue, 12 Jan 1999 14:31:51 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA253669143; Tue, 12 Jan 1999 11:39:03 -0500 Date: Tue, 12 Jan 1999 11:39:03 -0500 (EST) From: Bill Fumerola To: Robert Hough Cc: hackers@FreeBSD.ORG Subject: Re: More troubles... In-Reply-To: <3.0.32.19990112172331.00caac10@iserve.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 Tue, 12 Jan 1999, Robert Hough wrote: > After a suggestion, I installed and ran cvsup, ran it, no problems... Ran > make world, in hopes that it would aleviate some of my problems. However, > when I tried a 'w' or 'who' I got an error. I figured, ok, maybe I need to > update the kernel then. I recompile the generic kernel, and reboot. Now > it's giving me 'Invalid Format' as it tries to boot up. I can type in > kernel.JAN12 and it boots up just fine. Can someone tell me what I'm doing > wrong here? I've compiled at least 15-20 kernels before, and have never > gotten this error before. I've tried 4 times now, still no luck. :( (I'm > starting to think a re-install is in order) Your kernel needs to be friendly with your userland. If you are going to update your kernel sources and build, you need to update your outher sources as well. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 14:37:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21935 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:37:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21928 for ; Tue, 12 Jan 1999 14:37:26 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id JAA08808; Wed, 13 Jan 1999 09:38:35 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901122238.JAA08808@cimlogic.com.au> Subject: Re: What are the advantages of ELF kernels? In-Reply-To: <199901122228.PAA06757@usr09.primenet.com> from Terry Lambert at "Jan 12, 1999 10:28:35 pm" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 13 Jan 1999 09:38:35 +1100 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > It's also a pity that ELF objects generated on a 3.0 system won't > be usable on a 3.1 (or later, if things go as slow as they have been, > lately) system, since binutils 2.9.1 made a gratuitous change in > the object file layout. Too bad FreeBSD didn't go to 2.9.1 and skip > over the bad format entirely, but whatever. We shipped binutils 2.9.1 with 3.0-RELEASE. We upgraded not long before 3.0-RELEASE was due. The upgrade caused compatibility problems on alpha, but obviously wasn't noticed on i386. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 14:53:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29896 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 14:53:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29879 for ; Tue, 12 Jan 1999 14:53:53 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.64]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA600A for ; Tue, 12 Jan 1999 23:53:15 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 13 Jan 1999 00:00:55 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Hackers Subject: tcpdump and localhost Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I got a question which is bothering me, well intriguing might be a better term for it. I have a fxp0 (Interl 100 Pro+) NIC and I have no cable attached to it as I am setting up the local LAN at home now. I wanted to test a simple ping on the localhost and watch with tcpdump. I got no response. This got me curious, because as far as I know, a ping to localhost never leaves the card and should thus be seen by the tcpdump. Or does tcpdump, when listening on a NIC, only pick up ethernet frames which have been sent over the wire? Thanks for any hints/enlightenments... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:02:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00757 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:02:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00750 for ; Tue, 12 Jan 1999 15:02:13 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.64]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6D39; Wed, 13 Jan 1999 00:01:34 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901122228.PAA06757@usr09.primenet.com> Date: Wed, 13 Jan 1999 00:09:08 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Terry Lambert Subject: Re: What are the advantages of ELF kernels? Cc: hackers@FreeBSD.ORG, dillon@apollo.backplane.com, dervish@bantu.cl.msu.edu, (Daniel C. Sobral) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-99 Terry Lambert wrote: >> I might be misleading here, but I'd think the Number One reason for >> changing to Elf is the lack of availability of binutils for a.out. >> Support for a.out has been abandoned in binutils (gcc tools). So, it >> seriously impacted on FreeBSD's ability to upgrade the compiler >> toolchain. > It's also a pity that ELF objects generated on a 3.0 system won't > be usable on a 3.1 (or later, if things go as slow as they have been, > lately) system, since binutils 2.9.1 made a gratuitous change in > the object file layout. Too bad FreeBSD didn't go to 2.9.1 and skip > over the bad format entirely, but whatever. I do hope that the transition of the new binutils have already taken? Or is going to take place before we fork off? (It might be that I missed some commitlogs, but I try to keep up =) --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:03:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00837 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:03:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00832 for ; Tue, 12 Jan 1999 15:03:05 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.1/8.9.1) id PAA00860; Tue, 12 Jan 1999 15:02:29 -0800 (PST) (envelope-from mph) Date: Tue, 12 Jan 1999 15:02:29 -0800 From: Matthew Hunt To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Hackers Subject: Re: tcpdump and localhost Message-ID: <19990112150229.A804@wopr.caltech.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Wed, Jan 13, 1999 at 12:00:55AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 12:00:55AM +0100, Jeroen Ruigrok/Asmodai wrote: > I got no response. This got me curious, because as far as I know, a ping to > localhost never leaves the card and should thus be seen by the tcpdump. Or A ping to localhost will travel on the loopback interface, not the Ethernet card. Try "tcpdump -i lo0". -- Matthew Hunt * UNIX is a lever for the intellect. -J.R. Mashey http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:22:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03168 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:22:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03163 for ; Tue, 12 Jan 1999 15:22:15 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA15297; Tue, 12 Jan 1999 15:34:57 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd015255; Tue Jan 12 15:34:54 1999 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA07104; Tue, 12 Jan 1999 15:34:53 -0700 (MST) From: Terry Lambert Message-Id: <199901122234.PAA07104@usr09.primenet.com> Subject: Re: More troubles... To: billf@chc-chimes.com (Bill Fumerola) Date: Tue, 12 Jan 1999 22:34:53 +0000 (GMT) Cc: rch@iserve.net, hackers@FreeBSD.ORG In-Reply-To: from "Bill Fumerola" at Jan 12, 99 11:39:03 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 > Your kernel needs to be friendly with your userland. If you are going to > update your kernel sources and build, you need to update your outher > sources as well. Will the userland please keep its grubby hands out of the kernel's undershorts? Thanks... 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 Jan 12 15:30:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03973 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:30:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03968 for ; Tue, 12 Jan 1999 15:30:20 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.64]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA503; Wed, 13 Jan 1999 00:29:46 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990112150229.A804@wopr.caltech.edu> Date: Wed, 13 Jan 1999 00:37:36 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Matthew Hunt Subject: Re: tcpdump and localhost Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-99 Matthew Hunt wrote: > On Wed, Jan 13, 1999 at 12:00:55AM +0100, Jeroen Ruigrok/Asmodai wrote: > >> I got no response. This got me curious, because as far as I know, a ping >> to localhost never leaves the card and should thus be seen by tcpdump. > > A ping to localhost will travel on the loopback interface, not the > Ethernet card. > > Try "tcpdump -i lo0". D'oh... OK, and if I ping the IP address associated with the NIC then it gets put on the wire right? --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:32:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04118 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:32:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04110 for ; Tue, 12 Jan 1999 15:32:10 -0800 (PST) (envelope-from tague@netscape.com) Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42]) by netscape.com (8.8.5/8.8.5) with ESMTP id PAA26537 for ; Tue, 12 Jan 1999 15:31:15 -0800 (PST) Received: from netscape.com ([208.12.36.157]) by tintin.mcom.com (Netscape Messaging Server 4.01) with ESMTP id F5H00400.5LE; Tue, 12 Jan 1999 15:31:16 -0800 Message-ID: <369BDB22.FB41F328@netscape.com> Date: Tue, 12 Jan 1999 15:30:42 -0800 From: tague@netscape.com (Tague Griffith) Reply-To: tague@netscape.com Organization: Netscape Communications X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en,ja,de,zh-TW MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: problems with setlocale on freebsd 3.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'm trying to get gtk-1.1.12 up and running with support for japanese input. one of the problems that i'm running into is the behavior of setlocale. according to the man page setlocale should in theory allow LC_CTYPE to be set to a locale other than C or POSIX, but in practice setlocale won't let me set LC_CTYPE to anything but POSIX or C. i'm currious if anyone has a work around for some of these problems for getting japanese apps up and running. /t -- ---------------------------------------------------------- tague griffith (tague@netscape.com) client internationalization To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:35:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04363 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:35:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04357 for ; Tue, 12 Jan 1999 15:35:22 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 100DKa-000APT-00 for hackers@freebsd.org; Wed, 13 Jan 1999 01:34:40 +0200 From: Sheldon Hearn To: hackers@FreeBSD.ORG Subject: what was the old devstat interface's dk_wds? Date: Wed, 13 Jan 1999 01:34:40 +0200 Message-ID: <40018.916184080@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm trying to teach sysutils/xosview about the new kernel device statistics interface so that its DiskMeter will work for CURRENT. At the moment, it expects FreeBSD to use "the older method" for pulling device statistics out of the kernel. I'm getting to grips with devstat(3) and the source for iostat, but I still need to understand how "the older method" worked, so that I can translate what xosview wants to do into what it should do. I would greatly appreciate it if someone could help me with one of the following: 1) A pointer to the devstat(3) manpage's predecessor. OR 2) An explanation of the timeframe context for a comment like this one from STABLE's /usr/include/sys/dkstat.h: extern long dk_wds[DK_NDRIVE]; /* # blocks of 32*16-bit words transferred */ It's the number of 32*16-bit words transferred since when? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:36:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04595 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:36:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wireless.net (wireless.net [207.137.156.159] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04586 for ; Tue, 12 Jan 1999 15:36:42 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id PAA21176; Tue, 12 Jan 1999 15:52:03 -0800 (PST) Date: Tue, 12 Jan 1999 15:52:03 -0800 (PST) From: Bernie Doehner To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? In-Reply-To: <199901121757.JAA05222@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is it that under bash's ulimit -v, the swap space utilization is the sum of the data segment size and the stack size? Is this correct / valid for all shells (not just bash, which explicitly prints this out as the per process swap space limitation)? Thanks. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:39:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04807 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:39:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wireless.net (wireless.net [207.137.156.159] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04802 for ; Tue, 12 Jan 1999 15:39:18 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id PAA21184; Tue, 12 Jan 1999 15:54:38 -0800 (PST) Date: Tue, 12 Jan 1999 15:54:38 -0800 (PST) From: Bernie Doehner To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? 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, 12 Jan 1999, Bernie Doehner wrote: > Why is it that under bash's ulimit -v, the swap space utilization is the > sum of the data segment size and the stack size? Sorry, I should have said, I understand the reason for this (you cannot swap out more than entire size of the program). The question should rather have been, WHY/HOW can the value for swap space limitation not be reduced to less than data segment + stack? Bernie > Is this correct / valid for all shells (not just bash, which explicitly > prints this out as the per process swap space limitation)? > > Thanks. > > Bernie > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 15:44:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05524 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:44:02 -0800 (PST) (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 PAA05499 for ; Tue, 12 Jan 1999 15:43:54 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 11939 invoked by uid 1001); 12 Jan 1999 23:43:18 +0000 (GMT) To: asmodai@wxs.nl Cc: mph@pobox.com, hackers@FreeBSD.ORG Subject: Re: tcpdump and localhost In-Reply-To: Your message of "Wed, 13 Jan 1999 00:37:36 +0100 (CET)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 13 Jan 1999 00:43:18 +0100 Message-ID: <11937.916184598@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, and if I ping the IP address associated with the NIC then it gets put > on the wire right? If you ping the IP address associated with the NIC from *the host itself*, it won't be put on the wire. You have to ping it from another host. 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 Tue Jan 12 15:48:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06360 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:48:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06324 for ; Tue, 12 Jan 1999 15:48:47 -0800 (PST) (envelope-from dwhite@pond.net) Received: from localhost (dwhite@localhost) by guppy.pond.net (8.8.8/8.8.7) with SMTP id PAA07543; Tue, 12 Jan 1999 15:43:47 -0800 (PST) Date: Tue, 12 Jan 1999 15:43:47 -0800 (PST) From: Doug White To: Bill Fenner cc: hackers@FreeBSD.ORG Subject: Re: using raw sockets In-Reply-To: <99Jan12.135925pst.177534@crevenia.parc.xerox.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, 12 Jan 1999, Bill Fenner wrote: > What OS version, and what kind of ethernet card, are you using when you > see the BPF symptoms that you mention? I've never seen either of the > problems you describe. It seems to me that fixing bpf is a much better > target than creating a whole new mechanism. I'm on 2.2.7-RELEASE with a 3Com 3c509 (ep0). I'm using a program I wrote that's derived from ppp(8), which operates in a select() loop. I don't know exactly where the holdup is, but from my debugging output I don't think it's my code (it reads the packets I send out immediately, just not any inbound packets). It very well could be the remote router, but looking at it's logs it's responding to my pings immediately, but bpf doesn't register them until I stop sending packets for a few moments. It could also be the DSL modem I'm using for testing. An independent tcpdump on the same interface shows the same behavior. I'm assuming the timestamps are generated by tcpdump, or are they the real packet timestamps? I'm going to try this on a 3.0-generation machine with a de-based card (if I can find one and if the P100 workstation I have has enough slots left). Doug White | Pacific Crest Networks Internet: dwhite@pond.net | http://www.pond.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 16:26:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13216 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:26:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13208 for ; Tue, 12 Jan 1999 16:26:42 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA10945; Tue, 12 Jan 1999 17:26:06 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd010917; Tue Jan 12 17:26:01 1999 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA15418; Tue, 12 Jan 1999 17:25:59 -0700 (MST) From: Terry Lambert Message-Id: <199901130025.RAA15418@usr08.primenet.com> Subject: Re: What are the advantages of ELF kernels? To: jb@cimlogic.com.au (John Birrell) Date: Wed, 13 Jan 1999 00:25:59 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199901122238.JAA08808@cimlogic.com.au> from "John Birrell" at Jan 13, 99 09:38:35 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 > > It's also a pity that ELF objects generated on a 3.0 system won't > > be usable on a 3.1 (or later, if things go as slow as they have been, > > lately) system, since binutils 2.9.1 made a gratuitous change in > > the object file layout. Too bad FreeBSD didn't go to 2.9.1 and skip > > over the bad format entirely, but whatever. > > We shipped binutils 2.9.1 with 3.0-RELEASE. We upgraded not long before > 3.0-RELEASE was due. The upgrade caused compatibility problems on > alpha, but obviously wasn't noticed on i386. Cool. At least FreeBSD-Native software won't have the same problem that some Linux-Native software has had. I had thought the decision was to delay the upgrade until after the 3.0 release. I'm glad I was wrong. 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 Jan 12 16:31:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13889 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:31:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13882 for ; Tue, 12 Jan 1999 16:31:54 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA13098; Tue, 12 Jan 1999 17:31:11 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd012984; Tue Jan 12 17:31:05 1999 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA15567; Tue, 12 Jan 1999 17:30:51 -0700 (MST) From: Terry Lambert Message-Id: <199901130030.RAA15567@usr08.primenet.com> Subject: Re: limiting per process swap space utilization like Solaris ulimit? To: bad@wireless.net (Bernie Doehner) Date: Wed, 13 Jan 1999 00:30:51 +0000 (GMT) Cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG In-Reply-To: from "Bernie Doehner" at Jan 12, 99 03:52:03 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 > Why is it that under bash's ulimit -v, the swap space utilization is the > sum of the data segment size and the stack size? Read-only pages don't need to be backed by swap? > Is this correct / valid for all shells (not just bash, which explicitly > prints this out as the per process swap space limitation)? On machines where the program image is not used as a read-only swap store, this would be different. You may have to install an old copy of Xenix or SVR3.2 to find such a machine, though... 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 Jan 12 16:40:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15293 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:40:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15223 for ; Tue, 12 Jan 1999 16:40:04 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA16181; Tue, 12 Jan 1999 17:39:19 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd016057; Tue Jan 12 17:39:15 1999 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA15783; Tue, 12 Jan 1999 17:39:03 -0700 (MST) From: Terry Lambert Message-Id: <199901130039.RAA15783@usr08.primenet.com> Subject: Re: limiting per process swap space utilization like Solaris ulimit? To: bad@wireless.net (Bernie Doehner) Date: Wed, 13 Jan 1999 00:39:03 +0000 (GMT) Cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG In-Reply-To: from "Bernie Doehner" at Jan 12, 99 03:54:38 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 > > Why is it that under bash's ulimit -v, the swap space utilization is the > > sum of the data segment size and the stack size? > > Sorry, I should have said, I understand the reason for this (you cannot > swap out more than entire size of the program). The question should rather > have been, WHY/HOW can the value for swap space limitation not be reduced > to less than data segment + stack? OK. Basically, any page that can be dirtied will potentially have to take up swap space for it to be swapped out if it's dirty. So the minimum size of swap space necessary is data segment size plus stack size (data segment size including any allocated heap space via sbrk(2)). Consider the alternatives if you could limit swap size to less than this: If the kernel needs to make the pages non-resident to make room for other pages, it has to: (A) Kill the program, since it's not allowed to swap those pages. (B) Keep the pages in memory instead of swapping them, reducing teh available physical memory for all other programs (open itself to denial of service attack by some schmuck setting the limit to zero and then sbrk'ing as much memory as possible until physical memory is exhausted). Not a good thing. It *might* be useful to limit swap space to larger than the current usage, but only in the case that that limit is not applied, as above, but to an agregate of the data space size and the stack size. The advantage of this would be one more frob for users to tweak. The disadvantage is that it's more work to enforce this when allocating backing pages in the trap handler, making page allocation slower, with the only benefit from the tradeoff being another frob. 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 Jan 12 16:40:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15546 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:40:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15527 for ; Tue, 12 Jan 1999 16:40:34 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <61513(4)>; Tue, 12 Jan 1999 16:39:44 PST Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id QAA06354; Tue, 12 Jan 1999 16:39:40 -0800 (PST) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199901130039.QAA06354@mango.parc.xerox.com> To: Doug White cc: Bill Fenner , hackers@FreeBSD.ORG Subject: Re: using raw sockets In-reply-to: Your message of "Tue, 12 Jan 1999 15:43:47 PST." Date: Tue, 12 Jan 1999 16:39:40 PST From: Bill Fenner Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message you write: >I'm assuming the timestamps are generated by tcpdump, >or are they the real packet timestamps? The timestamp that tcpdump prints is the timestamp that bpf attaches (i.e. when the driver calls bpf_[m]tap() ). Can you compare that timestamp against gettimeofday(), to see if it looks like the latency is in the bpf buffer? >From a brief inspection of the bpf code, it looks like bpf won't wake up a selecting process until the buffer is almost full. Have you tried using the BIOCIMMEDIATE ioctl? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 16:46:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16744 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:46:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16731 for ; Tue, 12 Jan 1999 16:46:04 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA08179; Wed, 13 Jan 1999 11:14:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901121743.JAA04999@apollo.backplane.com> Date: Wed, 13 Jan 1999 11:15:30 +1030 (CST) From: "Daniel O'Connor" To: Matthew Dillon Subject: Re: What are the advantages of ELF kernels? Cc: "Eric J. Chet" , Andreas Braukmann , hackers@FreeBSD.ORG, Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-99 Matthew Dillon wrote: > Ooohh... dnet. I remember dnet. Yah, there were a few byte ordering > problems. There was also a bug somewhere in the protocol that I never > was able to track down. That was also my first attempt at using SIGIO. > What a disaster! A lot of people managed to get it to work, though, and > I would occassionally get an email from some unix system administrator > asking me what the frig was the little process his users were leaving > running in the background! Heh heh. Yep.. I battled with it and LOST! Evil prgram! :) Then along came SLirp and TIA, and PPP stacks.. All these modern conveniences.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 16:51:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17988 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:51:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wireless.net (wireless.net [207.137.156.159] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17968 for ; Tue, 12 Jan 1999 16:51:12 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id RAA21479; Tue, 12 Jan 1999 17:06:32 -0800 (PST) Date: Tue, 12 Jan 1999 17:06:32 -0800 (PST) From: Bernie Doehner To: Terry Lambert cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? In-Reply-To: <199901130030.RAA15567@usr08.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 Wed, 13 Jan 1999, Terry Lambert wrote: > > Why is it that under bash's ulimit -v, the swap space utilization is the > > sum of the data segment size and the stack size? > > Read-only pages don't need to be backed by swap? Actualy I already asked the very same question in a different forum. I assume the text segment is NOT swapped out because it is referenced way TOO often to be practical/efficient to swap out? > > Is this correct / valid for all shells (not just bash, which explicitly > > prints this out as the per process swap space limitation)? > > On machines where the program image is not used as a read-only > swap store, this would be different. You may have to install an > old copy of Xenix or SVR3.2 to find such a machine, though... > Actualy I think Solaris does this too.. Thanks. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 19:35:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02797 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 19:35:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02731 for ; Tue, 12 Jan 1999 19:35:30 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA22496 for hackers@FreeBSD.ORG; Wed, 13 Jan 1999 04:34:37 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E91D01509; Wed, 13 Jan 1999 00:24:49 +0100 (CET) Date: Wed, 13 Jan 1999 00:24:49 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: X question Message-ID: <19990113002449.A94530@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Daniel Hauer on Sun, Jan 10, 1999 at 03:09:28PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Daniel Hauer: > root in it to run an app as root, (cvsup for example) I get an "unable to > open display localhost:0" error message. What have I missed? I haven't tried sudo recently to say but my own equivalent, named Calife[1], doesn't have this problem. It will ask you for your password then fork a shell with the new uid (generally root). ----- [1] -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 19:42:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05067 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 19:42:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05054 for ; Tue, 12 Jan 1999 19:42:07 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id VAA14056 for freebsd-hackers@freebsd.org; Tue, 12 Jan 1999 21:41:32 -0600 (CST) From: Mohit Aron Message-Id: <199901130341.VAA14056@cs.rice.edu> Subject: Performance counters on Pentium Pro's To: freebsd-hackers@FreeBSD.ORG Date: Tue, 12 Jan 1999 21:41:32 -0600 (CST) 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 Hi, it seems that the driver for reading Pentium Pro performance counters in FreeBSD-2.2.6 doesn't work (it works with a Pentium though). I've already configured and compiled my kernel with support for the driver and I'm trying to read the data cache misses. Below are some sample commands with the example program provided in /usr/share/examples/perfmon. # ./perfmon -o -u -e -l 2 -s 1 72 1: 3298535393077 2: 3298535358033 total: 6597070751110.000000 mean: 3298535375555.000000 clocks (at 299-MHz): 603885293 # ./perfmon -o -u -e -l 2 -s 1 0 1: 3298534883328 2: 3298534883328 total: 6597069766656.000000 mean: 3298534883328.000000 clocks (at 299-MHz): 603491159 # ./perfmon -o -u -l 2 -s 1 72 1: 3298535418313 2: 3298535807953 total: 6597071226266.000000 mean: 3298535613133.000000 clocks (at 299-MHz): 603927055 Notice that using event 72 (or 0x48 as suggested in /usr/include/machine/perfmon.h for reading data cache misses) seems to throw out a large number. This number seems to remain relatively unchanged when I use other events (the 2nd example above uses 0). In fact the output of the program even seems to be similar when I don't use the '-e' flag which is supposed to count the number of events rather than their duration. I've also contacted the person who wrote the code (Garrett Wollman) and he agrees that he had some questionable results with Pentium Pro in the past but never tracked them down. Does someone have a fix for this problem ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 19:46:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06659 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 19:46:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06647 for ; Tue, 12 Jan 1999 19:46:46 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA29985; Tue, 12 Jan 1999 20:46:11 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd029902; Tue Jan 12 20:46:07 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA07058; Tue, 12 Jan 1999 20:45:55 -0700 (MST) From: Terry Lambert Message-Id: <199901130345.UAA07058@usr06.primenet.com> Subject: Re: limiting per process swap space utilization like Solaris ulimit? To: bad@wireless.net (Bernie Doehner) Date: Wed, 13 Jan 1999 03:45:55 +0000 (GMT) Cc: tlambert@primenet.com, dillon@apollo.backplane.com, hackers@FreeBSD.ORG In-Reply-To: from "Bernie Doehner" at Jan 12, 99 05:06:32 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 > > > Why is it that under bash's ulimit -v, the swap space utilization is the > > > sum of the data segment size and the stack size? > > > > Read-only pages don't need to be backed by swap? > > Actualy I already asked the very same question in a different forum. I > assume the text segment is NOT swapped out because it is referenced way > TOO often to be practical/efficient to swap out? No; it's mostly not swapped out because it's referenced sufficiently frequently that it never gets tot he end of the LRU list. If, however, your system is starving for memory, or you have a lot of dirty data being accessed so that it's at the front of the LRU, clean text pages will, in fact, be discarded, and then read back in as needed. [ ... A combination quota on swap and vm ... ] > Actualy I think Solaris does this too.. If you mean "doesn't enforce a quota", yeah. The closest thing you could get would be "memoryuse", but that includes code pages, too. See the csh "limit" command instead of the bash command. ;-). 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 Jan 12 20:03:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11083 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 20:03:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11046 for ; Tue, 12 Jan 1999 20:02:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA49342; Tue, 12 Jan 1999 21:01:57 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901130401.VAA49342@panzer.plutotech.com> Subject: Re: what was the old devstat interface's dk_wds? In-Reply-To: <40018.916184080@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 13, 99 01:34:40 am" To: axl@iafrica.com (Sheldon Hearn) Date: Tue, 12 Jan 1999 21:01:57 -0700 (MST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Sheldon Hearn wrote... > > Hi folks, > > I'm trying to teach sysutils/xosview about the new kernel device > statistics interface so that its DiskMeter will work for CURRENT. At the > moment, it expects FreeBSD to use "the older method" for pulling device > statistics out of the kernel. > > I'm getting to grips with devstat(3) and the source for iostat, but I > still need to understand how "the older method" worked, so that I can > translate what xosview wants to do into what it should do. > > I would greatly appreciate it if someone could help me with one of the > following: > > 1) A pointer to the devstat(3) manpage's predecessor. I don't think there was a predecessor. You'll have to read the source. Check out a -current from sometime before Sept. 15th, 1998. > OR > > 2) An explanation of the timeframe context for a comment like this one > from STABLE's /usr/include/sys/dkstat.h: > > extern long dk_wds[DK_NDRIVE]; /* # blocks of 32*16-bit words transferred */ > > It's the number of 32*16-bit words transferred since when? Since boot, I believe. One of the problems with that is that it's a 32 bit signed value on i386, and so would probably wrap every so often on a server with a lot of I/O going on. devstat uses 64 bit counters, so it's much more difficult for them to wrap. There are a couple of other ports that use the devstat code, in addition to systat(1), vmstat(8), and iostat(8). Check out xperfmon, and xsysinfo. I think they both support devstat. If you've got questions, just ask. I wrote the devstat code. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 12 23:43:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15551 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 23:43:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15533 for ; Tue, 12 Jan 1999 23:43:35 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id UAA28121; Wed, 13 Jan 1999 20:42:59 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id UAA01417; Wed, 13 Jan 1999 20:42:53 +1300 (NZDT) (envelope-from jabley) Date: Wed, 13 Jan 1999 20:42:53 +1300 From: Joe Abley To: Andrzej Bialecki Cc: "Daniel C. Sobral" , Mike Smith , freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990113204253.D1312@clear.co.nz> References: <369B29E8.335B11E5@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Andrzej Bialecki on Tue, Jan 12, 1999 at 02:25:52PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, Has anybody had a chance to look at the boot help merge script I posted the other day? Just interested as to whether I had got the right end of the stick. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 00:17:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23616 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 00:17:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23609 for ; Wed, 13 Jan 1999 00:17:53 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.43]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3333; Wed, 13 Jan 1999 09:17:15 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <11937.916184598@verdi.nethelp.no> Date: Wed, 13 Jan 1999 09:24:56 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: sthaug@nethelp.no Subject: Re: tcpdump and localhost Cc: hackers@FreeBSD.ORG, mph@pobox.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-99 sthaug@nethelp.no wrote: >> OK, and if I ping the IP address associated with the NIC then it gets >> put >> on the wire right? > > If you ping the IP address associated with the NIC from *the host > itself*, > it won't be put on the wire. You have to ping it from another host. Aha thanks... So I needed to tcpdump lo0 and ping fxp0's IP address... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 02:28:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04397 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 02:28:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04354 for ; Wed, 13 Jan 1999 02:28:18 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id LAA16293; Wed, 13 Jan 1999 11:31:48 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 13 Jan 1999 11:31:48 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Joe Abley cc: "Daniel C. Sobral" , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: FICL and setting BTX variables In-Reply-To: <19990113204253.D1312@clear.co.nz> 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, 13 Jan 1999, Joe Abley wrote: > Hi again, > > Has anybody had a chance to look at the boot help merge script I posted the > other day? Just interested as to whether I had got the right end of the stick. Yes, I tried it. There are several things which should be corrected - see the diffs attached below. Besides obvious errors, I think we should preserve blank lines inside the help topics in order to improve readability. The diffs are between loader.help generated with perl script, and loader.help1 generated from the same sources by your awk script, with command: diff -u --ignore-space-change loader.help loader.help1 Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- --- loader.help Wed Jan 13 11:14:28 1999 +++ loader.help1 Wed Jan 13 11:15:30 1999 @@ -24,11 +24,7 @@ Emits , with no trailing newline if -n is specified. This is most useful in conjunction with scripts and the '@' line prefix. - Variables are substituted by prefixing them with $, eg. - - echo Current device is $currdev - will print the current device. ################################################################################ @@ -43,14 +39,12 @@ # Thelp DDisplay command help help [topic [subtopic]] - ? + ? The help command displays help on commands and their usage. - In command help, a term enclosed with <...> indicates a value as described by the term. A term enclosed with [...] is optional, and may not be required by all forms of the command. - Some commands may not be availalble. Use the '?' command to list most available commands. @@ -62,7 +56,6 @@ Loads the module contained in into memory. If no other modules are loaded, must be a kernel or the command will fail. - If -t is specified, the module is loaded as raw data of , for later use by the kernel or other modules. may be any string. @@ -73,7 +66,6 @@ Displays a listing of files in the directory , or the root directory of the current device if is not specified. - The -l argument displays file sizes as well; the process of obtaining file sizes on some media may be very slow. @@ -100,7 +92,6 @@ Scan for Plug-and-Play devices. This command is normally automatically run as part of the boot process, in order to dynamically load modules required for system operation. - If the -v argument is specified, details on the devices found will be printed. @@ -113,10 +104,8 @@ -t argument is specified, it will return nothing if no input has been received after seconds. (Any keypress will cancel the timeout). - If -p is specified, is printed before reading input. No newline is emitted after the prompt. - If a variable name is supplied, the variable is set to the value read, less any terminating newline. @@ -131,8 +120,8 @@ # Tset DSet a variable set - set = + set = The set command is used to set variables. ################################################################################ @@ -240,8 +229,6 @@ Variable substitution is performed on the prompt. The default prompt can be set with: - set prompt=\$currdev> - ################################################################################ # Tset Srootdev DSet the root filesystem @@ -258,7 +245,6 @@ Displays the value of , or all variables if not specified. Multiple paths can be separated with a semicolon. - See the set command for a list of some variables. ################################################################################ @@ -268,15 +254,9 @@ The entire contents of are read into memory before executing commands, so it is safe to source a file from removable media. - A number of modifiers may be prefixed to commands within a script file to alter their behaviour: - @ Suppresses the printing of the command when executed. - - - Prevents the script from terminating if the command returns - an error. - ################################################################################ # Tunload DRemove all modules from memory @@ -290,6 +270,4 @@ unset If allowed, the named variable's value is discarded and the variable - is removed. -################################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 02:45:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10214 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 02:45:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10189 for ; Wed, 13 Jan 1999 02:45:32 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with SMTP id LAA26263; Wed, 13 Jan 1999 11:45:16 +0100 (MET) Date: Wed, 13 Jan 1999 11:45:15 +0100 (MET) From: Marcin Cieslak To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-Reply-To: <199901121821.SAA13888@keep.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Brian Somers wrote: > This sounds nice, but it's more than just a packet translation > mechanism. It requires the ability to create a new process on the > fly and pass all the necessary information to it. It also requires > libalias to create a channel to that process so that it can pick up > the response and send it as a packet back to the ident requestor. > This is non-trivial as it would require natd to select() at the top > level rather than just reading from the divert socket. I think that ident should be made by a separate daemon, like midentd. The only problem with libalias is to make information about proxified connections available to other processes. If aliasing were done in kernel, it would be ioctl() or /proc or whatever. Since it is not, I suggest using a named pipe or other form of IPC (control socket?) in order to allow ident - and perhaps others processes interested - to gain information about current network translation table. Perhaps we should publish this information via sysctl(8) or SNMP MIB. Of course, information about NAT should be exposed carefully since it is used as a way of securing the internal network against the outernet. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 02:53:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13222 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 02:53:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13208 for ; Wed, 13 Jan 1999 02:53:35 -0800 (PST) (envelope-from caroline.beauchamps@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur (local) with SMTP; Wed, 13 Jan 1999 10:52:07 +0000 Received: from mussel.futures.bt.co.uk (actually mussel) by rambo with SMTP (PP); Wed, 13 Jan 1999 10:56:03 +0000 Received: by mussel.futures.bt.co.uk with Microsoft Exchange (IMC 4.0.837.3) id <01BE3EE1.FB147C20@mussel.futures.bt.co.uk>; Wed, 13 Jan 1999 10:46:31 -0000 Message-ID: From: Caroline Beauchamps To: "'freebsd-hackers@freebsd.org'" Subject: no buffer space available Date: Wed, 13 Jan 1999 10:57:30 -0000 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have two identical PCMCIA wavelan cards wlp0, and I configured them the same way. I have also a waveLAN ISA card from Lucent. One of the PCMCIA is working fine, and it can ping the ISA card. The other wlp0 card can only receive ICMP packets , but it cannot transmit...(I checked that with tcpdump). It can ping its own IP address, but not the other ones. When I try to ping the other IP address, I get the message: "ping : no buffer space available " The only difference I could notice between the two cards wlp0 is when I use the command: ifconfig -a The card which doesn't work has the flag : OACTIVE I also tried to do ifconfig wlp0 down and up, but I was still unsuccessful. Do you know how to remove this flag ? Do you have an idea why one of the card is working and not the other one ? Should I change the drivers for wlp0 ? I use the one provided in 2.2.6 Thanks for your help. Caroline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 02:55:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14175 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 02:55:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14158 for ; Wed, 13 Jan 1999 02:55:42 -0800 (PST) (envelope-from debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id LAA14182 for ; Wed, 13 Jan 1999 11:55:15 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa14180; Wed Jan 13 11:55:13 1999 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id LAA03645 for ; Wed, 13 Jan 1999 11:46:44 +0100 Original: Received: from kryptokom.de (localhost [127.0.0.1]) by borg.kryptokom.de (8.8.8/8.8.8) with ESMTP id MAA16269 for ; Wed, 13 Jan 1999 12:08:08 +0100 (CET) (envelope-from eT@kryptokom.de) Message-ID: <369C7E94.C9242BCD@kryptokom.de> Date: Wed, 13 Jan 1999 12:08:04 +0100 From: eT Organization: KryptoKom GmbH X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-19980804-SNAP i386) X-Accept-Language: en MIME-Version: 1.0 To: Hackers FreeBSD Subject: security mailing lists Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, can anyone out there suggest some network security related mailing lists? more specifically for ipsec [and] freebsd? thanks eT -- Etienne de Bruin; eT@kryptokom.de; edebruin@iname.com "my soul is full of gold and precious metals" - hothouse flowers, forever more. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 05:08:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28436 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 05:08:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28230 for ; Wed, 13 Jan 1999 05:07:11 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem39.masternet.it [194.184.65.49]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id NAA13322 for ; Wed, 13 Jan 1999 13:49:09 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990113134850.009484f0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 13 Jan 1999 13:57:06 +0100 To: hackers@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: What are the advantages of ELF kernels? In-Reply-To: <199901121404.WAA66113@spinner.netplex.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 22.04 12/01/99 +0800, you wrote: > >AARGH!!!! This whole thread is making me break out in a cold sweat! :-) > >I don't know if Matt will take this as a compliment or an insult, but I >learned most of my early C programming from his code...... > >And I learned a lot of my early server and/or systems programming from >trying to backport dnet to run on a vax after Matt had switched to >something Sun-like and was byte order problems started to slip into the >code for exporting a unix tree to an Amiga mountable filesystem the packet >serial link. Amiga was an incredible system and we (amiga users) were a wonderfull "race" :-) My "little-used Amiga is still here, sitting in a corner", perhaps in the future her 68040 will kick again. Sorry for the off-topics (it was my first and the last:-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:13:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04493 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:13:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04404 for ; Wed, 13 Jan 1999 11:13:31 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA51655; Wed, 13 Jan 1999 09:52:19 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901131652.JAA51655@panzer.plutotech.com> Subject: Re: what was the old devstat interface's dk_wds? In-Reply-To: <92363.916241941@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 13, 99 05:39:01 pm" To: axl@iafrica.com (Sheldon Hearn) Date: Wed, 13 Jan 1999 09:52:19 -0700 (MST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Sheldon Hearn wrote... > > > On Tue, 12 Jan 1999 21:01:57 MST, "Kenneth D. Merry" wrote: > > > There are a couple of other ports that use the devstat code, in > > addition to systat(1), vmstat(8), and iostat(8). Check out xperfmon, > > and xsysinfo. think they both support devstat. > > Thanks, Kenneth. > > Looking at systat gave me enough to figure out what was needed. So much > so that I shamelessly borrowed its code and changed all of 5 lines. ;) Just remember to give credit if you swipe code. > One question. If buildmatch is passed "da" as match_str, what devices > will I end up selecting? Just SCSI and IDE disk drives? I ask because I > don't really know what "Direct Access devices" does and doesn't include. You'll end up selecting any sort of disk drive. That includes SCSI and IDE disks, and any disks that happen to be on a different type of interface. It doesn't include optical disks, though. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:16:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05426 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:16:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05358 for ; Wed, 13 Jan 1999 11:16:43 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id HAA07665; Thu, 14 Jan 1999 07:46:48 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id HAA02584; Thu, 14 Jan 1999 07:46:41 +1300 (NZDT) (envelope-from jabley) Date: Thu, 14 Jan 1999 07:46:41 +1300 From: Joe Abley To: Andrzej Bialecki Cc: "Daniel C. Sobral" , Mike Smith , freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990114074641.B2521@clear.co.nz> References: <19990113204253.D1312@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Andrzej Bialecki on Wed, Jan 13, 1999 at 11:31:48AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 11:31:48AM +0100, Andrzej Bialecki wrote: > On Wed, 13 Jan 1999, Joe Abley wrote: > > > Has anybody had a chance to look at the boot help merge script I posted the > > other day? Just interested as to whether I had got the right end of the stick. > > Yes, I tried it. There are several things which should be corrected - see > the diffs attached below. Besides obvious errors, I think we should > preserve blank lines inside the help topics in order to improve > readability. So the bits I need to fix are + you can have more than one synopsis line + the help text can contain blank lines Anything else? I will make some modifications later today. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:17:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05645 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:17:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05515 for ; Wed, 13 Jan 1999 11:17:19 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.150]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3352 for ; Wed, 13 Jan 1999 20:15:56 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 13 Jan 1999 20:23:39 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Hackers Subject: cvs question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I am back again to bother some more ;) Since I am starting some more serious development on CURRENT I switched cvsup from getting the checked out version to getting the updated version(,v) files. I made the base and prefix directory both /usr so CVSROOT lies in /usr I know from some meedling with cvs that I need to specify a CVSROOT environment variable, so I did a CVSROOT=/usr before starting work on the cvs stuff. [root@daemon] (138) # echo $CVSROOT /usr Because I already have doc, ports and src in place I did a cvs update -P -d from /usr and the following startled me: [root@daemon] (139) # cvs update -P -d cvs update: Updating ports cvs [update aborted]: cannot open directory /home/ncvs/ports: No such file or directory I looked in CVSROOT and saw that there were some log entries regarding hardlinked /home/ncvs for CVSROOT which would be set back to $CVSROOT. But I have no clue whatsoever where this /home/ncvs comes from. Any ideas are appreciated... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:23:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07449 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:23:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07292 for ; Wed, 13 Jan 1999 11:22:49 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA09730; Wed, 13 Jan 1999 19:21:38 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id IAA74669; Wed, 13 Jan 1999 08:58:47 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901130858.IAA74669@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White cc: Bill Fenner , hackers@FreeBSD.ORG Subject: Re: using raw sockets In-reply-to: Your message of "Tue, 12 Jan 1999 15:43:47 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Jan 1999 08:58:46 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 12 Jan 1999, Bill Fenner wrote: > > > What OS version, and what kind of ethernet card, are you using when you > > see the BPF symptoms that you mention? I've never seen either of the > > problems you describe. It seems to me that fixing bpf is a much better > > target than creating a whole new mechanism. > > I'm on 2.2.7-RELEASE with a 3Com 3c509 (ep0). I'm using a program I wrote > that's derived from ppp(8), which operates in a select() loop. I don't > know exactly where the holdup is, but from my debugging output I don't > think it's my code (it reads the packets I send out immediately, just not > any inbound packets). [.....] I don't know if it'll help, but if you enable the (rather verbose) ``timer'' diagnostics going to the screen of an interactive session, you may be able to determine if something's holding up the select(). Normal logs are probably useless as you've got the syslogd latency added in. Something like ``set log local timer'' will show you what descriptors are being added to what fd_set's. It may give you a "feel" for whether the select() is being done as required. Also, I'm not sure if you've merged version 1.32 of timer.c from the HEAD branch into your current sources. If you have, you might try backing that out and seeing if that improves things. The change reduces ppps interrupt overheads, but exposes any small latency problems, making them into more serious errors. This sounds quite plausible given your latency timings (just over a second). There are a number of other timers that are set at one second (the modem carrier timer and the throughput timers spring to mind) which will break ppp out of the select() and cause another batch of *_UpdateSet() calls. The danger here (or the thing to be wary of) is that if you return from your local *_UpdateSet() function without updating any of the passed fd_set's, you won't be called again for an arbitrary amount of time. This means that you sometimes need to recurse in *_UpdateSet() - take a look at datalink.c for an example. There are a few places in datalink_UpdateSet() that ``return datalink_UpdateSet()'' after altering the datalink::state. If recursing isn't appropriate (you really have nothing else to do at the moment, but would like to be called again pretty soon), you need to implement a ``timer'' (which doesn't actually need to do anything). That'll drop ppp out of the select() and cause a new call to all the *_UpdateSet() functions too. > Doug White | Pacific Crest Networks > Internet: dwhite@pond.net | http://www.pond.net/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:29:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09361 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:29:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09285 for ; Wed, 13 Jan 1999 11:29:23 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 100SNp-000O1k-00; Wed, 13 Jan 1999 17:39:01 +0200 From: Sheldon Hearn To: "Kenneth D. Merry" cc: hackers@FreeBSD.ORG Subject: Re: what was the old devstat interface's dk_wds? In-reply-to: Your message of "Tue, 12 Jan 1999 21:01:57 MST." <199901130401.VAA49342@panzer.plutotech.com> Date: Wed, 13 Jan 1999 17:39:01 +0200 Message-ID: <92363.916241941@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999 21:01:57 MST, "Kenneth D. Merry" wrote: > There are a couple of other ports that use the devstat code, in > addition to systat(1), vmstat(8), and iostat(8). Check out xperfmon, > and xsysinfo. think they both support devstat. Thanks, Kenneth. Looking at systat gave me enough to figure out what was needed. So much so that I shamelessly borrowed its code and changed all of 5 lines. ;) One question. If buildmatch is passed "da" as match_str, what devices will I end up selecting? Just SCSI and IDE disk drives? I ask because I don't really know what "Direct Access devices" does and doesn't include. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 11:50:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14802 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 11:50:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14780 for ; Wed, 13 Jan 1999 11:50:34 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA26620; Thu, 14 Jan 1999 02:37:58 +0900 (JST) Message-ID: <369CD9A2.C8F595F6@newsguy.com> Date: Thu, 14 Jan 1999 02:36:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Robert Hough CC: hackers@FreeBSD.ORG Subject: Re: More troubles... References: <3.0.32.19990112172331.00caac10@iserve.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Hough wrote: > > After a suggestion, I installed and ran cvsup, ran it, no problems... Ran > make world, in hopes that it would aleviate some of my problems. However, > when I tried a 'w' or 'who' I got an error. I figured, ok, maybe I need to > update the kernel then. I recompile the generic kernel, and reboot. Now > it's giving me 'Invalid Format' as it tries to boot up. I can type in > kernel.JAN12 and it boots up just fine. Can someone tell me what I'm doing > wrong here? I've compiled at least 15-20 kernels before, and have never > gotten this error before. I've tried 4 times now, still no luck. :( (I'm > starting to think a re-install is in order) Ok, I don't have the details here, but let me make a wild guess. 1) You were NOT running elf kernels. 2) You were using the old boot blocks (3.0-RELEASE, for instance). 3) Your recently cvsupped tree is compiling elf kernels by default, and... 4) You didn't notice a "please install the new bootblocks" message that is supposed to appear in this case, after making a new kernel, or... 5) The message didn't appear. What happens then is that the old boot blocks do not work with the new elf kernel. Hopefully, there is a workaround. Instead of booting /kernel, try /boot/loader instead. It will load the third stage of the new boot loader (which was installed during make world), which is still a.out and will then proceed to load your new Elf kernel. If that happens, please check /usr/src/UPDATING for more information on how to install the new boot blocks (which usually amounts to running disklabel -B /dev/). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 12:11:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19436 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 12:11:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19412 for ; Wed, 13 Jan 1999 12:11:22 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id JAA25111; Thu, 14 Jan 1999 09:10:13 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id JAA02990; Thu, 14 Jan 1999 09:10:07 +1300 (NZDT) (envelope-from jabley) Date: Thu, 14 Jan 1999 09:10:07 +1300 From: Joe Abley To: Andrzej Bialecki Cc: "Daniel C. Sobral" , Mike Smith , freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: FICL and setting BTX variables Message-ID: <19990114091007.D2686@clear.co.nz> References: <19990113204253.D1312@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Andrzej Bialecki on Wed, Jan 13, 1999 at 11:31:48AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 11:31:48AM +0100, Andrzej Bialecki wrote: > On Wed, 13 Jan 1999, Joe Abley wrote: > > > Has anybody had a chance to look at the boot help merge script I posted the > > other day? Just interested as to whether I had got the right end of the stick. > > Yes, I tried it. There are several things which should be corrected - see > the diffs attached below. Besides obvious errors, I think we should > preserve blank lines inside the help topics in order to improve > readability. Aah... I just found the perl script which does this right now, so I know a bit more about what I am doing now. I was treating the initial "synopsis" lines as different and required, but it seems this is not the case - they're just part of the help text. Also, the enforced tab formatting and blank line removal is not required, as you mentioned. I'm still stripping blank characters from the end of lines, though, so you will see some (non-printable) diffs: % cat help.common help.i38 | ./mergehelp.awk >version.awk % perl ./merge_help.pl help.common help.i386 >version.perl % diff version.awk version.perl 59c59 < --- > 112c112 < The read command reads a line of input from the terminal. If the --- > The read command reads a line of input from the terminal. If the 114c114 < received after seconds. (Any keypress will cancel the --- > received after seconds. (Any keypress will cancel the 117c117 < If -p is specified, is printed before reading input. No --- > If -p is specified, is printed before reading input. No 198c198 < It may be overridden by setting the bootfile variable to a --- > It may be overridden by setting the bootfile variable to a 240c240 < Variable substitution is performed on the prompt. The default --- > Variable substitution is performed on the prompt. The default 293c293 < is removed. --- > is removed. % Revised script below, and at http://www.patho.gen.nz/~jabley/mergehelp.awk if that's more convenient. Joe #!/usr/bin/awk -f # # $Id: mergehelp.awk,v 1.3 1999/01/13 20:06:52 jabley Exp $ # # Merge two boot loader help files for FreeBSD 3.0 # Joe Abley BEGIN \ { state = 0; first = 0; ind = 0; } # beginning of first command /^###/ && (state == 0) \ { state = 1; next; } # entry header /^# T[[:graph:]]+ (S[[:graph:]]+ )*D[[:graph:]][[:print:]]*$/ && (state == 1) \ { match($0, " T[[:graph:]]+"); T = substr($0, RSTART + 2, RLENGTH - 2); match($0, " S[[:graph:]]+"); S = (RLENGTH == -1) ? "" : substr($0, RSTART + 2, RLENGTH - 2); match($0, " D[[:graph:]][[:print:]]*$"); D = substr($0, RSTART + 2); # find a suitable place to store this one... ind++; if (ind == 1) { first = ind; help[ind, "T"] = T; help[ind, "S"] = S; help[ind, "link"] = -1; } else { i = first; j = -1; while (help[i, "T"] help[i, "S"] < T S) { j = i; i = help[i, "link"]; if (i == -1) break; } if (i == -1) { help[j, "link"] = ind; help[ind, "link"] = -1; } else { help[ind, "link"] = i; if (j == -1) first = ind; else help[j, "link"] = ind; } } help[ind, "T"] = T; help[ind, "S"] = S; help[ind, "D"] = D; # set our state state = 2; help[ind, "text"] = 0; next; } # end of last command, beginning of next one /^###/ && (state == 2) \ { state = 1; } (state == 2) \ { sub("[[:blank:]]+$", ""); if (help[ind, "text"] == 0 && $0 ~ /^[[:blank:]]*$/) next; help[ind, "text", help[ind, "text"]] = $0; help[ind, "text"]++; next; } # show them what we have (it's already sorted in help[]) END \ { node = first; while (node != -1) { printf "################################################################################\n"; printf "# T%s ", help[node, "T"]; if (help[node, "S"] != "") printf "S%s ", help[node, "S"]; printf "D%s\n\n", help[node, "D"]; for (i = 0; i < help[node, "text"]; i++) printf "%s\n", help[node, "text", i]; node = help[node, "link"]; } printf "################################################################################\n"; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 14:09:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10257 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 14:09:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10245 for ; Wed, 13 Jan 1999 14:08:54 -0800 (PST) (envelope-from dwhite@pond.net) Received: from localhost (dwhite@localhost) by guppy.pond.net (8.8.8/8.8.7) with SMTP id OAA11635; Wed, 13 Jan 1999 14:03:49 -0800 (PST) Date: Wed, 13 Jan 1999 14:03:49 -0800 (PST) From: Doug White To: Bill Fenner cc: hackers@FreeBSD.ORG Subject: Re: using raw sockets In-Reply-To: <199901130039.QAA06354@mango.parc.xerox.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, 12 Jan 1999, Bill Fenner wrote: > In message you write: > >I'm assuming the timestamps are generated by tcpdump, > >or are they the real packet timestamps? > > The timestamp that tcpdump prints is the timestamp that bpf attaches > (i.e. when the driver calls bpf_[m]tap() ). Hm, I'll have to look at that. It might be a peculiarity with the ep driver. I want to try a de card and see what I get. > Can you compare that timestamp against gettimeofday(), to see if it > looks like the latency is in the bpf buffer? > >From a brief inspection of the bpf code, it looks like bpf won't > wake up a selecting process until the buffer is almost full. Have > you tried using the BIOCIMMEDIATE ioctl? Assuming I did the ioctl right, it is set. Doug White | Pacific Crest Networks Internet: dwhite@pond.net | http://www.pond.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 14:26:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12399 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 14:25:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12393 for ; Wed, 13 Jan 1999 14:25:42 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) id OAA29088; Wed, 13 Jan 1999 14:22:45 -0800 (PST) Message-ID: <19990113142245.A28487@la.best.com> Date: Wed, 13 Jan 1999 14:22:45 -0800 From: "Joseph T. Lee" To: Marcin Cieslak , Brian Somers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident References: <199901121821.SAA13888@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Marcin Cieslak on Wed, Jan 13, 1999 at 11:45:15AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 11:45:15AM +0100, Marcin Cieslak wrote: > I think that ident should be made by a separate daemon, like midentd. > The only problem with libalias is to make information about proxified > connections available to other processes. If aliasing were done in > kernel, it would be ioctl() or /proc or whatever. Ident is already a separate daemon, namely pidentd. > Since it is not, I suggest using a named pipe or other form of IPC > (control socket?) in order to allow ident - and perhaps others > processes interested - to gain information about current > network translation table. Even with the local ident daemon having the necessary information to forward the ident query, it still would not work due to the way the RFC 113 protocol works. It matches the query's remote ip with a same remote ip, and port gleaned from the query. If the natd host made the query, then it would not work, as the ips would not match. I've coded far enough into libalias to test this, as I understand it. This is all due to the host behind natd connecting 'through' the natd firewall instead of 'to' the firewall, as how other proxying schemes work. I'm not even sure why identd supports a PROXY query command, since it wouldn't match the ip/port tables anyways... Any better ways to hack around this crux would be most welcome. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 14:32:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13520 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 14:32:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13509 for ; Wed, 13 Jan 1999 14:32:13 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.80]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4A0F; Wed, 13 Jan 1999 18:45:38 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <369C7E94.C9242BCD@kryptokom.de> Date: Wed, 13 Jan 1999 18:53:19 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: eT Subject: RE: security mailing lists Cc: Hackers FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-99 eT wrote: > hi, can anyone out there suggest some network security related mailing > lists? > more specifically for ipsec [and] freebsd? *G* security@freebsd.org? ;) also, www.greatcircle.org might have something of interest, www.ssh.fi has also mailinglists. try those =) --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 15:47:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21949 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 15:47:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21944 for ; Wed, 13 Jan 1999 15:47:04 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40358>; Thu, 14 Jan 1999 10:45:10 +1100 Date: Thu, 14 Jan 1999 10:45:41 +1100 From: Peter Jeremy Subject: Re: Problems with 3.0 To: hackers@FreeBSD.ORG Cc: tlambert@primenet.com Message-Id: <99Jan14.104510est.40358@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999 22:18:07 +0000 (GMT), Terry Lambert wrote: >Another one recently discovered is that it *appears* that you can >map (read only) the same file twice letting the system decide where >to put it (pass NULL as binding location), and the second time the >system will return the same address as the first time, instead of >doing the right thing and setting up the mapping at a different >location. Why is this behaviour wrong? Given that both mappings are read-only and you haven't said that you want it mapped at a specific location, why shouldn't the system just reuse the pre-existing mapping? This is definitely easier for the kernel, and reduces system resource requirements (page table entries and suchlike). 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 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 16:06:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24913 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 16:06:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24902 for ; Wed, 13 Jan 1999 16:06:10 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40363>; Thu, 14 Jan 1999 11:04:15 +1100 Date: Thu, 14 Jan 1999 11:04:44 +1100 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #364 To: hackers@FreeBSD.ORG Message-Id: <99Jan14.110415est.40363@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Jan 1999 00:43:18 +0100, sthaug@nethelp.no wrote: >If you ping the IP address associated with the NIC from *the host itself*, >it won't be put on the wire. You have to ping it from another host. Actually, this is an artifact of the 4.4BSD IP stack: If you look at the routing tables, you will see there is an explicit entry routing your hosts own IP address through lo0. In theory, you should be able to route packets to your own IP address via the NIC (in which case they _will_ be seen by tcpdump and will probably appear on the wire), but I can't work out the correct incantation. Other OSs may behave differently: DEC OSF/1 seems to send the packet over the wire, Solaris 2.5 seems not to. 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 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 16:36:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29198 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 16:36:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.bitmine.com (adsl-209-233-238-103.dsl.pacbell.net [209.233.238.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29193 for ; Wed, 13 Jan 1999 16:36:29 -0800 (PST) (envelope-from rdas@bitmine.com) Received: from bitmine.com (highlands [192.68.1.3]) by ns.bitmine.com (8.8.7/8.8.7) with ESMTP id QAA12495 for ; Wed, 13 Jan 1999 16:33:33 -0800 (PST) (envelope-from rdas@bitmine.com) Message-ID: <369DE3A8.44868F4E@bitmine.com> Date: Thu, 14 Jan 1999 04:31:36 -0800 From: rdas-bitmine X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: PPTP through NATD binaries and source available... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got tired of not being able to use my PPTP client on my NT workstation with my aliased network at home, so I modifed both natd and the aliasing libraries to alias GRE packets. I have included both source and binary downloads. It has only been tested on 2.2.5 and it only works with one PPTP client because I'm lazy. Sorry. However I hope you find it useful. Check out http://www.bitmine.com/pptp-patch for details... Cheers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 17:38:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06458 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 17:38:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p165.tfs.net [139.146.210.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06426; Wed, 13 Jan 1999 17:37:56 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id TAA35796; Wed, 13 Jan 1999 19:36:47 -0600 (CST) From: Jim Bryant Message-Id: <199901140136.TAA35796@unix.tfs.net> Subject: Forward all spam to UCE@FTC.GOV To: freebsd-hackers@FreeBSD.ORG Date: Wed, 13 Jan 1999 19:36:35 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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 This announcement is located on the Federal Trade Commission's complaint form page http://www.ftc.gov/ftc/complaint.htm ------------------ If you would like to forward unsolicited commercial e-mail (spam) to the Commission, please send it directly to UCE@FTC.GOV without using this form. ------------------ Could this be added to sendmail.cf somehow by default? maybe as a comment? Maybe as some kind of autoforwarder in spam filtering? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 17:48:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07565 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 17:48:46 -0800 (PST) (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 RAA07560; Wed, 13 Jan 1999 17:48:44 -0800 (PST) (envelope-from stone1@nandomail.com) Received: from firewall.powel.no (firewall.powel.no [193.215.74.177]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id RAA13964; Wed, 13 Jan 1999 17:48:08 -0800 (PST) Received: from harnny (unverified) by firewall.powel.no (Content Technologies SMTPRS 2.0.15) with ESMTP id ; to, 14 jan 1999 01:33:05 +0100 Message-Id: From: "Ron" Subject: HOT FOR 1999 !!! To: members562@FreeBSD.ORG X-Mailer: Microsoft Outlook Express 4.72.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V(null).1712.3 MIME-Version: 1.0 Date: Wed, 13 Jan 1999 18:41:41 -0500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAB07561 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Own your own Adult Website or 900# business. No chargbacks, Quick payouts. Complete program start at only $99 Call for a free color brochure 1-888-883-9851 or 305-650-2928 remove at: mailto:claak@freemail.com.au?subject=remove To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 18:24:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00616 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 18:24:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00606 for ; Wed, 13 Jan 1999 18:24:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA16315; Wed, 13 Jan 1999 18:23:01 -0800 (PST) (envelope-from dillon) Date: Wed, 13 Jan 1999 18:23:01 -0800 (PST) From: Matthew Dillon Message-Id: <199901140223.SAA16315@apollo.backplane.com> To: Bernie Doehner Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, 13 Jan 1999, Terry Lambert wrote: : :> > Why is it that under bash's ulimit -v, the swap space utilization is the :> > sum of the data segment size and the stack size? :> :> Read-only pages don't need to be backed by swap? : :Actualy I already asked the very same question in a different forum. I :assume the text segment is NOT swapped out because it is referenced way :TOO often to be practical/efficient to swap out? : :> > Is this correct / valid for all shells (not just bash, which explicitly :> > prints this out as the per process swap space limitation)? :> :> On machines where the program image is not used as a read-only :> swap store, this would be different. You may have to install an :> old copy of Xenix or SVR3.2 to find such a machine, though... :> : :Actualy I think Solaris does this too.. : :Thanks. : :Bernie Only memory that does not otherwise have backing store is swapped. Other memory is backed by the original object - the system simply syncs the page if necessary and then frees it. If the program needs the page again, the system reloads it. If the system wishes to reuse idle unbacked memory, swap space is allocated for it and the page synced to swap before being freed for reuse. A slight aberration of this occurs when you have MAP_PRIVATE mapped pages - in this case the system uses the backing store that already exists for the page until you make a modification, then uses swap to back your modifications. These types of pages are used to fixup vectors for shared libraries and to map the DATA portion of a program binary. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 18:39:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02009 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 18:39:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02002 for ; Wed, 13 Jan 1999 18:39:28 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA16535; Wed, 13 Jan 1999 18:58:04 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd016379; Wed Jan 13 18:57:51 1999 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id SAA12304; Wed, 13 Jan 1999 18:57:44 -0700 (MST) From: Terry Lambert Message-Id: <199901140157.SAA12304@usr02.primenet.com> Subject: Re: Problems with 3.0 To: peter.jeremy@auss2.alcatel.com.au (Peter Jeremy) Date: Thu, 14 Jan 1999 01:57:43 +0000 (GMT) Cc: hackers@FreeBSD.ORG, tlambert@primenet.com In-Reply-To: <99Jan14.104510est.40358@border.alcanet.com.au> from "Peter Jeremy" at Jan 14, 99 10:45:41 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 > >Another one recently discovered is that it *appears* that you can > >map (read only) the same file twice letting the system decide where > >to put it (pass NULL as binding location), and the second time the > >system will return the same address as the first time, instead of > >doing the right thing and setting up the mapping at a different > >location. > > Why is this behaviour wrong? Given that both mappings are read-only > and you haven't said that you want it mapped at a specific location, > why shouldn't the system just reuse the pre-existing mapping? This > is definitely easier for the kernel, and reduces system resource > requirements (page table entries and suchlike). Because it doesn't reference count the unmappings. This damages data encapsulation sematics. If I have: some_context * f1_open() { some_context *ctxp; ctxp = (some_context *)malloc(sizeof(some_context)); ctxp->sc_region = mmap( ...); } different_context * f2_open() { different_context *ctxp; ctxp = (different_context *)malloc(sizeof(different_context)); ctxp->dc_region = mmap( ...); } then I'm screwed, since if I: c1 = f1_open(); c2 = f2_open(); do_some_stuff( c1); f1_close( c1); /* XXX blows c2's head off*/ do_different_stuff( c2); f2_close( c2); references to c2->dc_region will explode because the region is no longer valid. If this type of thing is OK, then I'm anticipating your implementation of WSOCK32.DLL for FreeBSD so we can "take all the socket bloat out of the kernel, since kernel-based resource tracking is unnecessary"... 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 Jan 13 19:08:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06132 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 19:08:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06123 for ; Wed, 13 Jan 1999 19:08:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA16614; Wed, 13 Jan 1999 19:07:17 -0800 (PST) (envelope-from dillon) Date: Wed, 13 Jan 1999 19:07:17 -0800 (PST) From: Matthew Dillon Message-Id: <199901140307.TAA16614@apollo.backplane.com> To: Terry Lambert Cc: mike@smith.net.au (Mike Smith), rch@iserve.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with 3.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > This error will repeat itself over and over, untill I stop the process, and :> > restart it. I'm not sure if it's a problem with apache though, as it has :> > happened to inetd, and cron as well. At first I thought maybe it was a :> > problem with the ram, so I've replaced that twice, still no luck. I'm :> > getting ready to swap the CPU as well. Any ideas would be appeciated. :> :> The fact that the error repeats indicates that the cached copy of the :> program's text has been corrupted. This typically requires bad RAM, :> CPU or motherboard. Are you overclocking? : :Actually, no. All it requires is the VM system reclaiming a clean :page from an in core object without telling the object about it. : :This can't happen for most things, but mmap seems immune from :correct functioning in a lot of ways, and this happens to be one :of them. The pages that get zapped are in the libc code section :for the mmap'ed libc.so image. This probably has something to do :with the fact that the same libc is mapped into multiple processes :(e.g., here's some place where having aliases in your VM sucks out). The only libc interaction with mmap() that I know of occurs if you ( as programs do ) MAP_PRIVATE mmap libc. The pages the program modifies to fixup jump vectors become swap-backed, but the rest of libc remains backed by the libc.so file. If the shared library is then updated, the modified fixup pages remain untouched (of course!) while the rest of libc is changed out from under the running program. This could certainly cause a seg fault. It is also possible for the system's program TEXT object for a program binary to become confused when the binary is updated while the program is also running. It doesn't always happen. I'm not sure how it's possible for this to happen but it does. Usually, updating the program binary a second time fixes the problem. If the author updated either libc or httpd while the web server was running, it could certainly have caused the segfault later on. -Matt :Another one recently discovered is that it *appears* that you can :map (read only) the same file twice letting the system decide where :to put it (pass NULL as binding location), and the second time the :system will return the same address as the first time, instead of :doing the right thing and setting up the mapping at a different :location. : : : Terry Lambert : terry@lambert.org I've not seen this either. Do you have an example or PR? I wrote a quick little test program to map the same file several times and it seems to map it at different locations as it should. It was hardly an exhaustive test, though. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 19:31:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08228 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 19:31:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08221 for ; Wed, 13 Jan 1999 19:31:03 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id EAA22289; Thu, 14 Jan 1999 04:29:54 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id EAA86886; Thu, 14 Jan 1999 04:29:51 +0100 (MET) Date: Thu, 14 Jan 1999 04:29:51 +0100 From: Eivind Eklund To: "Joseph T. Lee" Cc: hackers@FreeBSD.ORG Subject: Re: libalias and ident Message-ID: <19990114042951.I76923@bitbox.follo.net> References: <199901121821.SAA13888@keep.lan.Awfulhak.org> <19990113142245.A28487@la.best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990113142245.A28487@la.best.com>; from Joseph T. Lee on Wed, Jan 13, 1999 at 02:22:45PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 02:22:45PM -0800, Joseph T. Lee wrote: > Any better ways to hack around this crux would be most welcome. I think the only way to do this is (1) 'Take over' port 113, faking an endpoint for all connections to it. (2) When the actual request comes in, parse it to find out which alias_link it belongs to. If it doesn't belong to any, synthezise a 'not found' response and be done. Otherwise, start creating a TCP-connection to true target, where you'll be repeating the request (with appropriate sequence number skew etc). (3) Create an alias_link for the ingoing connection. Of course, all of this requires that you are able to synthesise new packets, not just modify or drop packets. The present libalias API is not up to it; the API must be re-done, and all the clients updated. While we're at it, I think the library should be renamed to libnat. The code should also be made to not use these enormous amounts of global data, but instead work on data structures passed in by the client - this allow several instances in a single unit, and makes it much more suitable for more serious use. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 19:59:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11147 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 19:59:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11133; Wed, 13 Jan 1999 19:59:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA91310; Wed, 13 Jan 1999 19:57:29 -0800 (PST) To: Eivind Eklund cc: "Joseph T. Lee" , hackers@FreeBSD.ORG Subject: Re: libalias and ident In-reply-to: Your message of "Thu, 14 Jan 1999 04:29:51 +0100." <19990114042951.I76923@bitbox.follo.net> Date: Wed, 13 Jan 1999 19:57:28 -0800 Message-ID: <91306.916286248@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While we're at it, I think the library should be renamed to libnat. Hear hear! Just be sure that Brian changes ppp also so that it becomes -nat with -alias as a backwards-compat option only. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 23:10:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00378 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 23:10:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00369 for ; Wed, 13 Jan 1999 23:10:47 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA02521 for ; Thu, 14 Jan 1999 17:39:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA57065 for hackers@freebsd.org; Thu, 14 Jan 1999 17:38:57 +1030 (CST) Date: Thu, 14 Jan 1999 17:38:57 +1030 From: Greg Lehey To: FreeBSD Hackers Subject: Mounting on NFS directories: is this kosher? Message-ID: <19990114173856.J55525@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.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 I'm just playing around with mounting Vinum file systems, and I found myself in the following rather unusual situation: $ df Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0s1a 38991 31833 4039 89% / /dev/da0s1e 38991 22253 13619 62% /Root /dev/da0s1f 921679 632050 215895 75% /Usr /dev/da0s1g 921951 516094 332101 61% /usr procfs 4 4 0 100% /proc freebie:/src 3667758 1788307 1586031 53% /src /dev/vinum/obj 396895 186398 178746 51% /usr/obj /dev/vinum/src 396895 255126 110018 70% /src/PANIC/src Here, the Vinum volume /dev/vinum/src is mounted on the nfs file system freebie:/src. Is this allowed? An attempt to umount /src fails with Device busy, but it seems that I've heard you're not allowed to mount on nfs directories. Greg -- See complete headers for address, home page 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 Wed Jan 13 23:21:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01724 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 23:21:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01716; Wed, 13 Jan 1999 23:21:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA22609; Wed, 13 Jan 1999 23:20:22 -0800 (PST) (envelope-from dillon) Date: Wed, 13 Jan 1999 23:20:22 -0800 (PST) From: Matthew Dillon Message-Id: <199901140720.XAA22609@apollo.backplane.com> To: "John S. Dyson" , dg@root.com, jkh@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Review and report of linux kernel VM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG General Overview I've been looking at the linux kernel VM - mainly just to see what they've changed since I last looked at it. It's quite interesting... not bad at all though it is definitely a bit more memory-resource-intensive then FreeBSD's. However, it needs a *lot* of work when it comes to freeing up pages. I apologize in advance for any mistakes I've made! Basically, the linux kernel uses persistent hardware-level page tables in a mostly platform-independant fashion. The function of the persistent page tables is roughly equivalent to the function of FreeBSD's vm_object's. That is, the page tables are used to manage sharing and copy-on-write functions for VM objects. For example, when a process fork()'s, pages are duplicated literally by copying pte's. Writeable MAP_PRIVATE pages are write-protected and marked for copy-on-write. A global resident-page array is used to keep track of shared reference counts. Swapped-out pages are also represented by pte's and also marked for copy-on-write as appropriate. The swap block is stored in the PFN area of the pte (as far as I can tell). The swap system keeps a separate shared reference count to manage swap usage. The overhead is around 3 bytes per swap page (whether it is in use or not), and another pte-sized (int usually) field when storing the swap block in the pagetable. Linux cannot swap out its page tables, mainly due to the direct use of the page tables in handling VM object sharing. In general terms, linux's VM system is much cleaner then FreeBSD's... and I mean a *whole lot* cleaner, but at the cost of eating some extra memory. It isn't a whole lot of extra memory - maybe a meg or two for a typical system managing a lot of processes, and much less for typical 'small' systems. They are able to completely avoid the vm_object stacking (and related complexity) that we do, and they are able to completely avoid most of the pmap complexity in FreeBSD as well. Linux appears to implement a unified buffer cache. It's pretty straight forward except the object relationship is stored in the memory-map management structures in each process rather then in a vm_object type of structure. Linux appears to map all of physical memory into KVM. This avoids FreeBSD's (struct buf) complexity at the cost of not being able to deal with huge-memory configurations. I'm not 100% sure of this, but its my read of the code until someone corrects me. Problems Swap allocation is terrible. Linux uses a linear array which it scans looking for a free swap block. It does a relatively simple swap cluster cache, but eats the full linear scan if that fails which can be terribly nasty. The swap clustering algorithm is a piece of crap, too -- once swap becomes fragmented, the linux swapper falls on its face. It does read-ahead based on the swapblk which wouldn't be bad if it clustered writes by object or didn't have a fragmentation problem. As it stands, their read clustering is useless. Swap deallocation is fast since they are using a simple reference count array. File read-ahead is half-hazard at best. The paging queues ( determing the age of the page and whether to free or clean it) need to be written... the algorithms being used are terrible. * For the nominal page scan, it is using a one-hand clock algorithm. All I can say is: Oh my god! Are they nuts? That was abandoned a decade ago. The priority mechanism they've implemented is nearly useless. * To locate pages to swap out, it takes a pass through the task list. Ostensibly it locates the task with the largest RSS to then try to swap pages out from rather then select pages that are not in use. From my read of the code, it also botches this badly. Linux does not appear to do any page coloring whatsoever, but it would not be hard to add it in. Linux cannot swap-out its page tables or page directories. Thus, idle tasks can eat a significant amount of memory. This isn't a big deal for most systems ( small systems: no problem. Big systems: probably have lots of memory anyway ). But, mmap()'d files can create a significant burden if you have a lot of forked processes ( news, sendmail, web server, etc...). Not only does Linux have to scan the page tables for all the processes mapping the file, whether or not they are actively using the page being checked for, but Linux's swapout algorithm scans page tables and, effectively, makes redundant scans of shared objects. What FreeBSD can learn Well, the main thing is that the Linux VM system is very, very clean compared to the FreeBSD implementation. Cleaning up FreeBSD's VM system complexity is what I've been concentrating on and will continue to concentrate on. However, part of the reason that FreeBSD's VM system is more complex is because it does not use the page tables to store reference information. Instead, it uses the vm_object and pmap modules. I actually like this feature of FreeBSD. A lot. The biggest thing we need to do to clean up our VM system is, basically, to completely rewrite the struct buf filesystem buffering mechanism to make it much, much less complex - basically it should only be used as placeholders for read and write ops and not used to cache block number mappings between the files and the VM system, nor should it be used to map pages into KVM. Separating out these three mechanisms into three different subsystems would simplify the code enormously, I think. For example, we could implement a simple vm_object KVM mapping mechanism using FreeBSD's existing vm_object stacking model to map portions of a vm_object (aka filesystem partition) into KVM. Linux demarks interrupts from supervisor code much better then we do. If we move some of the more sophisticated operational capabilities out of our interrupt subsystem, we could get rid of most of the spl*() junk we currently have to do. This is a real sore spot in current FreeBSD code. Interrupts are just too complex. I'd also get rid of FreeBSD's intermediate 'software interrupt' layer, which is able to do even more complex things then hard interrupt code. The latency considerations just don't make any sense verses running pending software interrupts synchronously in tsleep(), prior to actually sleeping. We need to do this anyway ( or move softints to kernel threads ) to be able to take advantage of SMP mechanisms. The *only* thing our interrupts should be allowed to do is finish I/O on a page or use zalloc(). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 13 23:53:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04203 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 23:53:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04085 for ; Wed, 13 Jan 1999 23:50:59 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA21807; Thu, 14 Jan 1999 09:48:38 +0200 (EET) Date: Thu, 14 Jan 1999 09:48:37 +0200 From: Ruslan Ermilov To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Hackers Subject: Re: cvs question Message-ID: <19990114094837.B17491@ucb.crimea.ua> Mail-Followup-To: Jeroen Ruigrok/Asmodai , FreeBSD Hackers References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Wed, Jan 13, 1999 at 08:23:39PM +0100 X-Operating-System: FreeBSD 2.2.8-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 08:23:39PM +0100, Jeroen Ruigrok/Asmodai wrote: > Hi guys, > > I am back again to bother some more ;) > > Since I am starting some more serious development on CURRENT I switched > cvsup from getting the checked out version to getting the updated > version(,v) files. > > I made the base and prefix directory both /usr so CVSROOT lies in /usr > I think it's a bad idea. You'd better make your CVSROOT as /usr/FreeBSD-CVS. > I know from some meedling with cvs that I need to specify a CVSROOT > environment variable, so I did a CVSROOT=/usr before starting work on the > cvs stuff. > > [root@daemon] (138) # echo $CVSROOT > /usr > > Because I already have doc, ports and src in place I did a cvs update -P -d > from /usr and the following startled me: > > [root@daemon] (139) # cvs update -P -d > cvs update: Updating ports > cvs [update aborted]: cannot open directory /home/ncvs/ports: No such file > or directory > > I looked in CVSROOT and saw that there were some log entries regarding > hardlinked /home/ncvs for CVSROOT which would be set back to $CVSROOT. But > I have no clue whatsoever where this /home/ncvs comes from. > > Any ideas are appreciated... I guess you have your /usr/src, /usr/ports installed from your Release CD-ROM. You may want to delete them, and then `cvs co' from your local CVSROOT. Best regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 00:14:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06254 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 00:14:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06249 for ; Thu, 14 Jan 1999 00:14:46 -0800 (PST) (envelope-from joerg@krdl.org.sg) Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [137.132.247.30]) by krdl.org.sg (8.9.0/8.9.0) with ESMTP id QAA14351 for ; Thu, 14 Jan 1999 16:19:23 +0800 (SGT) Received: from krdl.org.sg (negara [137.132.248.175]) by mailhost.krdl.org.sg (8.9.0/8.9.0) with ESMTP id QAA09958 for ; Thu, 14 Jan 1999 16:13:38 +0800 (SGT) Received: (from joerg@localhost) by krdl.org.sg (8.8.7/8.8.5) id RAA04654 for freebsd-hackers@freebsd.org; Thu, 14 Jan 1999 17:14:35 +0800 (SGT) Message-ID: <19990114171434.D3310@krdl.org.sg> Date: Thu, 14 Jan 1999 17:14:34 +0800 From: "Joerg B. Micheel" To: freebsd-hackers@FreeBSD.ORG Subject: Loadable PCI device drivers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Kent Ridge Digital Labs, Singapore Project: SingAREN, the Singapore Advanced Research and Education Network Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got a PCI network device driver that I'd like to support for the next couple of years on FreeBSD. I have written an initial implementation for 2.2.6 and, with a little effort, was able to make it (un)loadable. Now with 3.0 and the changes in both the PCI device driver framework and the switch from LKM to KLD modules everything is different. I'm willing to spend time and efforts to make loadable PCI device drivers work again. I need some kind soul to give me the proper directions, intended architecture etc. You may respond in private, if this is not of general interest. Thank you. Joerg -- Joerg B. Micheel Email: SingAREN Technology Center Phone: +65 8742582 Kent Ridge Digital Labs, Rm 3-65, C041 Fax: +65 7744990 21 Heng Mui Keng Terrace Pager: +65 96016020 Singapore 119613 Plan: Troubleshooting ATM Republic of Singapore Networks and Applications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 00:27:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07648 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 00:27:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA07642 for ; Thu, 14 Jan 1999 00:27:44 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA28781; Thu, 14 Jan 1999 07:21:54 +0100 From: Luigi Rizzo Message-Id: <199901140621.HAA28781@labinfo.iet.unipi.it> Subject: Re: Review and report of linux kernel VM To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 14 Jan 1999 07:21:54 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <199901140720.XAA22609@apollo.backplane.com> from "Matthew Dillon" at Jan 13, 99 11:20:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > General Overview > > I've been looking at the linux kernel VM - mainly just to see what they've > changed since I last looked at it. It's quite interesting... not bad at very nice review. Now can you do a similar thing for the FreeBSD VM ? It would be greatly useful for a lot of people cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 00:50:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09838 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 00:50:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09810 for ; Thu, 14 Jan 1999 00:50:13 -0800 (PST) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id KAA10509 for freebsd-hackers@freebsd.org; Thu, 14 Jan 1999 10:48:41 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199901140848.KAA10509@oskar.nanoteq.co.za> Subject: Dysan cdrom and 3.0 problems To: freebsd-hackers@FreeBSD.ORG Date: Thu, 14 Jan 1999 10:48:37 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I have a Dysan 32x CDROM (atapi) in my system .. I Upgraded from 2.2.7 to 3.0-RELEASE and then to an almost current. In both the 3.0-RELEASe and the "almost current" it doesn't seem like the atapi cdrom gets probed .. here is the output from my dmesg wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S Shouldn't it attach acd0 or something to the atapi cdrom ?? When I do a "mount_cd9660 /dev/wcd0c /mnt" it returns with a acd0: read_toc failed and an input/output error ... Any ideas ? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 02:43:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21322 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 02:43:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21313 for ; Thu, 14 Jan 1999 02:43:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 100kDY-0008cf-00; Thu, 14 Jan 1999 12:41:36 +0200 From: Sheldon Hearn To: Reinier Bezuidenhout cc: hackers@FreeBSD.ORG Subject: Re: Dysan cdrom and 3.0 problems In-reply-to: Your message of "Sat, 14 Jan 1999 10:48:37 +0200." <199901140848.KAA10509@oskar.nanoteq.co.za> Date: Thu, 14 Jan 1999 12:41:36 +0200 Message-ID: <33148.916310496@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Jan 1999 10:48:37 +0200, Reinier Bezuidenhout wrote: > Shouldn't it attach acd0 or something to the atapi cdrom ?? No. It "attaches" wcd* "to the atapi cdrom", to use your wording. > When I do a "mount_cd9660 /dev/wcd0c /mnt" > it returns with a > > acd0: read_toc failed > > and an input/output error ... I get this from my Creative Infra36 with some discs, not with others. Did the same mount_cd9660 operation succeed for the same disc you're trying to mount now under STABLE? If not, you can probably just do what I've done. Throw up your hands in despair, resolve never to buy atapi hardware again and fire up kgdb every now and then to try and fail to come up with a software fix for broken hardware. :) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 03:42:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25391 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 03:42:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25384 for ; Thu, 14 Jan 1999 03:42:20 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with SMTP id MAA29739 for ; Thu, 14 Jan 1999 12:42:15 +0100 (MET) Date: Thu, 14 Jan 1999 12:42:15 +0100 (MET) From: Marcin Cieslak To: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident In-Reply-To: <91306.916286248@zippy.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 Wed, 13 Jan 1999, Jordan K. Hubbard wrote: > Hear hear! Just be sure that Brian changes ppp also so that it > becomes -nat with -alias as a backwards-compat option only. :) Isn't NAT copyrighted by Cisco or whoever? :) -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 05:11:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05454 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 05:11:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05446 for ; Thu, 14 Jan 1999 05:10:50 -0800 (PST) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id PAA16583; Thu, 14 Jan 1999 15:08:16 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199901141308.PAA16583@oskar.nanoteq.co.za> Subject: Re: Dysan cdrom and 3.0 problems In-Reply-To: <33148.916310496@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 14, 99 12:41:36 pm" To: axl@iafrica.com (Sheldon Hearn) Date: Thu, 14 Jan 1999 15:08:16 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 .. > On Sat, 14 Jan 1999 10:48:37 +0200, Reinier Bezuidenhout wrote: > > > Shouldn't it attach acd0 or something to the atapi cdrom ?? > > No. It "attaches" wcd* "to the atapi cdrom", to use your wording. > > > When I do a "mount_cd9660 /dev/wcd0c /mnt" > > it returns with a > > > > acd0: read_toc failed > > > > and an input/output error ... > > I get this from my Creative Infra36 with some discs, not with others. > Did the same mount_cd9660 operation succeed for the same disc you're > trying to mount now under STABLE? As far as I can recall ... yes ... the system also works fine when I boot in Dindowz (windows :) ) Then it reads the disc etc. I also tried moving the CDROM from primary slave to secondary master .. but it acts the same. It does this with ANY disc in the drive. It returns so quickly ... it almost seems as if it's trying to access the disc even. Cheers Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 05:19:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06244 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 05:19:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06238 for ; Thu, 14 Jan 1999 05:19:43 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id NAA26852; Thu, 14 Jan 1999 13:18:31 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma026848; Thu, 14 Jan 99 13:18:27 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 100mfL-0005ml-00; Thu, 14 Jan 1999 13:18:27 +0000 To: hackers@FreeBSD.ORG From: Tony Finch Subject: Re: Review and report of linux kernel VM In-Reply-To: <199901140621.HAA28781@labinfo.iet.unipi.it> References: <199901140720.XAA22609@apollo.backplane.com> Message-Id: Date: Thu, 14 Jan 1999 13:18:27 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > >very nice review. Now can you do a similar thing for the FreeBSD VM ? Matt already has: http://apollo.backplane.com/FreeBSD/FreeBSDVM.txt Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 06:12:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10355 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 06:12:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10336; Thu, 14 Jan 1999 06:12:46 -0800 (PST) (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 GAA08476; Thu, 14 Jan 1999 06:11:27 -0800 (PST) (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 GAA15249; Thu, 14 Jan 1999 06:11:26 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA25453; Thu, 14 Jan 1999 06:11:24 -0800 (PST) From: Don Lewis Message-Id: <199901141411.GAA25453@salsa.gv.tsc.tdk.com> Date: Thu, 14 Jan 1999 06:11:24 -0800 In-Reply-To: Jim Bryant "Forward all spam to UCE@FTC.GOV" (Jan 13, 7:36pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 13, 7:36pm, Jim Bryant wrote: } Subject: Forward all spam to UCE@FTC.GOV } This announcement is located on the Federal Trade Commission's } complaint form page http://www.ftc.gov/ftc/complaint.htm } } ------------------ } If you would like to forward unsolicited commercial e-mail (spam) to } the Commission, please send it directly to UCE@FTC.GOV without using } this form. } ------------------ } } Could this be added to sendmail.cf somehow by default? maybe as a } comment? Maybe as some kind of autoforwarder in spam filtering? This would also forward non UCE spam (religious, revenge spams, etc.) as well as any false positives that tripped the spam filter. Also, not all UCE type spams are best reported to the UCE address. Stock spams should be reported to the SEC, and quack medicines should be reported to the FDA. I also think that overstuffing the FTC mailbox may make them less effective at whacking the spammers that need it the most. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 06:36:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12207 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 06:36:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12176 for ; Thu, 14 Jan 1999 06:35:51 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:gYyZRwFKOZv6CZx2l1RZrLmgPtYzQueD@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id XAA17976; Thu, 14 Jan 1999 23:34:20 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA10694; Thu, 14 Jan 1999 23:36:49 +0900 (JST) Message-Id: <199901141436.XAA10694@zodiac.mech.utsunomiya-u.ac.jp> To: Don Lewis cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Forward all spam to UCE@FTC.GOV In-reply-to: Your message of "Thu, 14 Jan 1999 06:11:24 PST." <199901141411.GAA25453@salsa.gv.tsc.tdk.com> References: <199901141411.GAA25453@salsa.gv.tsc.tdk.com> Date: Thu, 14 Jan 1999 23:36:49 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sort of forwarding facility should be an option; do not make it default! FreeBSD is used not only in US, but also all over the world, you know. I don't think FTC would in any way like to deal with spams outside of US. Kazu >On Jan 13, 7:36pm, Jim Bryant wrote: >} Subject: Forward all spam to UCE@FTC.GOV >} This announcement is located on the Federal Trade Commission's >} complaint form page http://www.ftc.gov/ftc/complaint.htm >} >} ------------------ >} If you would like to forward unsolicited commercial e-mail (spam) to >} the Commission, please send it directly to UCE@FTC.GOV without using >} this form. >} ------------------ >} >} Could this be added to sendmail.cf somehow by default? maybe as a >} comment? Maybe as some kind of autoforwarder in spam filtering? > >This would also forward non UCE spam (religious, revenge spams, etc.) >as well as any false positives that tripped the spam filter. Also, >not all UCE type spams are best reported to the UCE address. Stock >spams should be reported to the SEC, and quack medicines should be >reported to the FDA. I also think that overstuffing the FTC mailbox >may make them less effective at whacking the spammers that need it >the most. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 07:07:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15730 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 07:07:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p90.tfs.net [139.146.210.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15718 for ; Thu, 14 Jan 1999 07:07:07 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id JAA65083; Thu, 14 Jan 1999 09:05:43 -0600 (CST) From: Jim Bryant Message-Id: <199901141505.JAA65083@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <199901141436.XAA10694@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 14, 99 11:36:49 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 14 Jan 1999 09:05:39 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: > This sort of forwarding facility should be an option; do not make it > default! FreeBSD is used not only in US, but also all over the world, > you know. I don't think FTC would in any way like to deal with spams > outside of US. > > Kazu > > >On Jan 13, 7:36pm, Jim Bryant wrote: > >} Subject: Forward all spam to UCE@FTC.GOV > >} This announcement is located on the Federal Trade Commission's > >} complaint form page http://www.ftc.gov/ftc/complaint.htm > >} > >} ------------------ > >} If you would like to forward unsolicited commercial e-mail (spam) to > >} the Commission, please send it directly to UCE@FTC.GOV without using > >} this form. > >} ------------------ > >} > >} Could this be added to sendmail.cf somehow by default? maybe as a > >} comment? Maybe as some kind of autoforwarder in spam filtering? > > > >This would also forward non UCE spam (religious, revenge spams, etc.) > >as well as any false positives that tripped the spam filter. Also, > >not all UCE type spams are best reported to the UCE address. Stock > >spams should be reported to the SEC, and quack medicines should be > >reported to the FDA. I also think that overstuffing the FTC mailbox > >may make them less effective at whacking the spammers that need it > >the most. i understand your point of view, even though I disagree with it to an extent. the ftc must be made aware of all spam terminating in the us. the sec and fda are secondary recipients in all cases, the ftc handles trade issues, and has the authority to forward to other agencies for further actions. regulation, on a worldwide scale, is only a matter of when, not if. that time is probably going to come a lot faster than a lot of people think. IMHO, it should have been done five years ago when the abusers started showing up in force. all internationally originated or relayed spam is just as important so as to intelligently allow the state department here to draft new, and more effective telecommunications treaties that could potentially punish countries who don't take spam seriously. having an autoforwarder forward all spam to the ftc address, including false positives, can only help our government realize the extent of the problem, and the state of the technologies that currently attempt to fight it. also, we need isps to get a bit more responsible. if you identify a local high-volume spammer, hire a dump truck, buy a load of manure, and dump it on the front yard of the spammer's home/business. call it freedom of speech, they do. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 07:15:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16801 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 07:15:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16796 for ; Thu, 14 Jan 1999 07:15:17 -0800 (PST) (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 HAA08930; Thu, 14 Jan 1999 07:14:01 -0800 (PST) (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 HAA16327; Thu, 14 Jan 1999 07:14:00 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id HAA25643; Thu, 14 Jan 1999 07:13:59 -0800 (PST) From: Don Lewis Message-Id: <199901141513.HAA25643@salsa.gv.tsc.tdk.com> Date: Thu, 14 Jan 1999 07:13:59 -0800 In-Reply-To: Greg Lehey "Mounting on NFS directories: is this kosher?" (Jan 14, 5:38pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Greg Lehey , FreeBSD Hackers Subject: Re: Mounting on NFS directories: is this kosher? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 14, 5:38pm, Greg Lehey wrote: } Subject: Mounting on NFS directories: is this kosher? } } Here, the Vinum volume /dev/vinum/src is mounted on the nfs file } system freebie:/src. Is this allowed? Sure, why not? } An attempt to umount /src } fails with Device busy, but it seems that I've heard you're not } allowed to mount on nfs directories. That would make it kind of hard to access multiple filesystems on a diskless machine. The only real problem with mounting (NFS or otherwise) on an NFS filesystem is that if the server for the NFS filesystem dies, you can't access the filesystems that are mounted on it because any process that tries to traverse the path will wedge, and you can't unmount the NFS filesystem because because it is busy. If you can't restart the dead server, the only way to clean things up on the client is to reboot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 08:34:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25802 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 08:34:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25797 for ; Thu, 14 Jan 1999 08:34:54 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA07797; Thu, 14 Jan 1999 09:32:31 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <369E1C1F.41BAE1F9@softweyr.com> Date: Thu, 14 Jan 1999 09:32:31 -0700 From: Wes =?iso-8859-1?Q?Peters=D4?==?iso-8859-1?Q?=40=21=EA?= =?iso-8859-1?Q?=80?==?iso-8859-1?Q?=EA?==?iso-8859-1?Q?=80=DD=E7?= =?iso-8859-1?Q?=805=EA?==?iso-8859-1?Q?=C0?==?iso-8859-1?Q?=EA?= Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn CC: Reinier Bezuidenhout , hackers@FreeBSD.ORG Subject: Re: Dysan cdrom and 3.0 problems References: <33148.916310496@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Sat, 14 Jan 1999 10:48:37 +0200, Reinier Bezuidenhout wrote: > > > Shouldn't it attach acd0 or something to the atapi cdrom ?? > > No. It "attaches" wcd* "to the atapi cdrom", to use your wording. Right, a healthy probe should show: wdc0: unit 1 (atapi): < ICD-1200AT/ A01>, removable, dma, iordy wcd0: 1367Kb/sec, 120Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked If you don't see a wcdx line in the boot messages, your system has failed to recognize the device and attach a driver. IDE CD-ROMs are cheap, can you try another? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 08:46:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27442 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 08:46:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27437 for ; Thu, 14 Jan 1999 08:46:39 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA07830; Thu, 14 Jan 1999 09:45:23 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <369E1F23.AD6078D6@softweyr.com> Date: Thu, 14 Jan 1999 09:45:23 -0700 From: Wes =?iso-8859-1?Q?Peters=D4?==?iso-8859-1?Q?=40=21=EA?= =?iso-8859-1?Q?=80?==?iso-8859-1?Q?=EA?==?iso-8859-1?Q?=80=DD=E7?= =?iso-8859-1?Q?=805=EA?==?iso-8859-1?Q?=C0?==?iso-8859-1?Q?=EA?= Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tony Finch CC: hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM References: <199901140720.XAA22609@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch wrote: > > Luigi Rizzo wrote: > > > >very nice review. Now can you do a similar thing for the FreeBSD VM ? > > Matt already has: http://apollo.backplane.com/FreeBSD/FreeBSDVM.txt How do the relative strengths and weaknesses of the Linux and FreeBSD VMs stack up against the NetBSD UVM? (I'm no VM expert, but I imagine the NetBSD one must be complicated somewhat by the bewildering array of architectures they support. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 09:23:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03309 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 09:23:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03303 for ; Thu, 14 Jan 1999 09:23:19 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:w35JcRSDmr3DWzBf17UQzo7VSggkusZI@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id CAA18469; Fri, 15 Jan 1999 02:21:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id CAA11334; Fri, 15 Jan 1999 02:24:26 +0900 (JST) Message-Id: <199901141724.CAA11334@zodiac.mech.utsunomiya-u.ac.jp> To: jbryant@unix.tfs.net cc: freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Forward all spam to UCE@FTC.GOV In-reply-to: Your message of "Thu, 14 Jan 1999 09:05:39 CST." <199901141505.JAA65083@unix.tfs.net> References: <199901141505.JAA65083@unix.tfs.net> Date: Fri, 15 Jan 1999 02:24:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This sort of forwarding facility should be an option; do not make it >> default! FreeBSD is used not only in US, but also all over the world, >> you know. I don't think FTC would in any way like to deal with spams >> outside of US. >> >> Kazu [...] >i understand your point of view, even though I disagree with it to an >extent. Well, you seem to believe FreeBSD systems exist only in US.... >the ftc must be made aware of all spam terminating in the us. the sec ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >and fda are secondary recipients in all cases, the ftc handles trade >issues, and has the authority to forward to other agencies for further >actions. I can understand that you want the FTC to deal with spams arriving in US. But, if you enable forwarding to the FTC in sendmail.cf, the FTC will also receive spams which originate outside US and end outside US. I ran a FreeBSD box in Japan, you know. And I receive spams originate in Japan, written in Japanese and delivered in Japan. And you want my sendmail to forward these spams to the FTC? (Not that I love these spams and would like to keep :-) >all internationally originated or relayed spam is just as important so ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >as to intelligently allow the state department here to draft new, and >more effective telecommunications treaties that could potentially >punish countries who don't take spam seriously. I do understand that the FTC should be made aware of spams arriving in US from outside. But, I don't think forwarding all spams circulating only outside US and never reaching US is necessary too. Do you want the FTC to make a collection of spam mails of entire world? >having an autoforwarder forward all spam to the ftc address, including >false positives, can only help our government realize the extent of >the problem, and the state of the technologies that currently attempt >to fight it. Ok, your goverment will realize the scale of the problem. What about other goverments in the world? Are we going to forward spams to them too? Kazu >also, we need isps to get a bit more responsible. if you identify a >local high-volume spammer, hire a dump truck, buy a load of manure, >and dump it on the front yard of the spammer's home/business. call it >freedom of speech, they do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 10:14:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10349 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 10:14:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p11.tfs.net [139.146.210.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10343 for ; Thu, 14 Jan 1999 10:14:16 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id MAA66211; Thu, 14 Jan 1999 12:12:52 -0600 (CST) From: Jim Bryant Message-Id: <199901141812.MAA66211@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <199901141724.CAA11334@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 15, 99 02:24:26 am" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 14 Jan 1999 12:12:48 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: > >> This sort of forwarding facility should be an option; do not make it > >> default! FreeBSD is used not only in US, but also all over the world, > >> you know. I don't think FTC would in any way like to deal with spams > >> outside of US. > >> > >> Kazu > [...] > >i understand your point of view, even though I disagree with it to an > >extent. > > Well, you seem to believe FreeBSD systems exist only in US.... actually i don't... and i agree that it should be an option. something that is already set up, and can be turned on with either a switch or by uncommenting something. > I ran a FreeBSD box in Japan, you know. And I receive spams originate > in Japan, written in Japanese and delivered in Japan. And you want my > sendmail to forward these spams to the FTC? (Not that I love these > spams and would like to keep :-) maybe we can get a list of governmental agencies for forwarding in several countries. i'm sure there are as many pissed-off japanese as there are pissed-off americans. no doubt the japanese government and others will be involved in any treaty negotiations on the issue. > Ok, your goverment will realize the scale of the problem. What about > other goverments in the world? Are we going to forward spams to them > too? well, if our government has set up such a forwarding address, i'm sure many others will set up their own for spam terminating in their countries. and if they don't have one, make them set one up. internet regulation is only a matter of time [long overdue]. let's make our governments aware so that they can regulate intelligently. the united states government is asking for spam terminating here to be forwarded to them for this reason. other governments will follow in like manner in short time. > >also, we need isps to get a bit more responsible. if you identify a > >local high-volume spammer, hire a dump truck, buy a load of manure, > >and dump it on the front yard of the spammer's home/business. call it > >freedom of speech, they do. i was being perfectly and legally serious about that. without the fear of retribution, self-regulation has always failed miserably throughout history. if a spammer has nothing to fear for as a result of his actions, he will continue. if it takes dumping truckloads of manure on spammer's front porches to wake up legislators, let's do it. right now, in the climate of "self-regulation" this falls into the realm of legal possiblity. here in the usa, any injunction against dumping the manure can be fought on a freedom of speech defense. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 10:24:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11825 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 10:24:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11811 for ; Thu, 14 Jan 1999 10:24:15 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.1/8.8.8) id SAA71863; Thu, 14 Jan 1999 18:22:42 GMT (envelope-from joe) Date: Thu, 14 Jan 1999 18:22:42 +0000 From: Josef Karthauser To: Gianmarco Giovannelli Cc: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? Message-ID: <19990114182241.A63613@florence.pavilion.net> References: <199901121404.WAA66113@spinner.netplex.com.au> <4.1.19990113134850.009484f0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <4.1.19990113134850.009484f0@194.184.65.4>; from Gianmarco Giovannelli on Wed, Jan 13, 1999 at 01:57:06PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-1273-607072 Fax: +44-1273-607073 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 01:57:06PM +0100, Gianmarco Giovannelli wrote: > > Amiga was an incredible system and we (amiga users) were a wonderfull "race" > :-) > My "little-used Amiga is still here, sitting in a corner", perhaps in the > future > her 68040 will kick again. > > Sorry for the off-topics (it was my first and the last:-) > I wondered where all the Amiga programmers went - I too get the same kicks out of FreeBSD that I got out of programming the Amiga, apart from this time I get _all_ the source code :) :) Long live FreeBSD. Joe (Excitable chap today aren't I :) -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 10:31:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12987 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 10:31:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12972 for ; Thu, 14 Jan 1999 10:31:04 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.1/8.8.8) id SAA72740; Thu, 14 Jan 1999 18:28:16 GMT (envelope-from joe) Date: Thu, 14 Jan 1999 18:28:16 +0000 From: Josef Karthauser To: Marcin Cieslak Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: libalias and ident Message-ID: <19990114182816.B63613@florence.pavilion.net> References: <91306.916286248@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Marcin Cieslak on Thu, Jan 14, 1999 at 12:42:15PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-1273-607072 Fax: +44-1273-607073 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 14, 1999 at 12:42:15PM +0100, Marcin Cieslak wrote: > On Wed, 13 Jan 1999, Jordan K. Hubbard wrote: > > > Hear hear! Just be sure that Brian changes ppp also so that it > > becomes -nat with -alias as a backwards-compat option only. :) > > Isn't NAT copyrighted by Cisco or whoever? :) I don't believe so, at least RFC1631 (The IP Network Address Translator (NAT)) doesn't claim so. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 11:01:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18484 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 11:01:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18464 for ; Thu, 14 Jan 1999 11:01:27 -0800 (PST) (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 NAA21129; Thu, 14 Jan 1999 13:59:21 -0500 (EST) Date: Thu, 14 Jan 1999 13:59:21 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kazutaka YOKOTA cc: Don Lewis , jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <199901141436.XAA10694@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Jan 1999, Kazutaka YOKOTA wrote: > This sort of forwarding facility should be an option; do not make it > default! FreeBSD is used not only in US, but also all over the world, > you know. I don't think FTC would in any way like to deal with spams > outside of US. Besides which, if every freebsd machine had it turned on by default, the FTC would receive tens of thousands of copies of each spam (and all via automated delivery) so we would be in effect spamming them. Let's not discourage them from having such an address because it gets mailbombed by freebsd hosts :). Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 11:15:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21274 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 11:15:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21256; Thu, 14 Jan 1999 11:15:21 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA23974; Thu, 14 Jan 1999 19:12:21 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.1) with ESMTP id IAA44254; Thu, 14 Jan 1999 08:59:51 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901140859.IAA44254@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Eivind Eklund , "Joseph T. Lee" , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Gratuitous name changes (was: libalias and ident) In-reply-to: Your message of "Wed, 13 Jan 1999 19:57:28 PST." <91306.916286248@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Jan 1999 08:59:51 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-current cc'd for feedback] > > While we're at it, I think the library should be renamed to libnat. > > Hear hear! Just be sure that Brian changes ppp also so that it > becomes -nat with -alias as a backwards-compat option only. :) If libalias changes to libnat, I'd prefer to just change the ppp flag to -nat, update the ppp version to 2.1 and update src/usr.sbin/ppp/README.changes, otherwise I'll be running around with the crud forever. But this isn't necessarily a good idea as it may attract a pile of ``why the hell did you break my configuration for no good reason'' messages. Anyone with any strong opinions on this ? Of course it's not guaranteed that libalias will change to libnat, there's another thread starting on -hackers about that :-) It's also possible to change the ppp flag, even if libalias isn't renamed. > - Jordan -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 11:16:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21509 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 11:16:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21364; Thu, 14 Jan 1999 11:15:58 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA23988; Thu, 14 Jan 1999 19:13:09 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.1) with ESMTP id IAA44236; Thu, 14 Jan 1999 08:51:57 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901140851.IAA44236@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: "Joseph T. Lee" , hackers@FreeBSD.ORG, Charles Mott , Ari Suutari Subject: Re: libalias and ident (& API changes) In-reply-to: Your message of "Thu, 14 Jan 1999 04:29:51 +0100." <19990114042951.I76923@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Jan 1999 08:51:57 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charles & Ari cc'd] [discussion about supporting ident queries back through libalias] > On Wed, Jan 13, 1999 at 02:22:45PM -0800, Joseph T. Lee wrote: > > Any better ways to hack around this crux would be most welcome. > > I think the only way to do this is > > (1) 'Take over' port 113, faking an endpoint for all connections to > it. > (2) When the actual request comes in, parse it to find out which > alias_link it belongs to. If it doesn't belong to any, synthezise a > 'not found' response and be done. Otherwise, start creating a > TCP-connection to true target, where you'll be repeating the request > (with appropriate sequence number skew etc). > (3) Create an alias_link for the ingoing connection. > > Of course, all of this requires that you are able to synthesise new > packets, not just modify or drop packets. The present libalias API is > not up to it; the API must be re-done, and all the clients updated. > > While we're at it, I think the library should be renamed to libnat. > The code should also be made to not use these enormous amounts of > global data, but instead work on data structures passed in by the > client - this allow several instances in a single unit, and makes it > much more suitable for more serious use. I agree with the data localisation and don't really care one way or the other about the naming. However, Charles Mott (the libalias author - cc'd) had something to say about this last time it was discussed IIRC. > Eivind. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 11:25:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22907 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 11:25:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22900 for ; Thu, 14 Jan 1999 11:25:53 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA16485; Thu, 14 Jan 1999 14:24:44 -0500 (EST) Message-ID: <19990114142444.A7476@netmonger.net> Date: Thu, 14 Jan 1999 14:24:44 -0500 From: Christopher Masto To: hackers@FreeBSD.ORG Subject: Re: What are the advantages of ELF kernels? References: <199901121404.WAA66113@spinner.netplex.com.au> <4.1.19990113134850.009484f0@194.184.65.4> <19990114182241.A63613@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990114182241.A63613@florence.pavilion.net>; from Josef Karthauser on Thu, Jan 14, 1999 at 06:22:42PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 14, 1999 at 06:22:42PM +0000, Josef Karthauser wrote: > I wondered where all the Amiga programmers went - I too get the same kicks There's definately an eerie connection somewhere. When I was in high school, I ran a bulletin board on my little A500 and even had it hooked up to that network of big scary unix machines with Internet e-mail and a newsfeed, thanks to Matt's DUUCP. Also thanks to some nice guy named Steve in Massachussets who ran a node called genesis and was willing to let us try it, though these uucico and L.sys and such might as well have been alien technology to me at the time. Many years later I had a go at patching up the floppy tape driver and what do I find at the bottom of the man page? AUTHORS Steve Gerakines If you're out there somewhere Steve, thanks! toshiki!exidor aka postmaster@toshiki.broadalbin.ny.us aka -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 11:27:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23355 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 11:27:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23305; Thu, 14 Jan 1999 11:26:52 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id UAA19603; Thu, 14 Jan 1999 20:25:42 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA90126; Thu, 14 Jan 1999 20:25:40 +0100 (MET) Date: Thu, 14 Jan 1999 20:25:40 +0100 From: Eivind Eklund To: Brian Somers Cc: "Jordan K. Hubbard" , "Joseph T. Lee" , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Gratuitous name changes (was: libalias and ident) Message-ID: <19990114202540.C88792@bitbox.follo.net> References: <91306.916286248@zippy.cdrom.com> <199901140859.IAA44254@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901140859.IAA44254@keep.lan.Awfulhak.org>; from Brian Somers on Thu, Jan 14, 1999 at 08:59:51AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 14, 1999 at 08:59:51AM +0000, Brian Somers wrote: > If libalias changes to libnat, I'd prefer to just change the ppp flag > to -nat, update the ppp version to 2.1 and update > src/usr.sbin/ppp/README.changes, otherwise I'll be running around > with the crud forever. > > But this isn't necessarily a good idea as it may attract a pile of > ``why the hell did you break my configuration for no good reason'' > messages. I think the old option should stay around for backwards compatibility through at least one branch; however, I'd also suggest adding -nat as an option _now_, as -alias is pretty non-intuitive. Of course, as you'll probably have to deal with the largest amount of crud, you're free to make the choice. > Of course it's not guaranteed that libalias will change to libnat, > there's another thread starting on -hackers about that :-) It's also > possible to change the ppp flag, even if libalias isn't renamed. As we'll have to do really significant API changes if this is to work, I don't think it matters much if it keep the same name, so we could just as well rename it when we have the chance. Whether apps use libalias.so v1 vs libalias.so v2 or libalias v1 vs libnat v1 should IMO not really matter much from the point of view of the program - and then we can get rid of our private terminology. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 12:05:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29460 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 12:05:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29411 for ; Thu, 14 Jan 1999 12:04:52 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.195]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1189; Thu, 14 Jan 1999 21:03:36 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990114094837.B17491@ucb.crimea.ua> Date: Thu, 14 Jan 1999 21:11:21 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Ruslan Ermilov Subject: Re: cvs question Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-99 Ruslan Ermilov wrote: > On Wed, Jan 13, 1999 at 08:23:39PM +0100, Jeroen Ruigrok/Asmodai wrote: >> I made the base and prefix directory both /usr so CVSROOT lies in /usr >> > > I think it's a bad idea. You'd better make your CVSROOT as > /usr/FreeBSD-CVS. Well, I didn't have much to say about it at first ;) >> >> I looked in CVSROOT and saw that there were some log entries regarding >> hardlinked /home/ncvs for CVSROOT which would be set back to $CVSROOT. >> But I have no clue whatsoever where this /home/ncvs comes from. >> >> Any ideas are appreciated... > > I guess you have your /usr/src, /usr/ports installed from your Release > CD-ROM. You may want to delete them, and then `cvs co' from your local > CVSROOT. Ehm no, frankly I went ahead and used the `other' cvsup process that gets the checked out versions of the sources. Hmm guess those might have some sort of reference to it... Will try it, spanks ;) --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 12:29:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02933 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 12:29:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02886; Thu, 14 Jan 1999 12:28:47 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 14 Jan 1999 15:27:07 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 14 Jan 1999 12:27:03 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 14 Jan 1999 15:27:02 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: "Jordan K. Hubbard" , Eivind Eklund , "Joseph T. Lee" , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Gratuitous name changes (was: libalias and ident) In-Reply-To: Brian Somers's (brian@Awfulhak.org) message dated Thu, 14 Jan 1999 08:59:51. <199901140859.IAA44254@keep.lan.Awfulhak.org> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Jan 1999 15:27:02 -0500 Message-ID: <7351.916345622@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the few things that irritate me (and I now expect) is that every so often, Somebody is going to change Something in the PPP configuration and I'll need to go in to my box (and the boxes at all of my customer sites) and reconfigure ppp.conf. It's why I always update my boxes fist, get a clean compile, update my customers' boxes, get things stable on my end, and then pray I got everything right on my customers' boxes. While this is only an issue for my customers that use PPP, since I'm connecting to them over that link, if something goes wrong... H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 12:57:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06906 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 12:57:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p11.tfs.net [139.146.210.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06884; Thu, 14 Jan 1999 12:57:26 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id OAA66441; Thu, 14 Jan 1999 14:56:06 -0600 (CST) From: Jim Bryant Message-Id: <199901142056.OAA66441@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: from Alfred Perlstein at "Jan 14, 99 01:33:31 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Thu, 14 Jan 1999 14:55:58 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: > On Thu, 14 Jan 1999, Jim Bryant wrote: > > > In reply: > > > >> This sort of forwarding facility should be an option; do not make it > > > >> default! FreeBSD is used not only in US, but also all over the world, > > > >> you know. I don't think FTC would in any way like to deal with spams > > > >> outside of US. > > > >> > > > >> Kazu > > > [...] > > > >i understand your point of view, even though I disagree with it to an > > > >extent. > > > > > > Well, you seem to believe FreeBSD systems exist only in US.... > > > > actually i don't... and i agree that it should be an option. > > something that is already set up, and can be turned on with either a > > switch or by uncommenting something. > > (let's move this to -chat?) > > Since spam is mass mailing automating replies will swamp the poor folks at > FTC. > > If anything, a spam condensing local server for a region that co-odinated > with a centralized server to reduce dup'ing spam complaints (and perhaps > keep a count would be a good thing) you mean reduce the number of submissions to give a false impression that the problem isn't as bad as it really is. stop defending spammers. the more submissions, the faster something gets done. anything else would give a false impression that the problem is smaller than it really is, and thus more of the same ineffective regulation that we already have. let the reduction and counting be done by the FTC which more than probably already has such measures in place locally. let them standardize what they do with it, anything else is obstruction of justice. i'm sorry if i'm reading you wrong, but i understand how the government operates. also, anyone who doesn't take a hard-line stand on this topic can't be trusted, and is part of the problem. to not deal with spammers ruthlessly is to pander to spammers. if a million people forward a million copies of the exact same spam, but addressed to each individual that forwards it will get something done. one copy and a note saying that it went to a million people means nothing. a thousand individual spams a day forwarded by the recipients in a billon seperate submissions a day will have a new consumer-friendly/isp-friendly law passed in short order with means of enforcement. a thousand messages with a note saing that each went to a million people means nothing, and thus nothing gets done. let the FTC do the reduction. they did not ask for reduced data. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 13:24:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10719 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 13:24:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10704 for ; Thu, 14 Jan 1999 13:24:09 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA19924 for ; Thu, 14 Jan 1999 16:22:34 -0500 (EST) Date: Thu, 14 Jan 1999 16:22:33 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: TSS and context switch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am a little surprised to see that the TSS mechanism is not used in context switch done by FreeBSD. In cpu_switch(), we save the return address (the one immediately follows the cpu_switch() call) of the current process. We do not jump to a TSS selector (like in SCO UNIX) to do a context switch. I am wondering why FreeBSD does not use the underlying hardware feature which provides a clean separation between tasks (processes) and does so in an efficient way (I assume that hardware is always faster than software when doing the same job). Although we use the same format (see tss.h) as that defined by hardware, we save and restore registers "manually". Also, please confirm my understanding: any process calling cpu_switch() will resume execution *right after* the cpu_switch() call. We achieve this by modifing the stack before the instruction ret: movl PCB_EIP(%edx), %eax <-- at the end of cpu_switch() movl %eax, (%esp) .... ret By the way, the only place I find the TSS mechanism is used in FreeBSD is the double fault handling, where a task gate is put into the IDT. Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 13:31:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11549 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 13:31:33 -0800 (PST) (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 NAA11541 for ; Thu, 14 Jan 1999 13:31:29 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id QAA08154; Thu, 14 Jan 1999 16:25:17 -0500 Date: Thu, 14 Jan 1999 16:25:16 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: zhihuizhang cc: hackers Subject: Re: TSS and context switch 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'm assuming you measured all this and determined that TSS was faster? Ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 15:00:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24271 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 15:00:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24241 for ; Thu, 14 Jan 1999 15:00:04 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (qmail 4207 invoked from network); 14 Jan 1999 22:58:08 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 14 Jan 1999 22:58:08 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id RAA18466; Thu, 14 Jan 1999 17:58:02 -0500 (EST) From: "John S. Dyson" Message-Id: <199901142258.RAA18466@dyson.iquest.net> Subject: Re: Review and report of linux kernel VM In-Reply-To: <199901140720.XAA22609@apollo.backplane.com> from Matthew Dillon at "Jan 13, 99 11:20:22 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 14 Jan 1999 17:57:57 -0500 (EST) Cc: root@dyson.iquest.net, dg@root.com, jkh@FreeBSD.ORG, hackers@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 general terms, linux's VM system is much cleaner then FreeBSD's... and > I mean a *whole lot* cleaner, but at the cost of eating some extra memory. > It isn't a whole lot of extra memory - maybe a meg or two for a typical > system managing a lot of processes, and much less for typical 'small' > systems. They are able to completely avoid the vm_object stacking > (and related complexity) that we do, and they are able to completely > avoid most of the pmap complexity in FreeBSD as well. > IMO, the "cleaness" might be better described as "too simple." > > Linux appears to map all of physical memory into KVM. This avoids > FreeBSD's (struct buf) complexity at the cost of not being able to > deal with huge-memory configurations. I'm not 100% sure of this, but > its my read of the code until someone corrects me. > I suggest that we should get rid of the (struct buf) complexity by creating the concept of temporary kernel mappings. Such mappings are a resource limited so that the system doesn't have to map all of memory, yet have a cleaner, more consistant scheme than the current. The vm_page_t's at the end of the struct bufs were only a first step in that arena. There are about 5-10 more steps needed before it is really fully realized. > > * For the nominal page scan, it is using a one-hand clock algorithm. > All I can say is: Oh my god! Are they nuts? That was abandoned > a decade ago. The priority mechanism they've implemented is nearly > useless. > > * To locate pages to swap out, it takes a pass through the task list. > Ostensibly it locates the task with the largest RSS to then try to > swap pages out from rather then select pages that are not in use. > From my read of the code, it also botches this badly. > Yep, and it has been very difficult for me not to "educate" them on the right way to do it. Frankly, their code works really well until it is overused. Given the Linux VM code, "overused" mostly means used at all. :-). > > Linux does not appear to do any page coloring whatsoever, but it would > not be hard to add it in. > It wasn't hard to add to FreeBSD, but the coloring should be moved to a machine dependent section of the codebase. > > Linux cannot swap-out its page tables or page directories. Thus, idle > tasks can eat a significant amount of memory. This isn't a big deal for > most systems ( small systems: no problem. Big systems: probably have lots > of memory anyway ). But, mmap()'d files can create a significant burden > if you have a lot of forked processes ( news, sendmail, web server, > etc...). Not only does Linux have to scan the page tables for all the > processes mapping the file, whether or not they are actively using the > page being checked for, but Linux's swapout algorithm scans page tables > and, effectively, makes redundant scans of shared objects. > The key here is to NEVER swap out page tables or page directories. One should FREE them when it is possible. The notion of a dirty page table, or on that is on disk is meaningless. The FreeBSD code releases page table pages when they are empty. Page directories should be freeable when all descendants are no longer mapped (including page tables.) Of course, in that evaulation, the kernel mappings should be ignored, and when "swapping" page directories in, they are rebuilt from the kernel requirments. (FreeBSD doesn't release page directories yet, unless a process exits.) > What FreeBSD can learn > > Well, the main thing is that the Linux VM system is very, very clean > compared to the FreeBSD implementation. Cleaning up FreeBSD's VM system > complexity is what I've been concentrating on and will continue to > concentrate on. However, part of the reason that FreeBSD's VM system > is more complex is because it does not use the page tables to store > reference information. Instead, it uses the vm_object and pmap modules. > I actually like this feature of FreeBSD. A lot. > IMO, the pmap level is super flexible, but also there is too much stratification between the pmap code and the VM code. Layering is good for reference implementations, but also adds overhead. It would be "nice" to be able for the upper level VM code to simply modify page table entries sometimes, wouldn't it? One thing that I did in the FreeBSD code was to minimize the transitions between the pmap and VM layers. Perhaps that should be better defined, but if you wanted to rework the interfaces, you might see a major cleanup. > > The biggest thing we need to do to clean up our VM system is, basically, > to completely rewrite the struct buf filesystem buffering mechanism to > make it much, much less complex - basically it should only be used as > placeholders for read and write ops and not used to cache block number > mappings between the files and the VM system, nor should it be used to > map pages into KVM. Separating out these three mechanisms into three > different subsystems would simplify the code enormously, I think. For > example, we could implement a simple vm_object KVM mapping mechanism > using FreeBSD's existing vm_object stacking model to map portions of a > vm_object (aka filesystem partition) into KVM. > I agree. Take a look at using a seperate kernel mapping concept (there might even be some of that work still lying around somewhere.) You can then change buffers into what they should really be: I/O requests. The kernel mappings can be a dynamically allocated resource that are cached LRU or somesuch. Part of the technology to support them ended up being pmap_kenter/pmap_kremove and pmap_qenter/pmap_qremove. Without those, the temporary kernel mappings would have been terribly expensive. > > Linux demarks interrupts from supervisor code much better then we do. > If we move some of the more sophisticated operational capabilities > out of our interrupt subsystem, we could get rid of most of the spl*() > junk we currently have to do. This is a real sore spot in current > FreeBSD code. Interrupts are just too complex. I'd also get rid of > FreeBSD's intermediate 'software interrupt' layer, which is able to > do even more complex things then hard interrupt code. The latency > considerations just don't make any sense verses running pending software > interrupts synchronously in tsleep(), prior to actually sleeping. We > need to do this anyway ( or move softints to kernel threads ) to be able > to take advantage of SMP mechanisms. The *only* thing our interrupts > should be allowed to do is finish I/O on a page or use zalloc(). > Note that Linux doesn't even handle IDE PIO correctly, and has historically lost interrupts due to it (and they added a software interrupt scheme ot allow it to work.) IDE DMA saved their a**. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 15:24:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00738 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 15:24:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00731; Thu, 14 Jan 1999 15:24:51 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id PAA07241; Thu, 14 Jan 1999 15:23:20 -0800 (PST) Message-Id: <199901142323.PAA07241@lestat.nas.nasa.gov> To: "John S. Dyson" Cc: dillon@apollo.backplane.com (Matthew Dillon), root@dyson.iquest.net, dg@root.com, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 14 Jan 1999 15:23:20 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Jan 1999 17:57:57 -0500 (EST) "John S. Dyson" wrote: > implementations, but also adds overhead. It would be "nice" to be able > for the upper level VM code to simply modify page table entries sometimes, > wouldn't it? One thing that I did in the FreeBSD code was to minimize the It would? What if your architecture doesn't use page tables, in the traditional sense? (There are at least a couple modern RISC architectures for which this is the case...) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 16:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09983 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 16:13:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from stevie.loop.com (stevie-inet.loop.com [207.211.60.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09966 for ; Thu, 14 Jan 1999 16:12:58 -0800 (PST) (envelope-from icimjs@loop.com) Received: from knobel (p09.hwts15.loop.net [207.211.62.234]) by stevie.loop.com (8.9.1/8.9.1) with SMTP id QAA24296 for ; Thu, 14 Jan 1999 16:08:36 -0800 (PST) Message-Id: <3.0.5.32.19990114161019.015f59e0@pop.loop.com> X-Sender: icimjs@pop.loop.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 14 Jan 1999 16:10:19 -0800 To: freebsd-hackers@FreeBSD.ORG From: Elan Subject: sleep(unsigned) thread safe? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is it safe to call sleep in a threaded application? sleep is being called in a function that is running in a separate thread. Can that generate problems? TIA Elan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 16:24:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11537 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 16:24:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11519 for ; Thu, 14 Jan 1999 16:24:40 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id LAA16290; Fri, 15 Jan 1999 11:25:57 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901150025.LAA16290@cimlogic.com.au> Subject: Re: sleep(unsigned) thread safe? In-Reply-To: <3.0.5.32.19990114161019.015f59e0@pop.loop.com> from Elan at "Jan 14, 1999 4:10:19 pm" To: icimjs@loop.com (Elan) Date: Fri, 15 Jan 1999 11:25:56 +1100 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Elan wrote: > Hi, > > is it safe to call sleep in a threaded application? Yes it is. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 16:31:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12461 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 16:31:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12456 for ; Thu, 14 Jan 1999 16:31:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id JAA05942; Fri, 15 Jan 1999 09:30:19 +0900 (JST) Message-ID: <369E861E.8DE99189@newsguy.com> Date: Fri, 15 Jan 1999 09:04:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: jbryant@unix.tfs.net CC: Kazutaka YOKOTA , freebsd-hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV References: <199901141505.JAA65083@unix.tfs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > > i understand your point of view, even though I disagree with it to an > extent. You sure? Please explain exactly how your arguments below fit the "message in japanese, written by japanese, sent from a japanese site to a japanese on another japanese site" pov. > > the ftc must be made aware of all spam terminating in the us. the sec > and fda are secondary recipients in all cases, the ftc handles trade > issues, and has the authority to forward to other agencies for further > actions. > > regulation, on a worldwide scale, is only a matter of when, not if. > that time is probably going to come a lot faster than a lot of people > think. IMHO, it should have been done five years ago when the abusers > started showing up in force. > > all internationally originated or relayed spam is just as important so > as to intelligently allow the state department here to draft new, and > more effective telecommunications treaties that could potentially > punish countries who don't take spam seriously. > > having an autoforwarder forward all spam to the ftc address, including > false positives, can only help our government realize the extent of > the problem, and the state of the technologies that currently attempt > to fight it. > > also, we need isps to get a bit more responsible. if you identify a > local high-volume spammer, hire a dump truck, buy a load of manure, > and dump it on the front yard of the spammer's home/business. call it > freedom of speech, they do. > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ------------------------------------------------------------------------------ > Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw > voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant > ------------------------------------------------------------------------------ > HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 17:39:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21204 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 17:39:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21196 for ; Thu, 14 Jan 1999 17:39:02 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA00959; Fri, 15 Jan 1999 09:37:46 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA22504; Fri, 15 Jan 1999 09:37:46 +0800 Message-Id: <199901150137.JAA22504@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dillon@apollo.backplane.com cc: hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Jan 1999 09:37:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks good, fair & accurate. Now, do you have the cojones to post it to linux-kernel? 8^) Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 17:49:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22596 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 17:49:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22589 for ; Thu, 14 Jan 1999 17:49:04 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <8585-6537>; Fri, 15 Jan 1999 02:47:25 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id BAA58646 for ; Fri, 15 Jan 1999 01:36:25 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id BAA04190 for hackers@freebsd.org; Fri, 15 Jan 1999 01:36:36 +0100 (MET) Message-Id: <199901150036.BAA04190@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Fri, 15 Jan 99 01:36:33 +0100 To: hackers@FreeBSD.ORG Subject: Is there additional Zip drive doc available? Reply-To: ben@stuyts.nl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was looking at the Zip drivers (vpo.c etc) for a project I am doing. Basically we need to connect a Zip drive to an embedded computer's parallel port (nible mode), and the source of the FreeBSD drivers look very helpful in accomplishing this. Is there more docco available about the exact protocol? Preferably on the web? I looked at Iomega's home page, but there was nothing there that goes this deep. Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 17:52:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23055 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 17:52:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23028 for ; Thu, 14 Jan 1999 17:52:31 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id KAA10223; Fri, 15 Jan 1999 10:51:03 +0900 (JST) Message-ID: <369E9EF6.179F1A84@newsguy.com> Date: Fri, 15 Jan 1999 10:50:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Stephen Hocking-Senior Programmer PGS Tensor Perth CC: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM References: <199901150137.JAA22504@ariadne.tensor.pgs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > Looks good, fair & accurate. Now, do you have the cojones to post it to > linux-kernel? 8^) I think Dillon actually worked on Linux VM before seeing the light, isn't that so? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 18:55:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01111 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 18:55:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA01104 for ; Thu, 14 Jan 1999 18:55:15 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: "Ron G. Minnich" Cc: zhihuizhang , hackers Subject: Re: TSS and context switch References: From: "Robert V. Baron" Date: 14 Jan 1999 21:53:14 -0500 In-Reply-To: "Ron G. Minnich"'s message of Thu, 14 Jan 1999 16:25:16 -0500 (EST) Message-ID: Lines: 9 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron G. Minnich" writes: > I'm assuming you measured all this and determined that TSS was faster? > > Ron Let's make it simpler for him. Why don't you just let him look in the architecture manual for the 386/486/586 and PII and see how many cycles the load and save takes compared to what is done in practice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 19:57:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08568 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 19:57:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08561 for ; Thu, 14 Jan 1999 19:57:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA28463; Thu, 14 Jan 1999 19:56:11 -0800 (PST) (envelope-from dillon) Date: Thu, 14 Jan 1999 19:56:11 -0800 (PST) From: Matthew Dillon Message-Id: <199901150356.TAA28463@apollo.backplane.com> To: "Daniel C. Sobral" Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: :> :> Looks good, fair & accurate. Now, do you have the cojones to post it to :> linux-kernel? 8^) : :I think Dillon actually worked on Linux VM before seeing the light, :isn't that so? : :-- :Daniel C. Sobral (8-DCS) :dcs@newsguy.com : : If you sell your soul to the Devil and all you get is an MCSE from :it, you haven't gotten market rate. I did some minor work on the linux TCP stack about 3 iterations ago. Moving to FreeBSD was more an interest issue then a seeing-the-light issue. I also wrote dcron which was used in Linux for a bit, a long time ago. It should also be noted that I also did some work with the 4.2 and 4.3 kernels at UCB, long before either FreeBSD or Linux came on the scene and that is another reason why I moved over to FreeBSD. ( I changed the serial driver on the Perkin Elmer we had to use microcoded DMA rather then discrete serial interrupts. Unfortunately, the microcode was still subject to interrupt disablement so the improvement to the serial subsystem was only moderate ). I do feel that FreeBSD works better as an ISP platform, though, which is one reason why BEST went with FreeBSD rather then Linux. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 19:59:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08928 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 19:59:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08921 for ; Thu, 14 Jan 1999 19:59:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA28493; Thu, 14 Jan 1999 19:58:05 -0800 (PST) (envelope-from dillon) Date: Thu, 14 Jan 1999 19:58:05 -0800 (PST) From: Matthew Dillon Message-Id: <199901150358.TAA28493@apollo.backplane.com> To: Cc: Tony Finch , hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM References: <199901140720.XAA22609@apollo.backplane.com> <369E1F23.AD6078D6@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Tony Finch wrote: :> :> Luigi Rizzo wrote: :> > :> >very nice review. Now can you do a similar thing for the FreeBSD VM ? :> :> Matt already has: http://apollo.backplane.com/FreeBSD/FreeBSDVM.txt : :How do the relative strengths and weaknesses of the Linux and FreeBSD :VMs stack up against the NetBSD UVM? (I'm no VM expert, but I imagine :the NetBSD one must be complicated somewhat by the bewildering array :of architectures they support. ;^) : :-- : "Where am I, and what am I doing in this handbasket?" : :Wes Peters Softweyr LLC :http://www.softweyr.com/~softweyr wes@softweyr.com John's looked at UVM, I think. I haven't, so I can't comment. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:02:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09323 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:02:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09317 for ; Thu, 14 Jan 1999 20:02:34 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (qmail 13585 invoked from network); 15 Jan 1999 04:01:22 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 15 Jan 1999 04:01:22 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id XAA18990; Thu, 14 Jan 1999 23:01:19 -0500 (EST) From: "John S. Dyson" Message-Id: <199901150401.XAA18990@dyson.iquest.net> Subject: Re: Review and report of linux kernel VM In-Reply-To: <199901142323.PAA07241@lestat.nas.nasa.gov> from Jason Thorpe at "Jan 14, 99 03:23:20 pm" To: thorpej@nas.nasa.gov Date: Thu, 14 Jan 1999 23:01:18 -0500 (EST) Cc: dyson@dyson.iquest.net, dillon@apollo.backplane.com, root@dyson.iquest.net, dg@root.com, jkh@FreeBSD.ORG, hackers@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 > On Thu, 14 Jan 1999 17:57:57 -0500 (EST) > "John S. Dyson" wrote: > > > implementations, but also adds overhead. It would be "nice" to be able > > for the upper level VM code to simply modify page table entries sometimes, > > wouldn't it? One thing that I did in the FreeBSD code was to minimize the > > It would? What if your architecture doesn't use page tables, in the > traditional sense? (There are at least a couple modern RISC architectures > for which this is the case...) > In those cases, then they simulate the page table schemes. (I am VERY familiar with such, currently doing a port to such a machine.) However, if you look at the VM code, the issues of the layer transitions are significant. It is clear that there is *something* wrong with the place where the layering is between the upper and lower level VM code. I am not sure where to put it though. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:13:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10578 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:13:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10547; Thu, 14 Jan 1999 20:13:30 -0800 (PST) (envelope-from piet@cup.hp.com) Received: from hpfsvr02.cup.hp.com (root@hpfsvr02.cup.hp.com [15.28.74.198]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id UAA13222; Thu, 14 Jan 1999 20:09:05 -0800 (PST) Received: from hpfsvr02 (piet@localhost [127.0.0.1]) by hpfsvr02.cup.hp.com with SMTP (8.8.6/8.7.3 TIS Messaging 5.0) id UAA25388; Thu, 14 Jan 1999 20:09:04 -0800 (PST) Message-ID: <369EBF5F.23AC@cup.hp.com> Date: Thu, 14 Jan 1999 20:09:03 -0800 From: Piet Delaney Organization: Hewlett-Packard Co. X-Mailer: Mozilla 3.01 (X11; I; HP-UX B.10.20 9000/770) MIME-Version: 1.0 To: dg@root.com, ckempf@enigami.com CC: piet@hpfsvr02.cup.hp.com, piet@piet.net, obrien@nuxi.com, tef@postgres.dtcom.dp.ua, joe@monk.via.ne, stevet@acs.stritch.edu, casanoba@ailab10.sogang.ac.kr, fischer@nwe.ufl.edu, stealth-admin@viaduk.net, freebsd-questions@FreeBSD.ORG, gibbs@FreeBSD.ORG, edmond@shaman.cup.hp.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG, jack@rome.cs.miami.edu, deischen@iworks.InterWorks.org, hank@wsm.com, xiyuan@npc.haplink.com.cn, gigabyte@tpts1.seed.net.tw, info-gbt@giga-byte.com, freebsd-questions@FreeBSD.ORG, dg@root.com, nasir@asacomputers.com, rwm@tansoft.com, oblio@eyeintegrated.com, mango@staff.communique.net Subject: Looking for Suggestion on Booting FreeBSD 3.0 on a Gigabyte GA-6BXDS board with Dual Pentiun II and Adaptec 7895 Ultra Wide SCSI-3 Controlers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, Cory, Dave, Folks: I thought it was about time to try out FreeBSD, most likely 3.0, so I picked up a PC board from Gigabyte, the GA-6BXDS Dual Scsi-3 that has an onboard Adaptec 7895 controler. About a year ago you (David) said Justin was working on a 7895 scsi controler. I didn't see anything in the FreeBSD handbook on support for the Adaptic 7895 (seems to be getting rather out of date). Now I've read from Cory that you need a CAM scsi driver. Last I see it was still only available as patches. Why is it taking so long to get it integrated into the current src? So I have to get an IDE drive and install onto that, get the CAM patches (from where?), run patch, etc... and linux supports it a standard controler? I can't believe this. Perhaps you could update me on the 7895 support and perhaps have some suggestion on setting up this board to run FreeBSD. For example can I boot the 3.0 FreeBSD off of a CDROM on the scsi adapters; I sort of doubt it. Is the FreeBSD getting the information it needs from Gigabyte and Adaptec so that these boards are well supported? -piet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:15:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10874 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:15:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10869 for ; Thu, 14 Jan 1999 20:15:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA28638; Thu, 14 Jan 1999 20:08:32 -0800 (PST) (envelope-from dillon) Date: Thu, 14 Jan 1999 20:08:32 -0800 (PST) From: Matthew Dillon Message-Id: <199901150408.UAA28638@apollo.backplane.com> To: "Robert V. Baron" Cc: "Ron G. Minnich" , zhihuizhang , hackers Subject: Re: TSS and context switch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :"Ron G. Minnich" writes: : :> I'm assuming you measured all this and determined that TSS was faster? :> :> Ron :Let's make it simpler for him. Why don't you just let him look :in the architecture manual for the 386/486/586 and PII and see :how many cycles the load and save takes compared to what is done :in practice. The Intel TSS stuff is *extremely* *slow* compared to doing it with discrete instructions, especially since many of the major supervisory registers do not change. There are a number of intel instructions which were designed to run fast on a 486, which turn out to be dogs on higher-end cpu's. For example, the ENTER instruction is considerably slower then doing the frame pointer / stack pointer manipulation manually. There are many others. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:32:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13147 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:32:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13142; Thu, 14 Jan 1999 20:32:43 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id UAA08107; Thu, 14 Jan 1999 20:31:26 -0800 (PST) Message-Id: <199901150431.UAA08107@lestat.nas.nasa.gov> To: "John S. Dyson" Cc: dillon@apollo.backplane.com, root@dyson.iquest.net, dg@root.com, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 14 Jan 1999 20:31:25 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Jan 1999 23:01:18 -0500 (EST) "John S. Dyson" wrote: > In those cases, then they simulate the page table schemes. (I am > VERY familiar with such, currently doing a port to such a machine.) Ewww, yuck! :-) Anyhow, the copying of PTEs or whatever is precisely what pmap_copy() is for, anyhow... and... > However, if you look at the VM code, the issues of the layer transitions > are significant. ...on these fancy RISC systems, the function calls are amazingly efficient because the architecture doesn't suck nearly as bad as the x86 :-) > It is clear that there is *something* wrong with the place where the > layering is between the upper and lower level VM code. I am not sure > where to put it though. Hm, why not spell out all the things that are wrong with it? Specifics, John, specifics. And, also, please use sentences that make sense :-) "...the place where the layering is between the upper and lower level..."? Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:34:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13384 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:34:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13377 for ; Thu, 14 Jan 1999 20:34:23 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id VAA08904; Thu, 14 Jan 1999 21:32:54 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <369EC4F6.EE0E27BD@softweyr.com> Date: Thu, 14 Jan 1999 21:32:54 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Hocking-Senior Programmer PGS Tensor Perth CC: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Review and report of linux kernel VM References: <199901150137.JAA22504@ariadne.tensor.pgs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > Looks good, fair & accurate. Now, do you have the cojones to post it to > linux-kernel? 8^) It's already been forwarded to Allan Cox, along with Mr. Dyson's followup. My doing, but only indirectly. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:40:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14156 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:40:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14075 for ; Thu, 14 Jan 1999 20:39:59 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id UAA08145; Thu, 14 Jan 1999 20:36:27 -0800 (PST) Message-Id: <199901150436.UAA08145@lestat.nas.nasa.gov> To: Matthew Dillon Cc: "Robert V. Baron" , "Ron G. Minnich" , zhihuizhang , hackers Subject: Re: TSS and context switch Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 14 Jan 1999 20:36:27 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Jan 1999 20:08:32 -0800 (PST) Matthew Dillon wrote: > There are a number of intel instructions which were designed to > run fast on a 486, which turn out to be dogs on higher-end cpu's. > For example, the ENTER instruction is considerably slower then > doing the frame pointer / stack pointer manipulation manually. > > There are many others. I distinctly remember there being several instructions on the VAX that were like this (perhaps the polynomial evaluation instructions.. it's been a while :-) ... you were better off open-coding them than using the single instruction :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:52:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15098 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:52:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15093 for ; Thu, 14 Jan 1999 20:52:50 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:KA1MOBzqumBUIueT8WeMHDbzVYkEUT1i@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id NAA19650; Fri, 15 Jan 1999 13:51:36 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA19828; Fri, 15 Jan 1999 13:54:05 +0900 (JST) Message-Id: <199901150454.NAA19828@zodiac.mech.utsunomiya-u.ac.jp> To: jbryant@unix.tfs.net cc: freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Forward all spam to UCE@FTC.GOV In-reply-to: Your message of "Thu, 14 Jan 1999 12:12:48 CST." <199901141812.MAA66211@unix.tfs.net> References: <199901141812.MAA66211@unix.tfs.net> Date: Fri, 15 Jan 1999 13:53:51 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> This sort of forwarding facility should be an option; do not make it >> >> default! FreeBSD is used not only in US, but also all over the world, >> >> you know. I don't think FTC would in any way like to deal with spams >> >> outside of US. >> >> >> >> Kazu >> [...] >> >i understand your point of view, even though I disagree with it to an >> >extent. >> >> Well, you seem to believe FreeBSD systems exist only in US.... > >actually i don't... and i agree that it should be an option. >something that is already set up, and can be turned on with either a >switch or by uncommenting something. So long as it is kept as an option, it's OK (although I am not 100% convinced that dumping every single spam mail to the authority is a good strategy...) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 20:58:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15834 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 20:58:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15829 for ; Thu, 14 Jan 1999 20:58:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA29086; Thu, 14 Jan 1999 20:56:53 -0800 (PST) (envelope-from dillon) Date: Thu, 14 Jan 1999 20:56:53 -0800 (PST) From: Matthew Dillon Message-Id: <199901150456.UAA29086@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: Path to SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone currently working on the next big step in the SMP puzzle? That is, implementing kernel threads with preemptive scheduling? The idea being that one then has the ability to run preemptable kernel threads in parallel on SMP-capable boxes because the code must assume preemption in the same manner on both uni and multi cpu systems. Once implemented, we would begin to migrate functionality from non-preemptive threads to preemptive threads from the outside-in, and parallel SMP operation in supervisor mode migrates along with it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 21:43:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22637 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 21:43:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beast.freibergnet.de (beast.freibergnet.de [194.123.255.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22605; Thu, 14 Jan 1999 21:43:24 -0800 (PST) (envelope-from mw@freibergnet.de) Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.11]) by beast.freibergnet.de (8.8.8/8.8.8) with ESMTP id GAA12426; Fri, 15 Jan 1999 06:32:31 +0100 (CET) (envelope-from mw@freibergnet.de) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <369EBF5F.23AC@cup.hp.com> Date: Fri, 15 Jan 1999 06:32:20 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Liebscher & Partner Werbeagentur und XLink-PoP Freiberg From: Martin Welk To: Piet Delaney Subject: RE: Looking for Suggestion on Booting FreeBSD 3.0 on a Gigabyte Cc: mango@staff.communique.net, oblio@eyeintegrated.com, rwm@tansoft.com, nasir@asacomputers.com, info-gbt@giga-byte.com, gigabyte@tpts1.seed.net.tw, xiyuan@npc.haplink.com.cn, hank@wsm.com, deischen@iworks.InterWorks.org, jack@rome.cs.miami.edu, current@FreeBSD.ORG, hackers@FreeBSD.ORG, edmond@shaman.cup.hp.com, gibbs@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, stealth-admin@viaduk.net, fischer@nwe.ufl.edu, casanoba@ailab10.sogang.ac.kr, stevet@acs.stritch.edu, joe@monk.via.ne, tef@postgres.dtcom.dp.ua, obrien@nuxi.com, piet@piet.net, piet@hpfsvr02.cup.hp.com, ckempf@enigami.com, dg@root.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jan-99 Piet Delaney wrote: () I thought it was about time to try out () FreeBSD, most likely 3.0, so I picked up a PC () board from Gigabyte, the GA-6BXDS Dual Scsi-3 () that has an onboard Adaptec 7895 controler. () About a year ago you (David) said Justin was working () on a 7895 scsi controler. I didn't see anything () in the FreeBSD handbook on support for the Adaptic () 7895 (seems to be getting rather out of date). () Now I've read from Cory that you need a CAM scsi () driver. Last I see it was still only available as () patches. Why is it taking so long to get it integrated () into the current src? So I have to get an IDE drive and () install onto that, get the CAM patches (from where?), () run patch, etc... and linux supports it a standard () controler? I can't believe this. 3.0-RELEASE and newer uses CAM as default supporting 7895 and a bunch of other newer Adaptec chipsets. We have three machines here with an Asus P2B-S motherboard that run fine. We have recently upgraded all of them to the 3.0-CURRENT tree as we run a local CVS archive. Seems like your information is pretty old. We have decided to use -CURRENT for what is usually called a "production machine" that won´t run very critical applications these days (our own fax server, our own news server, experimental database server). So we will see if it runs "stable enough" for our purpose. For now, it looks very good and we didn't experience any serious problems yet. () Perhaps you could update me on the 7895 support () and perhaps have some suggestion on setting up this () board to run FreeBSD. For example can I boot the () 3.0 FreeBSD off of a CDROM on the scsi adapters; () I sort of doubt it. My 3.0-RELEASE CD-ROM had no problems booting on the machines mentioned above. They also had no problems with running a custom install :-) Look at http://www.freebsd.org/ (which is always a good starting point for asking most main questions about FreeBSD) at the release information for 3.0. It says: 1. What's new since 2.2.X-RELEASE --------------------------------- All changes described here are unique to the 3.0 branch unless specifically marked as [MERGED] features. 1.1. KERNEL CHANGES ------------------- o The 2.2.x SCSI subsystem has been almost entirely replaced with a new "CAM" (Common Access Method) SCSI system which offers improved performance, better error recovery and support for more SCSI controllers. (and it says more, of course, but I didn´t to quote that all) There is also a 2.2-CAM tree available, but I have no experiences with that, look at ftp.freebsd.org. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 21:48:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23019 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 21:46:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA23013 for ; Thu, 14 Jan 1999 21:46:54 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (qmail 18301 invoked from network); 15 Jan 1999 05:45:40 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 15 Jan 1999 05:45:40 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id AAA19169; Fri, 15 Jan 1999 00:45:34 -0500 (EST) From: "John S. Dyson" Message-Id: <199901150545.AAA19169@dyson.iquest.net> Subject: Re: Review and report of linux kernel VM In-Reply-To: <199901150431.UAA08107@lestat.nas.nasa.gov> from Jason Thorpe at "Jan 14, 99 08:31:25 pm" To: thorpej@nas.nasa.gov Date: Fri, 15 Jan 1999 00:45:34 -0500 (EST) Cc: dyson@dyson.iquest.net, dillon@apollo.backplane.com, root@dyson.iquest.net, dg@root.com, jkh@FreeBSD.ORG, hackers@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 > > Anyhow, the copying of PTEs or whatever is precisely what pmap_copy() is > for, anyhow... and... > You are missing the point, and note that pmap_copy is only an obvious work-around for a small subset of the problem. It seems that those kinds of entry points were attempts (mostly in vain) to work around the pmap layering (and vm_fault) overheads. It seems to me (also) that vm_fault isn't quite at the right level -- at least a formal structure needs to be designed to support a fault mechanism that efficiently supports all types of processors. > > > However, if you look at the VM code, the issues of the layer transitions > > are significant. > > ...on these fancy RISC systems, the function calls are amazingly efficient > because the architecture doesn't suck nearly as bad as the x86 :-) > Why are alot (most) of those "fancy" RISC systems are actually slower than X86's :-)? Layer transitions cost relatively the same on current architectures -- I am not really interested in Vaxes, R3000's and 486's anymore. Sure, 486's are slow, but alot of the RISCs from that day were also slow. RISC systems do have that terrible overhead of macro instruction TLB mgmt, and that cost is often seen by those machines. Even though the benefits (better control, etc) are used as selling points, those "advantages" don't ever seem to provide value to anyone other than those who write sales brochures. However, all that said, I am working on a port of a TLB based RISC machine, and it will be fun :-). It seems to me the coolest thing about TLB-only MMUs is that they support variable page sizes. That is yet another challenge to take proper advantages of those capabilities (since TLB fills are often ugly, and it is good to minimize those, if you can at low cost.) I don't think that work on the current MACH code will go very far to optimize the use of TLBs (only alittle can be done in that structure), but a future VM system will be able to do a little more.) > > > It is clear that there is *something* wrong with the place where the > > layering is between the upper and lower level VM code. I am not sure > > where to put it though. > > Hm, why not spell out all the things that are wrong with it? Specifics, > John, specifics. And, also, please use sentences that make sense :-) > The things wrong with it are obvious -- too many layer transitions. RISC vs. CISC isn't the issue here. If you speak of pmap_copy, you are speaking of one optimization, but miss alot of the really wasteful VM system to pmap calls. I fixed alot more than just pmap copy (in fact, if you remove it from FreeBSD, you'll notice only a small performance difference.) The rest of the fixes vastly outweigh the pmap copy, preloading of pte's, and other such optimizations that are obvious, but only marginally valuable (in the scheme of things.) Actually, pmap_copy is MUCH MUCH less valuable on X86 architectures than preloading ptes. Now I am looking at "design" issues and far far beyond discussing minor implementation issues such as pmap_copy. > > "...the place where the layering is between the upper and lower level..."? > Jason, I guess you want to criticize me? :-). Maybe you cannot parse it, but you do understand? The place where the layering is, is not ideal (from a performance or even architectural standpoint.) I really am not sure where to split the machine dependent and machine independent layers yet in a new, re-thought out and modular VM system. There are aspects of current VM systems, including the inability to properly (cleanly) handle limited feature sets for (perhaps) embedded apps, that just need rethinking. I think that it is important to visit the problem again, divorcing onself from the arrogance associated with ownership of previous work, or arrogance associated with previous competition. Mostly, in this discussion, there is a statement of obvious problem, but the solution (and even the full formulation of the problem) needs to be thought about (probably iteratively.) I haven't seen an excellent VM system (ever), either commercial or free. That statement also includes FreeBSD's (mostly my baby). FreeBSD might work very very well, but it does have some limitations. The goal (for me) is for the new VM code to be appropriate for the new G2 kernel, and also applicable for other applications (perhaps.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 21:59:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24183 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 21:59:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24176 for ; Thu, 14 Jan 1999 21:59:21 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA09037; Thu, 14 Jan 1999 22:56:26 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <369ED88A.873515B3@softweyr.com> Date: Thu, 14 Jan 1999 22:56:26 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jason Thorpe CC: Matthew Dillon , "Robert V. Baron" , "Ron G. Minnich" , zhihuizhang , hackers Subject: Re: TSS and context switch References: <199901150436.UAA08145@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe wrote: > > On Thu, 14 Jan 1999 20:08:32 -0800 (PST) > Matthew Dillon wrote: > > > There are a number of intel instructions which were designed to > > run fast on a 486, which turn out to be dogs on higher-end cpu's. > > For example, the ENTER instruction is considerably slower then > > doing the frame pointer / stack pointer manipulation manually. > > > > There are many others. > > I distinctly remember there being several instructions on the VAX that > were like this (perhaps the polynomial evaluation instructions.. it's > been a while :-) ... you were better off open-coding them than using > the single instruction :-) ALL of the instructions on the VAX were like this, and some sucked even worse. ;^) Intel's history in this area dates all the way back to the 286 and PUSHA instruction, which was generally much slower than just pushing the registers you were going to diddle. Too bad they never grokked the concept of movem, huh? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 22:09:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25564 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 22:09:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p3.tfs.net [139.146.210.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25556 for ; Thu, 14 Jan 1999 22:08:58 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id AAA67506; Fri, 15 Jan 1999 00:07:32 -0600 (CST) From: Jim Bryant Message-Id: <199901150607.AAA67506@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <199901150454.NAA19828@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 15, 99 01:53:51 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Fri, 15 Jan 1999 00:07:27 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: > >> >> This sort of forwarding facility should be an option; do not make it > >> >> default! FreeBSD is used not only in US, but also all over the world, > >> >> you know. I don't think FTC would in any way like to deal with spams > >> >> outside of US. > >> >> > >> >> Kazu > >> [...] > >> >i understand your point of view, even though I disagree with it to an > >> >extent. > >> > >> Well, you seem to believe FreeBSD systems exist only in US.... > > > >actually i don't... and i agree that it should be an option. > >something that is already set up, and can be turned on with either a > >switch or by uncommenting something. > > So long as it is kept as an option, it's OK (although I am not 100% > convinced that dumping every single spam mail to the authority is a > good strategy...) it's what they asked for. really. their intent is clear. gathering evidence for use to obtain effective laws. i realize they probably don't have the staffing to handle each one, and i'm sure they realize that too, the intent is clear. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 23:29:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04141 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 23:29:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04131 for ; Thu, 14 Jan 1999 23:29:13 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id KAA11228 for ; Fri, 15 Jan 1999 10:27:41 +0300 (MSK) Received: from shuttle.svib.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by shuttle.svib.ru (8.8.8/8.8.8) with ESMTP id KAA18434 for ; Fri, 15 Jan 1999 10:27:47 +0300 (MSK) (envelope-from tarkhil@shuttle.svib.ru) Message-Id: <199901150727.KAA18434@shuttle.svib.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Disklabel repair tool X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Fri, 15 Jan 1999 10:27:47 +0300 From: Alex Povolotsky Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! After crashing my disklabel recently, I've written a small stupid program that helped me restore disklabel (all FSes were OK). Does FBSD community need this tool, completed to allow full auto recover of disklabel? Alex. -- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 14 23:57:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07506 for freebsd-hackers-outgoing; Thu, 14 Jan 1999 23:57:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07501 for ; Thu, 14 Jan 1999 23:57:30 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.9.1) with ESMTP id XAA02985; Thu, 14 Jan 1999 23:56:05 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Thu, 14 Jan 1999 23:56:05 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Alex Povolotsky cc: hackers@FreeBSD.ORG Subject: Re: Disklabel repair tool In-Reply-To: <199901150727.KAA18434@shuttle.svib.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Jan 1999, Alex Povolotsky wrote: > After crashing my disklabel recently, I've written a small stupid program that > helped me restore disklabel (all FSes were OK). > > Does FBSD community need this tool, completed to allow full auto recover of > disklabel? Most definitely! Anything to remedy the current lack of automated filesystem-recovery tools other than fsck would be very helpful. "Daemon Disk Doctor"? :) -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD 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 Jan 15 00:11:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08879 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 00:11:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08874 for ; Fri, 15 Jan 1999 00:11:29 -0800 (PST) (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 AAA24154; Fri, 15 Jan 1999 00:10:11 -0800 (PST) (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 AAA04374; Fri, 15 Jan 1999 00:10:09 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA28286; Fri, 15 Jan 1999 00:10:08 -0800 (PST) From: Don Lewis Message-Id: <199901150810.AAA28286@salsa.gv.tsc.tdk.com> Date: Fri, 15 Jan 1999 00:10:08 -0800 In-Reply-To: Jim Bryant "Re: Forward all spam to UCE@FTC.GOV" (Jan 15, 12:07am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: jbryant@unix.tfs.net, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Subject: Re: Forward all spam to UCE@FTC.GOV Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 15, 12:07am, Jim Bryant wrote: } Subject: Re: Forward all spam to UCE@FTC.GOV } } it's what they asked for. really. their intent is clear. gathering } evidence for use to obtain effective laws. Actually the FTC is more interested in fraud and deceptive practices. See and . They've announced a few crackdowns on fraud on the Internet and actually gone after a few of the more notorious scamming spammers. } i realize they probably don't have the staffing to handle each one, } and i'm sure they realize that too, the intent is clear. They don't even have the staff to enforce the existing laws ... This is really offtopic for -hackers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 01:09:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14045 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 01:09:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ska.bsn (d230.syd2.zeta.org.au [203.26.9.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14019; Fri, 15 Jan 1999 01:09:40 -0800 (PST) (envelope-from atrn@zeta.org.au) Received: (from andy@localhost) by ska.bsn (8.8.8/8.8.8) id TAA06812; Fri, 15 Jan 1999 19:19:09 +1100 (EST) (envelope-from atrn) Message-Id: <199901150819.TAA06812@ska.bsn> Date: Fri, 15 Jan 1999 19:19:09 +1100 (EST) From: Andy Newman Reply-To: atrn@zeta.org.au Subject: Re: What are the advantages of ELF kernels? To: freebsd-hackers@FreeBSD.ORG cc: freebsd-chat@FreeBSD.ORG In-Reply-To: <19990114142444.A7476@netmonger.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's definately an eerie connection somewhere. (Note attempt to move this to chat) I'm another who had an Amiga. Don't know about the rest of you but in 1986 (or whenever it was) I couldn't afford a Sun workstation at home and the Amiga was about the closest thing to a Unix box I could afford. Oh, and it could do graphics & sound better than anything else. I think it's ironic that ten or more years ago we'd be using Unix at work and at home people had lots of clunky machines running CP/M or MS-DOS or OS/9 or TRS/DOS or whatever. The Amiga and some other systems were almost okay. Now it's reversed for many people, they have (full source) Unix systems at home and have to use these clunky PCs at work. (I'm lucky enough to work on Unix systems 99% of the time). -- AN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 02:12:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20048 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 02:12:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p3.tfs.net [139.146.210.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20031; Fri, 15 Jan 1999 02:12:24 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id EAA08250; Fri, 15 Jan 1999 04:11:03 -0600 (CST) From: Jim Bryant Message-Id: <199901151011.EAA08250@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <199901150810.AAA28286@salsa.gv.tsc.tdk.com> from Don Lewis at "Jan 15, 99 00:10:08 am" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Fri, 15 Jan 1999 04:10:58 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: > On Jan 15, 12:07am, Jim Bryant wrote: > } Subject: Re: Forward all spam to UCE@FTC.GOV > } > } it's what they asked for. really. their intent is clear. gathering > } evidence for use to obtain effective laws. > > Actually the FTC is more interested in fraud and deceptive practices. > See and > . They've > announced a few crackdowns on fraud on the Internet and actually gone > after a few of the more notorious scamming spammers. their intent is to get new laws made. laws that mandate enforcement spending. also, have you ever seen a non-scam spam? i haven't. so what if they get the 0.01% of the spam that isn't a fraud scam. the 99.99% that is will reach the proper agency. dealing with onesies and twosies won't get anything to change. brutal enforcement of new and effective laws will. first, there must be incentive for effective laws and enforcement budgets. > } i realize they probably don't have the staffing to handle each one, > } and i'm sure they realize that too, the intent is clear. > > They don't even have the staff to enforce the existing laws ... gee, i wonder why? could it be all of the bribes from the direct marketing association that helped re-elect congress? when are people going to start holding their congressmen responsible for their actions? a lot of talk about integrity going on right now, unfortunately, we have the most corrupt congressional majority of the 20th century that just got re-elected. let's hope people have now waken up, as THE RECALL VOTES ARE A DONE DEAL. once the current anti-enforcement majority is out, we can have effective laws with bite. we can also organize and ratify international treaties dealing with the REAL problem issues. if spammers want to break the current feeble spam law, then they should be held to answer for it. unsolicited commercial email should have been made a felony, just like junk faxing is. it's only a matter of time before it is, because of the fact that the ftc has better things to do than deal with spam scams constantly. if effectively applied the current spam law will cost more money in taxes for enforcement than making it a felony would have ever cost with an effective opt-in law. unfortunately this integrity-challanged majority in congress refuses to fund ALL kinds of enforcement activities properly. thus a law without bite is worse than no law at all, and thus the problem blooms into the ROTTING CESSPOOL it currently is in MANY areas of life. they want fraudlant spam sent to them... by my experience and all those around me, 99.99% of all spam IS fraudlant. since internet regulation is only a matter of time, it's best that they understand the problem at the extent that it exists, so that intelligent regulation can be done. the sheer volume of what they are asking for will overwhelm them. it will only serve one purpose, to create new EFFECTIVE regulations that can deal with the problem, both domestically and internationally. what criteria would you use to determine what spam is good, when 99.99% of it is fraudluant? as a selectable option in sendmail.cf, fraud-friendly isps can easily leave the option deselected. but i'm sure the majority of decent people out there will agree with me and enable the option. if the problem gets much worse, joe blow down the street may be willing to boycott an isp that doesn't fully block and report fraudulant spam scams. boycott is such a nasty thing to do, but boycotts are effective in getting companies and governments to listen to the will of the people. since freebsd is used by many isps, we should offer the isp owners the option to block and forward such messages to the proper authorities. they will find it easier to do than deal with boycotts. someone has to be held responsible for the invasion of privacy that spam is. if i started an isp today and used the theme that we block spam and report each occurrance to the feds as our sole advertising point, then i guarantee that i will take over the majority of the internet market in kansas city in very short order. i'd be willing to bet a million dollars on that one, any interested investors, please contact me via email. i'm only suggesting a selectable option to automate delivery of what the ftc is asking for here in the usa. they didn't ask for filtration and selective submissions, they asked for unsolicited commercial email. period .-.-.- nowhere in the paragraph did it mention the word fraudulant, because these days, the word fraudulant is implied when talking about spam. the spammers have only themselves to blame. the people have both congress and the isps to blame. if you are not supporting people that want the problem solved once and for all, then you are part of the problem. unsolicited junk faxes are now pretty much a thing of the past, except in isolated incidents that are easily dealt with at the felony level. unsolicited commercial email can be too. people are serious. the ftc has provided the means, and they did not ask people to be selective except for the word "unsolicited". a selectable sendmail.cf option shipped in the distribution is acceptable to suit my proposal. isps that lack moral character can leave it deselected as they wish. to disagree with this is to admit that self-policing the internet [or anything else for that matter] is an utterly sophistic concept that needs to be relegated to the status of fairie tale. which, by the way is a circular concept anyhow, since to agree with my reasoning is to admit the same. at least i have enough moral character to admit it. sorry to bring politics into the issue, but due to the fact of the bribes from the direct marketing association to a certain party enjoying majority status on the hill, we have the law that has not only perpetuated the problem, but indeed has made it worse. thus to not bring politics into the discussion would be VERY NAIEVE. i think that the ftc can overlook the fact that one out of every 10,000 spams forwarded to them is not fraudulant. keep in mind that even if that 1 in 10,000 is not fraudulant, it was still unsolicited, and thus met the definition of what they are asking for. > This is really offtopic for -hackers. not really. given the percentages, there are probably more than a few -hackers subscribers that this is all about, at least they are not in the majority even though they may have helped buy a fraud-friendly majority on the hill. the only way to deal with criminals and hypocrites is to treat them as such. it's the only thing they understand. note the new Cc: to -chat. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 02:51:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23200 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 02:51:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23192 for ; Fri, 15 Jan 1999 02:51:43 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA27916; Fri, 15 Jan 1999 05:45:43 -0500 (EST) From: Peter Dufault Message-Id: <199901151045.FAA27916@hda.hda.com> Subject: Re: Path to SMP In-Reply-To: <199901150456.UAA29086@apollo.backplane.com> from Matthew Dillon at "Jan 14, 99 08:56:53 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 15 Jan 1999 05:45:42 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is anyone currently working on the next big step in the SMP > puzzle? That is, implementing kernel threads with preemptive > scheduling? > > The idea being that one then has the ability to run > preemptable kernel threads in parallel on SMP-capable > boxes because the code must assume preemption in the > same manner on both uni and multi cpu systems. > > Once implemented, we would begin to migrate functionality > from non-preemptive threads to preemptive threads from > the outside-in, and parallel SMP operation in supervisor > mode migrates along with it. No, but I'm working on something easier - per-"cpu resource" scheduling classes to dedicate cycles to a class of processes, along with detection and notification when rules are violated. I don't have an SMP system though. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 03:00:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24386 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 03:00:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24380; Fri, 15 Jan 1999 03:00:03 -0800 (PST) (envelope-from marko@uk.radan.com) Received: from [158.152.75.22] (helo=uk.radan.com) by post.mail.demon.net with smtp (Exim 2.10 #2) id 1016xm-0006Vy-00; Fri, 15 Jan 1999 10:58:50 +0000 Organisation: Radan Computational Ltd., Bath, UK. Phone: +44-1225-320320 Fax: +44-1225-320311 Received: from beavis.uk.radan.com (beavis [193.114.228.122]) by uk.radan.com (8.6.10/8.6.10) with SMTP id KAA02796; Fri, 15 Jan 1999 10:58:43 GMT Received: from uk.radan.com (gppsun4) by beavis.uk.radan.com (4.1/SMI-4.1) id AA04648; Fri, 15 Jan 99 10:58:41 GMT Message-Id: <369F1F52.650C9E6E@uk.radan.com> Date: Fri, 15 Jan 1999 10:58:27 +0000 From: Mark Ovens Organization: Radan Computational Ltd X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 4.1.3_U1 sun4m) X-Accept-Language: en-GB Mime-Version: 1.0 To: jbryant@unix.tfs.net Cc: freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV References: <199901151011.EAA08250@unix.tfs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > [ snip ] > unsolicited commercial email should have been made a felony, just like > junk faxing is. it's only a matter of time before it is, because of > the fact that the ftc has better things to do than deal with spam > scams constantly. if effectively applied the current spam law will > cost more money in taxes for enforcement than making it a felony would > have ever cost with an effective opt-in law. > Your post made very intersting reading Jim, but, for the benefit of a non-US citizen, could you explain the definition of "felony" in the US legal system to put the above paragraph into context. I was under the impression that felony was 'serious' crimes, murder, rape, burglary etc, etc. which makes it seem a bit extreme to make junk faxing/e-mailing a felony. TIA -- Trust the computer industry to shorten Year 2000 to Y2K. It was this thinking that caused the problem in the first place. FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://www.users.globalnet.co.uk/~markov _______________________________________________________________ Mark Ovens, CNC Apps Engineer, Radan Computational Ltd. Bath UK CAD/CAM solutions for Sheetmetal Working Industry mailto:marko@uk.radan.com http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 05:19:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12896 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 05:19:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay2.aha.ru (relay2.aha.ru [195.2.64.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12891 for ; Fri, 15 Jan 1999 05:19:02 -0800 (PST) (envelope-from abb@zenon.net) Received: from mp.aha.ru (mp [195.2.69.103]) by relay2.aha.ru (8.9.2/8.9.2/aha-r/0.04B) with ESMTP id QAA20395 for ; Fri, 15 Jan 1999 16:17:04 +0300 (MSK) Received: (from uucp@localhost) by mp.aha.ru (8.8.8/8.8.5) id QAA17977 for ; Fri, 15 Jan 1999 16:17:04 +0300 (MSK) Received: from p87-n69.zenon.net(195.2.69.87) by koi.zenon.net via smap (V1.3) id sma017952; Fri Jan 15 16:16:45 1999 Message-ID: <369F3FBD.ED99E422@zenon.net> Date: Fri, 15 Jan 1999 16:16:45 +0300 From: Alexander Bezroutchko X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: problem with permission at mount point again. Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a problem with permission at mount point. 2.2.7-STABLE behaves as described in thread titled 'permission confusion at mount point' (freebsd-hackers, July 1998) and the CAVEATS section of mount(8), it's bad for me (I have to shutdown running server), but understandable: -- mount(8) ----------------------- ... CAVEATS After a successful mount, the permissions on the original mount point de- termine if .. is accessible from the mounted file system. The minimum ^^^^^^^^^^^ permissions for the mount point for traversal across the mount point in ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ both directions to be possible for all users is 0111 (execute for all). ^^^^^^^ ... ----------------------------------- But 3.0-RELEASE (i386), doesn't satisfy this description. As root: 1 root@abb:/var# /bin/pwd 2 /var 3 root@abb:/var# ls -ld /var/ch 4 drwx------ 2 root wheel 512 15 Jan 10:53 /var/ch 5 root@abb:/var# mount /dev/wd2a /var/ch 6 root@abb:/var# ls -ld /var/ch 7 drwxr-xr-x 2 root wheel 512 15 Jan 14:03 /var/ch 8 root@abb:/var# As ordinary user: 10 abb@abb:~> cd /var/ch 11 abb@abb:/var/ch> ls -ld .. 12 ls: ..: Permission denied 13 abb@abb:/var/ch> /bin/pwd 14 /var/ch 15 abb@abb:/var/ch> cd .. 16 abb@abb:/var> /bin/pwd 17 /var 18 abb@abb:/var> As far as I understand, in compliance with manpage commands 13 & 15 must return 'Permission denied'. Behaviour described in the thread was claimed as correct and only possible. So why pwd and cd succeeds but ls fails ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 05:59:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17351 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 05:59:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fan.net.au (fan.net.au [203.20.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17344 for ; Fri, 15 Jan 1999 05:59:44 -0800 (PST) (envelope-from q@fan.net.au) Received: from dialup-nas1-31.gc.fan.net.au (dialup-nas1-31.gc.fan.net.au [203.23.134.32]) by fan.net.au (8.9.1/8.9.1) with ESMTP id XAA24098 for ; Fri, 15 Jan 1999 23:58:28 +1000 (EST) Date: Fri, 15 Jan 1999 23:58:26 +1000 (EST) From: Q To: freebsd-hackers@FreeBSD.ORG Subject: Console driver mouse support chewing cycles/interrupts 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 written a driver under FreeBSD 3.0 for an Infra-Red receiver I have, the receiver is serial port based, and the driver itself is interrupt driven. When receiving a signal, interrupts are generated quite rapidly (20-30 ints @ 600-2400usec apart). When receiving a repeat code (from my test remote) the interupts are at approx 9Hz. Timing is calculated in the kernel driver the moment the interrupt handler is called. All these signals are decoded by a daemon process and passed on to socket connected clients. All this works perfectly under X and while the remote is in signal range I haven't been able to fault the decoder. I have written (and been using) a remote controlled mouse emulator that uses the syscons mouse interface to control my X session. All fine so far. The problem: When I jump out of X to the console I have all sorts of problems (when the mouse cursor is visible). I am using the default spiffy little mouse pointer, not a square block. When controlling the mouse on the console (remotely or with a real mouse), moving the mouse with no output going to the console will cause some delayed interrupts with almost every movement of the mouse, more if additional output is displayed on the console in the process. Is this the price you pay for having mouse support on the console or is there something missing from the mouse support portion of the console driver that should handle things better? Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan - q@fan.net.au __ __/ / / __/ / / Systems Administrator / __ / _/ / / Fast Access Network __/ __/ __/ ____/ / - / Gold Coast, QLD, Australia _______ / Ph: +61 7 5574 1050 \_\ SAGE-AU Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 06:10:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18942 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 06:10:58 -0800 (PST) (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 GAA18933 for ; Fri, 15 Jan 1999 06:10:57 -0800 (PST) (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 JAA21986; Fri, 15 Jan 1999 09:09:27 -0500 Date: Fri, 15 Jan 1999 09:09:27 -0500 (EST) From: Jamie Bowden To: "Daniel C. Sobral" cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <369E861E.8DE99189@newsguy.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, 15 Jan 1999, Daniel C. Sobral wrote: > Jim Bryant wrote: > > > > i understand your point of view, even though I disagree with it to an > > extent. > > You sure? Please explain exactly how your arguments below fit the > "message in japanese, written by japanese, sent from a japanese site > to a japanese on another japanese site" pov. I'm still curious why anyone wants the US govt. Regulating Content (TM) on the internet. Jim seems to think the govt. will work on his terms, and not their own. If you can't make the leap from regulating spam (limited content) to REGULATING CONTENT, you've never dealt with the US govt. 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 Jan 15 06:17:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19611 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 06:17:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA19606 for ; Fri, 15 Jan 1999 06:17:21 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 15555 invoked by uid 1001); 15 Jan 1999 14:18:28 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 15 Jan 1999 09:18:28 -0500 (EST) X-Face: *0^4Iw) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jan-99 Jamie Bowden wrote: > On Fri, 15 Jan 1999, Daniel C. Sobral wrote: > >> Jim Bryant wrote: >> > >> > i understand your point of view, even though I disagree with it to an >> > extent. >> >> You sure? Please explain exactly how your arguments below fit the >> "message in japanese, written by japanese, sent from a japanese site >> to a japanese on another japanese site" pov. > > I'm still curious why anyone wants the US govt. Regulating Content (TM) on > the internet. Jim seems to think the govt. will work on his terms, and > not their own. If you can't make the leap from regulating spam (limited > content) to REGULATING CONTENT, you've never dealt with the US govt. I have the same concern. Last time they did anything about it they said that if you put the instructions at the beginning of the spam on how to get off that spam list it's ok to spam. We sure don't need to give them any more ideas. Remember the CDA? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 06:37:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22247 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 06:37:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22218; Fri, 15 Jan 1999 06:37:21 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id JAA06236; Fri, 15 Jan 1999 09:35:51 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Fri, 15 Jan 1999 09:35:50 -0500 (EST) From: Matt Behrens To: Brian Somers cc: "Jordan K. Hubbard" , Eivind Eklund , "Joseph T. Lee" , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Gratuitous name changes (was: libalias and ident) In-Reply-To: <199901140859.IAA44254@keep.lan.Awfulhak.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, 14 Jan 1999, Brian Somers wrote: : But this isn't necessarily a good idea as it may attract a pile of : ``why the hell did you break my configuration for no good reason'' : messages. : : Anyone with any strong opinions on this ? : : Of course it's not guaranteed that libalias will change to libnat, : there's another thread starting on -hackers about that :-) It's also : possible to change the ppp flag, even if libalias isn't renamed. I winced when I heard that the flag was named -alias in the first place, since aliasing really is a different animal. (At least, that's what they taught *me* in school.) :) I say, if the change can be made before the -STABLE branch, do it. People should expect to rewrite a lot of config files anyway. However, if it's not too much trouble, -alias could be kept temporarily with a deprecation warning that would display on invocation. (Most people, while loath to read announcements and manpages, would probably think about investigating if their ppp started beeping and printing annoying error messages on bootup.) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 07:59:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03201 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 07:59:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from k6n1.znh.org ([207.109.235.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02938; Fri, 15 Jan 1999 07:59:02 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id PAA17283; Fri, 15 Jan 1999 15:56:53 GMT (envelope-from zach) Message-ID: <19990115095653.A16631@znh.org> Date: Fri, 15 Jan 1999 09:56:53 -0600 From: Zach Heilig To: Mark Ovens , jbryant@unix.tfs.net Cc: freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV References: <199901151011.EAA08250@unix.tfs.net> <369F1F52.650C9E6E@uk.radan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <369F1F52.650C9E6E@uk.radan.com>; from Mark Ovens on Fri, Jan 15, 1999 at 10:58:27AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I am not a lawyer, nor do I play one on TV ] On Fri, Jan 15, 1999 at 10:58:27AM +0000, Mark Ovens wrote: > Your post made very intersting reading Jim, but, for the benefit of a > non-US citizen, could you explain the definition of "felony" in the US > legal system to put the above paragraph into context. > I was under the impression that felony was 'serious' crimes, murder, > rape, burglary etc, etc. which makes it seem a bit extreme to make > junk faxing/e-mailing a felony. Literally (from a 1965 edition of Webster's dictionary [*]): (a) a grave crime formerly differing from a misdemeanor under English common law by involving forfeiture in addition to any other punishment (b) a grave crime expressly declared to be a felony by the common law (c) a crime declared a felony by statute because of the punishment imposed. I'm pretty sure anytime there are damages [perhaps fines as well?] in excess of a certain amount (I think $1000), it is also considered felony. [*] ok, a bit "out of date", but it's the only one quickly available :-) -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 08:00:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03377 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 08:00:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03355 for ; Fri, 15 Jan 1999 08:00:22 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:alxSKZIkZWbuee4s/+0xvFVWgOOBz2pn@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id AAA20509; Sat, 16 Jan 1999 00:58:57 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id BAA26821; Sat, 16 Jan 1999 01:01:27 +0900 (JST) Message-Id: <199901151601.BAA26821@zodiac.mech.utsunomiya-u.ac.jp> To: Q cc: freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Console driver mouse support chewing cycles/interrupts In-reply-to: Your message of "Fri, 15 Jan 1999 23:58:26 +1000." References: Date: Sat, 16 Jan 1999 01:01:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have written a driver under FreeBSD 3.0 for an Infra-Red receiver I >have, the receiver is serial port based, and the driver itself is >interrupt driven. [...] >The problem: > >When I jump out of X to the console I have all sorts of problems (when the >mouse cursor is visible). I am using the default spiffy little mouse >pointer, not a square block. When controlling the mouse on the console >(remotely or with a real mouse), moving the mouse with no output going to >the console will cause some delayed interrupts with almost every movement >of the mouse, more if additional output is displayed on the console in the >process. > >Is this the price you pay for having mouse support on the console or I am afraid yes ;-< The current version of syscons draws the mouse pointer by manipulating font data. This takes time and may cause interrupt delay. Kazu >is >there something missing from the mouse support portion of the console >driver that should handle things better? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 08:09:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04365 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 08:09:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04357 for ; Fri, 15 Jan 1999 08:09:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA09863; Fri, 15 Jan 1999 09:08:08 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <369F67E8.E778EABA@softweyr.com> Date: Fri, 15 Jan 1999 09:08:08 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Bezroutchko CC: hackers@FreeBSD.ORG Subject: Re: problem with permission at mount point again. References: <369F3FBD.ED99E422@zenon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Bezroutchko wrote: > > I have a problem with permission at mount point. > > 2.2.7-STABLE behaves as described in thread titled 'permission confusion > at mount point' (freebsd-hackers, July 1998) and the CAVEATS section of > mount(8), it's bad for me (I have to shutdown running server), but > understandable: > > [...] > > As far as I understand, in compliance with manpage commands 13 & 15 must > return 'Permission denied'. Behaviour described in the thread was > claimed > as correct and only possible. So why pwd and cd succeeds but ls fails ? Because neither cd nor pwd attempt to read/list the directory contents, they just set and get the per-process working directory. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 12:34:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07522 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 12:34:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07430 for ; Fri, 15 Jan 1999 12:33:43 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA13986 for freebsd-hackers@FreeBSD.ORG; Fri, 15 Jan 1999 21:33:33 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8D7971573; Fri, 15 Jan 1999 21:03:03 +0100 (CET) Date: Fri, 15 Jan 1999 21:03:03 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Synaptics TouchPad driver Message-ID: <19990115210303.A13893@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <199901071731.CAA24735@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901071731.CAA24735@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Fri, Jan 08, 1999 at 02:31:33AM +0900 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kazutaka YOKOTA: > No major update is planned at the moment. But there may be > a minor adjustment when keyboard controller related code is > updated. Speaking of TouchPad, is the one one the VAIO laptops from Sony considered as a PS/2 mouse or as something else ? I'd hate to have to put the port replicator just for a mouse... Ollivier, still thinking about buying one of these nice laptops... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 14:31:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24763 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 14:31:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24757 for ; Fri, 15 Jan 1999 14:31:28 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA19155 for freebsd-hackers@FreeBSD.ORG; Fri, 15 Jan 1999 23:31:19 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1EEE41573; Fri, 15 Jan 1999 23:22:11 +0100 (CET) Date: Fri, 15 Jan 1999 23:22:10 +0100 From: Ollivier Robert To: "FreeBSD Hackers' list" Subject: Problem with ntp4 & DCF77 clock Message-ID: <19990115232210.A40217@keltia.freenix.fr> Mail-Followup-To: FreeBSD Hackers' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the following message after a few hours running ntp4 (4.0.90f) with my DCF77 receiver... Is there anything I could do to prevent that ? Jan 15 21:54:31 tara ntpd[25909]: time error 3600 over 1000 seconds; set clock manually) After that message, ntpd is gone. Any idea ? The machine is a 2xPPro/200 with 64 MB RAM, running FreeBSD/SMP from 25th of December. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #8: Sat Dec 26 01:22:22 CET 1998 roberto@tara.freenix.org:/src/src/sys/compile/TARA_SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 67108864 (65536K bytes) machdep.i8254_freq: 1193182 machdep.tsc_freq: 198656034 When it runs, it displays that: ntpq> cv status=0003 clk_okay, last_clk_fault device="RAW DCF77 CODE (Conrad DCF77 receiver module)", timecode="------------------M-S--4-1--p-----2P1-4-1-1-41----1--81--8p", poll=12705, noreply=1534, badformat=284, baddata=0, fudgetime1=254.000, fudgetime2=0.000, stratum=0, refid=DCFa, flags=0, refclock_time="ba4a1201.00000000 Fri, Jan 15 1999 20:14:09.000 (+0100)", refclock_status="TIME CODE; (LEAP INDICATION; ANTENNA)", refclock_format="RAW DCF77 Timecode", refclock_states="*NOMINAL: 10:01:31 (88.36%); NO RESPONSE: 00:48:41 (7.15%); FAULT: 00:02:41 (0.39%); ILLEGAL DATE: 00:27:52 (4.09%); running time: 11:20:45" ntpq> rv status=02f7 leap_none, sync_lf_clock, 15 events, event_clock_excptn, processor="i386", system="FreeBSD3.0-CURRENT", leap=00, stratum=1, precision=-20, rootdelay=0.000, rootdispersion=48.688, peer=48388, refid=DCFa, reftime=ba4a3bfd.3ee9ee45 Fri, Jan 15 1999 23:13:17.245, poll=6, clock=ba4a3c22.22605ee5 Fri, Jan 15 1999 23:13:54.134, state=4, phase=-0.714, frequency=-0.144, jitter=48.116, stability=0.031 244 [21:41] root@tara:ntp-4.0.90f/ntpdc# ntpq -c lop remote local st t when poll reach delay offset disp =========================================================================== *GENERIC(0) 0.0.0.0 0 - 43 64 377 0.00 12.306 0.02 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 14:48:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26784 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 14:48:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26760; Fri, 15 Jan 1999 14:48:30 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.2/8.9.2/best.sh) id OAA04207; Fri, 15 Jan 1999 14:48:18 -0800 (PST) Message-ID: <19990115144818.A4150@la.best.com> Date: Fri, 15 Jan 1999 14:48:18 -0800 From: "Joseph T. Lee" To: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV References: <199901140136.TAA35796@unix.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901140136.TAA35796@unix.tfs.net>; from Jim Bryant on Wed, Jan 13, 1999 at 07:36:35PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 07:36:35PM -0600, Jim Bryant wrote: > This announcement is located on the Federal Trade Commission's > complaint form page http://www.ftc.gov/ftc/complaint.htm I've been using the address for over half a year.. Nada for response nor spam reduction. So I just tightened up my procmail filters instead.. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 15:10:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29311 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 15:10:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29306 for ; Fri, 15 Jan 1999 15:10:57 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA27171; Fri, 15 Jan 1999 16:10:45 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd027019; Fri Jan 15 16:10:42 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA17271; Fri, 15 Jan 1999 16:10:27 -0700 (MST) From: Terry Lambert Message-Id: <199901152310.QAA17271@usr04.primenet.com> Subject: Re: Problems with 3.0 To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 15 Jan 1999 23:10:25 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, rch@iserve.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199901140307.TAA16614@apollo.backplane.com> from "Matthew Dillon" at Jan 13, 99 07:07:17 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 > :Actually, no. All it requires is the VM system reclaiming a clean > :page from an in core object without telling the object about it. > : > :This can't happen for most things, but mmap seems immune from > :correct functioning in a lot of ways, and this happens to be one > :of them. The pages that get zapped are in the libc code section > :for the mmap'ed libc.so image. This probably has something to do > :with the fact that the same libc is mapped into multiple processes > :(e.g., here's some place where having aliases in your VM sucks out). [ ... ] > If the author updated either libc or httpd while the web > server was running, it could certainly have caused the > segfault later on. I see this consistently in 2.2.7 and 2.2.6 systems, after the Dyson patches, but before the fixes to mmap and other areas that have happened subsequently. I have also seen this, in a few limited cases, in a 2.2.8 system, and in a 3.0-current system that is supposedly fixed. Most frequently, it's related to the use of a Cyrix 486 core, or a Cyrix Media GX processor. The 486 core doesn't have an L2 cache on the board, so "bad 486 cache coherency", runored to cause the problem, must remain an unconfirmed rumor. In general, I can see this in sendmail *without* needing to have inetd puke first to cause the problem (e.g., this is *not* a swap reclaim, it is an LRU reclaim). The end result is a page mapping for the libc hung of the vmobject hung off the libc vnode that is pointed to by another object at the same time, apparently as a result of a reclaim of the clean page from the libc vnode's object, but without correctly removing it from the object's list of page references. A subsequent use of the page as a data page results in the correct data for the second reference being in the page, but of course the libc's vnode's object's page appears to be "corrupted". Killing and restarting the daemon, which reinstances the page table for the process, fixes the problem (obviously). I've been considering modifying the procfs so that one can dump region mappings and then represent them graphically so as to quickly locate the problem; there has been some interest in this by the KAFFE people working on the new garbage collector routines, since there are situations where there are memory leaks and/or mappings that are unreferenced, but not recovered, and such a tool would show that pretty dramatically. A similar, but, I believe, unrelated issue occurs in the Vixie cron code. The Vixie cron code modifies the returned pwent entries; this is something that it should not do, since it is based on the incorrect assumption that the content fields are, in fact, static buffers. Given that the returned data is, in fact, in an mmap'ed Berkeley DBM record, what is happening is a copy-on-write fault for the modified data. In an error that appears to be related to the use of a read-only file being mapped copy-on-write instead of private (for the password database page affected), the result is that another file ends up referencing the page that nominally belongs to the password database. In other words, a "read-only" page that has been written is reclaimed, leaving it dirty. The resulting failure is that the modified page from the password database is written back to another file on the system. In general, the file that gets spammed is the crontab; I suspect that this is the result of the file being very active (the system in question runs newsyslog from cron with *absurd* frequency). However, there have been reports of the /etc/aliases.db file (also an mmap'ed Berkeley DB file!) and the /etc/group file. Therefore the problem is not limited to the crontab, and, in effect, all files in the system are subject to damage by "the page sniper". > :Another one recently discovered is that it *appears* that you can > :map (read only) the same file twice letting the system decide where > :to put it (pass NULL as binding location), and the second time the > :system will return the same address as the first time, instead of > :doing the right thing and setting up the mapping at a different > :location. > > I've not seen this either. Do you have an example or PR? I > wrote a quick little test program to map the same file several > times and it seems to map it at different locations as it > should. It was hardly an exhaustive test, though. I'll try to come up with an example. The problem is that the program that causes this problem is a derivative work of a commercial product, and so I will have to do some work to duplicate it in a smaller piece of code. The apparent problem is twofold: 1) Calling munmap(2) with a formerly good mapping address should result in a -1 return and an "EINVAL", not a page fault. I think this is (occasionally) broken, from a truss of the affected program. We recognized the problem existing first by seeing the resulting coredumps, apparently from the munmap(2) call. 2) The mmap(2) is *definitely* returning the same address for the second mapping. This should be pretty trivial to reproduce, but it could be dependent on the other parameters to mmap(2). One would think, though, that it would have to be pretty glaringly obvious, but I believe that there are few programs that actually do this type of weird crap, so it may just be a corner case that was never tested. If worse comes to worse, I'll drop the sample program problem on the lap of the person whose code it was affecting... PS: You missed the BAFUG meeting last night! 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 Fri Jan 15 15:23:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00754 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 15:23:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00748 for ; Fri, 15 Jan 1999 15:23:20 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA04759; Fri, 15 Jan 1999 16:23:13 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd004489; Fri Jan 15 16:23:02 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA19979; Fri, 15 Jan 1999 16:22:51 -0700 (MST) From: Terry Lambert Message-Id: <199901152322.QAA19979@usr04.primenet.com> Subject: Re: Forward all spam to UCE@FTC.GOV To: jbryant@unix.tfs.net Date: Fri, 15 Jan 1999 23:22:51 +0000 (GMT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199901141505.JAA65083@unix.tfs.net> from "Jim Bryant" at Jan 14, 99 09:05:39 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 > regulation, on a worldwide scale, is only a matter of when, not if. > that time is probably going to come a lot faster than a lot of people > think. IMHO, it should have been done five years ago when the abusers > started showing up in force. Regulation can not be effective when there are no insurmountable barriers to the behaviour. Prohibiting human behaviour in ways not prohibited by the laws of physics has historically had a poor succes rate. The soloution to "the SPAM problem" is "callerid" certificates, which can be obtained by proxy for older systems, if necessary, and validated via DNS reverse lookup. The certificates would be signed by an authority which was contractually obligated to not sign certificates for SPAM'mers, and time limited such that they would have to be renewed on a periodic basis. When someone sends SPAM, their machines are (effectively) diked out of the Internet. Problem solved. No law, international or otherwise, will be able to control the contents of packets. Comparing packet content in real time as it enters or leaves your country is an impossible task, and does nothing for packets that don't cross one of your "checkpoints". 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 Fri Jan 15 15:36:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02364 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 15:36:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02357 for ; Fri, 15 Jan 1999 15:36:52 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA22925; Fri, 15 Jan 1999 16:36:40 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd022665; Fri Jan 15 16:36:31 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA20785; Fri, 15 Jan 1999 16:36:10 -0700 (MST) From: Terry Lambert Message-Id: <199901152336.QAA20785@usr04.primenet.com> Subject: Re: TSS and context switch To: thorpej@nas.nasa.gov Date: Fri, 15 Jan 1999 23:36:10 +0000 (GMT) Cc: dillon@apollo.backplane.com, rvb@cs.cmu.edu, rminnich@Sarnoff.COM, bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199901150436.UAA08145@lestat.nas.nasa.gov> from "Jason Thorpe" at Jan 14, 99 08:36:27 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 distinctly remember there being several instructions on the VAX that > were like this (perhaps the polynomial evaluation instructions.. it's > been a while :-) ... you were better off open-coding them than using > the single instruction :-) Many VAX instructions, especially on lower end processors, like the uVAX II, or instructions which were somewhat deperecated, were emulated in software. For these instructions, if you didn't really need "the full effect", then the emulation tended to be slower. There's also the issue of whether the geometry of the problem was already suited to the instruction, or if there was work going in and out (which was most likely duplicated going in and out of the emulation, as well, transforming it back to be suitable for discrete instructions). One of the people I went to school with, Val Kartchner, did an "infinite" precision math library using VAX assembly. He could tell you very accurately which instructions were emulated on which VAXen. All I can rememebr is the CRC32 instruction on the uVAX... 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 Fri Jan 15 17:06:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12342 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 17:06:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12243 for ; Fri, 15 Jan 1999 17:05:03 -0800 (PST) (envelope-from dwhite@pond.net) Received: from localhost (dwhite@localhost) by guppy.pond.net (8.8.8/8.8.7) with SMTP id RAA17428 for ; Fri, 15 Jan 1999 17:00:17 -0800 (PST) Date: Fri, 15 Jan 1999 17:00:16 -0800 (PST) From: Doug White To: hackers@FreeBSD.ORG Subject: PPTP patches for NAT -- where? 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 Yesterday or earlier today someone posted patches to make natd work with PPTP. Unfortunately I dumped the message, but I'd be _very_ willing to test these out and perhaps sponsor their addition to the main src tree. We have a client that is screaming for them. Please contact me if you have these ... Doug White | Pacific Crest Networks Internet: dwhite@pond.net | http://www.pond.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 17:16:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13108 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 17:16:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13103 for ; Fri, 15 Jan 1999 17:16:16 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id UAA58724; Fri, 15 Jan 1999 20:16:13 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199901160116.UAA58724@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: TSS and context switch References: <199901152336.QAA20785@usr04.primenet.com> In-reply-to: Your message of "Fri, 15 Jan 1999 23:36:10 GMT." <199901152336.QAA20785@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Jan 1999 20:16:13 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One of the people I went to school with, Val Kartchner, did an > "infinite" precision math library using VAX assembly. He could > tell you very accurately which instructions were emulated on which > VAXen. All I can rememebr is the CRC32 instruction on the uVAX... The other one I tripped over due to incorrect emulation on a MicroVAX-II was the matchc instruction. This was, of course, used in MH in some scary looking code to parse RFC-822 headers that was hacked by Van Jacobson. The module in question (still in NMH) is sbr/m_getfld.c. The long comment at the start of the file begins: /* This module has a long and checkered history. and then: (Written by Van Jacobson for the mh6 m_getfld, January, 1986): This routine was accounting for 60% of the cpu time used by most mh programs. I spent a bit of time tuning and it now accounts for <10% of the time used. Like any heavily tuned routine, it's a bit complex and you want to be sure you understand everything that it's doing before you start hacking on it. Let me try to emphasize that: every line in this atrocity depends on every other line, sometimes in subtle ways. You should understand it all, in detail, before trying to change any part. If you do change it, test the result thoroughly (I use a hand-constructed test file that exercises all the ways a header name, header body, header continuation, header-body separator, body line and body eom can align themselves with respect to a buffer boundary). "Minor" bugs in this routine result in garbaged or lost mail. If you hack on this and slow it down, I, my children and my children's children will curse you. and later: * packed maildrop - only take up to the (possible) * start of the next message. This "matchc" should * probably be a Boyer-Moore matcher for non-vaxen, * particularly since we have the alignment table * all built for the end-of-buffer test (next). * But our vax timings indicate that the "matchc" * instruction is 50% faster than a carefully coded * B.M. matcher for most strings. (So much for elegant * algorithms vs. brute force.) Since I (currently) * run MH on a vax, we use the matchc instruction. --vj Of course, this code had an "#ifdef vax" optimization using an asm() of a scanc instruction. So the attempt at optimizing was pessimized by trapping into the (broken) kernel emulator for the complex instruction. I suppose when you had 50 people sharing a 1 or 2 MIPS CPU, you resorted to this stuff. I know I was guilty of it on an old Univac 1108 with 262K of (36-bit words) memory that ran 40 or 60 people. This truly was a pain in the ass to find; typically, you expect the instructions to work. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 17:51:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17298 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 17:51:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from findmail.com (m4.findmail.com [209.185.96.139]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA17293 for ; Fri, 15 Jan 1999 17:51:01 -0800 (PST) (envelope-from dnelson@redwoodsoft.com) From: dnelson@redwoodsoft.com Message-Id: <199901160151.RAA17293@hub.freebsd.org> Received: (qmail 20153 invoked by uid 505); 16 Jan 1999 01:50:57 -0000 Content-Type: text/plain Subject: Re: PPTP patches for NAT -- where? In-Reply-To: To: hackers@FreeBSD.ORG Date: Sat, 16 Jan 1999 01:50:57 -0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have them, and I'll send them to you. > Yesterday or earlier today someone posted patches to make natd work with > PPTP. Unfortunately I dumped the message, but I'd be _very_ willing to > test these out and perhaps sponsor their addition to the main src tree. > We have a client that is screaming for them. > > Please contact me if you have these ... > > Doug White | Pacific Crest Networks > Internet: dwhite@pond.net | http://www.pond.net/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 17:53:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17781 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 17:53:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17765 for ; Fri, 15 Jan 1999 17:53:48 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA19428; Fri, 15 Jan 1999 18:53:47 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd026700; Fri Jan 15 16:55:43 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA21837; Fri, 15 Jan 1999 16:55:36 -0700 (MST) From: Terry Lambert Message-Id: <199901152355.QAA21837@usr04.primenet.com> Subject: Re: Path to SMP To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 15 Jan 1999 23:55:35 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199901150456.UAA29086@apollo.backplane.com> from "Matthew Dillon" at Jan 14, 99 08:56:53 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 > Is anyone currently working on the next big step in the SMP > puzzle? That is, implementing kernel threads with preemptive > scheduling? > > The idea being that one then has the ability to run > preemptable kernel threads in parallel on SMP-capable > boxes because the code must assume preemption in the > same manner on both uni and multi cpu systems. > > Once implemented, we would begin to migrate functionality > from non-preemptive threads to preemptive threads from > the outside-in, and parallel SMP operation in supervisor > mode migrates along with it. Jason Evans has started work on an async call based mechanism. The functional decomposition is into flags for each system call to tell the trap code whether the call will: (A) Never block (B) Sometimes block (C) Always block The kernel work moves the kernel stack into a call context structure, which includes a pointer to the VM for the process making the call. Effectively, this make all entries into the kernel seperately schedulable, and allows a process to enter the kernel. The use of the type-of-call flags is an optimization, allowing the use of a "fake" (static, user space) call context structure pointer for calls in category (A), or (B), in the case that they run to completion instead of blocking. The mechanism necessitates the addition of a multiplexed system call that accepts the commands ACG_WAIT (Async Call Gate Wait) and ACG_CANCEL. This is similar to the SVID III aiowait(RT), aiocancel(RT) mechanism, and is also similar to the "aio" mechanisms in both UnixWare and Solaris, semantically. It's also like the POSIX stuff, only with the ability to do all calls, not just some of them. The mechanism should provide an SMP scalable basis for cooperative user and kernel space thread scheduling which fully obeys POSIX semantics. This sidesteps or resolves many of the issues for decomposition, as pointed out in: Scheduling and Load Balancing in Parallel and Distributed Systems Behrooz A. Shirazi, Ali R Hurson, and Krisna M. Kavi IEEE Computer Society Press ISBN 0-8186-6587-4 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 Fri Jan 15 18:43:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21424 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 18:43:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zephyr.cybercom.net (zephyr.cybercom.net [209.21.146.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21418 for ; Fri, 15 Jan 1999 18:43:14 -0800 (PST) (envelope-from rhuff@cybercom.net) Received: from shell1.cybercom.net (shell1.cybercom.net [209.21.136.6]) by zephyr.cybercom.net (8.8.7/8.8.7) with ESMTP id VAA11884 for ; Fri, 15 Jan 1999 21:43:08 -0500 (EST) Received: (from rhuff@localhost) by shell1.cybercom.net (8.8.5/8.8.5) id VAA11318; Fri, 15 Jan 1999 21:43:08 -0500 (EST) Date: Fri, 15 Jan 1999 21:43:08 -0500 (EST) From: Robert Huff Message-Id: <199901160243.VAA11318@shell1.cybercom.net> To: hackers@FreeBSD.ORG Subject: Re: Forward all spam to UCE@FTC.GOV In-Reply-To: <87597569@toto.iv> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zach Heilig writes: > [ I am not a lawyer, nor do I play one on TV ] > > On Fri, Jan 15, 1999 at 10:58:27AM +0000, Mark Ovens wrote: > > > I was under the impression that felony was 'serious' crimes, > > murder, rape, burglary etc, etc. which makes it seem a bit > > extreme to make junk faxing/e-mailing a felony. > > Literally (from a 1965 edition of Webster's dictionary [*]): (a) a > grave crime formerly differing from a misdemeanor under English > common law by involving forfeiture in addition to any other > punishment (b) a grave crime expressly declared to be a felony by > the common law (c) a crime declared a felony by statute because of > the punishment imposed. Bottom line: "felony" is whatever the legislature says it is. Rule of thumb: it's a felony if it involves possible incarceration of over 1 year, or a fine of more than $1000. Robert Huff (Not a lawyer either) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 20:49:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01982 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 20:49:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01974 for ; Fri, 15 Jan 1999 20:49:34 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id FAA08115; Sat, 16 Jan 1999 05:49:27 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA11660; Sat, 16 Jan 1999 05:49:26 +0100 (MET) Date: Sat, 16 Jan 1999 05:49:25 +0100 From: Eivind Eklund To: Alex Povolotsky Cc: hackers@FreeBSD.ORG Subject: Re: Disklabel repair tool Message-ID: <19990116054925.A6405@bitbox.follo.net> References: <199901150727.KAA18434@shuttle.svib.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901150727.KAA18434@shuttle.svib.ru>; from Alex Povolotsky on Fri, Jan 15, 1999 at 10:27:47AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 15, 1999 at 10:27:47AM +0300, Alex Povolotsky wrote: > Hello! > > After crashing my disklabel recently, I've written a small stupid program that > helped me restore disklabel (all FSes were OK). > > Does FBSD community need this tool, completed to allow full auto recover of > disklabel? YES! I need it yesterday - no, I mean, I need it last saturday. And I still need it today. Thank you! Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 21:12:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03969 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 21:12:37 -0800 (PST) (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 VAA03963; Fri, 15 Jan 1999 21:12:36 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA08645; Fri, 15 Jan 1999 21:12:35 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma008643; Fri, 15 Jan 99 21:12:08 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA07999; Fri, 15 Jan 1999 21:12:08 -0800 (PST) From: Archie Cobbs Message-Id: <199901160512.VAA07999@bubba.whistle.com> Subject: Automated debug sanity checkers To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Fri, 15 Jan 1999 21:12:07 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking about the DIAGNOSTICS replacement macros and had a random thought... Suppose you're sitting in front of a ddb (or better yet gdb) prompt because your kernel has just crashed due to who knows what reason. What do you do to debug this? You start looking at variables, memory, etc for anything funny going on. For example, several times we've spent hours going through a crash dump to find, for example, that a process was on two queues, or some mbuf was mangled, etc. The thought is that it would be really easy to help automate this process, by doing the following: 1. Define a new kernel option INCLUDE_SANITY_CHECKS (or whatever) 2. When this is defined, all the various FreeBSD kernel submodules (VM, networking, device drivers, etc) would include a function that exhaustively runs sanity checks -- ie, validations that all the assumptions in the code are true -- for that particular submodule. This means checking all queues, flags, whatever. 3. The function is required to only READ memory, not modify it. It can report any inconsistencies, though, obviously. 4. The function is linked into a linker set SANITY_SET(...) or whatever Then by simply calling this function from the debugger you can much more quickly narrow down on the problem (and hopefully fix it before you get tired and go to sleep :-) Moreover, since the function is running post-mortem, it can do very detailed checks that would otherwise take way too long. E.g., check every mbuf, every queue entry, check the filesystem, etc. Basically a "fsck" for the kernel memory. Is this something that people would be motivated enough to make as "official" FreeBSD kernel good housekeeping policy? -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 Jan 15 22:33:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11996 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 22:33:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11975; Fri, 15 Jan 1999 22:33:07 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id HAA08781; Sat, 16 Jan 1999 07:33:04 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id HAA11937; Sat, 16 Jan 1999 07:33:03 +0100 (MET) Date: Sat, 16 Jan 1999 07:33:03 +0100 From: Eivind Eklund To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Automated debug sanity checkers Message-ID: <19990116073302.B6405@bitbox.follo.net> References: <199901160512.VAA07999@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901160512.VAA07999@bubba.whistle.com>; from Archie Cobbs on Fri, Jan 15, 1999 at 09:12:07PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 15, 1999 at 09:12:07PM -0800, Archie Cobbs wrote: > I was thinking about the DIAGNOSTICS replacement macros and > had a random thought... > > Suppose you're sitting in front of a ddb (or better yet gdb) prompt > because your kernel has just crashed due to who knows what reason. > What do you do to debug this? You start looking at variables, > memory, etc for anything funny going on. > > For example, several times we've spent hours going through a crash > dump to find, for example, that a process was on two queues, or > some mbuf was mangled, etc. > > The thought is that it would be really easy to help automate this > process, by doing the following: > > 1. Define a new kernel option INCLUDE_SANITY_CHECKS (or whatever) INVARIANT_SUPPORT. Hey, I just happen to remember that somebody added this a couple of days ago - hmm, could it have been me? :-) > 2. When this is defined, all the various FreeBSD kernel > submodules (VM, networking, device drivers, etc) would > include a function that exhaustively runs sanity checks -- > ie, validations that all the assumptions in the code are true -- > for that particular submodule. This means checking all queues, > flags, whatever. Ie, invariants. > 4. The function is linked into a linker set SANITY_SET(...) or whatever I've not thought of that - that may be a good idea. > Then by simply calling this function from the debugger you can > much more quickly narrow down on the problem (and hopefully fix > it before you get tired and go to sleep :-) > > Moreover, since the function is running post-mortem, it can do > very detailed checks that would otherwise take way too long. > E.g., check every mbuf, every queue entry, check the filesystem, > etc. Basically a "fsck" for the kernel memory. You do not only want to call this at post-mortem. You often want to selectively use this while the kernel is running. Example: At one point (a year and half or so ago), I was debugging the tty driver in bisdn. For some reason, it was crashing in various ways at various times, with no sane reason - just garbage data. I spent quite a bit of time looking at this, finding no reason for the faults - they "just happened", taking on average perhaps 4 hours hours under load to trigger. As I was getting more and more frustrated with attempting to shotgun debug this, I went back to my normal mode of development - I wrote invariants for all data structures in the vicinity. When I added an invariant for the clist structures (and check of it all over the place), I found that my "crash" (now an invariant incorrect panic) time went down to two minutes - and that it was always the same way, with the same stack backtrace, instead of crashing at various random points. The reason for the bug turned out to be that both I and the implementor of the driver had missed the change of spls from levels in BSD4.4 to masks in FreeBSD. After I had seen the invariant failure, I could see that something was being interrupted between two spls - and after 3 minutes of reading the FreeBSD manpage and three lines of changes I had something that worked. That driver had been non-functional for at least three releases of bisdn (and the userland code to handle it was not even there, which I expect was due to this). I further expect that somebody had tried pretty hard to debug it, as they had spent the time to actually write it. The fact that I (which at that point had little experience with the FreeBSD kernel) was able able to debug that in a couple of hours where others had used more time and failed before me show some of the power of invariants for finding obscure bugs. I would like to have invariants available for all significant data structures, and I'm planning to write them up as I get time for it. > Is this something that people would be motivated enough to make > as "official" FreeBSD kernel good housekeeping policy? I suspect a large number of us will use it, making it likely it will sort of maintain itself. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 15 23:33:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15472 for freebsd-hackers-outgoing; Fri, 15 Jan 1999 23:33:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15453; Fri, 15 Jan 1999 23:33:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA98824; Fri, 15 Jan 1999 23:32:43 -0800 (PST) To: Brian Somers cc: Eivind Eklund , "Joseph T. Lee" , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Gratuitous name changes (was: libalias and ident) In-reply-to: Your message of "Thu, 14 Jan 1999 08:59:51 GMT." <199901140859.IAA44254@keep.lan.Awfulhak.org> Date: Fri, 15 Jan 1999 23:32:43 -0800 Message-ID: <98821.916471963@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If libalias changes to libnat, I'd prefer to just change the ppp flag > to -nat, update the ppp version to 2.1 and update You would change it, and you'd only document -nat, but you'd still preserve -alias as a synonym for it (for at least a year or so) because otherwise: > But this isn't necessarily a good idea as it may attract a pile of > ``why the hell did you break my configuration for no good reason'' > messages. That will happen. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 01:46:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24561 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 01:46:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p135.tfs.net [139.146.210.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24523; Sat, 16 Jan 1999 01:45:59 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id DAA54755; Sat, 16 Jan 1999 03:45:41 -0600 (CST) From: Jim Bryant Message-Id: <199901160945.DAA54755@unix.tfs.net> Subject: Re: Forward all spam to UCE@FTC.GOV [please take to -chat] In-Reply-To: <4.1.19990115143915.03abd400@mail.thirdage.com> from Jamie Lawrence at "Jan 15, 99 03:32:58 pm" To: jal@ThirdAge.com (Jamie Lawrence) Date: Sat, 16 Jan 1999 03:45:35 -0600 (CST) Cc: freebsd-chat@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, dennis.moore@mail.house.gov Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 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: [absurd uneducated anarchist crotch-rot rant deleted] > >to disagree with this is to admit that self-policing the internet [or > >anything else for that matter] is an utterly sophistic concept that > >needs to be relegated to the status of fairie tale. which, by the way > >is a circular concept anyhow, since to agree with my reasoning is to > >admit the same. at least i have enough moral character to admit it. > > What? You're not making any sense. what part did you not understand. self-regulation DOES NOT work, HAS NEVER worked, and WILL NEVER work. it is a historically sophistic concept. where there is no threat of punishment, there is no incentive to not do something. anarchists like you have made the internet a ROTTING CESSPOOL of criminal activity. every now and then the toilet does need flushed lest the whole house become diseased! > The net is built on collaboration and self regulation. What are you > trying to say? That the inconvenience spam poses to you should bring > the regulators (who of course will have no idea what they're regulating, > but the voters want it, so so be it) running to regulate speech? how you criminals sit back and use the worn-out [and totally inappropriate to the conversation] phrase "free speech" to support criminal acts is amazing. free speech has it's limitations, constitutionally tested limitations. i understand your opposition to laws, as laws are the criminal's worst enemy. this is NOT a free speech issue. this is an issue of property rights. owners of private property have rights, the renters of private property have rights. well tested rights. your free speech right ends when you leave your owned/rented property or public property, and enter someone else's owned/rented property. disagree with me? what if someone throws a rock through your living room window with a note attached, and defends the act based on the free speech clause? are you starting to see the point? freedom of speech protections constitutionally end when you enter someone's domicile or place of business against their will [either personally, or by proxy like the rock through the window], or when you have been asked to leave. we rent domiciles and places of business on the internet. we have constantly asked you assholes to leave our owned/rented property and not to come back. you keep coming back. time to call the sheriff! if you believe in sending unsolicited shit so much, i'll let you do it the day you start paying my internet bills, until then you criminal assholes need to keep your shit out of the general public's owned/rented property that they pay good money for. THIS IS NOT THE POST OFFICE! until the spammers or the government starts paying for everyone's service, the supreme court agrees with me [ref. the "Recipient" ruling from the fifties, and every private property and rented property case ever heard by the court]. If effective laws aren't made, THE CURRENT LAW ALLOWING SPAM WILL BE OVERTURNED AS UNCONSTITUTIONAL, and the entire question of violating the rights of the owner/lessee of owned/rented property will be before the supreme court. i'm sure you know what the decision will be, no matter how conservative the Justice. you and your criminal friends are free to set up web pages and advertise them in an APPROPRIATE PLACE, such as an appropriately named newsgroup like alt.scams.advertised. by the way, spamming in inappropriate newsgroups is another good target for reform. based on the number of available newsgroups, and the ability to create new ones easily, such reforms would not in any way violate free speech. yell: "I have a bomb" in a public place and see what I mean about "APPROPRIATE PLACE", pass out a tract in a publically owned airport and see what I mean about "APPROPRIATE PLACE". have a public demonstration without a permit. the words "APPROPRIATE PLACE" are also constitutionally tested and found to be VALID limitations on free speech. you and your criminal friends are on very shaky ground. support a fair opt-in spam law, with real and involuntary enforcement, with real budgets for enforcement, or lose your scam method altogether. your choice. 270,000,000 americans are pissed. who the fuck are you to defy the will of the american public, or the U.S. Constitution [as upheld time and time again]?! stop violating OUR rights on OUR owned/rented property! 220+ years of tested cases can not be wrong, and WILL be upheld. take your faux pas "free speech" defense and go crawl back under your victorian rock while we piss on your parade. throwing rocks through windows is a criminal act, regardless if a note is tied to it or not! Posted: PRIVATE PROPERTY! -------------------------------------------------------- NOTE TO HONORABLE ISP OWNERS AND INTERNET PATRONS: remember this argument. remember it well. it will win EVERY case EVERY time you press charges against or sue a spammer. they will, as this criminal/criminal-supporter has, use "free speech" sophistry as the cornerstone of their case every time. what their uneducated and feeble minds don't understand is that it's not a free speech issue, and that it is a private/rented property issue. in some states it is perfectly legal to bash someone's skull in if they won't leave your private property. gee, i wonder why people get so emotional? as renters and property owners, it is up to us to do something about the problem [legal action], and when we cannot handle it ourselves, to compel our governments to handle the issue once and for all. Americans, forward all UNSOLICITED commercial email, regardless of fraud status to uce@ftc.gov AS THEY HAVE ASKED. If it overwhelms them, then they will see no other choice but to call the current [unconstitutional] laws allowing spam into question, as well as push for clear international treaties on the issue. time to call the sheriff! time to fire your right wing criminal supporting hypocrite congressman! politics are central to this issue, any intelligent discussion cannot fail to point out who enabled the problem to grow like a mushroom out of shit, while taking the money from the criminal's umbrella organization: the Direct Marketing Association. if you are not in america, keep in mind that most countries honor such private property laws and also have equivilant laws of their own along the same lines. relating the internet to private property is simply the natural progression of existing, applicable laws into the 21st century. we cannot prevent someone from renting space for a web page to advertise their scams, so long as their landlord allows them to. what we can do is to boot them off of OUR property FOREVER, and prevent them from entering unless directly invited [not by proxy], with the support of the constitution. a child of five understands that what i am saying is already a law of nature. unfortunately, due to the criminal elements, it also has to be made a federal statue [it already is, but criminals require the law to be specific to the internet before they take it seriously]. regulation on the internet is an issue of simple property rights, and a natural extention to existing laws. it's only a matter of time, and that time will be sooner than the criminals think. the U.S. Constitution requires that any law regarding interstate and international commerce be a federal law. constitutionally, this is a mandate. states are also free to make laws [to a certain degree] concerning commerce into or out of their states. the right wing idea of not enforcing regulations/laws has done nothing for America or the world for that matter but make things intolerable for anyone except criminals. the same goes for the whole concept of "self-regulation" which is simply a sophistic fairie tale concept that has no meaning. any regulation with a vague meaning is legally the same as no regulation at all. if they are not careful, the private property question will be put in the terms of "any unsolicited direct marketing" before the supreme court, that includes telemarketing. the constitution is on the side of the people. since it's a private property issue, restraint of trade doesn't even enter into the picture. free speech defenses in private property issues usually end up in a summary judgment for the property owner or lessee, so long as the legally valid point is made that it is a private property issue. anyone want to fund a test in the supreme court? i'll challange spammers! if i don't see any support for fair laws on the public's terms, i'll constitutionally challange the entire concept of all direct marketing not terminating in my U.S. Mail box. As soon as I file, they will have already lost because free speech and restraint of trade are invalid arguments in a private property case. any attorney on this mailing list will have no choice but to concur with my argument. spam will be beat based on private property issues. anything short of nationalization of the internet and integration into the functions of the post office, or a complete buyout of the internet by spammers offering free service for all conditional on users accepting spam will fall short on challange. i'm sure nobody wants either of those to happen! the spammer's only choice to remain in existance legally is to agree to new enforcable laws [and the applicable enforcement budget] on the public's terms. -------------------------------------------------------- TO MEMBERS OF THE DIRECT MARKETING ASSOCIATION, RIGHT-WING WHACKOS, AND SPAMMING ISPs: THIS IS NOT THE POST OFFICE. your denial of the validity of my argument, or the seriousness of the situation CAN be interpreted as a verbal waiver of your rights to protection from denial-of-service attacks which are based on the same legal principles. if you are against laws and regulations, please don't be selective. you, by your own arguments deserve no more legal protection than you believe in the general public, honest businesses, and honorable isps having. you have had your chance to "self-regulate". by not doing so, you have shown your true colors. time for the people to take over. if we remove your kind from legal existance, it's your fault. you have had how many years to try to "self-regulate"? it does not work, and thus other solutions must be found. no more sophistic "voluntary" plans. "voluntary self-regulation" is synonymous with the phrase "honor amongst theives". fucking hypocrites. -------------------------------------------------------- to -hackers: please take this to -chat. i posted this in -hackers as well as -chat because of several rebuttals in -hackers based on similar invalid arguments. sorry for the length, but based on the refusals to comply with the wishes of a federal agency, and the sophistic arguments presented skirting the subject by defending the criminals sending the unsolicited commercial email [yes, a tresspasser is a criminal], I felt it necessary to clarify the whole issue in PROPER terms. please note that this is also Cc:'ed to my congressman. i'd appreciate if the honorable people out there would write similar statements to theirs. please ask your users to also do so blatently on your ISP home page, you might find that you get a lot of positive comments, and a larger customer base by doing so. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 06:12:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17409 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 06:12:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from clubserv.rp-online.de (clubserv.rp-online.de [149.221.232.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17404 for ; Sat, 16 Jan 1999 06:12:44 -0800 (PST) (envelope-from veith@bigfoot.com) Received: from bigfoot.com (as8-pri4.rp-plus.de [149.221.239.132]) by clubserv.rp-online.de (8.9.1a/8.9.1) with ESMTP id PAA14842 for ; Sat, 16 Jan 1999 15:13:47 +0100 (MET) Message-ID: <36A09E81.8DF04971@bigfoot.com> Date: Sat, 16 Jan 1999 15:13:21 +0100 From: Stefan Veith X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Problems with egcs-1.1.1 port Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone! I installed the egcs-1.1.1 port on my system (3.0-R) and tried to compile a programme which uses extentions. But I did not succed to compile it properly so far. The configure script of mico for example tries to test the extention capability of egcs and causes a core dump. Is this a known problem? Is there any possibility to compile programmes with extensions under FreeBSD? N.B.: Please make a cc: to my address as I am not on this list. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 09:16:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01147 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 09:16:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ipf.net (oldrelay.ipf.net [195.88.0.13]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA01141 for ; Sat, 16 Jan 1999 09:16:06 -0800 (PST) (envelope-from graemer@okay.net) Received: (qmail 3960 invoked from network); 16 Jan 1999 17:16:00 -0000 Received: from ip101.dresden.okay.net (HELO nt2) (195.211.202.101) by relay.ipf.net with SMTP; 16 Jan 1999 17:16:00 -0000 Message-ID: <000f01be4174$53e2b210$0301a8c0@nt2.network.de> From: "Oliver Graemer" To: Subject: freebsd for alpha? Date: Sat, 16 Jan 1999 18:19:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi FreeBSD team, I have two questions: - When will FreeBSD available for the Alpha architecture (spec. Universal Desktop Box)? - Whats the native file system of FreeBSD? thx! Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 09:20:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02072 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 09:20:52 -0800 (PST) (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 JAA02067 for ; Sat, 16 Jan 1999 09:20:51 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with ESMTP id MAA07269; Sat, 16 Jan 1999 12:20:47 -0500 (EST) Date: Sat, 16 Jan 1999 12:20:47 -0500 (EST) From: Snob Art Genre Reply-To: ben@rosengart.com To: Oliver Graemer cc: hackers@FreeBSD.ORG Subject: Re: freebsd for alpha? In-Reply-To: <000f01be4174$53e2b210$0301a8c0@nt2.network.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, 16 Jan 1999, Oliver Graemer wrote: > - When will FreeBSD available for the Alpha architecture (spec. > Universal Desktop Box)? FreeBSD runs on Alphas now. I don't know about the specific machine in question, but check the web pages at http://www.freebsd.org, there should be a compatibility list there somewhere. > - Whats the native file system of FreeBSD? FFS (aka UFS). 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 Sat Jan 16 09:59:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05309 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 09:59:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05301 for ; Sat, 16 Jan 1999 09:59:17 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id RAA32272; Sat, 16 Jan 1999 17:58:57 GMT Date: Sat, 16 Jan 1999 17:58:57 +0000 (GMT) From: Doug Rabson To: ben@rosengart.com cc: Oliver Graemer , hackers@FreeBSD.ORG Subject: Re: freebsd for alpha? 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, 16 Jan 1999, Snob Art Genre wrote: > On Sat, 16 Jan 1999, Oliver Graemer wrote: > > > - When will FreeBSD available for the Alpha architecture (spec. > > Universal Desktop Box)? > > FreeBSD runs on Alphas now. I don't know about the specific machine in > question, but check the web pages at http://www.freebsd.org, there > should be a compatibility list there somewhere. FreeBSD works just fine on the UDB. We don't yet support some of its devices (tga, floppy, pccard). There are possibilities of tga support in the fairly near future and someone promised to work on the floppy driver. I don't expect anyone to tackle pccard anytime soon though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 10:15:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06847 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 10:15:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.bitmine.com (adsl-209-233-238-103.dsl.pacbell.net [209.233.238.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06842 for ; Sat, 16 Jan 1999 10:15:39 -0800 (PST) (envelope-from rdas@bitmine.com) Received: from bitmine.com (highlands [192.68.1.3]) by ns.bitmine.com (8.8.7/8.8.7) with ESMTP id KAA18117 for ; Sat, 16 Jan 1999 10:13:46 -0800 (PST) (envelope-from rdas@bitmine.com) Message-ID: <36A0D663.FFE42ED2@bitmine.com> Date: Sat, 16 Jan 1999 10:11:47 -0800 From: rdas-bitmine X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: PPTP patches....a clarification Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some people have asked if my patches will allow a PPTP client to talk to a PPTP server behind natd. This wasn't the intent of my patch, so let me clarify it a bit: I have 'natd' running at home on a FreeBSD box. I also have several NT workstations at home that talk to the internet via that FreeBSD box on a single IP address (which is obviously why I am running natd). I needed a single one of these NT workstations to run a PPTP client (via RAS) to talk to the PPTP server in my office. My patches allow this to happen with only the single workstation that is specified on the command line to natd ('-gre_client_address' option). Once you have these libraries and the natd executable installed, you can test it out like this: * Kill natd * Run natd like this ('natd -verbose -gre_client_address 10.10.10.1 -interface ep1'), where 10.10.10.1 will be your internal PPTP client's IP address, and 'ep1' will be your external interface. * Natd will not run in the background, but will instead show all of the aliasing information on the terminal where it was launched * Now fire up your PPTP dialup entry and watch the TCP and GRE packets get aliased..... If you see the GRE packets getting aliased correctly, you should be up and running correctly. Check out the sources. Look specifically at 'alias.c'. The changes I made were very simple. -Rob Das- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 12:53:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20949 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 12:53:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wind.freenet.am ([194.151.101.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20694 for ; Sat, 16 Jan 1999 12:52:09 -0800 (PST) (envelope-from casper@acc.am) Received: from lemming.acc.am (acc.freenet.am [194.151.101.251]) by wind.freenet.am (8.9.1/8.9.1) with ESMTP id AAA02430; Sun, 17 Jan 1999 00:50:21 +0400 (GMT) Received: from acc.am (nightmar.acc.am [192.168.100.108]) by lemming.acc.am (8.9.1a/8.9.1) with ESMTP id BAA23045; Sun, 17 Jan 1999 01:05:27 +0400 (AMT) Message-ID: <36A08B81.BB91F906@acc.am> Date: Sat, 16 Jan 1999 16:52:17 +0400 From: Casper Organization: Armenian Computer Center X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: sthaug@nethelp.no CC: asmodai@wxs.nl, mph@pobox.com, hackers@FreeBSD.ORG Subject: Re: tcpdump and localhost References: <11937.916184598@verdi.nethelp.no> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Put phisical feedback there - 1.5m of Ethernet & 1 T-connector :) I also done this at home to test my program that uses phisical layer of Ethernet .... all working just OK sthaug@nethelp.no wrote: > > > OK, and if I ping the IP address associated with the NIC then it gets put > > on the wire right? > > If you ping the IP address associated with the NIC from *the host itself*, > it won't be put on the wire. You have to ping it from another host. > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 14:15:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28793 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 14:15:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-50.ppp.wenet.net [206.15.84.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28787 for ; Sat, 16 Jan 1999 14:15:33 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA07361; Sat, 16 Jan 1999 14:18:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 16 Jan 1999 14:18:40 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Stefan Veith cc: hackers@FreeBSD.ORG Subject: Re: Problems with egcs-1.1.1 port In-Reply-To: <36A09E81.8DF04971@bigfoot.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, 16 Jan 1999, Stefan Veith wrote: > I installed the egcs-1.1.1 port on my system (3.0-R) and tried to > compile a programme which uses extentions. But I did not succed to > compile it properly so far. The configure script of mico for example > tries to test the extention capability of egcs and causes a core dump. By extensions do you perhaps mean exceptions? > Is this a known problem? Is there any possibility to compile programmes > with extensions under FreeBSD? Ok here's the deal. Exceptions in egcs (and probably gcc 2.8) have their own requirements. Since they manipulate the stack, and attempt to be thread safe, and all sorts of other fun stuff, etc, they've come up with their own incompatable way of doing things. This is fine, but requires some tweaking of egcs 1.1.1 when you build it. Not fun. There is somewhat of a solution, and that is to use setjmp and longjmp to handle exceptions. You can do this by adding the switch -fsjlj-exceptions to the CXXFLAGS before you run configure. Also keep in mind that without any effort, shared libs are somewhat broken, so to make sure mico builds, you'll want to use --disable-shared on the configure command line. What in the world are you trying to build that needs mico? If it's koffice, make sure you configure mico with --disable-ministl (or whatever it's called to make sure that the half hearted implementation of the STL isn't used). - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 14:22:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29269 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 14:22:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29264 for ; Sat, 16 Jan 1999 14:22:16 -0800 (PST) (envelope-from pb@ludd.luth.se) Received: from sister.ludd.luth.se (pb@sister.ludd.luth.se [130.240.16.77]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id XAA03163 for ; Sat, 16 Jan 1999 23:22:12 +0100 From: Peter Brevik Received: (pb@localhost) by sister.ludd.luth.se (8.6.11/8.6.11) id XAA26618 for freebsd-hackers@freebsd.org; Sat, 16 Jan 1999 23:22:11 +0100 Message-Id: <199901162222.XAA26618@sister.ludd.luth.se> Subject: Auto config idea To: freebsd-hackers@FreeBSD.ORG Date: Sat, 16 Jan 1999 23:22:11 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I been thinking on this w95 start/settings/system "utility". In there most hardware config data for a machine that is currently running w95 stored. Would it not be a real "nice" thing to have a fbsd utility that can read the data and create a proper fbsd kernel config out of that? (using mount_msdos -l .. .. and friends ;) The ultimate w95 upgrade :-> /pb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 18:38:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22015 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 18:38:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sims-ha.videotron.net (faure.videotron.net [205.151.222.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22009 for ; Sat, 16 Jan 1999 18:38:24 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (ppp050.104.mmtl.videotron.net) by sims-ha.videotron.net (Sun Internet Mail Server sims.3.5.1998.09.21.23.34) with ESMTP id <0F5O00GACNAL6T@sims-ha.videotron.net> for Hackers@Freebsd.org; Sat, 16 Jan 1999 21:37:35 -0500 (EST) Date: Sat, 16 Jan 1999 21:37:32 -0500 From: "Stephane E. Potvin" Subject: Re: New bootloader and network iface To: Mike Smith , Hackers@FreeBSD.ORG Message-id: <36A14CEC.5B57D680@videotron.ca> Organization: Galea Network Security MIME-version: 1.0 X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_K78XnBrKi0QGreU1scT0Cw)" References: <199812180212.SAA00576@dingo.cdrom.com> <36859F9F.5B8DAFF@videotron.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Boundary_(ID_K78XnBrKi0QGreU1scT0Cw) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit I guess that my previous post got overlooked in the mayhem on the list just before new years eve or that I was less that clearer with my questions. So here is a new rephrased version which I hope will be a little clearer. I'm currently trying to add remote booting to the bootloader (i386) for a pet project that I'm currently working on. I first stumbled on the fact that as soon as I tried to add a new netif_driver entry I got the following error: zfree (0x,2048): wild pointer I guess from the code around line 153 of the zalloc.c file of the stand library that the start of the heap must be MEMNODE_SIZE_MASK+1 aligned. Am I completely off-track??? I attached the patch I'm using to fix this. It patches the file /usr/src/sys/boot/i386/loader/main.c Ok, here comes the real question. How does the match mechanism work. I understand very well that it is a vague question but I just doesn't seems to be able to just grasp how it is supposed to work. A general explanation of the motives behind this would probably be enough. Is the lsdev function expected to list the network booting devices available? Currently, the probing of the network devices happens only upon the actual opening of the device. I guess I could move it to the initialization of the network devsw entry if wanted/expected. I've got one last question. What is the preferred way to access the pci configuration space. Must I use the biospcipnphandler to check if the card is there and if so use the pci bios functions to retreive the data. Or, on the other hand, can I use the pci config registers to scan the bus myself. I know that both of these approachs would be feasible, I just want to know which one would be the most politically correct. I'm personnaly more enclined to use the second one because I have no knowledge whatsoever of the pci bios but I know pretty well how to do manual pci bus probing/configuration. Thanks in advance! Stephane E. Potvin Galea Network Security --Boundary_(ID_K78XnBrKi0QGreU1scT0Cw) Content-type: text/plain; name=main.c.diff; charset=us-ascii Content-disposition: inline; filename=main.c.diff Content-transfer-encoding: 7bit *** main.c.orig Sat Jan 16 21:11:30 1999 --- main.c Sat Jan 16 21:10:54 1999 *************** *** 32,37 **** --- 32,38 ---- */ #include + #include #include #include #include *************** *** 71,76 **** --- 72,78 ---- main(void) { int i; + u_int32_t aligned_end; /* Pick up arguments */ kargs = (void *)__args; *************** *** 82,89 **** * Initialise the heap as early as possible. Once this is done, malloc() is usable. * * XXX better to locate end of memory and use that */ ! setheap((void *)end, (void *)(end + (384 * 1024))); /* * XXX Chicken-and-egg problem; we want to have console output early, but some --- 84,94 ---- * Initialise the heap as early as possible. Once this is done, malloc() is usable. * * XXX better to locate end of memory and use that + * + * heap start must be MEMNODE_SIZE_MASK aligned for zfree to work */ ! aligned_end = ((u_int32_t) end + MEMNODE_SIZE_MASK) & ~MEMNODE_SIZE_MASK; ! setheap ((void *) aligned_end, (void *) (aligned_end + (384 * 1024))); /* * XXX Chicken-and-egg problem; we want to have console output early, but some --Boundary_(ID_K78XnBrKi0QGreU1scT0Cw)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 18:43:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22515 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 18:43:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailgate.fore.com (mailgate.fore.com [169.144.68.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22509; Sat, 16 Jan 1999 18:43:08 -0800 (PST) (envelope-from rv@fore.com) Received: from mailman.fore.com (mailman.fore.com [169.144.2.12]) by mailgate.fore.com (8.9.1/8.9.1) with ESMTP id VAA07142; Sat, 16 Jan 1999 21:42:57 -0500 (EST) Received: from sol.eng.fore.com (sol [169.144.155.73]) by mailman.fore.com (8.8.8/8.8.8) with ESMTP id VAA00414; Sat, 16 Jan 1999 21:43:16 -0500 (EST) Received: from agastya.eng.fore.com (agastya [169.144.1.196]) by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id VAA12767; Sat, 16 Jan 1999 21:42:57 -0500 (EST) Received: from localhost (rv@localhost) by agastya.eng.fore.com (8.9.1b+Sun/8.9.1) with SMTP id VAA21270; Sat, 16 Jan 1999 21:42:57 -0500 (EST) Message-Id: <199901170242.VAA21270@agastya.eng.fore.com> X-Authentication-Warning: agastya.eng.fore.com: rv owned process doing -bs X-Authentication-Warning: agastya.eng.fore.com: rv@localhost didn't use HELO protocol To: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: kernel build breaks after the latest cvsup Reply-to: rv@fore.com X-Mailer: MH v6.8.3 X-LoopDetect: rv@eng.fore.com Date: Sat, 16 Jan 1999 21:42:57 -0500 From: Rajesh Vaidheeswarran Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello folks, I just did a cvsup and tried rebuilding world and the kernel, but I keep getting an error during the kernel linking stage. loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' ... and many more... psm.o: In function `enable_aux_dev': psm.o(.text+0xd): undefined reference to `send_aux_command' psm.o: In function `disable_aux_dev': psm.o(.text+0x4d): undefined reference to `send_aux_command' ... and psm.o having many such undefined references too. I have not done any changes to my kernel config since the last make update. Any ideas? Any help is appreciated. Thanks! rv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 19:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24482 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 19:08:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24463; Sat, 16 Jan 1999 19:08:30 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id GAA01356; Sun, 17 Jan 1999 06:05:22 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sun, 17 Jan 1999 06:05:22 +0300 (MSK) From: oZZ!!! To: Rajesh Vaidheeswarran cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kernel build breaks after the latest cvsup In-Reply-To: <199901170242.VAA21270@agastya.eng.fore.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, 16 Jan 1999, Rajesh Vaidheeswarran wrote: > Hello folks, > > I just did a cvsup and tried rebuilding world and the kernel, > but I keep getting an error during the kernel linking stage. > > loading kernel > syscons.o: In function `scvidprobe': > syscons.o(.text+0x231): undefined reference to `vid_configure' > syscons.o(.text+0x24e): undefined reference to `vid_allocate' > syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' > ... and many more... > > psm.o: In function `enable_aux_dev': > psm.o(.text+0xd): undefined reference to `send_aux_command' > psm.o: In function `disable_aux_dev': > psm.o(.text+0x4d): undefined reference to `send_aux_command' > ... > and psm.o having many such undefined references too. > > I have not done any changes to my kernel config since the last > make update. > > Any ideas? Any help is appreciated. > > Thanks! You may c /usr/src/UPDATING & /sys/i386/conf/LINT kernel sources is changed. I think you must read following for compile new kernel: http://www.freebsd.org/~yokota/sc_update.txt > > rv Rgdz, Sergey A. Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 20:37:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01326 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 20:37:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailgate.fore.com (mailgate.fore.com [169.144.68.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01307; Sat, 16 Jan 1999 20:37:31 -0800 (PST) (envelope-from rv@fore.com) Received: from mailman.fore.com (mailman.fore.com [169.144.2.12]) by mailgate.fore.com (8.9.1/8.9.1) with ESMTP id XAA08380; Sat, 16 Jan 1999 23:37:22 -0500 (EST) Received: from sol.eng.fore.com (sol [169.144.155.73]) by mailman.fore.com (8.8.8/8.8.8) with ESMTP id XAA03375; Sat, 16 Jan 1999 23:37:45 -0500 (EST) Received: from agastya.eng.fore.com (tejas [169.144.86.36]) by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id XAA14689; Sat, 16 Jan 1999 23:37:27 -0500 (EST) Received: from localhost (rv@localhost) by agastya.eng.fore.com (8.9.1b+Sun/8.9.1) with SMTP id XAA26152; Sat, 16 Jan 1999 23:37:27 -0500 (EST) Message-Id: <199901170437.XAA26152@agastya.eng.fore.com> X-Authentication-Warning: agastya.eng.fore.com: rv owned process doing -bs X-Authentication-Warning: agastya.eng.fore.com: rv@localhost didn't use HELO protocol To: Chris Timmons cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: kernel build breaks after the latest cvsup In-reply-to: Message from Chris Timmons of "Sat, 16 Jan 1999 20:11:34 PST." Reply-to: rv@fore.com X-Mailer: MH v6.8.3 X-LoopDetect: rv@fore.com Date: Sat, 16 Jan 1999 23:37:26 -0500 From: Rajesh Vaidheeswarran Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Chris, and thank you all who have replied to my message. I did as per your suggestions, and my kernel compiles now. (I haven't yet tried a reboot though). Thanks, once again. rv -- using MH template repl.format -- In a previous message, Chris Timmons writes: > > You probably need to add kbd0 and update sc0 in your kernel config file. > Have a look in the GENERIC kernel config to see how it is done now... > > On Sat, 16 Jan 1999, Rajesh Vaidheeswarran wrote: > > > Hello folks, > > > > I just did a cvsup and tried rebuilding world and the kernel, > > but I keep getting an error during the kernel linking stage. > > > > loading kernel > > syscons.o: In function `scvidprobe': > > syscons.o(.text+0x231): undefined reference to `vid_configure' > > syscons.o(.text+0x24e): undefined reference to `vid_allocate' > > syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' > > ... and many more... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 16 22:41:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10326 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 22:41:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10321 for ; Sat, 16 Jan 1999 22:41:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA46889; Sat, 16 Jan 1999 22:41:01 -0800 (PST) (envelope-from dillon) Date: Sat, 16 Jan 1999 22:41:01 -0800 (PST) From: Matthew Dillon Message-Id: <199901170641.WAA46889@apollo.backplane.com> To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: Path to SMP References: <199901152355.QAA21837@usr04.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sounds like it is solving a different problem. It would be a rather complex solution to a relatively simple problem - processes can already 'almost' run in supervisor mode, in parallel, in an SMP environment. -Matt : :Jason Evans has started work on an async call based mechanism. : :The functional decomposition is into flags for each system call :to tell the trap code whether the call will: : :(A) Never block :(B) Sometimes block :(C) Always block : :The kernel work moves the kernel stack into a call context structure, :which includes a pointer to the VM for the process making the call. : :Effectively, this make all entries into the kernel seperately :schedulable, and allows a process to enter the kernel. : :The use of the type-of-call flags is an optimization, allowing the :use of a "fake" (static, user space) call context structure pointer :for calls in category (A), or (B), in the case that they run to :completion instead of blocking. : :The mechanism necessitates the addition of a multiplexed system call :that accepts the commands ACG_WAIT (Async Call Gate Wait) and :ACG_CANCEL. This is similar to the SVID III aiowait(RT), aiocancel(RT) :mechanism, and is also similar to the "aio" mechanisms in both :UnixWare and Solaris, semantically. It's also like the POSIX :stuff, only with the ability to do all calls, not just some of them. : :The mechanism should provide an SMP scalable basis for cooperative :user and kernel space thread scheduling which fully obeys POSIX :semantics. : :This sidesteps or resolves many of the issues for decomposition, :as pointed out in: : : Scheduling and Load Balancing in Parallel and Distributed : Systems : : Behrooz A. Shirazi, Ali R Hurson, and Krisna M. Kavi : IEEE Computer Society Press : ISBN 0-8186-6587-4 : : 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 : Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message