From owner-freebsd-hackers Sun Nov 16 00:23:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27685 for hackers-outgoing; Sun, 16 Nov 1997 00:23:08 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from csnet.cs.technion.ac.il (csnet.cs.technion.ac.il [132.68.32.7]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA27673 for ; Sun, 16 Nov 1997 00:22:56 -0800 (PST) (envelope-from nadav@cs.technion.ac.il) Received: from csd.csa (csd [132.68.32.8]) by csnet.cs.technion.ac.il (8.6.11/8.6.10) with ESMTP id KAA21482; Sun, 16 Nov 1997 10:20:36 +0200 Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id KAA15243; Sun, 16 Nov 1997 10:21:07 +0200 Date: Sun, 16 Nov 1997 10:21:07 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: "John S. Dyson" cc: Alex , tom@sdf.com, hackers@FreeBSD.ORG Subject: Re: 256Meg In-Reply-To: <199711160742.CAA12053@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, John S. Dyson wrote: > Alex said: > > > > > > On Fri, 14 Nov 1997, Tom wrote: > > > > > > > > On Fri, 14 Nov 1997, dennis wrote: > > > > > > > Is there a maximum that FreeBSD can support? > > > > > > > > Dennis > > > > > > > > > What? Filesystems? RAM? Something else? > > > > > > RAM... no problem. I'm running two 256MB RAM servers now. > > > > Actually, there's a limit of 4GB or so of ram, on the 486 (if you call > > tha ta limit ;-) ), and AFAIK the P5, P6 and PII and clones as well. > > > Physically, the limit is 36Bits on a P6. It would require some mods to > the pmap layer, and maybe some enhancements to the upper level VM code. > One disadvantage with the extended 3 level translation mode is that > the PTE's become twice as large. I seriously doubt that we'll need that > on a P6, but on future Slot1/Slot2 processors, we might find that 4GB > is a real limit, and have to accomodate the modified PTD/PTE format. > > Imagine a processor that is perhaps 2X to 5X as fast as a P6, in a > multiprocessor config -- that would appear to be able to use more than the typical There is such a processor! It's called an Alpha! (sorry, couldn't resists). > upper end of 1GByte of memory, and even more than the normally addressable > 4Gbytes. > > I haven't given this alot of thought yet, but these issues are probably going > to be important in the medium-term future (approx 1yr.) > > -- > John > dyson@freebsd.org > jdyson@nc.com > Nadav From owner-freebsd-hackers Sun Nov 16 00:36:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28424 for hackers-outgoing; Sun, 16 Nov 1997 00:36:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28400 for ; Sun, 16 Nov 1997 00:35:58 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.7.3) id JAA11296; Sun, 16 Nov 1997 09:36:25 +0100 (MET) Message-Id: <199711160836.JAA11296@sos.freebsd.dk> Subject: Re: VESA VBE 1.2 and 2.0 library In-Reply-To: <19971115163359.29992@micron.mini.net> from Jonathan Mini at "Nov 15, 97 04:33:59 pm" To: mini@d198-232.uoregon.edu (Jonathan Mini) Date: Sun, 16 Nov 1997 09:36:23 +0100 (MET) Cc: hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jonathan Mini who wrote: Sounds VERY interesting! I'll help out testing and what else I'm able to do... You have commit privs right?, just grap yourself the next free dev #... > I am developing a library which will provide VESA VBE 1.2 and 2.0 support > for FreeBSD. It works as follows : > 1) There is a device in the kernel which provides memory mappings for > the video card, and (if needed) a virtual framebuffer mapping in kernel > memory. (this ensures that the framebuffer won't get swapped out) > 2) a vm86 daemon which contains mappings to the virtual framebuffer (if > in use) and io privelege to the video card's I/O space. This daemon has > two purposes : one, it performs VBE calls requested by the vesa device > and returns the results (often data tables) where the vesa device can > reach them to pass back to the caller. > 3) A library which acts as a front-end for the vesa device and hides the > whole interface between the vesa device and userland. It also will manage > contention against syscons, if enabled. (For example, it will handle > switching between vtys, changing the keyboard mode, etc) > > This provides support for all VESA VBE video modes on any card which supports > 1.2 or better of the spec. (I have never seen a card which did not suport at > least VBE 1.2, and this is including old 8 bit VGA wanna-be cards that are so > slow you would never want to use one) It will also use a linear framebuffer > if the card provides it, and if not, a virtual frambuffer will be made > available. The virtual framebuffer is much slower, but it works. > > So, I am officially requesting a major number to be assigned to me for the > device 'vesa' which provides the memory mappings needed for this system to > work. > > -- > Jonathan Mini Ingenious Productions > Software Development P.O. Box 5693, > Eugene, Or. 97405 > > "A child of five could understand this! Quick -- Fetch me a child of five." > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Nov 16 00:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28799 for hackers-outgoing; Sun, 16 Nov 1997 00:42:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28778 for ; Sun, 16 Nov 1997 00:42:41 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA13089; Sun, 16 Nov 1997 00:45:44 -0800 (PST) Message-Id: <199711160845.AAA13089@implode.root.com> To: Mark Mayo cc: hackers@FreeBSD.ORG Subject: Re: de underflow errors. huh? In-reply-to: Your message of "Sun, 16 Nov 1997 00:17:10 EST." <19971116001710.02627@vmunix.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Nov 1997 00:45:44 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I posted this questions 2 weeks ago on -questions, and 1 week ago >on -stable (since it's happening on a -STABLE machine..) but I >haven't got a response yet. So here it is for the -hackers crowd: > >I've got a firewall machine with 2 ethernet cards. One Digital 21040 >based card on de0, and one Intel Pro/100B on fxp0. Everything seems >to be working fine, with the exception of numerous errors on the >console: > >de0: abnormal interrupt: transmit underflow > >I have no clue what this means. Packets seem to be flowing through >the interface nicely, and there is no noticeable packet loss. >If anyone has any ideas what could be causing this, or if I should >give a hoot, please let me know. It's indicating that the PCI bus was sufficiently busy enough to cause the transmit DMA to be stalled too long. The proper response to this condition in the device driver it to dynamically increase the transmit threshold (the number of bytes that are DMA'ed onto the card before the transmission is actually started on the wire). The fxp driver does this, the de driver doesn't. I think Matt Thomas might have fixed this in a later rev., but I'm not sure about that. Anyway, other than the annoying console messages and perhaps a packet drop when it happens, the problem can be ignored. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Nov 16 00:45:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28983 for hackers-outgoing; Sun, 16 Nov 1997 00:45:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28978 for ; Sun, 16 Nov 1997 00:45:43 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id DAA01863 for ; Sun, 16 Nov 1997 03:46:00 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Sun, 16 Nov 1997 03:46:00 -0500 (EST) From: "David E. Cross" To: freebsd-hackers@freebsd.org Subject: 'Official' Intel Fix Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I have seen the 'official' intel fix... it is the one to move the IDT over a page boundry. As has been said before, it is a nasty hairy kludge. Q: Does our fix 'work'.. in the SIGBUS code can we acurately determine if it was really SIGILL and return it? (what I am asking is why Intel picked that evil workaround) Q2: Considering that Intel's 'official' fix can result in a fair performance hit, any word on if they will be doing a recall? -- David Cross ACS Consultant From owner-freebsd-hackers Sun Nov 16 00:47:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA29101 for hackers-outgoing; Sun, 16 Nov 1997 00:47:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA29093 for ; Sun, 16 Nov 1997 00:47:52 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id AAA19107; Sun, 16 Nov 1997 00:47:13 -0800 (PST) Message-ID: <19971116004713.06932@micron.mini.net> Date: Sun, 16 Nov 1997 00:47:13 -0800 From: Jonathan Mini To: sos@FreeBSD.dk Cc: hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library References: <19971115163359.29992@micron.mini.net> <199711160836.JAA11296@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.85e In-Reply-To: =?iso-8859-1?Q?=3C199711160836=2EJAA11296=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Sun=2C_Nov_16=2C_1997_at_09=3A36=3A2?= =?iso-8859-1?Q?3AM_+0100?= X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt stands accused of saying: > In reply to Jonathan Mini who wrote: > > Sounds VERY interesting! > I'll help out testing and what else I'm able to do... Cool. I will probably be asking you a few questions abotu how syscons functions.. > You have commit privs right?, just grap yourself the next free dev #... :) Nope. > > > I am developing a library which will provide VESA VBE 1.2 and 2.0 support > > for FreeBSD. It works as follows : > > 1) There is a device in the kernel which provides memory mappings for > > the video card, and (if needed) a virtual framebuffer mapping in kernel > > memory. (this ensures that the framebuffer won't get swapped out) > > 2) a vm86 daemon which contains mappings to the virtual framebuffer (if > > in use) and io privelege to the video card's I/O space. This daemon has > > two purposes : one, it performs VBE calls requested by the vesa device > > and returns the results (often data tables) where the vesa device can > > reach them to pass back to the caller. > > 3) A library which acts as a front-end for the vesa device and hides the > > whole interface between the vesa device and userland. It also will manage > > contention against syscons, if enabled. (For example, it will handle > > switching between vtys, changing the keyboard mode, etc) > > > > This provides support for all VESA VBE video modes on any card which supports > > 1.2 or better of the spec. (I have never seen a card which did not suport at > > least VBE 1.2, and this is including old 8 bit VGA wanna-be cards that are so > > slow you would never want to use one) It will also use a linear framebuffer > > if the card provides it, and if not, a virtual frambuffer will be made > > available. The virtual framebuffer is much slower, but it works. > > > > So, I am officially requesting a major number to be assigned to me for the > > device 'vesa' which provides the memory mappings needed for this system to > > work. > > > > -- > > Jonathan Mini Ingenious Productions > > Software Development P.O. Box 5693, > > Eugene, Or. 97405 > > > > "A child of five could understand this! Quick -- Fetch me a child of five." > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Sun Nov 16 01:25:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA02752 for hackers-outgoing; Sun, 16 Nov 1997 01:25:52 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.cs.msu.su (root@redsun.cs.msu.su [158.250.10.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA02741 for ; Sun, 16 Nov 1997 01:25:48 -0800 (PST) (envelope-from laskavy@Hedgehog.Moscow.Ru) Received: from Hedgehog.Moscow.Ru (hedgehog [158.250.10.225]) by ns.cs.msu.su (8.8.6/8.6.12) with ESMTP id MAA03101 for ; Sun, 16 Nov 1997 12:26:13 +0300 (MSK) Received: (from laskavy@localhost) by Hedgehog.Moscow.Ru (8.8.8/8.8.8) id LAA00823 for freebsd-hackers@FreeBSD.ORG; Sun, 16 Nov 1997 11:31:30 +0300 (MSK) (envelope-from laskavy) Date: Sun, 16 Nov 1997 11:31:30 +0300 (MSK) From: "Sergei S. Laskavy" Message-Id: <199711160831.LAA00823@Hedgehog.Moscow.Ru> To: freebsd-hackers@FreeBSD.ORG Subject: src/games/hack/Makefile: mode 666 (?) for files in /var/games Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dear (net) hackers! I wonder if there is a reason for having mode rw-rw-rw- files in /var/games/hackdir. And... do we have a /var/games/hackdir by default? { I'm running 2.2.5-STABLE (sources as of 12 of November), but I'm not sure if I did upgrade from 2.2.2-RELEASE right. But I saw the "666" in hack's Makefile, and can't find "save" in /etc/mtree/* I was able to start game, then save or quit with this permissions: drwx------ 2 games bin 512 Nov 16 11:27 save ---------- 1 games bin 0 Nov 11 22:10 perm -rw-r--r-- 1 games bin 166 Nov 16 11:29 record -r--r--r-- 1 games bin 25080 Nov 11 22:10 rumors } Sincerely, Sergei Laskavy From owner-freebsd-hackers Sun Nov 16 01:41:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA04104 for hackers-outgoing; Sun, 16 Nov 1997 01:41:52 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA04093 for ; Sun, 16 Nov 1997 01:41:49 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA13671; Sun, 16 Nov 1997 01:44:55 -0800 (PST) Message-Id: <199711160944.BAA13671@implode.root.com> To: "David E. Cross" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 'Official' Intel Fix In-reply-to: Your message of "Sun, 16 Nov 1997 03:46:00 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Nov 1997 01:44:55 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Well, I have seen the 'official' intel fix... it is the one to move the >IDT over a page boundry. As has been said before, it is a nasty hairy >kludge. > >Q: Does our fix 'work'.. in the SIGBUS code can we acurately determine if >it was really SIGILL and return it? (what I am asking is why Intel picked >that evil workaround) Yes, I've found a way to distiguish the illegal instruction and generate the proper SIGILL in all the cases that matter. I'm having trouble with the fix working reliably, however, so we may end up doing the Intel fix afterall. It is too early to tell. >Q2: Considering that Intel's 'official' fix can result in a fair >performance hit, any word on if they will be doing a recall? I haven't heard anything from Intel other than they intend to have the bug fixed in a future stepping of the part. If I were calling the shots at AMD, I'd issue rebate coupons for people upgrading their broken Pentiums. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Nov 16 01:49:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05074 for hackers-outgoing; Sun, 16 Nov 1997 01:49:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05022 for ; Sun, 16 Nov 1997 01:49:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id KAA13268 for ; Sun, 16 Nov 1997 10:48:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org Subject: Twice as many OS/2 as FreeBSD ??? From: Poul-Henning Kamp Date: Sun, 16 Nov 1997 10:48:08 +0100 Message-ID: <13266.879673688@critter.freebsd.dk> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If you think this is embarrasing for FreeBSD: http://rc5stats.distributed.net/oslist.html How about joining "Team FreeBSD" and improving the number ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hackers Sun Nov 16 02:12:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA07982 for hackers-outgoing; Sun, 16 Nov 1997 02:12:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA07976 for ; Sun, 16 Nov 1997 02:12:40 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.7.3) id LAA11576; Sun, 16 Nov 1997 11:13:03 +0100 (MET) Message-Id: <199711161013.LAA11576@sos.freebsd.dk> Subject: Re: VESA VBE 1.2 and 2.0 library In-Reply-To: <19971116004713.06932@micron.mini.net> from Jonathan Mini at "Nov 16, 97 00:47:13 am" To: mini@d198-232.uoregon.edu (Jonathan Mini) Date: Sun, 16 Nov 1997 11:13:03 +0100 (MET) Cc: sos@FreeBSD.dk, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jonathan Mini who wrote: > Søren Schmidt stands accused of saying: > > In reply to Jonathan Mini who wrote: > > > > Sounds VERY interesting! > > I'll help out testing and what else I'm able to do... > > Cool. I will probably be asking you a few questions abotu how syscons > functions.. OK, I'll be here... > > You have commit privs right?, just grap yourself the next free dev #... > > :) Nope. OK, you now have char Major #85 for the VESA device... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Nov 16 02:20:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA08487 for hackers-outgoing; Sun, 16 Nov 1997 02:20:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA08482 for ; Sun, 16 Nov 1997 02:20:15 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id CAA19285; Sun, 16 Nov 1997 02:20:01 -0800 (PST) Message-ID: <19971116022000.64032@micron.mini.net> Date: Sun, 16 Nov 1997 02:20:00 -0800 From: Jonathan Mini To: sos@FreeBSD.dk Cc: hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library References: <19971116004713.06932@micron.mini.net> <199711161013.LAA11576@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.85e In-Reply-To: =?iso-8859-1?Q?=3C199711161013=2ELAA11576=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Sun=2C_Nov_16=2C_1997_at_11=3A13=3A0?= =?iso-8859-1?Q?3AM_+0100?= X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt stands accused of saying: > > > > You have commit privs right?, just grap yourself the next free dev #... > > > > :) Nope. > > OK, you now have char Major #85 for the VESA device... Excellent... As I write this, my hard drives are clattering with the commit to my local kernel tree with the change to that major. -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Sun Nov 16 02:32:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09486 for hackers-outgoing; Sun, 16 Nov 1997 02:32:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09480 for ; Sun, 16 Nov 1997 02:32:23 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id LAA19633; Sun, 16 Nov 1997 11:15:10 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id KAA01509; Sun, 16 Nov 1997 10:43:49 +0100 (CET) (envelope-from andreas) Message-ID: <19971116104348.02246@klemm.gtn.com> Date: Sun, 16 Nov 1997 10:43:48 +0100 From: Andreas Klemm To: Alex Nash Cc: hackers@FreeBSD.ORG Subject: Re: kernel options for turning off source routing and ip accounting ? References: <19971115231043.02073@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Alex Nash on Sat, Nov 15, 1997 at 08:09:55PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Nov 15, 1997 at 08:09:55PM -0600, Alex Nash wrote: > On Sat, 15 Nov 1997, Andreas Klemm wrote: > > > Just read an article about Linux as firewall system and noticed > > the ability to turn off source routing and turn on ip accounting. > > > > http://www.linux-magazin.de/ > > > > Do we also have such options ? > > Source routing: sysctl net.inet.ip.sourceroute Ah, fine, should have browsed this file earlier ;-) > Accounting: man ipfw Ok, thanks ! > I'll give you one guess as to where the original firewall code in > Linux comes from :) ;-) -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' From owner-freebsd-hackers Sun Nov 16 02:41:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09955 for hackers-outgoing; Sun, 16 Nov 1997 02:41:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bubble.didi.com (sjx-ca115-54.ix.netcom.com [207.223.162.118]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09943; Sun, 16 Nov 1997 02:41:50 -0800 (PST) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.7) id CAA01059; Sun, 16 Nov 1997 02:41:41 -0800 (PST) (envelope-from asami) Date: Sun, 16 Nov 1997 02:41:41 -0800 (PST) Message-Id: <199711161041.CAA01059@bubble.didi.com> To: gibbs@plutotech.com CC: hbarker@rhiannon.sm.dsms.com, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG, aic7xxx@FreeBSD.ORG In-reply-to: <199711160511.WAA24691@pluto.plutotech.com> (gibbs@plutotech.com) Subject: Re: AHC / SCSI UPDATE From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Justin: * Sorry for not responding sooner, but I don't read this list regularly * anymore... Which list you are talking about? (I hope that's not scsi! :) * Remeber that it's not really the type of device that matters, but the * possibility of starvation. If you have lots of concurrent I/O going on * to multiple disks on a single chain, you can still experience this problem * (Hi Satoshi!). Yeah, we've seen it too. Lots of IBM DCHS drives on a couple of chains, lots of random I/O, and sooner or later we'll get the "timed out while idle" on one of the drives. (And then that drive spins down, which has been a headache for us for quite a while...however, recently Justin & co. have given us patches to fix this and we're testing it now.) Satoshi From owner-freebsd-hackers Sun Nov 16 02:49:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10429 for hackers-outgoing; Sun, 16 Nov 1997 02:49:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cbu.pvtnet.cz (cbu.pvtnet.cz [194.149.105.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10419 for ; Sun, 16 Nov 1997 02:49:15 -0800 (PST) (envelope-from x8068@pha.pvtnet.cz) Received: from pha.pvtnet.cz (phaD009.pvt.net [194.149.98.9]) by cbu.pvtnet.cz (8.8.5/8.7.3) with ESMTP id LAA07390 for ; Sun, 16 Nov 1997 11:56:49 +0100 (MET) Message-ID: <346ECF3D.B9CBE602@pha.pvtnet.cz> Date: Sun, 16 Nov 1997 11:47:25 +0100 From: "Ondøej Poøádek" X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-hackers Sun Nov 16 04:10:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA14302 for hackers-outgoing; Sun, 16 Nov 1997 04:10:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from jkh.cdrom.com (jkh.cdrom.com [204.216.27.61]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA14260 for ; Sun, 16 Nov 1997 04:09:57 -0800 (PST) (envelope-from jkh@jkh.cdrom.com) Received: from jkh.cdrom.com (localhost.cdrom.com [127.0.0.1]) by jkh.cdrom.com (8.8.6/8.8.5) with ESMTP id EAA05648; Sun, 16 Nov 1997 04:09:37 -0800 (PST) Message-Id: <199711161209.EAA05648@jkh.cdrom.com> To: Jonathan Mini cc: sos@FreeBSD.dk, hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library In-reply-to: Your message of "Sun, 16 Nov 1997 02:20:00 PST." <19971116022000.64032@micron.mini.net> Reply-to: jkh@FreeBSD.ORG Date: Sun, 16 Nov 1997 04:09:37 -0800 From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk By the way, do you *want* commit privileges? I think it could be easily arranged. And greetings from Comdex, everyone. Gawd, I don't want to see what my calling card bill is going to look like when I get back - I'm calling back home to California from my hotel room in order to send this email. :-) Jordan From owner-freebsd-hackers Sun Nov 16 04:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA14865 for hackers-outgoing; Sun, 16 Nov 1997 04:21:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA14855; Sun, 16 Nov 1997 04:21:08 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id EAA19492; Sun, 16 Nov 1997 04:21:04 -0800 (PST) Message-ID: <19971116042103.28008@micron.mini.net> Date: Sun, 16 Nov 1997 04:21:04 -0800 From: Jonathan Mini To: jkh@FreeBSD.ORG Cc: sos@FreeBSD.dk, hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library References: <19971116022000.64032@micron.mini.net> <199711161209.EAA05648@jkh.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199711161209.EAA05648@jkh.cdrom.com>; from Jordan K. Hubbard on Sun, Nov 16, 1997 at 04:09:37AM -0800 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > By the way, do you *want* commit privileges? I think it > could be easily arranged. Commit privileges would be helpful, although not a requirement by any means. It really depends on how you want me to contribute my work. (Aside from the fact that it would be cool to have commit privleges) > And greetings from Comdex, everyone. Gawd, I don't want to see what > my calling card bill is going to look like when I get back - I'm > calling back home to California from my hotel room in order to send > this email. :-) I know the feeling. ;) > Jordan -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Sun Nov 16 05:33:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21249 for hackers-outgoing; Sun, 16 Nov 1997 05:33:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21242 for ; Sun, 16 Nov 1997 05:33:39 -0800 (PST) (envelope-from rjs@fdy2.demon.co.uk) Received: from fdy2.demon.co.uk ([194.222.102.143]) by post.mail.demon.net id aa2004522; 16 Nov 97 13:33 GMT Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.7/8.6.12) id NAA00432; Sun, 16 Nov 1997 13:34:32 GMT Date: Sun, 16 Nov 1997 13:34:32 GMT From: Robert Swindells Message-Id: <199711161334.NAA00432@fdy2.demon.co.uk> To: hackers@freebsd.org Subject: Netscape 4.04 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FYI - Netscape 4.04 for FreeBSD is out. The path is: ftp://ftp.netscape.com/pub/communicator/4.04/development/english/unix/freebsd It isn't listed as a version that they will accept payment for though. Robert Swindells ------------------------------------- Robert Swindells - GenRad Ltd rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home From owner-freebsd-hackers Sun Nov 16 05:43:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21721 for hackers-outgoing; Sun, 16 Nov 1997 05:43:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA21716 for ; Sun, 16 Nov 1997 05:43:28 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id OAA20092 for hackers@FreeBSD.ORG; Sun, 16 Nov 1997 14:43:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id OAA06381; Sun, 16 Nov 1997 14:36:03 +0100 (CET) (envelope-from roberto) Message-ID: <19971116143603.29098@keltia.freenix.fr> Date: Sun, 16 Nov 1997 14:36:03 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: mkmodules? References: <9216.879649089@mumps.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <9216.879649089@mumps.pfcs.com>; from Harlan Stenn on Sat, Nov 15, 1997 at 09:58:09PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3818 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Harlan Stenn: > What happened to the mkmodules program? It doesn't seem to be build > anymore (at least in -stable), and I'd like to be using CVS for other > things. You don't need it anymore, it is handled directly inside CVS (provide that you have a recent version of CVS). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #49: Sat Nov 15 20:03:33 CET 1997 From owner-freebsd-hackers Sun Nov 16 06:26:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA23530 for hackers-outgoing; Sun, 16 Nov 1997 06:26:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA23514; Sun, 16 Nov 1997 06:26:35 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id OAA27333; Sun, 16 Nov 1997 14:15:48 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711161415.OAA27333@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jonathan M. Bresler" cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@freebsd.org Subject: Re: /etc/mail filters in 2.2.5 In-reply-to: Your message of "Sat, 15 Nov 1997 20:09:52 PST." <199711160409.UAA15831@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Nov 1997 14:15:48 +0000 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Brian, > there are a couple issues here: > > Brian Somers wrote: > > I installed the /etc/mail stuff a few days ago, and added a few sites > > to domains.txt, specifically: > > > > BIGFOOT.DALTEK.NET^M #blocked. contact postmaster > > first, that "^M" is it in the file? > is so please delete it. > after deleting the "^M" > cd /etc/mail; make install Hmm, the domains.txt I got with the ``make'' had 'em in, so I figured they were meant to be :-I > second, the way i wrote the rules, they block mail > from a domain, hence the file is called domains.txt ;) > bigfoot.daltek.net is a host, rather than a domain. > you can change the entry domains.txt to "daltek.net". > that will block mail from all of daltek.net. or you can > use the amended rules below to block mail from both > hosts and domains. then you can use entries like > "bigfoot.daltek.net" in domains.txt. > > add the rules below that are *not* preceded by a ">" > at the start of the line ;) Ok, done - thanks. I'll keep an eye on things. > jmb It also looks like my FEATURE(`nocanonify') dodges all these rules anyway, so I've lost that. Mike Burgett pointed me at an interesting site: http://www.informatik.uni-kiel.de/%7Eca/email/check.html and suggests HACK(`use_ip', `/etc/LocalIP')dnl HACK(`use_relayto', `/etc/RelayTo')dnl HACK(`check_mail2', `hash /etc/Banned.db')dnl HACK(`check_relay')dnl HACK(`check_rcpt4')dnl as a cleaner solution. I'm only half-quoting, so forgive me if I'm missing something relevent. I'm really gonna have to figure out how all this works at some point (Yep, O'Reilly & Assoc. is the best read I suspect, but does it cover all the m4 stuff ?). -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Nov 16 06:46:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA24597 for hackers-outgoing; Sun, 16 Nov 1997 06:46:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: (from jmb@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA24588; Sun, 16 Nov 1997 06:46:04 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199711161446.GAA24588@hub.freebsd.org> Subject: Re: /etc/mail filters in 2.2.5 To: brian@awfulhak.org (Brian Somers) Date: Sun, 16 Nov 1997 06:46:03 -0800 (PST) Cc: jmb@freebsd.org, brian@awfulhak.org, freebsd-hackers@freebsd.org In-Reply-To: <199711161415.OAA27333@awfulhak.demon.co.uk> from "Brian Somers" at Nov 16, 97 02:15:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Somers wrote: > > > Brian, > > there are a couple issues here: > > > > Brian Somers wrote: > > > I installed the /etc/mail stuff a few days ago, and added a few sites > > > to domains.txt, specifically: > > > > > > BIGFOOT.DALTEK.NET^M #blocked. contact postmaster > > > > first, that "^M" is it in the file? > > is so please delete it. > > after deleting the "^M" > > cd /etc/mail; make install > > Hmm, the domains.txt I got with the ``make'' had 'em in, so I figured > they were meant to be :-I ahh.....did you use DOS! "^M" is teh DOS extra end-of-line character. DOS uses both and to indicate and end-of-line. Unix uses only one, the Mac uses the other. > > > second, the way i wrote the rules, they block mail > > from a domain, hence the file is called domains.txt ;) > > bigfoot.daltek.net is a host, rather than a domain. > > you can change the entry domains.txt to "daltek.net". > > that will block mail from all of daltek.net. or you can > > use the amended rules below to block mail from both > > hosts and domains. then you can use entries like > > "bigfoot.daltek.net" in domains.txt. > > > > add the rules below that are *not* preceded by a ">" > > at the start of the line ;) > > Ok, done - thanks. I'll keep an eye on things. cool....let me know if there are any problems. > > > jmb > > It also looks like my FEATURE(`nocanonify') dodges all these rules > anyway, so I've lost that. Mike Burgett pointed me at an interesting > site: > > http://www.informatik.uni-kiel.de/%7Eca/email/check.html > > and suggests > > HACK(`use_ip', `/etc/LocalIP')dnl > HACK(`use_relayto', `/etc/RelayTo')dnl > HACK(`check_mail2', `hash /etc/Banned.db')dnl > HACK(`check_relay')dnl > HACK(`check_rcpt4')dnl there are a number of ways to skin this cat. ohhh...sorry, jordan. i chose not to use HACK's or m4 macros so that whatever eric allman decides upon will not create a name conflict. (peter weem asked me about this too ;) > > as a cleaner solution. I'm only half-quoting, so forgive me if I'm > missing something relevent. I'm really gonna have to figure out how > all this works at some point (Yep, O'Reilly & Assoc. is the best read > I suspect, but does it cover all the m4 stuff ?). m4 is just a preprocessor, but be carefull it expanes keywords in comment lines as well ;* be sure to get the second edition of sendmail from O'Reilly & Assoc its their biggest book, enjoy! ;) jmb From owner-freebsd-hackers Sun Nov 16 09:12:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA00764 for hackers-outgoing; Sun, 16 Nov 1997 09:12:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA00758 for ; Sun, 16 Nov 1997 09:12:20 -0800 (PST) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id JAA00808; Sun, 16 Nov 1997 09:11:58 -0800 (PST) Date: Sun, 16 Nov 1997 09:11:58 -0800 (PST) From: "Eric J. Schwertfeger" To: Robert Swindells cc: hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 In-Reply-To: <199711161334.NAA00432@fdy2.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Robert Swindells wrote: > FYI - Netscape 4.04 for FreeBSD is out. Does anyone know if netscape is planning on releasing a version with 128 bit security? I've been watching their site daily, and haven't found anything yet. From owner-freebsd-hackers Sun Nov 16 09:37:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01936 for hackers-outgoing; Sun, 16 Nov 1997 09:37:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01931 for ; Sun, 16 Nov 1997 09:37:16 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id MAA00298; Sun, 16 Nov 1997 12:37:15 -0500 (EST) (envelope-from henrich) Date: Sun, 16 Nov 1997 12:37:15 -0500 (EST) From: Charles Henrich Message-Id: <199711161737.MAA00298@crh.cl.msu.edu> To: ejs@bfd.com, freebsd-hackers@freebsd.org Subject: Re: Netscape 4.04 Newsgroups: lists.freebsd.hackers References: <64nakm$89d$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >On Sun, 16 Nov 1997, Robert Swindells wrote: >> FYI - Netscape 4.04 for FreeBSD is out. >Does anyone know if netscape is planning on releasing a version with 128 >bit security? I've been watching their site daily, and haven't found >anything yet. They finally did for Linux, so I've been using that (successfully) under emulation. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sun Nov 16 09:46:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA02365 for hackers-outgoing; Sun, 16 Nov 1997 09:46:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA02355 for ; Sun, 16 Nov 1997 09:46:49 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id JAA01021; Sun, 16 Nov 1997 09:46:23 -0800 (PST) Date: Sun, 16 Nov 1997 09:46:23 -0800 (PST) From: "Jamil J. Weatherbee" To: "Eric J. Schwertfeger" cc: Robert Swindells , hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Do you just want 128 bit encryption on freebsd netscape, or do you want 128 bit encryption on freebsd netscape 4.04? On Sun, 16 Nov 1997, Eric J. Schwertfeger wrote: > > > On Sun, 16 Nov 1997, Robert Swindells wrote: > > > FYI - Netscape 4.04 for FreeBSD is out. > > Does anyone know if netscape is planning on releasing a version with 128 > bit security? I've been watching their site daily, and haven't found > anything yet. > > From owner-freebsd-hackers Sun Nov 16 09:51:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA02660 for hackers-outgoing; Sun, 16 Nov 1997 09:51:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA02624; Sun, 16 Nov 1997 09:51:21 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from eistla.ifi.uio.no (eistla.ifi.uio.no [129.240.65.62]) by ifi.uio.no (8.8.7/8.8.7/ifi0.2) with ESMTP id SAA22025; Sun, 16 Nov 1997 18:51:15 +0100 (MET) Received: (from dag-erli@localhost) by eistla.ifi.uio.no ; Sun, 16 Nov 1997 18:51:14 +0100 (MET) To: "Justin T. Gibbs" Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG, aic7xxx@FreeBSD.ORG Subject: Re: AHC / SCSI UPDATE References: <199711160511.WAA24691@pluto.plutotech.com> Organization: FMKY X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 16 Nov 1997 18:51:13 +0100 In-Reply-To: "Justin T. Gibbs"'s message of Sat, 15 Nov 1997 22:10:52 -0700 Message-ID: Lines: 46 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Justin T. Gibbs" writes: > Here's a little info about what we (Ken Merry and myself) have determined > about the problem so far. > > System: > P6-233 256k cache > 2940UW (SCSI ID 7) > 1 X PLEXTOR CD-ROM PX-4XCS 1.04 (SCSI ID 4) > 2 X QUANTUM XP34550W LXY4 (SCSI IDs 0 and 1) > > How to repeat: > run concurrent I/O to all 3 devices at the same time. > > Symptom: > After a varying period of time, disk 0 or 1 stops performing > reselections for it's outstanding I/O. This eventually results > in a timeout, usually with the controller in an "idle" state. If you're ever bored :) you might want to chew on this one: System: P5-150, 512 kB L2 cache, 128 MB EDO RAM, FreeBSD 2.2.1R 2940UW (SCSI ID 7) - TOSHIBA 5701TA (SCSI ID 4) - QUANTUM XP34550W (SCSI ID 1) - CONNER CFP1080S (SCSI ID 0) 2940 (SCSI ID 7) - OLYMPUS MOS330 (SCSI ID 6) How to repeat: run concurrent I/O to XP34450W and MOS330 at the same time. Symptom: With heavy disk activity on both the OD and the harddisk, random lockups occur. Just copying data from OD to harddisk to (or the reverse) works fine, but the machine freezes solid after a while if you put more load on the harddisk. Similar symptoms with all units connected to 2940. Similar symptoms with 5701TA and/or CFP1080S absent from system. If you want more details, mail me :) -- * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no * cellular +47-92835919 * RFC1123: "Be liberal in what you accept, and conservative in what you send" From owner-freebsd-hackers Sun Nov 16 09:53:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA02800 for hackers-outgoing; Sun, 16 Nov 1997 09:53:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA02789 for ; Sun, 16 Nov 1997 09:53:24 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id MAA23714; Sun, 16 Nov 1997 12:53:21 -0500 (EST) Date: Sun, 16 Nov 1997 12:53:21 -0500 (EST) Message-Id: <199711161753.MAA23714@dyson.iquest.net> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 From: root@dyson.iquest.net (John S. Dyson) Subject: Better F00F workaround (well, maybe...) (fwd) To: hackers@freebsd.org Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is this a good idea? Path: szdc!super.zippo.com!lotsanews.com!news-feed.inet.tele.dk!bofh.vszbr.cz!news.maxwell.syr.edu!news-was.dfn.de!news-kar1.dfn.de!news-fra1.dfn.de!news-ber1.dfn.de!zrz.TU-Berlin.DE!news.tu-chemnitz.de!not-for-mail From: Michael Tippach Newsgroups: comp.sys.intel Subject: Better F00F workaround (well, maybe...) Date: Sun, 16 Nov 1997 17:30:19 +0100 Organization: University of Technology Chemnitz, FRG Lines: 26 Message-ID: <346F1F9B.1E53@geocities.com> NNTP-Posting-Host: tiwu.csn.tu-chemnitz.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01 (WinNT; I) Xref: szdc comp.sys.intel:72500 Hi all! Anyone else willing to confirm that (at least with paging enabled) the #UD WILL be triggered if (and _only_ if) the idt lookup causes a TLB miss? Seems to be the sole condition for making "it" happen or not. Consructing a simple system where the handlers for exceptions 0..6 (alignment as in the Intel workaround) just do an invlpg [first_idt_page] enabled me to reliably trap any mutation of the f00fc7c8 (There are more than 8 possible mutations BTW since you can add prefixes in addition to the LOCK without changing anything to the matter.) The OS still would have to make sure the invlpg is done after _any_ access to the page in question, which shouldn't be too hard either. Just in case I'm right, wouldn't this provide a better workaround compared with the page fault mess in Intel's fix description? Best regards Michael Tippach From owner-freebsd-hackers Sun Nov 16 10:07:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03393 for hackers-outgoing; Sun, 16 Nov 1997 10:07:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03388 for ; Sun, 16 Nov 1997 10:07:26 -0800 (PST) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id KAA00925; Sun, 16 Nov 1997 10:07:15 -0800 (PST) Date: Sun, 16 Nov 1997 10:07:14 -0800 (PST) From: "Eric J. Schwertfeger" To: "Jamil J. Weatherbee" cc: Robert Swindells , hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Jamil J. Weatherbee wrote: > > Do you just want 128 bit encryption on freebsd netscape, or do you want > 128 bit encryption on freebsd netscape 4.04? I've got 128 bit 3.0X, and I need the 128 bit for online banking, but I'm using 4.0 at work, and I'd like to standardize. From owner-freebsd-hackers Sun Nov 16 10:10:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03567 for hackers-outgoing; Sun, 16 Nov 1997 10:10:10 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03536; Sun, 16 Nov 1997 10:10:04 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA20189; Sun, 16 Nov 1997 11:10:00 -0700 (MST) Message-Id: <199711161810.LAA20189@pluto.plutotech.com> To: dag-erli@ifi.uio.no (Dag-Erling Coidan Sm rgrav) cc: "Justin T. Gibbs" , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG, aic7xxx@FreeBSD.ORG Subject: Re: AHC / SCSI UPDATE In-reply-to: Your message of "16 Nov 1997 18:51:13 +0100." Date: Sun, 16 Nov 1997 11:08:52 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >If you're ever bored :) you might want to chew on this one: This one is probably caused by the Atlas reporting "QUEUE FULL" randomly combined with a known problem in the SCSI code in current with dealing with that condition. If you OD uses 512 byte sectors, it can probably be made to work with the CAM SCSI snapshots I've put up on ftp.cdrom.com so you can test this hypothesis out. CAM doesn't have a problem with QUEUE FULL conditions. -- Justin From owner-freebsd-hackers Sun Nov 16 10:13:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03792 for hackers-outgoing; Sun, 16 Nov 1997 10:13:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03784 for ; Sun, 16 Nov 1997 10:13:25 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id NAA05982; Sun, 16 Nov 1997 13:12:55 -0500 (EST) Date: Sun, 16 Nov 1997 13:12:54 -0500 (EST) From: John Fieber To: "Eric J. Schwertfeger" cc: Robert Swindells , hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Eric J. Schwertfeger wrote: > On Sun, 16 Nov 1997, Robert Swindells wrote: > > > FYI - Netscape 4.04 for FreeBSD is out. > > Does anyone know if netscape is planning on releasing a version with 128 > bit security? I've been watching their site daily, and haven't found > anything yet. Has anyone else had problems with it? As with 4.03b8, I occasionally had problems with it hanging on exit. I thought I would make sure there wasn't anything around from older versions causing problems so I moved my ~/.netscape directory out of the way. It starts up, creates its ~/.netscape directory and works fine. But after exiting the first time, it hangs on the next startup before opening a window and soaks up all free CPU time. A ktrace shows it looping with this: 5938 communicator-4.0^A CALL gettimeofday(0xefbfa3ec,0) 5938 communicator-4.0^A RET gettimeofday 0 5938 communicator-4.0^A CALL sigreturn(0xefbfa4b4) 5938 communicator-4.0^A RET sigreturn JUSTRETURN 5938 communicator-4.0^A PSIG SIGALRM caught handler=0x76cdf8 mask=0x0 code=0x The only way to get rid of it is kill -9. This is on a 2.2.5-RELEASE system. Aside from occasionally hanging up on exit, it workd with my age-old .netscape directory full of cruft from the whole 3.x series and various 3.x betas....go figure. -john From owner-freebsd-hackers Sun Nov 16 10:28:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04641 for hackers-outgoing; Sun, 16 Nov 1997 10:28:36 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zippy.dyn.ml.org (pm3-ppp22.well.com [206.15.85.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04635; Sun, 16 Nov 1997 10:28:32 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id KAA00692; Sun, 16 Nov 1997 10:29:16 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 16 Nov 1997 10:29:16 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Poul-Henning Kamp cc: hackers@FreeBSD.ORG Subject: Re: Twice as many OS/2 as FreeBSD ??? In-Reply-To: <13266.879673688@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Poul-Henning Kamp wrote: > > If you think this is embarrasing for FreeBSD: > > http://rc5stats.distributed.net/oslist.html > > How about joining "Team FreeBSD" and improving the number ? Or how bout making your own team, so you could collect the whole prize if you win? ;-) We've completed more blocks than Open or NetBSD however. - alex From owner-freebsd-hackers Sun Nov 16 10:31:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04814 for hackers-outgoing; Sun, 16 Nov 1997 10:31:01 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04809 for ; Sun, 16 Nov 1997 10:30:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA14150; Sun, 16 Nov 1997 19:29:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alex cc: hackers@FreeBSD.ORG Subject: Re: Twice as many OS/2 as FreeBSD ??? In-reply-to: Your message of "Sun, 16 Nov 1997 10:29:16 PST." Date: Sun, 16 Nov 1997 19:29:29 +0100 Message-ID: <14148.879704969@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Alex writ es: > > >On Sun, 16 Nov 1997, Poul-Henning Kamp wrote: > >> >> If you think this is embarrasing for FreeBSD: >> >> http://rc5stats.distributed.net/oslist.html >> >> How about joining "Team FreeBSD" and improving the number ? > >Or how bout making your own team, so you could collect the whole prize if >you win? ;-) We've completed more blocks than Open or NetBSD however. One team is plenty. I'm not in it for the money... Open & Net BSD are not competition, but that OS/2 should be above us is more than I can accept... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hackers Sun Nov 16 11:16:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07903 for hackers-outgoing; Sun, 16 Nov 1997 11:16:11 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07896 for ; Sun, 16 Nov 1997 11:16:06 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (max7-206.HiWAAY.net [208.147.145.206]) by fly.HiWAAY.net (8.8.7/8.8.6) with ESMTP id NAA26984; Sun, 16 Nov 1997 13:16:03 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id MAA03605; Sun, 16 Nov 1997 12:42:35 -0600 (CST) Message-Id: <199711161842.MAA03605@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: freebsd-hackers@FreeBSD.ORG From: David Kelly Subject: Re: AIOX Analog driver statistical analysis In-reply-to: Message from "Jamil J. Weatherbee" of "Sat, 15 Nov 1997 21:51:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Nov 1997 12:42:35 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I wonder just how much faster a PPro or Pentium is then a NexGen machine > (this is in purely integer performance since I am not doing any > calculations in the user process). I had a NexGen P90 prior to this PPro-166. The NexGen crunched the Bovine RC5-56 client at about 90k keys/sec. This PPro-166/512k is currently doing 420k. But a couple of days ago I upgraded to the 11/11/97 Bovine client and got several days of 460k keys/sec until I got the great idea to update my late October 2.2.5 kernel. Am back to 420k keys/sec. Don't know what it was, the old kernel doesn't run faster any more. Possibly I got the caches loaded just right or something? Maybe I hit a series of easy to crunch keys? The NexGen did "build world" in the 7 to 9 hour range. Moving the exact same memory, HD, 2940, video card, case and PS to the PPro yeilds 2:45 with sync mount, 2:15 async. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Sun Nov 16 11:16:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07949 for hackers-outgoing; Sun, 16 Nov 1997 11:16:43 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07935 for ; Sun, 16 Nov 1997 11:16:39 -0800 (PST) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.8.7/8.8.6) id OAA13572 for freebsd-hackers@FreeBSD.ORG; Sun, 16 Nov 1997 14:16:37 -0500 (EST) Date: Sun, 16 Nov 1997 14:16:37 -0500 (EST) From: "Stephen J. Roznowski" Message-Id: <199711161916.OAA13572@istari.home.net> To: freebsd-hackers@FreeBSD.ORG Subject: Diagnosing Intel EtherExpress Pro/10+ problem Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm been having a reoccuring problem with an Intel EtherExpress Pro/10+ Ethernet card. When I reboot into FreeBSD from Windows 95, occasionally the card won't come back in a working state. Rebooting multiple times will cause the card to eventually work. [This is on an 18 October kernel, but has occurred on earlier kernels as well.] Each time, the card seems to be recognized correctly during the probe, but when I try to (for example) ping a remote address, I get a "no route to host" message [not sure of exact wording]. If I configure the interface down, then back up, I get a "could not allocate llinfo" error. My question is, how can I go about diagnosing (and fixing :-) this problem? Thanks, -SR From owner-freebsd-hackers Sun Nov 16 11:49:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10053 for hackers-outgoing; Sun, 16 Nov 1997 11:49:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10041 for ; Sun, 16 Nov 1997 11:49:14 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id OAA06919 for ; Sun, 16 Nov 1997 14:49:11 -0500 (EST) Date: Sun, 16 Nov 1997 14:49:11 -0500 (EST) From: John Fieber To: hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, John Fieber wrote: > > On Sun, 16 Nov 1997, Robert Swindells wrote: > > > > > FYI - Netscape 4.04 for FreeBSD is out. > > Has anyone else had problems with it? As with 4.03b8, I > occasionally had problems with it hanging on exit. I thought I > It starts up, creates its ~/.netscape directory and works fine. > But after exiting the first time, it hangs on the next startup > before opening a window and soaks up all free CPU time. A ktrace > Aside from occasionally hanging up on exit, it workd with my > age-old .netscape directory full of cruft from the whole 3.x > series and various 3.x betas....go figure. Slight revision: it usually hangs on startup with my old config files too. I just didn't have 4.04 long enough to really notice the pattern. -john From owner-freebsd-hackers Sun Nov 16 11:58:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10700 for hackers-outgoing; Sun, 16 Nov 1997 11:58:12 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10692 for ; Sun, 16 Nov 1997 11:58:06 -0800 (PST) (envelope-from mark@quickweb.com) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id OAA23748; Sun, 16 Nov 1997 14:59:10 -0500 (EST) Message-ID: <19971116145910.31953@vmunix.com> Date: Sun, 16 Nov 1997 14:59:10 -0500 From: Mark Mayo To: dg@root.com Cc: hackers@FreeBSD.ORG Subject: Re: de underflow errors. huh? References: <19971116001710.02627@vmunix.com> <199711160845.AAA13089@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199711160845.AAA13089@implode.root.com>; from David Greenman on Sun, Nov 16, 1997 at 12:45:44AM -0800 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Nov 16, 1997 at 12:45:44AM -0800, David Greenman wrote: > > >de0: abnormal interrupt: transmit underflow > > > >I have no clue what this means. Packets seem to be flowing through > >the interface nicely, and there is no noticeable packet loss. > >If anyone has any ideas what could be causing this, or if I should > >give a hoot, please let me know. > > It's indicating that the PCI bus was sufficiently busy enough to cause > the transmit DMA to be stalled too long. The proper response to this condition > in the device driver it to dynamically increase the transmit threshold (the > number of bytes that are DMA'ed onto the card before the transmission is > actually started on the wire). The fxp driver does this, the de driver > doesn't. I think Matt Thomas might have fixed this in a later rev., but I'm > not sure about that. > Anyway, other than the annoying console messages and perhaps a packet > drop when it happens, the problem can be ignored. Do you think increasing the bus speed will make a difference? This machine is a P54C 150 - I originally wanted to run it at 75MHz * 2, but the dealer gave me one of the aftermarket Intel CPUs with the integrated heat sink, and the machine just plain won't make it past the memory check when I run the bus at 75... I've done this (75*2) setup on several other machines with no problems - but they had the OEM'ed version of the CPU with no heatsink, and a grey bottom. I'm guessing that this black bottomed jobby is preventing itself from being "overclocked" somehow. I may try and get a replacement CPU.. But before I do that do you think the jump from 60MHz to 75MHz will help the de card? Or is the 100Mb fxp simply delivering data too quickly for it to handle. Perhaps replacing the de with a fxp... I realize it's not really an error, but it bugs me for some reason. Plus it doesn't inspire confidence in the client when they look at their firewall machine and see abnormal interupt errors :-) Maybe I'll just change the error in the if_devar.h (I think that's what it's called..) to "Self integrity security pass completed successfully.". :-) TIA, -Mark > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hackers Sun Nov 16 12:21:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12038 for hackers-outgoing; Sun, 16 Nov 1997 12:21:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA12031 for ; Sun, 16 Nov 1997 12:20:57 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25050; Sun, 16 Nov 1997 21:20:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id VAA16116; Sun, 16 Nov 1997 21:08:28 +0100 (MET) Message-ID: <19971116210828.OU36167@uriah.heep.sax.de> Date: Sun, 16 Nov 1997 21:08:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: lgomez@guacari.udem.edu.co (=?iso-8859-1?Q?Lucas_Adri=A0n_G=A2mez_Bland=A2n?=) Subject: Re: Problems with passwd utility. References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: =?iso-8859-1?Q?=3CPine=2EBSF=2E3=2E96=2E971111093602=2E5773A-100000=40gu?= =?iso-8859-1?Q?acari=2Eudem=2Eedu=2Eco=3E=3B_from_Lucas_Adri=A0n_G=A2mez?= =?iso-8859-1?Q?_Bland=A2n_on_Nov_11=2C_1997_09=3A38=3A48_-0500?= Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Lucas Adri n G¢mez Bland¢n wrote: > Hi everyone, I'm install FreeBSD 2.1.7.1 (STABLE), it was a piece of > cake!, but when a user call "passwd" he receive "Permision denied". That most likely means you're attempting to change the password for someone else than yourself (e.g. since you're "su"ed to another user). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Nov 16 12:21:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12082 for hackers-outgoing; Sun, 16 Nov 1997 12:21:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA12071 for ; Sun, 16 Nov 1997 12:21:15 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25053 for hackers@FreeBSD.ORG; Sun, 16 Nov 1997 21:21:14 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id UAA16087; Sun, 16 Nov 1997 20:50:14 +0100 (MET) Message-ID: <19971116205014.XN38067@uriah.heep.sax.de> Date: Sun, 16 Nov 1997 20:50:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Reading kernel memory References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Charles Mott on Nov 10, 1997 13:30:38 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles Mott wrote: > So if one really wants to map a kernel variable to > user space, I am guessing something more sophisticated > than the kvm routines are needed. Not sure, but perhaps it's possible to mmap() /dev/kmem? > Wandering through the kernel source code, I have also > discovered that gettimeofday() actaully invokes a > microtime() call which actually tries to determine the > time by reading a timer and using it to refine the > kernel time variable. After ktracing X11 applications, and seeing how often gettimeofday() is actually called, i've been rather impressed that this entire process is still reasonably faster nevertheless. The featuere is very useful for fine-granularity traces, be it ktrace or tcpdump (or simply the ping response time). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Nov 16 12:29:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12650 for hackers-outgoing; Sun, 16 Nov 1997 12:29:07 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12642 for ; Sun, 16 Nov 1997 12:29:01 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gjallarhorn.ifi.uio.no (2602@gjallarhorn.ifi.uio.no [129.240.65.40]) by ifi.uio.no (8.8.7/8.8.7/ifi0.2) with ESMTP id VAA02242; Sun, 16 Nov 1997 21:28:57 +0100 (MET) Received: (from dag-erli@localhost) by gjallarhorn.ifi.uio.no ; Sun, 16 Nov 1997 21:28:56 +0100 (MET) To: "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Diagnosing Intel EtherExpress Pro/10+ problem References: <199711161916.OAA13572@istari.home.net> Organization: FMKY X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 16 Nov 1997 21:28:56 +0100 In-Reply-To: "Stephen J. Roznowski"'s message of Sun, 16 Nov 1997 14:16:37 -0500 (EST) Message-ID: Lines: 12 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Stephen J. Roznowski" writes: > I'm been having a reoccuring problem with an Intel EtherExpress Pro/10+ > Ethernet card. When I reboot into FreeBSD from Windows 95, occasionally > the card won't come back in a working state. Rebooting multiple times > [...] > My question is, how can I go about diagnosing (and fixing :-) this problem? Well, the fix is easy: stop using Windows 95 ;P -- * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no * cellular +47-92835919 * RFC1123: "Be liberal in what you accept, and conservative in what you send" From owner-freebsd-hackers Sun Nov 16 12:41:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13572 for hackers-outgoing; Sun, 16 Nov 1997 12:41:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13563 for ; Sun, 16 Nov 1997 12:41:36 -0800 (PST) (envelope-from mark@quickweb.com) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id PAA23993; Sun, 16 Nov 1997 15:42:25 -0500 (EST) Message-ID: <19971116154225.31523@vmunix.com> Date: Sun, 16 Nov 1997 15:42:25 -0500 From: Mark Mayo To: Poul-Henning Kamp Cc: Alex , hackers@FreeBSD.ORG Subject: Re: Twice as many OS/2 as FreeBSD ??? References: <14148.879704969@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <14148.879704969@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Nov 16, 1997 at 07:29:29PM +0100 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Nov 16, 1997 at 07:29:29PM +0100, Poul-Henning Kamp wrote: > In message , Alex writ > es: > > > >On Sun, 16 Nov 1997, Poul-Henning Kamp wrote: > > > >> > >> If you think this is embarrasing for FreeBSD: > >> > >> http://rc5stats.distributed.net/oslist.html > >> > >> How about joining "Team FreeBSD" and improving the number ? > > > >Or how bout making your own team, so you could collect the whole prize if > >you win? ;-) We've completed more blocks than Open or NetBSD however. > > One team is plenty. I'm not in it for the money... > > Open & Net BSD are not competition, but that OS/2 should be above us is > more than I can accept... Agreed. We should be placing far better... 5847.99 kkeys/sec is very low. I'm guessing that we are seeing low participation since it's so early in the contest. So everyone go out and grab the client at www.distributed.net/rc5/ and configure it to report as email team-freebsd@circle.net if you want to help out. www.circle.net/team-freebsd/ has more info. Personally, I renice the process to +20 - is there really much difference between +19 and +20? Just curious... :-) At any rate, with the process running at nice +20 I can see no notiecable slow down on my system. Pretty neat. Unix. It works. Go figure. :-) cya, -Mark > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hackers Sun Nov 16 12:44:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13748 for hackers-outgoing; Sun, 16 Nov 1997 12:44:35 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from fly.HiWAAY.net (sprice@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13742; Sun, 16 Nov 1997 12:44:32 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by fly.HiWAAY.net (8.8.7/8.8.6) with SMTP id OAA06254; Sun, 16 Nov 1997 14:44:30 -0600 (CST) Date: Sun, 16 Nov 1997 14:44:29 -0600 (CST) From: Steve Price To: alpha@FreeBSD.org, hackers@FreeBSD.org Subject: need an Alpha-based machine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi All, Does anybody out there in FreeBSD-land have a spare Alpha-based machine that they would be willing to loan/sell? I want to contribute to getting the FreeBSD Alpha port going. I'm not (yet) much of a kernel hacker, but I have been going through NetBSD's Alpha tree trying to shoehorn it into our tree. Yes, I know that pilfering NetBSD's tree may not be the right way to go about it, but at least it will give us a reference implementation within our four walls that we can play around with. Thanks, Steve From owner-freebsd-hackers Sun Nov 16 12:46:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13857 for hackers-outgoing; Sun, 16 Nov 1997 12:46:35 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13852 for ; Sun, 16 Nov 1997 12:46:31 -0800 (PST) (envelope-from mark@quickweb.com) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id PAA24038; Sun, 16 Nov 1997 15:47:40 -0500 (EST) Message-ID: <19971116154739.48444@vmunix.com> Date: Sun, 16 Nov 1997 15:47:39 -0500 From: Mark Mayo To: John Fieber Cc: "Eric J. Schwertfeger" , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: Netscape 4.04 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from John Fieber on Sun, Nov 16, 1997 at 01:12:54PM -0500 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Nov 16, 1997 at 01:12:54PM -0500, John Fieber wrote: > On Sun, 16 Nov 1997, Eric J. Schwertfeger wrote: > > > On Sun, 16 Nov 1997, Robert Swindells wrote: > > > > > FYI - Netscape 4.04 for FreeBSD is out. > > > > Does anyone know if netscape is planning on releasing a version with 128 > > bit security? I've been watching their site daily, and haven't found > > anything yet. > > Has anyone else had problems with it? As with 4.03b8, I > occasionally had problems with it hanging on exit. I thought I > would make sure there wasn't anything around from older versions > causing problems so I moved my ~/.netscape directory out of the > way. Yip. I have the exact same problem. 4.03b8 and 4.04 both hang quite often on exit. Just sits there eating my CPU ignoring the SIGALRM... I've aliased 'kn' to 'killall -9 netscape' to reduce typing. :-) I mailed them about the problem, but haven't gotten a response. It was disapointed to see the same behaviour in 4.04... I may try the Linux version, especially since it has 128-bit encryption. > -john -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hackers Sun Nov 16 12:52:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14176 for hackers-outgoing; Sun, 16 Nov 1997 12:52:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA14151 for ; Sun, 16 Nov 1997 12:52:14 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25443; Sun, 16 Nov 1997 21:52:12 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id VAA16209; Sun, 16 Nov 1997 21:37:06 +0100 (MET) Message-ID: <19971116213706.IV38048@uriah.heep.sax.de> Date: Sun, 16 Nov 1997 21:37:06 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: toby@milkyway.org (Toby Swanson) Subject: Re: security patch for open() References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Toby Swanson on Nov 11, 1997 21:52:01 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Toby Swanson wrote: > Please explain in plain American how to apply the patches for the open() > security hole that was recently released by the FreeBSD security > officer. Better yet, give this FreeBSD newbie the general instructions > for patch application. Sorry for not speaking plain American. I can speak quite a bit of German, and somewhat English. My American is rather lousy. I'm not sure what your background is. Most likely, you've read the FreeBSD security advisory, and are now stuck with the word `patch'. Well, your first option is to simply remove /dev/io. That's not too bad of an option, none of the official utilities do need it anyway. The second option requires that you first read the handbook section on building a new kernel. Once you know how to do this, simply pipe the entire security advisory to the command: cd /usr/src; patch ...and then, go to your kernel's compile directory (/sys/compile/...), and type make depend all install Reboot your computer. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Nov 16 12:54:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14262 for hackers-outgoing; Sun, 16 Nov 1997 12:54:10 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA14257 for ; Sun, 16 Nov 1997 12:54:03 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA25463 for hackers@FreeBSD.ORG; Sun, 16 Nov 1997 21:53:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id VAA16237; Sun, 16 Nov 1997 21:47:41 +0100 (MET) Message-ID: <19971116214740.JL63294@uriah.heep.sax.de> Date: Sun, 16 Nov 1997 21:47:40 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: A stylistic question... References: <199711120858.JAA06510@labinfo.iet.unipi.it> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199711120858.JAA06510@labinfo.iet.unipi.it>; from Luigi Rizzo on Nov 12, 1997 09:58:14 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Luigi Rizzo wrote: > I have always wondered about this: most if not all programs, and some > pieces of the kernel as well (e.g. userconfig.c) > have a menu/usage function which is written like this: > > usage() > { > printf( "bla bla bla...\n" ); > printf( "bla bla bla...\n" ); > printf( "bla bla bla...\n" ); > ... > printf( "bla bla bla...\n" ); > } > > instead of what in my opinion would be much better: > > usage() > { > printf( "%s", "bla bla bla...\n" > "bla bla bla...\n" > ... > "bla bla bla...\n"); > } The first piece has probably been written by people who still adhere to the Old Testament. I use split (ANSI) strings all over the place, and don't care anymore for non-ANSI compilers. If you ask *me*, go ahead and remove all the __P() garbage in the code... (Well, i actually know exactly one non-ANSI compiler i'm rather fond of to know: bcc. "Bruce's C compiler", it's in the ports, and seems to be the only way to generate 16-bit x86 code on FreeBSD.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Nov 16 13:11:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15371 for hackers-outgoing; Sun, 16 Nov 1997 13:11:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA15361 for ; Sun, 16 Nov 1997 13:11:45 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA21266; Sun, 16 Nov 1997 13:14:43 -0800 (PST) Message-Id: <199711162114.NAA21266@implode.root.com> To: Mark Mayo cc: hackers@FreeBSD.ORG Subject: Re: de underflow errors. huh? In-reply-to: Your message of "Sun, 16 Nov 1997 14:59:10 EST." <19971116145910.31953@vmunix.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Nov 1997 13:14:43 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Sun, Nov 16, 1997 at 12:45:44AM -0800, David Greenman wrote: > > >> >de0: abnormal interrupt: transmit underflow >> > >> >I have no clue what this means. Packets seem to be flowing through >> >the interface nicely, and there is no noticeable packet loss. >> >If anyone has any ideas what could be causing this, or if I should >> >give a hoot, please let me know. >> >> It's indicating that the PCI bus was sufficiently busy enough to cause >> the transmit DMA to be stalled too long. The proper response to this condition >> in the device driver it to dynamically increase the transmit threshold (the >> number of bytes that are DMA'ed onto the card before the transmission is >> actually started on the wire). The fxp driver does this, the de driver >> doesn't. I think Matt Thomas might have fixed this in a later rev., but I'm >> not sure about that. >> Anyway, other than the annoying console messages and perhaps a packet >> drop when it happens, the problem can be ignored. > >Do you think increasing the bus speed will make a difference? This machine >is a P54C 150 - I originally wanted to run it at 75MHz * 2, but the >dealer gave me one of the aftermarket Intel CPUs with the integrated >heat sink, and the machine just plain won't make it past the memory >check when I run the bus at 75... I've done this (75*2) setup on several >other machines with no problems - but they had the OEM'ed version of the >CPU with no heatsink, and a grey bottom. I'm guessing that this black >bottomed jobby is preventing itself from being "overclocked" somehow. >I may try and get a replacement CPU.. But before I do that do you think >the jump from 60MHz to 75MHz will help the de card? I don't know. > Or is the 100Mb fxp >simply delivering data too quickly for it to handle. Perhaps replacing >the de with a fxp... That would get rid of the problem. You didn't mention which chip was on the de card, but if it is the original 21140, then that might also be a problem - I seem to recall that it didn't do the memory-read-multiple PCI operation, resulting in very poor PCI performance. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Nov 16 13:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15525 for hackers-outgoing; Sun, 16 Nov 1997 13:12:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA15515 for ; Sun, 16 Nov 1997 13:12:45 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin1.anlw.anl.gov [141.221.254.101]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id OAA17550; Sun, 16 Nov 1997 14:12:39 -0700 Date: Sun, 16 Nov 1997 14:12:07 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: Reading kernel memory In-Reply-To: <19971116205014.XN38067@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, J Wunsch wrote: > As Charles Mott wrote: > > > So if one really wants to map a kernel variable to > > user space, I am guessing something more sophisticated > > than the kvm routines are needed. > > Not sure, but perhaps it's possible to mmap() /dev/kmem? Yes, mmap() to /dev/kmem works (I tested it), and so reading the kernel time variable can be done very quickly. I hadn't figured this out yet when I made the earlier posting. As mentioned below, though, the granularity of this measurement (usually 10 msec) is not nearly as good as gettimeofday() because of microtime(). > > > Wandering through the kernel source code, I have also > > discovered that gettimeofday() actaully invokes a > > microtime() call which actually tries to determine the > > time by reading a timer and using it to refine the > > kernel time variable. > > After ktracing X11 applications, and seeing how often gettimeofday() > is actually called, i've been rather impressed that this entire > process is still reasonably faster nevertheless. The featuere is very > useful for fine-granularity traces, be it ktrace or tcpdump (or simply > the ping response time). The high accuracy ping time is one thing I've always liked about FreeBSD over Linux. Does anyone know what the response time for gettimeofday() is on a reasonably modern Pentium? It is about 60 microseconds on my ancient 386. Although I originally though a non-privileged /dev/timeofday (Tony Newfield's idea) combined with mmap() might be a good way to get quick timestamps, I tend to think the existing system is good enough, especially since processors are getting faster. Charles Mott From owner-freebsd-hackers Sun Nov 16 13:15:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15704 for hackers-outgoing; Sun, 16 Nov 1997 13:15:02 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA15670 for ; Sun, 16 Nov 1997 13:14:46 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA21287; Sun, 16 Nov 1997 13:17:45 -0800 (PST) Message-Id: <199711162117.NAA21287@implode.root.com> To: "Stephen J. Roznowski" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Diagnosing Intel EtherExpress Pro/10+ problem In-reply-to: Your message of "Sun, 16 Nov 1997 14:16:37 EST." <199711161916.OAA13572@istari.home.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Nov 1997 13:17:44 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm been having a reoccuring problem with an Intel EtherExpress Pro/10+ >Ethernet card. When I reboot into FreeBSD from Windows 95, occasionally >the card won't come back in a working state. Rebooting multiple times >will cause the card to eventually work. [This is on an 18 October kernel, >but has occurred on earlier kernels as well.] > >Each time, the card seems to be recognized correctly during the probe, >but when I try to (for example) ping a remote address, I get a "no route >to host" message [not sure of exact wording]. If I configure the interface >down, then back up, I get a "could not allocate llinfo" error. > >My question is, how can I go about diagnosing (and fixing :-) this problem? Do you have the ISA version or the PCI version (which driver does it use)? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Nov 16 13:26:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16399 for hackers-outgoing; Sun, 16 Nov 1997 13:26:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16393 for ; Sun, 16 Nov 1997 13:26:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id WAA14484; Sun, 16 Nov 1997 22:24:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mark Mayo cc: Alex , hackers@FreeBSD.ORG Subject: Re: Twice as many OS/2 as FreeBSD ??? In-reply-to: Your message of "Sun, 16 Nov 1997 15:42:25 EST." <19971116154225.31523@vmunix.com> Date: Sun, 16 Nov 1997 22:24:37 +0100 Message-ID: <14482.879715477@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19971116154225.31523@vmunix.com>, Mark Mayo writes: >So everyone go out and grab the client at www.distributed.net/rc5/ and >configure it to report as email team-freebsd@circle.net if you want to >help out. www.circle.net/team-freebsd/ has more info. yes, go for it! >Personally, I renice the process to +20 - is there really much difference >between +19 and +20? Just curious... :-) Only if any other processes have +19 as priority. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hackers Sun Nov 16 14:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19477 for hackers-outgoing; Sun, 16 Nov 1997 14:24:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19420; Sun, 16 Nov 1997 14:23:59 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id VAA29224; Sun, 16 Nov 1997 21:41:45 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711162141.VAA29224@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jonathan M. Bresler" cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@freebsd.org Subject: Re: /etc/mail filters in 2.2.5 In-reply-to: Your message of "Sun, 16 Nov 1997 06:46:03 PST." <199711161446.GAA24588@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Nov 1997 21:41:44 +0000 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > BIGFOOT.DALTEK.NET^M #blocked. contact postmaster > > > > > > first, that "^M" is it in the file? > > > is so please delete it. > > > after deleting the "^M" > > > cd /etc/mail; make install > > > > Hmm, the domains.txt I got with the ``make'' had 'em in, so I figured > > they were meant to be :-I > > ahh.....did you use DOS! > "^M" is teh DOS extra end-of-line character. > DOS uses both and to indicate and end-of-line. > Unix uses only one, the Mac uses the other. Funny this. I did the ``make'' from a FreeBSD box. Perhaps ftp://ftp.gulf.net/pub/docs/domains.txt really has got nasty ^Ms at the end of the lines :-| AFAIK, fetch *never* does ascii (^M) translations (this is correct IMHO). Oh well, they're gone now :-) Thanks again. [.....] > jmb -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Nov 16 14:29:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19809 for hackers-outgoing; Sun, 16 Nov 1997 14:29:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from athena.veritas.com (athena.veritas.com [192.203.46.191]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA19798 for ; Sun, 16 Nov 1997 14:29:15 -0800 (PST) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com by athena.veritas.com with smtp (Smail3.1.29.0 #9) id m0xXDBO-000ikiC; Sun, 16 Nov 97 14:28 PST Received: from sigma.veritas.com by megami.veritas.com with smtp (Smail3.1.29.0 #7) id m0xXDBN-00000jC; Sun, 16 Nov 97 14:28 PST Message-Id: From: Aaron Smith To: "Stephen J. Roznowski" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Diagnosing Intel EtherExpress Pro/10+ problem In-reply-to: Your message of "Sun, 16 Nov 1997 13:17:44 PST." <199711162117.NAA21287@implode.root.com> Date: Sun, 16 Nov 1997 14:28:40 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997 13:17:44 PST, David Greenman writes: >>I'm been having a reoccuring problem with an Intel EtherExpress Pro/10+ >>Ethernet card. When I reboot into FreeBSD from Windows 95, occasionally >>the card won't come back in a working state. Rebooting multiple times >>will cause the card to eventually work. [This is on an 18 October kernel, >>but has occurred on earlier kernels as well.] >> >>Each time, the card seems to be recognized correctly during the probe, >>but when I try to (for example) ping a remote address, I get a "no route >>to host" message [not sure of exact wording]. If I configure the interface >>down, then back up, I get a "could not allocate llinfo" error. >> >>My question is, how can I go about diagnosing (and fixing :-) this problem? [i'm assuming you're talking about the ie driver] i saw this problem with the ie driver, but only when rebooting to Win95 *from* FreeBSD. is that what you meant? i fixed this when i worked on the ie0 driver by re-initializing the card in a shutdown() routine. it worked for me, but unfortunately it caused panics for some people which i lacked time to work on / wasn't able to reproduce. so it didn't get into the tree. if you want to try it i can hunt for the code. if you really meant booting to freebsd from win95, ignore this msg. aaron From owner-freebsd-hackers Sun Nov 16 16:19:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25440 for hackers-outgoing; Sun, 16 Nov 1997 16:19:48 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA25431 for ; Sun, 16 Nov 1997 16:19:43 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin1.anlw.anl.gov [141.221.254.101]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id RAA17739 for ; Sun, 16 Nov 1997 17:19:40 -0700 Date: Sun, 16 Nov 1997 17:19:07 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: hackers@freebsd.org Subject: Is fork() copy-on-write ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was curious to know when a process is forked, are the new vm pages which are created copy-on-write? [I know, I know I should just go look at the source code, but I haven't quite got up the nerve to start looking at that area. It is sort of like peering over a cliff into an infinite abyss.] -- Charles Mott From owner-freebsd-hackers Sun Nov 16 17:05:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28258 for hackers-outgoing; Sun, 16 Nov 1997 17:05:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA28245 for ; Sun, 16 Nov 1997 17:05:06 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id UAA26711; Sun, 16 Nov 1997 20:04:55 -0500 (EST) From: "John S. Dyson" Message-Id: <199711170104.UAA26711@dyson.iquest.net> Subject: Re: Is fork() copy-on-write ? In-Reply-To: from Charles Mott at "Nov 16, 97 05:19:07 pm" To: cmott@srv.net (Charles Mott) Date: Sun, 16 Nov 1997 20:04:54 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Charles Mott said: > I was curious to know when a process is forked, are the new vm pages which > are created copy-on-write? > > [I know, I know I should just go look at the source code, but I haven't > quite got up the nerve to start looking at that area. It is sort of like > peering over a cliff into an infinite abyss.] > In the FreeBSD kernel, ALL pages that can be COW are COW -- if anyone finds the contrary PLEASE tell me ASAP (and I'll fix it.) One of the original problems in the BSD 4.4VM, fixed in FreeBSD, was that originally, during a fork, as many as three (3) pages would exist for every page COW after a fork. We have reduced that to two (2) in the normal case. Of course, that is what is expected, but when figuring out what that code does, expect the unexpected!!! :-). (Note that many versions of UNIX don't bother COW on modified .data actually performing explicit copies for .data pages, but the FreeBSD/Mach VM doesn't do any unnecessary copies.) -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Sun Nov 16 17:14:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28843 for hackers-outgoing; Sun, 16 Nov 1997 17:14:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA28834 for ; Sun, 16 Nov 1997 17:14:11 -0800 (PST) (envelope-from ahd@kew.com) Received: from kew.com (sonata.hh.kew.com [192.195.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with ESMTP id UAA04203; Sun, 16 Nov 1997 20:13:57 -0500 (EST) Message-ID: <346F9A59.2C971682@kew.com> Date: Sun, 16 Nov 1997 20:14:01 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham MA 02180 X-Mailer: Mozilla 4.04 [en]C-MOENE (WinNT; I) MIME-Version: 1.0 To: Poul-Henning Kamp CC: hackers@freebsd.org Subject: Challanges and distributed computing References: <14482.879715477@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > In message <19971116154225.31523@vmunix.com>, Mark Mayo writes: > > >So everyone go out and grab the client at www.distributed.net/rc5/ and > >configure it to report as email team-freebsd@circle.net if you want to > >help out. www.circle.net/team-freebsd/ has more info. > > yes, go for it! Okay, I have taken the bait and fired it off on a spare virtual console with the requested return address. I presume it _knows_ it's a FreeBSD client and reports same to the bean counters? No additional work is needed? In a semi-related item, has anyone ever brought a MathLink client up on FreeBSD communicating with a Mathematica client running on a PC (Windows/Mac/whatever) GUI? My spouse the MIT geek wants to ... -- Internet: ahd@kew.com Voice: 781-279-9812 You are in a maze of little twisty passages, all alike From owner-freebsd-hackers Sun Nov 16 17:46:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01028 for hackers-outgoing; Sun, 16 Nov 1997 17:46:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01020 for ; Sun, 16 Nov 1997 17:46:35 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA20722; Mon, 17 Nov 1997 01:45:53 GMT Date: Mon, 17 Nov 1997 10:45:53 +0900 (JST) From: Michael Hancock To: Charles Mott cc: hackers@FreeBSD.ORG Subject: Re: Is fork() copy-on-write ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Charles Mott wrote: > I was curious to know when a process is forked, are the new vm pages which > are created copy-on-write? > > [I know, I know I should just go look at the source code, but I haven't > quite got up the nerve to start looking at that area. It is sort of like > peering over a cliff into an infinite abyss.] If you're ready to make a jump, start here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_fork.c?rev=1.48 From owner-freebsd-hackers Sun Nov 16 19:47:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA07531 for hackers-outgoing; Sun, 16 Nov 1997 19:47:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA07524 for ; Sun, 16 Nov 1997 19:47:21 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id TAA02067; Sun, 16 Nov 1997 19:47:03 -0800 (PST) Date: Sun, 16 Nov 1997 19:47:03 -0800 (PST) From: "Jamil J. Weatherbee" To: Charles Mott cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: Reading kernel memory In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone know what the response time for gettimeofday() is on a > reasonably modern Pentium? It is about 60 microseconds on my ancient 386. I wrote some test code for this, included below. My results (as measured by this code) Machine Calls Latency PPro-180 999998 4.06us Nexgen P-100 999977 23.92us Pentium-100 999987 4.81us Cyrix-PR166 999996 5.82us I guess that kinda says something bad about that NexGen machine I used to test the AIOX driver, mainly that it is slow, which for testing I guess is kinda good. Maybye it is just slower in the call gate or something because computational I think it is a bit faster than the Pentium 100 (at least that is my experience with the equally equipped machines). ------------------------ The Code ------------------------------------- #include #include #define TESTLEN 1000000 void main (void) { struct timeval a,b; long d; long t = 0; int x, c= 0; for (x=0;x Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08034 for hackers-outgoing; Sun, 16 Nov 1997 19:54:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08026 for ; Sun, 16 Nov 1997 19:54:36 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.6/8.8.6) id VAA20341; Sun, 16 Nov 1997 21:54:31 -0600 (CST) Message-ID: <19971116215431.16014@emsphone.com> Date: Sun, 16 Nov 1997 21:54:31 -0600 From: Dan Nelson To: Drew Derbyshire Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: Challanges and distributed computing References: <14482.879715477@critter.freebsd.dk> <346F9A59.2C971682@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.87.6e In-Reply-To: <346F9A59.2C971682@kew.com>; from "Drew Derbyshire" on Sun Nov 16 20:14:01 GMT 1997 X-OS: FreeBSD 2.2-970701-RELENG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In the last episode (Nov 16), Drew Derbyshire said: > Poul-Henning Kamp wrote: > > In message <19971116154225.31523@vmunix.com>, Mark Mayo writes: > > >So everyone go out and grab the client at www.distributed.net/rc5/ > > >and configure it to report as email team-freebsd@circle.net if you > > >want to help out. www.circle.net/team-freebsd/ has more info. > > > > yes, go for it! > > Okay, I have taken the bait and fired it off on a spare virtual > console with the requested return address. I presume it _knows_ it's > a FreeBSD client and reports same to the bean counters? No > additional work is needed? Note that the "rules" for running an rc5 client changed slightly after the rc5-56 challenge key was found. Use your own email address when submitting keys; that way if you are the lucky winner, you can be notified as soon as possible. After your client has been running for a day or two, you will be emailed a password. Then search for your email address at the rc5 stats page (http://rc5stats.distributed.net), and assign your blocks to Team FreeBSD - team number 988. Actually, the Team FreeBSD web page at http://www.circle.net/team-freebsd explains this rather well. -Dan Nelson dnelson@emsphone.com From owner-freebsd-hackers Sun Nov 16 20:04:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08430 for hackers-outgoing; Sun, 16 Nov 1997 20:04:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA08423 for ; Sun, 16 Nov 1997 20:04:28 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin1.anlw.anl.gov [141.221.254.101]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id VAA17938; Sun, 16 Nov 1997 21:04:18 -0700 Date: Sun, 16 Nov 1997 21:03:44 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: "Jamil J. Weatherbee" cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: Reading kernel memory In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Jamil J. Weatherbee wrote: > > > Does anyone know what the response time for gettimeofday() is on a > > reasonably modern Pentium? It is about 60 microseconds on my ancient 386. > > I wrote some test code for this, included below. > > My results (as measured by this code) > > Machine Calls Latency > > PPro-180 999998 4.06us > Nexgen P-100 999977 23.92us > Pentium-100 999987 4.81us > Cyrix-PR166 999996 5.82us > > I guess that kinda says something bad about that NexGen machine I used to > test the AIOX driver, mainly that it is slow, which for testing I guess is > kinda good. Maybye it is just slower in the call gate or something because > computational I think it is a bit faster than the Pentium 100 (at least > that is my experience with the equally equipped machines). That's interesting -- P100 and PPro 180 times are about the same. Gettimeofday() is mostly context switching I suppose although there are (I am guessing) 50 or so machine language instructions in microtime(). As far as the Nexgen, there are some Pentium optimizations in microtime() which it could be doing very slowly in microcode, or maybe context switch time is just lousy or maybe you were running something else on your Nexgen. Thanks for the feedback. Charles Mott From owner-freebsd-hackers Sun Nov 16 22:05:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14537 for hackers-outgoing; Sun, 16 Nov 1997 22:05:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA14531; Sun, 16 Nov 1997 22:05:27 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id AAA12766; Mon, 17 Nov 1997 00:05:26 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.8.7/8.8.7) id AAA02292; Mon, 17 Nov 1997 00:01:42 -0600 (CST) Date: Mon, 17 Nov 1997 00:01:42 -0600 (CST) Message-Id: <199711170601.AAA02292@zuhause.mn.org> From: Bruce Albrecht To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG Subject: Re: Twice as many OS/2 as FreeBSD ??? In-Reply-To: <13266.879673688@critter.freebsd.dk> References: <13266.879673688@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "New York" XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > If you think this is embarrassing for FreeBSD: > > http://rc5stats.distributed.net/oslist.html > > How about joining "Team FreeBSD" and improving the number ? Last time I checked, I've got nearly one third of the blocks allocated to Team FreeBSD, and only half of them are actually from a FreeBSD box. If you check the platform specs, Linux has about 10 times as many keys checked as FreeBSD, and the PowerPC Mac's I think have about 20 times as many checked as FreeBSD. If your machine is running idle much of the day (or night), why not replace the idle loop with rc564? From owner-freebsd-hackers Mon Nov 17 02:44:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01516 for hackers-outgoing; Mon, 17 Nov 1997 02:44:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from burka.carrier.kiev.ua ([195.145.31.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01494 for ; Mon, 17 Nov 1997 02:44:10 -0800 (PST) (envelope-from archer@burka.carrier.kiev.ua) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.8.6/8.Who.Cares) id MAA11030 for ; Mon, 17 Nov 1997 12:27:41 +0200 (EET) Message-ID: <19971117122741.11033@burka.carrier.kiev.ua> Date: Mon, 17 Nov 1997 12:27:41 +0200 From: Alexander Litvin To: hackers@freebsd.org Subject: FreeBSD crashes under heavy network load... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's 2.2.5-stable. Proxy server. Crashes constantly, always in the same place. Output of bt: ------------------------------------------------------------------------ bash# gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) symbol-file /kernel.debug Reading symbols from /kernel.debug...done. (kgdb) exec-file /var/crash/kernel.1 (kgdb) core-file /var/crash/vmcore.1 IdlePTD 1c3000 current pcb at 1ac9d0 panic: page fault #0 boot (howto=260) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:266 #1 0xf01116e2 in panic (fmt=0xf017b84f "page fault") at ../../kern/kern_shutdown.c:390 #2 0xf017c3b6 in trap_fatal (frame=0xf01a0dc4) at ../../i386/i386/trap.c:742 #3 0xf017bea4 in trap_pfault (frame=0xf01a0dc4, usermode=0) at ../../i386/i386/trap.c:653 #4 0xf017bb7f in trap (frame={tf_es = -266731504, tf_ds = -267255792, tf_edi = 0, tf_esi = -161442560, tf_ebp = -266727920, tf_isp = -266727956, tf_ebx = -158123136, tf_edx = 0, tf_ecx = -162092544, tf_eax = -158123264, tf_trapno = 12, tf_err = 0, tf_eip = -267186362, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -158123136}) at ../../i386/i386/trap.c:311 #5 0xf0130f46 in vget (vp=0xf6933b80, lockflag=1) at ../../kern/vfs_subr.c:817 #6 0xf015cd3c in ffs_sync (mp=0xf6573600, waitfor=2, cred=0xf3c17880, p=0xf01b7c94) at ../../ufs/ffs/ffs_vfsops.c:819 #7 0xf0132407 in sync (p=0xf01b7c94, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:360 #8 0xf01112ed in boot (howto=256) at ../../kern/kern_shutdown.c:199 #9 0xf01116e2 in panic (fmt=0xf017b84f "page fault") at ../../kern/kern_shutdown.c:390 #10 0xf017c3b6 in trap_fatal (frame=0xf01a0f48) at ../../i386/i386/trap.c:742 #11 0xf017bea4 in trap_pfault (frame=0xf01a0f48, usermode=0) at ../../i386/i386/trap.c:653 #12 0xf017bb7f in trap (frame={tf_es = -154664944, tf_ds = -267059184, ---Type to continue, or q to quit--- tf_edi = -1073741824, tf_esi = -1073741824, tf_ebp = -266727540, tf_isp = -266727568, tf_ebx = -265166040, tf_edx = 172511825, tf_ecx = -159965440, tf_eax = 87502848, tf_trapno = 12, tf_err = 0, tf_eip = -267083713, tf_cs = 8, tf_eflags = 66054, tf_esp = -266715032, tf_ss = -266714668}) at ../../i386/i386/trap.c:311 #13 0xf014a03f in tcp_fasttimo () at ../../netinet/tcp_timer.c:111 #14 0xf0124677 in pffasttimo (arg=0x0) at ../../kern/uipc_domain.c:234 #15 0xf01090fc in softclock () at ../../kern/kern_clock.c:715 (kgdb) ------------------------------------------------------------------------ Where is BSD(tm) excellnet networking? :(((( -- Alexander Litvin From owner-freebsd-hackers Mon Nov 17 03:14:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03254 for hackers-outgoing; Mon, 17 Nov 1997 03:14:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA03244 for ; Mon, 17 Nov 1997 03:14:50 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256552.003DB6FE ; Mon, 17 Nov 1997 08:14:05 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: hackers@freebsd.org Message-ID: <03256552.003D83E4.00@papagaio.voga.com.br> Date: Mon, 17 Nov 1997 08:13:59 -0300 Subject: Bootload Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What files comprise (sp?) the bootload source code? From owner-freebsd-hackers Mon Nov 17 03:22:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03635 for hackers-outgoing; Mon, 17 Nov 1997 03:22:02 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA03625 for ; Mon, 17 Nov 1997 03:21:56 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA07602; Mon, 17 Nov 1997 21:51:52 +1030 From: Kristian Kennaway Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA22088; Mon, 17 Nov 1997 21:51:55 +1030 Message-Id: <9711171121.AA22088@bragg> Subject: Re: Netscape 4.04 To: jfieber@indiana.edu (John Fieber) Date: Mon, 17 Nov 1997 21:51:55 +1030 (CST) Cc: ejs@bfd.com, rjs@fdy2.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: from "John Fieber" at Nov 16, 97 01:12:54 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Sun, 16 Nov 1997, Eric J. Schwertfeger wrote: > > > On Sun, 16 Nov 1997, Robert Swindells wrote: > > > > > FYI - Netscape 4.04 for FreeBSD is out. > > > > Does anyone know if netscape is planning on releasing a version with 128 > > bit security? I've been watching their site daily, and haven't found > > anything yet. > > Has anyone else had problems with it? As with 4.03b8, I > occasionally had problems with it hanging on exit. I thought I Same. Chews up all the CPU when I Alt-Q it. Not to mention the fact that it was tying up 70 MEGABYTES of swap when all I was doing was some routine browsing for an hour or so. *sigh* Kris From owner-freebsd-hackers Mon Nov 17 03:25:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03771 for hackers-outgoing; Mon, 17 Nov 1997 03:25:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from meowy.angio.net (meowy.angio.net [206.197.119.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA03766 for ; Mon, 17 Nov 1997 03:25:14 -0800 (PST) (envelope-from angio@meowy.angio.net) Received: from meowy.angio.net (localhost.angio.net [127.0.0.1]) by meowy.angio.net (8.8.8/8.7.3) with ESMTP id EAA22561 for ; Mon, 17 Nov 1997 04:25:09 -0700 (MST) Message-Id: <199711171125.EAA22561@meowy.angio.net> To: hackers@freebsd.org Subject: Re: Twice as many OS/2 as FreeBSD ??? In-reply-to: Your message of "Sun, 16 Nov 1997 15:42:25 EST." <19971116154225.31523@vmunix.com> Date: Mon, 17 Nov 1997 04:25:09 -0700 From: Dave Andersen Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Personally, I renice the process to +20 - is there really much difference > between +19 and +20? Just curious... :-) > > At any rate, with the process running at nice +20 I can see no > notiecable slow down on my system. Pretty neat. Unix. It works. Go > figure. :-) If you're really concerned about it, then idprio them: idprio 31 rc564 This will cause the process to _only_ execute when there is nothing else that can run; nice +20 will still grab a little tiny bit of CPU time every now and then. Functionally, it doesn't make much of a difference, but for the paranoid, the option is there, and it can't hurt if you're running the rc5 client on a machine that's used for other things. -Dave From owner-freebsd-hackers Mon Nov 17 03:49:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04970 for hackers-outgoing; Mon, 17 Nov 1997 03:49:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from konig.elte.hu (konig.elte.hu [157.181.6.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04790 for ; Mon, 17 Nov 1997 03:45:42 -0800 (PST) (envelope-from sebesty@cs.elte.hu) Received: from neumann.cs.elte.hu (neumann [157.181.6.200]) by konig.elte.hu (8.8.3/8.7.3/7s) with ESMTP id LAA05333; Mon, 17 Nov 1997 11:06:30 +0100 Received: from localhost (sebesty@localhost) by neumann.cs.elte.hu (8.8.3/8.7.3/4c) with ESMTP id LAA16928; Mon, 17 Nov 1997 11:05:53 +0100 X-Authentication-Warning: neumann.cs.elte.hu: sebesty owned process doing -bs Date: Mon, 17 Nov 1997 11:05:53 +0100 (MET) From: Zoltan Sebestyen To: Joerg Wunsch cc: FreeBSD hackers mailinglist Subject: Re: Problems with passwd utility. In-Reply-To: <19971116210828.OU36167@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, J Wunsch wrote: > As Lucas Adri n G¢mez Bland¢n wrote: > > > Hi everyone, I'm install FreeBSD 2.1.7.1 (STABLE), it was a piece of > > cake!, but when a user call "passwd" he receive "Permision denied". > > That most likely means you're attempting to change the password for > someone else than yourself (e.g. since you're "su"ed to another user). I've got the same problem(and still have). I have to type 'passwd ' to get it work. Before that, I used vipw to edit the passwd file, because I discovered that my account was in a non-existent group. -------------------------------------------------------------------------------- Sebestyen Zoltan It all seems so stupid, it makes me want to give up. szoli@digo.inf..elte.hu But why should I give up, when it all seems so stupid? MAKE INSTALL NOT WAR From owner-freebsd-hackers Mon Nov 17 04:22:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06861 for hackers-outgoing; Mon, 17 Nov 1997 04:22:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from jkh.cdrom.com (root@ppp-78.toiyabe.com [207.92.38.78]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06853; Mon, 17 Nov 1997 04:22:51 -0800 (PST) (envelope-from jkh@jkh.cdrom.com) Received: from jkh.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by jkh.cdrom.com (8.8.8/8.8.5) with ESMTP id EAA08161; Mon, 17 Nov 1997 04:22:41 -0800 (PST) To: Jonathan Mini cc: jkh@FreeBSD.ORG, sos@FreeBSD.dk, hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library In-reply-to: Your message of "Sun, 16 Nov 1997 04:21:04 PST." <19971116042103.28008@micron.mini.net> Date: Mon, 17 Nov 1997 04:22:39 -0800 Message-ID: <8157.879769359@jkh.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Commit privileges would be helpful, although not a requirement by any means . > It really depends on how you want me to contribute my work. > > (Aside from the fact that it would be cool to have commit privleges) Heh. Well, I'll tell you what. No one has objected to this idea, but Soren is also wanting to have a little oversight here anyway since much of this will be in his corner of the system and for that, you might as well have him review and commit it anyway since that'll be the shortest distance between two points for that particular model. Once you're up to speed and he's eager to get out of the loop, I'll transition you to full committer status and you can simply maintain and extend this work on your own. Sound reasonable? Jordan From owner-freebsd-hackers Mon Nov 17 04:23:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06922 for hackers-outgoing; Mon, 17 Nov 1997 04:23:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06874; Mon, 17 Nov 1997 04:23:08 -0800 (PST) (envelope-from ru@relay.ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id OAA14473; Mon, 17 Nov 1997 14:22:38 +0200 (EET) (envelope-from ru) From: Ruslan Ermilov Message-Id: <199711171222.OAA14473@relay.ucb.crimea.ua> Subject: IPSec and 2.2-STABLE To: itojun@freebsd.org Date: Mon, 17 Nov 1997 14:22:38 +0200 (EET) Cc: hackers@freebsd.org X-My-Interests: Unix,Oracle,Networking 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 X-Loop: FreeBSD.org Precedence: bulk Hi! What is the general state of IPSec for FreeBSD? Can I use it with post-2.2.5-RELEASE (i.e. 2.2-STABLE)? Thanks! -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN From owner-freebsd-hackers Mon Nov 17 04:27:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA07065 for hackers-outgoing; Mon, 17 Nov 1997 04:27:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA07060 for ; Mon, 17 Nov 1997 04:27:18 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id IAA02324 for ; Mon, 17 Nov 1997 08:32:33 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 17 Nov 1997 08:32:32 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: Status of patch? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i'm about to do a 'make world' and remake my kernel too, i was wondering if and what has been done to the kernel to fix the 'f00f' bug? i don't want to rebuild everything if there has been no fix for the 'f00f' bug. what kind of performance impact are we talking about with the fix? i was also wondering if any of the alternative fixes people have brought up seem to work? thank you, .________________________________________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" |perlsta@sunyit.edu --"who was that masked admin?" |http://www.cs.sunyit.edu/~perlsta : ' From owner-freebsd-hackers Mon Nov 17 04:37:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08176 for hackers-outgoing; Mon, 17 Nov 1997 04:37:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08171 for ; Mon, 17 Nov 1997 04:37:23 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA29124; Mon, 17 Nov 1997 04:36:49 -0800 (PST) Message-Id: <199711171236.EAA29124@implode.root.com> To: Alexander Litvin cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD crashes under heavy network load... In-reply-to: Your message of "Mon, 17 Nov 1997 12:27:41 +0200." <19971117122741.11033@burka.carrier.kiev.ua> From: David Greenman Reply-To: dg@root.com Date: Mon, 17 Nov 1997 04:36:49 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It's 2.2.5-stable. Proxy server. Crashes constantly, always in the same >place. Output of bt: Please describe in detail what sorts of networking things occur on the machine. The backtrace appears to indicate possible missing splnet protection in some other part of the kernel, probably when a TCP connection is rundown under unusual circumstances. I've never seen this myself, nor heard of any reports of this problem, so I'm interested in what your machine is doing to cause this. The "hackers" list is not the correct mailing list to report bugs. We have a "bugs" mailing list for that as well as a GNATS bug tracking system that we encourage people to use. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Nov 17 05:47:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11889 for hackers-outgoing; Mon, 17 Nov 1997 05:47:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from jkh.cdrom.com (root@ppp-78.toiyabe.com [207.92.38.78]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA11884 for ; Mon, 17 Nov 1997 05:47:15 -0800 (PST) (envelope-from jkh@jkh.cdrom.com) Received: from jkh.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by jkh.cdrom.com (8.8.8/8.8.5) with ESMTP id FAA08270; Mon, 17 Nov 1997 05:46:55 -0800 (PST) To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: Status of patch? In-reply-to: Your message of "Mon, 17 Nov 1997 08:32:32 EST." Date: Mon, 17 Nov 1997 05:46:53 -0800 Message-ID: <8266.879774413@jkh.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i'm about to do a 'make world' and remake my kernel too, i was wondering > if and what has been done to the kernel to fix the 'f00f' bug? > > i don't want to rebuild everything if there has been no fix for the 'f00f' > bug. Even if there were a fix for the F00F bug in the tree, which there isn't yet, it would have absolutely nothing to do with your make world. This change, when it's made, will be in the kernel and entirely separate from the world build. > what kind of performance impact are we talking about with the fix? Hopefully negligible enough to be unmeasurable. Jordan From owner-freebsd-hackers Mon Nov 17 06:39:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15021 for hackers-outgoing; Mon, 17 Nov 1997 06:39:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15010 for ; Mon, 17 Nov 1997 06:39:25 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA03228; Mon, 17 Nov 1997 14:39:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id PAA06929; Mon, 17 Nov 1997 15:39:18 +0100 (MET) Date: Mon, 17 Nov 1997 15:39:18 +0100 (MET) Message-Id: <199711171439.PAA06929@bitbox.follo.net> From: Eivind Eklund To: "Daniel Sobral" CC: hackers@FreeBSD.ORG In-reply-to: "Daniel Sobral"'s message of Mon, 17 Nov 1997 08:13:59 -0300 Subject: Re: Bootload References: <03256552.003D83E4.00@papagaio.voga.com.br> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What files comprise (sp?) the bootload source code? /usr/src/sys/i386/boot/biosboot/ contains the file for the standard bootloader. There are some other directories in sys/i386/boot, for other bootloaders (network, compressed, etc). Eivind. From owner-freebsd-hackers Mon Nov 17 09:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA25756 for hackers-outgoing; Mon, 17 Nov 1997 09:29:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA25625; Mon, 17 Nov 1997 09:27:55 -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 RAA17465; Mon, 17 Nov 1997 17:19:36 +0100 From: Luigi Rizzo Message-Id: <199711171619.RAA17465@labinfo.iet.unipi.it> Subject: snd971117.tgz To: multimedia@freebsd.org Date: Mon, 17 Nov 1997 17:19:35 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Bcc-ed to hackers because a little bit of advertising is always good...] After almost one month, a new snap of the sound code is available at http://www.iet.unipi.it/~luigi/FreeBSD.html (the actual URL is http://www.iet.unipi.it/~luigi/snd971117.tgz for those using wget/fetch or other command line programs). For the first time I have tried my audio driver with the linux emulator (and linux binaries) and I have to say I am quite pleased that it works pretty well. Noticeable changes in this snapshot include: + fixed a bug in snd_sync which caused errors on close (snd971022); + support for the Yamaha SA3; + some code cleanup for the SB16; + a few more Voxware ioctl() used by the rvplayer 5.0 for linux + patches for linux emulation in 2.2.x to make the driver work with rvplayer; and + initial hooks for the ESS1868 (untested and not working yet); Users of snd971022 or earlier should upgrade to this version. A patch for -current will be available in a day or so. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Nov 17 10:56:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03496 for hackers-outgoing; Mon, 17 Nov 1997 10:56:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03440 for ; Mon, 17 Nov 1997 10:55:45 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.7/8.8.7) id KAA07784 for hackers@freebsd.org; Mon, 17 Nov 1997 10:55:42 -0800 (PST) (envelope-from sef) Date: Mon, 17 Nov 1997 10:55:42 -0800 (PST) From: Sean Eric Fagan Message-Id: <199711171855.KAA07784@kithrup.com> To: hackers@freebsd.org Subject: temporary f00f workaround Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to Cy Schubert and Johnathan Lemon for pointers. Note that this is not final, nor complete -- it doesn't deal with VM86 mode, with user-defined LDT's, nor with some of the annoyances that have to be done. But Johnathan's other patch won't work reliably (I have a small test program that tries to cause the TLB entries to be flushed, and then executes the f00f instruction -- and causes a hang). Cy also has another suggestion, involving remapping the page temporarily, which I haven't tried. Anyway, this should do for now. In general, you don't need to apply it unless you've got people you don't trust running programs on your system, or are extra paranoid about security, or want to try fleshing out the bits I don't have here. Enjoy. Index: identcpu.c =================================================================== RCS file: /usr/home/sef/CVS-kernel/sys/i386/i386/identcpu.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 identcpu.c --- identcpu.c 1997/03/01 02:57:12 1.1.1.1 +++ identcpu.c 1997/11/15 18:40:04 @@ -78,6 +78,10 @@ { "Pentium Pro", CPUCLASS_686 }, /* CPU_686 */ }; +#ifndef NO_PENTIUM_F00F_HACK +int has_f00f_bug = 0; +#endif + void identifycpu(void) { @@ -104,6 +108,9 @@ strcat(cpu_model, "i486 "); break; case 0x500: +#ifndef NO_PENTIUM_F00F_HACK + has_f00f_bug = 1; +#endif strcat(cpu_model, "Pentium"); /* nb no space */ break; case 0x600: Index: machdep.c =================================================================== RCS file: /usr/home/sef/CVS-kernel/sys/i386/i386/machdep.c,v retrieving revision 1.2 diff -u -r1.2 machdep.c --- machdep.c 1997/03/01 05:36:35 1.2 +++ machdep.c 1997/11/15 19:04:20 @@ -1002,6 +1002,12 @@ ssd->ssd_gran = sd->sd_gran; } +#ifndef NO_PENTIUM_F00F_HACK +struct gate_descriptor *t_idt; +unsigned char hack_idt[PAGE_SIZE * 3]; +extern int has_f00f_bug; +#endif + void init386(first) int first; @@ -1394,6 +1400,44 @@ proc0.p_addr->u_pcb.pcb_flags = 0; proc0.p_addr->u_pcb.pcb_cr3 = IdlePTD; } + +#ifndef NO_PENTIUM_F00F_HACK +void f00f_hack(void); +SYSINIT(f00f_hack, SI_SUB_INTRINSIC, SI_ORDER_FIRST, f00f_hack, NULL); + +void +f00f_hack(void) { + struct region_descriptor r_idt; + unsigned char *tmp; + int i; + vm_offset_t vp; + unsigned *pte; + + if (!has_f00f_bug) + return; + + printf("Intel Pentium F00F detected, installing workaround\n"); + + r_idt.rd_limit = sizeof(idt) - 1; + + tmp = (unsigned char*)roundup2((unsigned)hack_idt, PAGE_SIZE); + tmp += PAGE_SIZE - (7*8); /* Put seven entries in lower page */ + t_idt = (struct gate_descriptor *)tmp; + for (i = 0; i < NIDT; i++) { + t_idt[i] = idt[i]; + if (t_idt != (struct gate_descriptor*)tmp) { + printf("t_idt changed! i = %d\n", i); + t_idt = (struct gate_descriptor*)tmp; + } + } + r_idt.rd_base = (int) t_idt; + lidt(&r_idt); + vp = trunc_page(t_idt); + pte = (unsigned *)vtopte(vp); + *pte = *pte & ~PG_V; /* Mark page as not present */ + invlpg(vp); +} +#endif /* NO_PENTIUM_F00F_HACK */ /* * The registers are in the frame; the frame is in the user area of Index: trap.c =================================================================== RCS file: /usr/home/sef/CVS-kernel/sys/i386/i386/trap.c,v retrieving revision 1.2 diff -u -r1.2 trap.c --- trap.c 1997/03/01 05:36:37 1.2 +++ trap.c 1997/11/15 23:37:27 @@ -133,6 +133,13 @@ static void userret __P((struct proc *p, struct trapframe *frame, u_quad_t oticks)); +#ifndef NO_PENTIUM_F00F_HACK +extern struct gate_descriptor *t_idt; +extern int has_f00f_bug; +static int f00f_traps[] = { T_DIVIDE, T_TRCTRAP, T_NMI, T_BPTFLT, + T_OFLOW, T_BOUND, T_PRIVINFLT }; +#endif + static inline void userret(p, frame, oticks) struct proc *p; @@ -188,7 +195,7 @@ #ifdef DEBUG u_long eva; #endif - +restart: type = frame.tf_trapno; code = frame.tf_err; @@ -254,6 +261,8 @@ case T_PAGEFLT: /* page fault */ i = trap_pfault(&frame, TRUE); + if (i == -2) + goto restart; if (i == -1) return; if (i == 0) @@ -504,6 +513,7 @@ eva = rcr2(); va = trunc_page((vm_offset_t)eva); + if (va < VM_MIN_KERNEL_ADDRESS) { vm_offset_t v; vm_page_t mpte; @@ -599,6 +609,24 @@ eva = rcr2(); va = trunc_page((vm_offset_t)eva); +#ifndef NO_PENTIUM_F00F_HACK + if (has_f00f_bug && + (eva >= (unsigned int)t_idt) && + (eva <= (unsigned int)(((unsigned char*)t_idt) + 7*8))) { + int nr; + unsigned char inst; + nr = (eva - (unsigned int)t_idt)/8; + inst = fubyte(frame->tf_eip); + frame->tf_trapno = f00f_traps[nr]; + if (inst == 0xcc || inst == 0xce || inst == 0xcf) { + frame->tf_eip++; + } + if (inst == 0x62) { + frame->tf_eip += 2; + } + return -2; + } +#endif if (va >= KERNBASE) { /* * Don't allow user-mode faults in kernel address space. From owner-freebsd-hackers Mon Nov 17 11:03:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03867 for hackers-outgoing; Mon, 17 Nov 1997 11:03:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03817 for ; Mon, 17 Nov 1997 11:02:40 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id OAA03050 for ; Mon, 17 Nov 1997 14:07:54 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 17 Nov 1997 14:07:54 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: Re: Status of patch? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk in my defense of my make world question to all, i've rebuilt a kernel and had some of the programs that access kernel variables stop working until i re-made them. that is why i would like to do both a kernel make and 'make world' at the same time when the source trees are from the same 'batch' :P thank you for the information though, i'm glad to hear that the pentium fix's effect on performance will be very small. -Alfred > Make world doesn't rebuild the kernel. > > On Mon, 17 Nov 1997, Alfred Perlstein wrote: > > > i'm about to do a 'make world' and remake my kernel too, i was wondering > > if and what has been done to the kernel to fix the 'f00f' bug? > > > > i don't want to rebuild everything if there has been no fix for the 'f00f' > > bug. > > > > what kind of performance impact are we talking about with the fix? > > > > i was also wondering if any of the alternative fixes people have brought > > up seem to work? > > > > thank you, > > > > .________________________________________________________________________ __ _ > > |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" > > |perlsta@sunyit.edu --"who was that masked admin?" > > |http://www.cs.sunyit.edu/~perlsta > > : > > ' > > > > > > > > Ben > > "You have your mind on computers, it seems." > > From owner-freebsd-hackers Mon Nov 17 11:51:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA08078 for hackers-outgoing; Mon, 17 Nov 1997 11:51:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA08068 for ; Mon, 17 Nov 1997 11:51:41 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA08325 for ; Mon, 17 Nov 1997 11:43:29 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd008320; Mon Nov 17 11:43:23 1997 Message-ID: <34709DE2.ABD322C@whistle.com> Date: Mon, 17 Nov 1997 11:41:22 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: FreeBSD based box wins prize at COMDEX! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of course we're thrilled at Whsitle, but I think the FreeBSD Community as a whole should take a little bow and pat itself on the back, for producing such a great base from which we could work! Great work.. keep it up. We're doing what we can to make sure it's not a one-way flow.. (unlike some of our competitors I might add (you listenning iplanet, freegate, gnatbox?)) julian p.s We're a bit annoyed that NT even got mentionned in OUR award.. grrrrr (seems that any IP based network is now called an 'NT network' in some circles.. (Microsoft invented IP didn't it? ) The main page: http://www.zdnet.com/pccomp/features/excl0198/mvp97/mvp97.html Whistle InterJet: http://www.zdnet.com/pccomp/features/excl0198/mvp97/storage/whistle_interjet.html -- Text from award-- Winner Networking Hardware Whistle InterJet 100 Whistle Communications Forget signing up for a crash course in network engineering, and don't waste your money hiring a professional. The Whistle InterJet 100 plugs your company's small network into the Net in minutes. This one-box wonder delivers Internet e-mail, Web browsing, Web publishing, and firewall protection to everyone on the network. All you need is a Windows NT network, a phone line, and an ISP account. Putting your net on the Net doesn't get any easier than this. From owner-freebsd-hackers Mon Nov 17 12:28:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11199 for hackers-outgoing; Mon, 17 Nov 1997 12:28:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11146 for ; Mon, 17 Nov 1997 12:27:56 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id PAA05034; Mon, 17 Nov 1997 15:27:44 -0500 (EST) From: "John S. Dyson" Message-Id: <199711172027.PAA05034@dyson.iquest.net> Subject: Re: Status of patch? In-Reply-To: from Alfred Perlstein at "Nov 17, 97 08:32:32 am" To: perlsta@cs.sunyit.edu (Alfred Perlstein) Date: Mon, 17 Nov 1997 15:27:44 -0500 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein said: > i'm about to do a 'make world' and remake my kernel too, i was wondering > if and what has been done to the kernel to fix the 'f00f' bug? > There are people working fairly aggressively on the problem. > > i don't want to rebuild everything if there has been no fix for the 'f00f' > bug. > The fix isn't in the tree yet, however, if you are running an ISP or shell machine and NEED the fix now, the SEF fix is likely the right way to go for now. I wouldn't apply any fixes unless you really need them yet. > > what kind of performance impact are we talking about with the fix? > Probably barely measurable. > > i was also wondering if any of the alternative fixes people have brought > up seem to work? > So far, it appears that the Intel-suggested approach is the safest and most reliable today. That can change, but I think that everyone agrees that the standard fix is ugly, and people are still looking at alternatives for inclusion into the official sources. There are some other, innovative approaches being tried. The Intel-suggested approach has some negative impact on some of the esoteric features of FreeBSD, and will require mods in various parts of the kernel. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Nov 17 12:33:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11813 for hackers-outgoing; Mon, 17 Nov 1997 12:33:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11808; Mon, 17 Nov 1997 12:33:15 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id MAA23407; Mon, 17 Nov 1997 12:32:47 -0800 (PST) Message-ID: <19971117123246.37655@micron.mini.net> Date: Mon, 17 Nov 1997 12:32:46 -0800 From: Jonathan Mini To: "Jordan K. Hubbard" Cc: Jonathan Mini , jkh@FreeBSD.ORG, sos@FreeBSD.dk, hackers@FreeBSD.ORG Subject: Re: VESA VBE 1.2 and 2.0 library Reply-To: Jonathan Mini References: <19971116042103.28008@micron.mini.net> <8157.879769359@jkh.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <8157.879769359@jkh.cdrom.com>; from Jordan K. Hubbard on Mon, Nov 17, 1997 at 04:22:39AM -0800 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Commit privileges would be helpful, although not a requirement by any means > . > > It really depends on how you want me to contribute my work. > > > > (Aside from the fact that it would be cool to have commit privleges) > > Heh. Well, I'll tell you what. No one has objected to this idea, but > Soren is also wanting to have a little oversight here anyway since > much of this will be in his corner of the system and for that, you > might as well have him review and commit it anyway since that'll be > the shortest distance between two points for that particular model. > Once you're up to speed and he's eager to get out of the loop, I'll > transition you to full committer status and you can simply maintain > and extend this work on your own. Sound reasonable? Yes. > > Jordan -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Mon Nov 17 12:43:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA12628 for hackers-outgoing; Mon, 17 Nov 1997 12:43:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA12590; Mon, 17 Nov 1997 12:43:21 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id NAA14731; Mon, 17 Nov 1997 13:43:20 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd014726; Mon Nov 17 13:43:18 1997 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA26135; Mon, 17 Nov 1997 13:43:15 -0700 (MST) From: Terry Lambert Message-Id: <199711172043.NAA26135@usr07.primenet.com> Subject: Re: need an Alpha-based machine To: sprice@hiwaay.net (Steve Price) Date: Mon, 17 Nov 1997 20:43:15 +0000 (GMT) Cc: alpha@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Steve Price" at Nov 16, 97 02:44:29 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anybody out there in FreeBSD-land have a spare > Alpha-based machine that they would be willing to > loan/sell? > > I want to contribute to getting the FreeBSD Alpha > port going. I'm not (yet) much of a kernel hacker, > but I have been going through NetBSD's Alpha tree > trying to shoehorn it into our tree. > > Yes, I know that pilfering NetBSD's tree may not be > the right way to go about it, but at least it will > give us a reference implementation within our four > walls that we can play around with. I've been taking the same approach, with time out for my move, so I haven't really done anything recently. I'm using a Multia, and not the "official" porting platform (there is no documentation for the "official" platform). You can obtain a Multia rather cheaply from www.onsale.com, if you are willing to wait for the interest to wane (it gets bumped by postings like this one -- might as well not compete with other FreeBSD'ers. ;-)). I got mine for less that $400. If you have a PS/2 keyboard (it came with a mouse) and a VGA monitor and 32M or so of memory, and an external SCSI disk (all lying around, at my place), then you can have a working Alpha pretty cheaply. Actually, I use an external JAZZ drive and switch it between my Alpha, my HP300, and a PPC603 (Motorola PowerStack system). You might want to consider the new Syquest, or the the newer Syquest that is either out (or will be in a few days/weeks) that is to compete with the 2G JAZZ. I have a problem with My JAZZ drive in that you can't install NT or Windows 95 on the things unless you have an Adaptec SCSI controller and tell the BIOS to pretend it's a fixed disk (the NT/95 removable media driver corrupts data paged in from a removable device), so I would recommend the Syquest (this is based on a manufacturer rep claiming you can install NT/95 on their drive without the same problem, so the claim may not be valid). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Nov 17 14:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20234 for hackers-outgoing; Mon, 17 Nov 1997 14:20:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from spokane.vmunix.com (mmayo.neon.sentex.ca [207.245.212.243]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20226 for ; Mon, 17 Nov 1997 14:20:30 -0800 (PST) (envelope-from mark@spokane.vmunix.com) Received: (from mark@localhost) by spokane.vmunix.com (8.8.7/8.8.7) id RAA01905; Mon, 17 Nov 1997 17:22:05 -0500 (EST) Message-ID: <19971117172204.06768@vmunix.com> Date: Mon, 17 Nov 1997 17:22:04 -0500 From: Mark Mayo To: hackers@freebsd.org Subject: Partitioning suggestions? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e X-Operating-System: FreeBSD 2.2-STABLE i386 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all. I just got a new 6.5GB SCSI disk, and I'm going to reinstall FreeBSD (probably tonight, maybe in a few days). I'm wondering what people suggest for slicing up a large disk like that to make it easier to do system upgrades, make worlds, etc.. I'm thinking something like this: Mount FS Size -------------------- / UFS 50M swap 128M /tmp UFS 80M (nosuid) /var UFS 65M /usr UFS 2.5G /srcs UFS 1G /home UFS the rest This is my home machine, so a small /var is fine. /home on a seperate parition so I can nuke the rest and keep my files. I may make /usr larger, since I really don't have much in my home directory.. (right now only a couple hundred MB, but I'm quite tight on space). I plan on holding the FreeBSD, NetBSD, and Linux sources on /srcs - I'm going to install NetBSD on the old 1.2GB SCSI disk. That way I can link /usr/obj in FreeBSD to the NetBSD /usr/tmp/obj and vice versa to get /usr and /obj on different spindles for both FreeBSD and NetBSD builds. Does this seems reasonable, or should I be leaving more/less room in places? TIA for any tips, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hackers Mon Nov 17 14:54:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22071 for hackers-outgoing; Mon, 17 Nov 1997 14:54:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22064 for ; Mon, 17 Nov 1997 14:53:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id OAA03988; Mon, 17 Nov 1997 14:53:49 -0800 (PST) Message-Id: <199711172253.OAA03988@rah.star-gate.com> To: Julian Elischer cc: hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: FreeBSD based box wins prize at COMDEX! In-reply-to: Your message of "Mon, 17 Nov 1997 11:41:22 PST." <34709DE2.ABD322C@whistle.com> Date: Mon, 17 Nov 1997 14:53:48 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Most Cool!!!! I feel like going home and opening a bottle of champagne 8) Amancio From owner-freebsd-hackers Mon Nov 17 14:58:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22354 for hackers-outgoing; Mon, 17 Nov 1997 14:58:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22338 for ; Mon, 17 Nov 1997 14:58:47 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id OAA23587; Mon, 17 Nov 1997 14:58:28 -0800 (PST) Message-ID: <19971117145827.11042@micron.mini.net> Date: Mon, 17 Nov 1997 14:58:27 -0800 From: Jonathan Mini To: Mark Mayo Cc: hackers@freebsd.org Subject: Re: Partitioning suggestions? Reply-To: Jonathan Mini References: <19971117172204.06768@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19971117172204.06768@vmunix.com>; from Mark Mayo on Mon, Nov 17, 1997 at 05:22:04PM -0500 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mark Mayo stands accused of saying: > [ ... snip ... ] > I'm thinking something like this: > > Mount FS Size > -------------------- > / UFS 50M > swap 128M > /tmp UFS 80M (nosuid) > /var UFS 65M > /usr UFS 2.5G > /srcs UFS 1G > /home UFS the rest Were I you, I'd merge the /tmp filesystem into swap, and then mount your /tmp via MFS. You will notice much better performance on /tmp. Also, personally, I always use a 32M root, especially when I have a /var filesystem, and have never had space problems with root. > [ ... snip ... ] -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Mon Nov 17 15:27:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA23857 for hackers-outgoing; Mon, 17 Nov 1997 15:27:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA23840 for ; Mon, 17 Nov 1997 15:27:14 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id SAA03592 for ; Mon, 17 Nov 1997 18:32:21 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 17 Nov 1997 18:32:20 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: Re: Partitioning suggestions? In-Reply-To: <19971117145827.11042@micron.mini.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i wasn't going to get into this thread, however i feel that a 32meg root is NOT a good idea, 50megs is nice, but with 32megs i've come across problems of filling the root partition. -Alfred > Were I you, I'd merge the /tmp filesystem into swap, and then mount your > /tmp via MFS. You will notice much better performance on /tmp. Also, > personally, I always use a 32M root, especially when I have a /var filesystem, > and have never had space problems with root. > > > [ ... snip ... ] > > -- > Jonathan Mini Ingenious Productions > Software Development P.O. Box 5693, > Eugene, Or. 97405 > > "A child of five could understand this! Quick -- Fetch me a child of five." > From owner-freebsd-hackers Mon Nov 17 15:53:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25439 for hackers-outgoing; Mon, 17 Nov 1997 15:53:52 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA25434 for ; Mon, 17 Nov 1997 15:53:48 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id PAA23909; Mon, 17 Nov 1997 15:52:56 -0800 (PST) Message-ID: <19971117155255.02937@micron.mini.net> Date: Mon, 17 Nov 1997 15:52:55 -0800 From: Jonathan Mini To: Alfred Perlstein Cc: hackers@freebsd.org Subject: Re: Partitioning suggestions? Reply-To: Jonathan Mini References: <19971117145827.11042@micron.mini.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Alfred Perlstein on Mon, Nov 17, 1997 at 06:32:20PM -0500 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein stands accused of saying: > i wasn't going to get into this thread, however i feel that a 32meg root > is NOT a good idea, 50megs is nice, but with 32megs i've come across > problems of filling the root partition. I stand corrected. The MFS /tmp is still a good idea, just remeber that MFS goes away when you reboot. :) > -Alfred > > > Were I you, I'd merge the /tmp filesystem into swap, and then mount your > > /tmp via MFS. You will notice much better performance on /tmp. Also, > > personally, I always use a 32M root, especially when I have a /var filesystem, > > and have never had space problems with root. > > > > > [ ... snip ... ] > > > > -- > > Jonathan Mini Ingenious Productions > > Software Development P.O. Box 5693, > > Eugene, Or. 97405 > > > > "A child of five could understand this! Quick -- Fetch me a child of five." > > > -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Mon Nov 17 16:21:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27205 for hackers-outgoing; Mon, 17 Nov 1997 16:21:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27107 for ; Mon, 17 Nov 1997 16:20:00 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id TAA01983; Mon, 17 Nov 1997 19:19:45 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180019.TAA01983@dyson.iquest.net> Subject: Re: Partitioning suggestions? In-Reply-To: from Alfred Perlstein at "Nov 17, 97 06:32:20 pm" To: perlsta@cs.sunyit.edu (Alfred Perlstein) Date: Mon, 17 Nov 1997 19:19:45 -0500 (EST) Cc: hackers@freebsd.org Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein said: > i wasn't going to get into this thread, however i feel that a 32meg root > is NOT a good idea, 50megs is nice, but with 32megs i've come across > problems of filling the root partition. > I am fond of 120-200MB root partitions. Disk is cheap, and as you say, running out of root space (or any other partition) is not a fun thing. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Nov 17 16:49:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA28930 for hackers-outgoing; Mon, 17 Nov 1997 16:49:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA28922 for ; Mon, 17 Nov 1997 16:49:38 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id BAA11114 for hackers@FreeBSD.ORG; Tue, 18 Nov 1997 01:49:32 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id BAA07016; Tue, 18 Nov 1997 01:43:32 +0100 (CET) (envelope-from roberto) Message-ID: <19971118014332.38551@keltia.freenix.fr> Date: Tue, 18 Nov 1997 01:43:32 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? References: <19971117145827.11042@micron.mini.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Alfred Perlstein on Mon, Nov 17, 1997 at 06:32:20PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3818 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Alfred Perlstein: > i wasn't going to get into this thread, however i feel that a 32meg root > is NOT a good idea, 50megs is nice, but with 32megs i've come across > problems of filling the root partition. With what ? The smallest "/" is, the better. Of course, none of "/var", "/tmp" and "/compat" are in it... And I have at least three kernels in "/", sorry 4. -r-xr-xr-x 1 root wheel 1048619 Nov 15 20:07 /kernel* -rwxr-xr-x 1 root wheel 1046412 Oct 24 22:11 /kernel.null* -r-xr-xr-x 1 root wheel 1043718 Nov 8 23:41 /kernel.old* -rwxr-xr-x 1 root wheel 1137770 Nov 15 20:07 /kernel.snd* Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 25247 17118 6110 74% / /dev/sd0s2e 199631 86891 96770 47% /usr /dev/sd0s2f 501231 293469 167664 64% /usr/local /dev/sd2s4a 99791 51033 40775 56% /var /dev/sd0s2g 399287 159068 208277 43% /users /dev/sd2s4e 144343 90137 42659 68% /news /dev/sd0s2h 698831 457930 184995 71% /src /dev/sd2s4d 705343 406069 242847 63% /spare /dev/sd0s2d 851149 593299 189759 76% /work /dev/sd12a 1033212 596966 353590 63% /x /dev/sd2s4f 988393 130248 779074 14% /y -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #49: Sat Nov 15 20:03:33 CET 1997 From owner-freebsd-hackers Mon Nov 17 17:52:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04387 for hackers-outgoing; Mon, 17 Nov 1997 17:52:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04378 for ; Mon, 17 Nov 1997 17:52:42 -0800 (PST) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id RAA26833; Mon, 17 Nov 1997 17:56:57 -0800 (PST) Date: Mon, 17 Nov 1997 17:56:57 -0800 (PST) From: Dmitry Kohmanyuk Message-Id: <199711180156.RAA26833@dog.farm.org> To: jfieber@indiana.edu (John Fieber) Cc: freebsd-hackers@freebsd.org Subject: Re: Netscape 4.04 Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > On Sun, 16 Nov 1997, Eric J. Schwertfeger wrote: > Has anyone else had problems with it? As with 4.03b8, I > occasionally had problems with it hanging on exit. I thought I > would make sure there wasn't anything around from older versions > causing problems so I moved my ~/.netscape directory out of the > way. I have the same problem (run once, than have it spinning in a loop consuming lots of CPU with no graphic output). solution (kludgy, but works): #!/bin/sh export XCMSDB; XCMSDB=/dev/null exec /usr/local/communicator/netscape $@ I got this info forwarded to somebody inside Netscape so hopefully they would fix it some day. -- I don't suffer from insanity. I enjoy every minute of it. From owner-freebsd-hackers Mon Nov 17 18:02:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05095 for hackers-outgoing; Mon, 17 Nov 1997 18:02:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ha1.rdc1.nj.home.com (siteadm@ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA05087 for ; Mon, 17 Nov 1997 18:02:29 -0800 (PST) (envelope-from luomat@luomat.peak.org) Received: from luomat.peak.org ([24.2.83.40]) by ha1.rdc1.nj.home.com (Netscape Mail Server v2.02) with ESMTP id AAA18088 for ; Mon, 17 Nov 1997 18:02:26 -0800 Received: (from luomat@localhost) by luomat.peak.org (8.8.5/8.8.7) id VAA04479 for hackers@FreeBSD.ORG; Mon, 17 Nov 1997 21:02:31 -0500 (EST) Message-Id: <199711180202.VAA04479@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.1mach v148) X-Image-URL: http://www.peak.org/~luomat/next/luomat@peak.org.tiff In-Reply-To: <199711180019.TAA01983@dyson.iquest.net> X-Nextstep-Mailer: Mail 4.1mach (Enhance 2.0b6.5) Received: by NeXT.Mailer (1.148.RR) From: Timothy J Luoma Date: Mon, 17 Nov 97 21:02:27 -0500 To: hackers@FreeBSD.ORG Subject: NBQ: Why partitioning? (was: Re: Partitioning suggestions?) References: <199711180019.TAA01983@dyson.iquest.net> X-Image-URL-Disclaimer: hey, it's off my student ID, gimme a break ;-) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As someone who has only booted FBSD twice (before it failed... not surprising since I am not sure what I am doing) I've been trying to learn by lurking,,,, and I'm still not understanding why FBSD and some other UN*X'es put /var /usr /tmp &etc on different partitions. To me it seems like it is just asking for wasted space here and running out of space there. What am I missing? Thanks TjL From owner-freebsd-hackers Mon Nov 17 18:14:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05855 for hackers-outgoing; Mon, 17 Nov 1997 18:14:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA05704 for ; Mon, 17 Nov 1997 18:11:49 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by earth.mat.net (8.8.8/8.6.12) with ESMTP id VAA18014; Mon, 17 Nov 1997 21:11:22 -0500 (EST) Message-Id: <199711180211.VAA18014@earth.mat.net> Date: Mon, 17 Nov 1997 21:11:18 -0500 (EST) From: chuckr@glue.umd.edu Subject: Re: Partitioning suggestions? To: roberto@keltia.freenix.fr cc: hackers@FreeBSD.ORG In-Reply-To: <19971118014332.38551@keltia.freenix.fr> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 18 Nov, Ollivier Robert wrote: > According to Alfred Perlstein: >> i wasn't going to get into this thread, however i feel that a 32meg root >> is NOT a good idea, 50megs is nice, but with 32megs i've come across >> problems of filling the root partition. > > With what ? The smallest "/" is, the better. Of course, none of "/var", > "/tmp" and "/compat" are in it... And I have at least three kernels in "/", > sorry 4. > > -r-xr-xr-x 1 root wheel 1048619 Nov 15 20:07 /kernel* > -rwxr-xr-x 1 root wheel 1046412 Oct 24 22:11 /kernel.null* > -r-xr-xr-x 1 root wheel 1043718 Nov 8 23:41 /kernel.old* > -rwxr-xr-x 1 root wheel 1137770 Nov 15 20:07 /kernel.snd* > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0a 25247 17118 6110 74% / > /dev/sd0s2e 199631 86891 96770 47% /usr > /dev/sd0s2f 501231 293469 167664 64% /usr/local > /dev/sd2s4a 99791 51033 40775 56% /var > /dev/sd0s2g 399287 159068 208277 43% /users > /dev/sd2s4e 144343 90137 42659 68% /news > /dev/sd0s2h 698831 457930 184995 71% /src > /dev/sd2s4d 705343 406069 242847 63% /spare > /dev/sd0s2d 851149 593299 189759 76% /work > /dev/sd12a 1033212 596966 353590 63% /x > /dev/sd2s4f 988393 130248 779074 14% /y Absolutely no sarcasm here, I'm honestly curious why you'd want to have so many filesystems. I would think that (unless you were a major invoestor in a drive manufacturer) you'd be exaggerating the chance of having one be overloaded, and then need to either reformat or swap out to another, bigger disk, much more often than I. A friend who programs a lot shocked me by saying that she regularly installs just one big partition, for /,/usr/ the whole works. I'd never done that myself, but I've been trying to come up with some solid reason why it's a bad idea. > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #49: Sat Nov 15 20:03:33 CET 1997 > -- ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Nov 17 18:21:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06641 for hackers-outgoing; Mon, 17 Nov 1997 18:21:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from chess.inetspace.com (chess.inetspace.com [206.50.163.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06615 for ; Mon, 17 Nov 1997 18:21:15 -0800 (PST) (envelope-from kgor@chess.inetspace.com) Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.8.5) id UAA05442; Mon, 17 Nov 1997 20:19:59 -0600 Date: Mon, 17 Nov 1997 20:19:59 -0600 Message-Id: <199711180219.UAA05442@chess.inetspace.com> From: "Kent S. Gordon" To: jdp@polstra.com CC: hackers@FreeBSD.ORG In-reply-to: <199711160506.VAA26780@austin.polstra.com> (message from John Polstra on Sat, 15 Nov 1997 21:06:36 -0800) Subject: Re: Problems with BusTek SCSI controller and CD-ROM Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "jdp" == John Polstra writes: > I have an old ISA bus machine with a BusTek (now BusLogic) BT542 > SCSI controller. It works fine with the two hard drives that I > have installed. But when I added a Plextor 4x CD-ROM drive > today, it caused the system to hang during the probe of the > controller. The last message on the console before the hang is: > bt0: reading board settings, dma=5, int=11 > If I wait several minutes, it eventually gives a further message > "bt0: not taking commands!". Then it drops into the kernel > debugger. I had similar problems with a VL Bus machine and a BusLogic BT445. At least your will boot with hard drives only. It had only two hard drive and no other SCSI devices. It stopped working on -current in April. It work in 2.2.2, but not 2.2.5 (It seemed to break somewhere in 2.2-STABLE around June). I could not figure out a solution, so the machine had to migrate to Linux :(. I posted to -hackers (and submitted a PR), but got no responce. I looked at the source and did not see any changes that looked like the source of the problem. The scsi code did not change a lot during the period that broke my machine. > I get identical failures with a -current system from late > September and with a 2.2.2 boot floppy. > It's not a problem with termination, and I've tried rearranging > the devices on the SCSI bus without results. The power-up > Messages from the controller's BIOS show that it recognizes the > CD-ROM drive as well as both hard disks. And booting from hard > disk (up until the hang) works fine. Also, if I boot from a DOS > floppy with the appropriate drivers on it, DOS talks to all the > devices without problems. > So this seems to be a problem specific to FreeBSD. Any ideas? > John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. > Seattle, Washington USA "Self-knowledge is always bad news." -- > John Barth -- Kent S. Gordon Architect iNetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com From owner-freebsd-hackers Mon Nov 17 18:49:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08509 for hackers-outgoing; Mon, 17 Nov 1997 18:49:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: (from hsu@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08502 for hackers; Mon, 17 Nov 1997 18:49:07 -0800 (PST) (envelope-from hsu) Date: Mon, 17 Nov 1997 18:49:07 -0800 (PST) From: Jeffrey Hsu Message-Id: <199711180249.SAA08502@hub.freebsd.org> To: hackers Subject: Re: Netscape 4.04 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Any news on an AWT 1.1 patch for Netscape for FreeBSD? From owner-freebsd-hackers Mon Nov 17 19:27:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11322 for hackers-outgoing; Mon, 17 Nov 1997 19:27:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA11309 for ; Mon, 17 Nov 1997 19:27:11 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id TAA24132; Mon, 17 Nov 1997 19:25:33 -0800 (PST) Message-ID: <19971117192532.37475@micron.mini.net> Date: Mon, 17 Nov 1997 19:25:32 -0800 From: Jonathan Mini To: Timothy J Luoma Cc: hackers@FreeBSD.ORG Subject: Re: NBQ: Why partitioning? (was: Re: Partitioning suggestions?) Reply-To: Jonathan Mini References: <199711180019.TAA01983@dyson.iquest.net> <199711180202.VAA04479@luomat.peak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199711180202.VAA04479@luomat.peak.org>; from Timothy J Luoma on Mon, Nov 17, 1997 at 09:02:27PM -0500 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Timothy J Luoma stands accused of saying: > > As someone who has only booted FBSD twice (before it failed... not > surprising since I am not sure what I am doing) I've been trying to learn by > lurking,,,, and I'm still not understanding why FBSD and some other UN*X'es > put /var /usr /tmp &etc on different partitions. > > To me it seems like it is just asking for wasted space here and > running out of space there. > > What am I missing? How many times have you had to reinstall Window 95 becuase one part of it got currupted? While FreeBSD is much more stable, accidents due happen (power failures and the like) If one filesystem is corrutped, less is lost. Not to metion that you should be making backups at any rate. Other than recovery from a crash, there are two other considerations : - performance : /usr /tmp and /var are often used at the same time (assuming a multi-user system) and if they are seperate drives, things move along faster. - size : Rember how (ahem) long-lived UNIX is. When you need to have a x Meg system ,and your drives are x/4 Megs in size, you've got to split it into several filesystems. There are your reasons. :) I'm sure there are probably more. > > Thanks > TjL > -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Mon Nov 17 19:35:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA12151 for hackers-outgoing; Mon, 17 Nov 1997 19:35:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA12142 for ; Mon, 17 Nov 1997 19:35:26 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id WAA00619; Mon, 17 Nov 1997 22:35:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180335.WAA00619@dyson.iquest.net> Subject: Re: Partitioning suggestions? In-Reply-To: <199711180211.VAA18014@earth.mat.net> from "chuckr@glue.umd.edu" at "Nov 17, 97 09:11:18 pm" To: chuckr@glue.umd.edu Date: Mon, 17 Nov 1997 22:35:06 -0500 (EST) Cc: roberto@keltia.freenix.fr, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk chuckr@glue.umd.edu said: > > A friend who programs a lot shocked me by saying that she regularly > installs just one big partition, for /,/usr/ the whole works. I'd > never done that myself, but I've been trying to come up with some solid > reason why it's a bad idea. > I have a huge number of partitions (usually use three per disk at the 4-8GB.) The only major things that I see is wrong with one big partition are some security issues, and the inability to have a read-only root. I don't generally like partitions less than 500MB for work space. I'd actually like to look into a mini-root system, to virtually eliminate the need for a fixit floppy. That mini-root would not normally be mounted, but would be there when you need it. I sure wish that floppies were always 100MB :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Nov 17 20:19:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA15754 for hackers-outgoing; Mon, 17 Nov 1997 20:19:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA15748 for ; Mon, 17 Nov 1997 20:19:30 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-132.HiWAAY.net [208.147.148.132]) by fly.HiWAAY.net (8.8.7/8.8.6) with ESMTP id WAA25095 for ; Mon, 17 Nov 1997 22:19:26 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id WAA05810 for ; Mon, 17 Nov 1997 22:19:25 -0600 (CST) Message-Id: <199711180419.WAA05810@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org From: David Kelly Subject: Re: Partitioning suggestions? In-reply-to: Message from chuckr@glue.umd.edu of "Mon, 17 Nov 1997 21:11:18 EST." <199711180211.VAA18014@earth.mat.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Nov 1997 22:19:25 -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A friend who programs a lot shocked me by saying that she regularly > installs just one big partition, for /,/usr/ the whole works. I'd > never done that myself, but I've been trying to come up with some solid > reason why it's a bad idea. We regularly do that at work with Irix and Solaris. When users totally fill the fs we simply shrug and say, "Yeah, so the whole system comes to a halt? What do you expect? Don't fill the disks to 100%". Actually the systems don't come to a complete halt and I usually learn of the full filesystem only when I read the syslog. Needless to say this isn't an ISP or typical server application. But one where somebody is likely to make a stink because they see 100M somewhere they can't write. Actually 4G root filesystems have worked pretty well for us. By splitting the disk into filesystems you establish limits where one kind of data is protected from other kinds of data. And you do it a bit more simply than the quota solution. A small root partition with the critical tools was once very useful for rescuing the rest of the system in the event of a nasty crash. Found out a couple of weeks ago that Solaris 2.5.1 with the C2 auditing module *won't boot single user*. Only way in is by booting off the CDROM. Also the more filesystems you have the less data you lose if you trash an entire filesystem. Since I converted my personal stuff from Linux to FreeBSD a couple of years ago I haven't had to deal with that problem. Hmmm. Still thinking about what to do with my new 9G disk: nospam: {145} df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 31775 19481 9752 67% / /dev/sd0s2f 1875679 1174571 551054 68% /usr /dev/sd0s2e 31775 2474 26759 8% /var procfs 4 4 0 100% /proc /dev/sd1s2a 38991 6 35866 0% /r /dev/sd1s2f 1017327 662103 273838 71% /r/usr /dev/sd1s2g 2427552 1 2233347 0% /r/usr1 /dev/sd1s2h 2427552 1 2233347 0% /r/usr2 /dev/sd1s2d 2427552 1 2233347 0% /r/usr3 /dev/sd1s2e 127151 1 116978 0% /r/var Think I'll make my new / (see /r above) about 64M. Think I like the above partitioning otherwise. No partition is much larger than I can get on a 4mm DAT without compression. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hackers Mon Nov 17 20:55:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18160 for hackers-outgoing; Mon, 17 Nov 1997 20:55:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18150 for ; Mon, 17 Nov 1997 20:55:00 -0800 (PST) (envelope-from craig@ProGroup.COM) Received: from ProGroup.COM (tuna.progroup.com [206.24.122.5]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id UAA08667; Mon, 17 Nov 1997 20:54:36 -0800 (PST) Received: from progroup.com by ProGroup.COM (SMI-8.6/SMI-SVR4) id UAA07541; Mon, 17 Nov 1997 20:54:06 -0800 Message-ID: <34711F6E.BCCE8D9B@progroup.com> Date: Mon, 17 Nov 1997 20:54:06 -0800 From: "Craig W. Shaver" Reply-To: craig@ProGroup.COM Organization: Productivity Group, Inc. X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: Partitioning suggestions? References: <199711180211.VAA18014@earth.mat.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk chuckr@glue.umd.edu wrote: > del ... > > A friend who programs a lot shocked me by saying that she regularly > installs just one big partition, for /,/usr/ the whole works. I'd > never done that myself, but I've been trying to come up with some solid > reason why it's a bad idea. > del ... > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- I think the original reasoning among sysadmins was to break up the file systems so that they could be backed up to tape easily. Tape size being somewhat on the small side at one time. So 60mb to 150mb file systems were the norm. I like to put / and /usr under 1 2g disk. That includes /var /tmp /etc .... Then I put development and databases on other disks. The poster of the original question had a 6.5g disk. I might be likely to partition that out to 2g for the base of / /usr /etc ... and then use the rest for development or whatever. The idea of using MFS mounted /tmp is appealing. How do you do that? Is there some documentation on that? Thanks, -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-hackers Mon Nov 17 21:06:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19289 for hackers-outgoing; Mon, 17 Nov 1997 21:06:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19277 for ; Mon, 17 Nov 1997 21:06:08 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id VAA12334; Mon, 17 Nov 1997 21:05:13 -0800 (PST) Message-ID: <19971117210512.32531@hydrogen.nike.efn.org> Date: Mon, 17 Nov 1997 21:05:12 -0800 From: John-Mark Gurney To: "John S. Dyson" Cc: chuckr@glue.umd.edu, roberto@keltia.freenix.fr, hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? References: <199711180211.VAA18014@earth.mat.net> <199711180335.WAA00619@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199711180335.WAA00619@dyson.iquest.net>; from John S. Dyson on Mon, Nov 17, 1997 at 10:35:06PM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John S. Dyson scribbled this message on Nov 17: > I'd actually like to look into a mini-root system, to virtually eliminate the > need for a fixit floppy. That mini-root would not normally be mounted, but would > be there when you need it. I sure wish that floppies were always 100MB :-). why not dedicate 32megs of another hard drive to a backup root? I've now decided to put a 32meg root on all hard drives even if they aren't going to normally boot from... (what's 32megs from 2gigs? :) ) -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Nov 17 21:09:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19660 for hackers-outgoing; Mon, 17 Nov 1997 21:09:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19619 for ; Mon, 17 Nov 1997 21:09:04 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id AAA00959; Tue, 18 Nov 1997 00:07:23 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180507.AAA00959@dyson.iquest.net> Subject: Re: Partitioning suggestions? In-Reply-To: <19971117210512.32531@hydrogen.nike.efn.org> from John-Mark Gurney at "Nov 17, 97 09:05:12 pm" To: gurney_j@resnet.uoregon.edu Date: Tue, 18 Nov 1997 00:07:22 -0500 (EST) Cc: toor@dyson.iquest.net, chuckr@glue.umd.edu, roberto@keltia.freenix.fr, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John-Mark Gurney said: > John S. Dyson scribbled this message on Nov 17: > > I'd actually like to look into a mini-root system, to virtually eliminate the > > need for a fixit floppy. That mini-root would not normally be mounted, but would > > be there when you need it. I sure wish that floppies were always 100MB :-). > > why not dedicate 32megs of another hard drive to a backup root? I've > now decided to put a 32meg root on all hard drives even if they aren't > going to normally boot from... (what's 32megs from 2gigs? :) ) > That works well also. It would be kind of nice to come up with an automatic mini-root setup. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Nov 17 21:10:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19845 for hackers-outgoing; Mon, 17 Nov 1997 21:10:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19823 for ; Mon, 17 Nov 1997 21:10:24 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id UAA02037 for ; Mon, 17 Nov 1997 20:39:01 -0800 (PST) Date: Mon, 17 Nov 1997 20:39:01 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: Please Verify This. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would I be correct to say that buffered I/O is necessarily blocking. In other words I noticed that FNONBLOCK flags cannot? be looked at in a strategy routine. Either the block read returns something or it returns an error, or it times out and returns an error. There is no way to look @ fflags though from a strategy routine, correct? From owner-freebsd-hackers Mon Nov 17 21:45:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA21785 for hackers-outgoing; Mon, 17 Nov 1997 21:45:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA21775 for ; Mon, 17 Nov 1997 21:45:25 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xXgMS-00066Q-00; Mon, 17 Nov 1997 21:38:08 -0800 Date: Mon, 17 Nov 1997 21:38:06 -0800 (PST) From: Tom To: "Craig W. Shaver" cc: hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <34711F6E.BCCE8D9B@progroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 17 Nov 1997, Craig W. Shaver wrote: > chuckr@glue.umd.edu wrote: > > > del ... > > > > A friend who programs a lot shocked me by saying that she regularly > > installs just one big partition, for /,/usr/ the whole works. I'd > > never done that myself, but I've been trying to come up with some solid > > reason why it's a bad idea. > > > I think the original reasoning among sysadmins was to break up the file > systems so that they could be backed up to tape easily. Tape size being > somewhat on the small side at one time. So 60mb to 150mb file systems > were the norm. I like to put / and /usr under 1 2g disk. That includes Huh? Backup tools have supported multiple tapes for a _long_ time. The real reason, is compartmentalizing functions. If one file system fills up, it doesn't bring down the entire system. For example, if '/' has no space, you won't even be able to change passwords. You want specific functions to be isolated to prevent such problems. This is only a real concern on server systems. On a desktop system, one big filesystem works ok. ... > The idea of using MFS mounted /tmp is appealing. How do you do that? > Is there some documentation on that? Yes, the manpages. The appeal factor depends on what you use /tmp for. I'll to like to quotas on /tmp to make sure users don't use it all it up. I also, use "-pipe" on gcc, so the compiler doesn't even use /tmp for anything. > Thanks, > > -- > Craig Shaver (craig@progroup.com) (415)390-0654 > Productivity Group POB 60458 Sunnyvale, CA 94088 > > Tom From owner-freebsd-hackers Mon Nov 17 22:22:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA24518 for hackers-outgoing; Mon, 17 Nov 1997 22:22:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA24507 for ; Mon, 17 Nov 1997 22:22:46 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id WAA12689; Mon, 17 Nov 1997 22:22:11 -0800 (PST) Message-ID: <19971117222210.05319@hydrogen.nike.efn.org> Date: Mon, 17 Nov 1997 22:22:10 -0800 From: John-Mark Gurney To: craig@ProGroup.COM Cc: hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? References: <199711180211.VAA18014@earth.mat.net> <34711F6E.BCCE8D9B@progroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <34711F6E.BCCE8D9B@progroup.com>; from Craig W. Shaver on Mon, Nov 17, 1997 at 08:54:06PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Craig W. Shaver scribbled this message on Nov 17: [...] > The idea of using MFS mounted /tmp is appealing. How do you do that? > Is there some documentation on that? well.. I have this in my /etc/fstab: /dev/sd1b /tmp mfs rw,nosuid,-s=524288 0 0 but be careful... normally you can only have a 64meg mfs unless you increase the datasize limit to be larger than 64megs... I build my kernel with: options "MAXDSIZ=(512*1024*1024)" options "DFLDSIZ=(512*1024*1024)" so that I can have: Filesystem 1K-blocks Used Avail Capacity Mounted on mfs:26 254319 62731 171243 27% /tmp note that the -s option specifies the size of the fs in 512byte blocks... there is an option to have the mfs /tmp backed by a file (so if you reboot your machine, your /tmp contents are saved, not sure if this hurts performane or not) which helps prevents lose of data... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Nov 17 22:37:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA25464 for hackers-outgoing; Mon, 17 Nov 1997 22:37:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25459 for ; Mon, 17 Nov 1997 22:37:12 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.7) with ESMTP id WAA14130; Mon, 17 Nov 1997 22:37:08 -0800 (PST) (envelope-from jdp) Message-Id: <199711180637.WAA14130@austin.polstra.com> To: "Kent S. Gordon" cc: hackers@FreeBSD.ORG Subject: Re: Problems with BusTek SCSI controller and CD-ROM In-reply-to: Your message of "Mon, 17 Nov 1997 20:19:59 CST." <199711180219.UAA05442@chess.inetspace.com> Date: Mon, 17 Nov 1997 22:37:08 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I had similar problems with a VL Bus machine and a BusLogic BT445. > At least your will boot with hard drives only. It had only two hard > drive and no other SCSI devices. It stopped working on -current > in April. It work in 2.2.2, but not 2.2.5 (It seemed to break > somewhere in 2.2-STABLE around June). Hmm, that's interesting. Mine doesn't work even with the 2.2.2 boot floppy. I have a feeling our problems are different. I've about decided that the firmware on my controller is just too old. I think I bought it in 1991, almost before there even were any SCSI CD-ROM drives in the PC market. I found an old DOS driver in the museum section of the BusLogic web site. That made it work OK under DOS (CD-ROM too). I used that to install Windows 95 (don't ask). But after Windows 95 was running, it didn't see the CD-ROM drive any more. I updated the driver to the current Windows 95 version, which killed the whole thing even for hard disk accesses. I guess I'll just turn that old machine into a firewall or a -current trashbox. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Nov 17 22:41:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA25789 for hackers-outgoing; Mon, 17 Nov 1997 22:41:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25781 for ; Mon, 17 Nov 1997 22:41:08 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id BAA02513; Tue, 18 Nov 1997 01:40:08 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180640.BAA02513@dyson.iquest.net> Subject: Re: Please Verify This. In-Reply-To: from "Jamil J. Weatherbee" at "Nov 17, 97 08:39:01 pm" To: jamil@trojanhorse.ml.org (Jamil J. Weatherbee) Date: Tue, 18 Nov 1997 01:40:08 -0500 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jamil J. Weatherbee said: > > > Would I be correct to say that buffered I/O is necessarily blocking. > In other words I noticed that FNONBLOCK flags cannot? be looked at in a > strategy routine. Either the block read returns something or it returns > an error, or it times out and returns an error. There is no way to look @ > fflags though from a strategy routine, correct? > I think that you are right, but our new AIO code (does/will) support the POSIX.4 (or POSIX.1b) features. I have better implemented code than in -current locally, but will not commit it until it is done. It also doesn't work with SMP yet. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Mon Nov 17 22:54:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA26544 for hackers-outgoing; Mon, 17 Nov 1997 22:54:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA26532 for ; Mon, 17 Nov 1997 22:54:32 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id BAA09940; Tue, 18 Nov 1997 01:54:30 -0500 (EST) Date: Tue, 18 Nov 1997 01:54:30 -0500 (EST) Message-Id: <199711180654.BAA09940@dyson.iquest.net> X-Newsreader: knews 0.9.8 From: root@dyson.iquest.net (John S. Dyson) Subject: Re: Better F00F workaround (well, maybe...) (fwd) To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Path: szdc!super.zippo.com!lotsanews.com!www.nntp.primenet.com!globalcenter0!news.primenet.com!nntp.primenet.com!newsxfer3.itd.umich.edu!newbabylon.rs.itd.umich.edu!joust.rs.itd.umich.edu!hasdi From: hasdi@umich.edu (Hasdi Rodzmann Hashim) Newsgroups: comp.sys.intel Subject: Re: Better F00F workaround (well, maybe...) Date: 18 Nov 1997 05:03:57 GMT Organization: University of Michigan ITD News Server Lines: 26 Message-ID: <64r7jt$lqo$1@newbabylon.rs.itd.umich.edu> References: <346F1F9B.1E53@geocities.com> NNTP-Posting-Host: joust.rs.itd.umich.edu X-Newsreader: TIN [version 1.2 PL2] Xref: szdc comp.sys.intel:72644 Mark Morgan Lloyd (mark_tbu@cix.compulink.co.uk) wrote: : > Consructing a simple system where the handlers for exceptions 0..6 : > (alignment as in the Intel workaround) just do an invlpg : > [first_idt_page] : > enabled me to reliably trap any mutation of the f00fc7c8 (There are : > more than 8 possible mutations BTW since you can add prefixes in : > addition : > to the LOCK without changing anything to the matter.) : Yeees... so what you're saying is make sure /every/ exception handler : invalidates the page containing the IDT before IRETing? I'd have thought : that would have worked except in cases where the user can install his own : x86 exception handlers (rather than Unix-style traps). You know, IA-32 supports non-cachable page. If this works, it will be easier to make the IDT entry 0..6 on a non-cachable page. Beats rewriting the exception handler. CYA. Hasdi (a happy AMD486 user) Outdated f0 bug homepage: http://www-personal.umich.edu/~hasdi/pentium_lock.htm From owner-freebsd-hackers Mon Nov 17 22:55:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA26607 for hackers-outgoing; Mon, 17 Nov 1997 22:55:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA26592 for ; Mon, 17 Nov 1997 22:54:58 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id HAA26351 for hackers@FreeBSD.ORG; Tue, 18 Nov 1997 07:54:44 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id HAA08048; Tue, 18 Nov 1997 07:26:16 +0100 (CET) (envelope-from roberto) Message-ID: <19971118072616.63159@keltia.freenix.fr> Date: Tue, 18 Nov 1997 07:26:16 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? References: <19971118014332.38551@keltia.freenix.fr> <199711180211.VAA18014@earth.mat.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199711180211.VAA18014@earth.mat.net>; from chuckr@glue.umd.edu on Mon, Nov 17, 1997 at 09:11:18PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3818 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to chuckr@glue.umd.edu: > Absolutely no sarcasm here, I'm honestly curious why you'd want to have > so many filesystems. I would think that (unless you were a major Old habits die hard. I have space enough so it is not a problem and I like to have things in their own filsystems. It has IMO several advantages: - you have have different policies for area (e.g. the area for /usr/obj is mounted "async,noatime" and I don't want "/usr" to be "async"), - it is easier to recover when you have a problem (I have 7.6 GB of disk and parallel fsck works fine when I have a crash), - it is easier to backup, remember that our dump doesn't support subdirectories, - having a big "/" for everything opens the door for problems (losing a file in /tmp could result of failing reboot), - it helps when you want to implement quotas (I don't use them personnally), - I like it that way :-) > invoestor in a drive manufacturer) you'd be exaggerating the chance of > having one be overloaded, and then need to either reformat or swap out > to another, bigger disk, much more often than I. This is a possibility but I generally size them large enough. When I need space, "nullfs" & symlinks are my friends. I generally buy a disk a year and the new disk is often the one I'll boot from and it gives me the opportunity to resize partitions when I install the new disk. > A friend who programs a lot shocked me by saying that she regularly > installs just one big partition, for /,/usr/ the whole works. I'd > never done that myself, but I've been trying to come up with some solid > reason why it's a bad idea. I like things neatly separated, thanks. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #49: Sat Nov 15 20:03:33 CET 1997 From owner-freebsd-hackers Mon Nov 17 23:59:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01514 for hackers-outgoing; Mon, 17 Nov 1997 23:59:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from super.zippo.com (perry.zippo.com [207.211.168.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01505 for ; Mon, 17 Nov 1997 23:59:40 -0800 (PST) (envelope-from reyesf@super.zippo.com) Received: (from reyesf@localhost) by super.zippo.com (8.8.6/8.8.7) id XAA20331; Mon, 17 Nov 1997 23:59:39 -0800 (PST) Message-Id: <199711180759.XAA20331@super.zippo.com> From: "Francisco Reyes" To: "hackers@freebsd.org" Date: Tue, 18 Nov 97 02:59:09 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Optimizing HD I/O. What size to use to read/write? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am going to start working on a program which will be heavy on I/O. I was wondering what would be a good size to read/write at a time. What is the minimun block size FreeBSD allocates? 4K? 8K? Is it HD dependent? From owner-freebsd-hackers Tue Nov 18 00:04:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA01878 for hackers-outgoing; Tue, 18 Nov 1997 00:04:43 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA01872 for ; Tue, 18 Nov 1997 00:04:39 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z14) with ESMTP id JAA23069 for ; Tue, 18 Nov 1997 09:04:30 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id JAA18647 for freebsd-hackers@freefall.cdrom.com; Tue, 18 Nov 1997 09:04:36 +0100 (MET) Date: Tue, 18 Nov 1997 09:04:36 +0100 (MET) From: Christoph Kukulies Message-Id: <199711180804.JAA18647@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: cvsup glitch Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Running a cvsup gave me a mysterious error: TreeList failed: Error in "/usr/sup/src-all/checkouts.cvs:.": 19769: Invalid modTime # cd /usr/sup/src-all # ls -l total 2800 -rw-r--r-- 1 root wheel 819244 Nov 11 04:37 #cvs.cvsup-27653.0 -rw-rw-r-- 1 root wheel 2020310 Nov 18 08:53 checkouts.cvs:. # Well, I removed both files. Probably not a good idea. Now cvsup is taking a deep breath for a while. I suspect it's fetching everything now. Anyway, what should I do in case this happens again? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Tue Nov 18 01:19:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA06447 for hackers-outgoing; Tue, 18 Nov 1997 01:19:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA06441 for ; Tue, 18 Nov 1997 01:19:17 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id BAA24569; Tue, 18 Nov 1997 01:17:04 -0800 (PST) Message-ID: <19971118011704.41903@micron.mini.net> Date: Tue, 18 Nov 1997 01:17:04 -0800 From: Jonathan Mini To: "John S. Dyson" Cc: gurney_j@resnet.uoregon.edu, chuckr@glue.umd.edu, roberto@keltia.freenix.fr, hackers@freebsd.org Subject: Re: Partitioning suggestions? Reply-To: Jonathan Mini References: <19971117210512.32531@hydrogen.nike.efn.org> <199711180507.AAA00959@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199711180507.AAA00959@dyson.iquest.net>; from John S. Dyson on Tue, Nov 18, 1997 at 12:07:22AM -0500 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson stands accused of saying: > [ ... snip ... ] > > why not dedicate 32megs of another hard drive to a backup root? I've > > now decided to put a 32meg root on all hard drives even if they aren't > > going to normally boot from... (what's 32megs from 2gigs? :) ) > > > That works well also. It would be kind of nice to come up with an automatic > mini-root setup. In /etc/rc.local, or daily, or weekly, or manually : dump 1af - / | restore f - /dev/other_root_partition -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Tue Nov 18 01:31:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA07363 for hackers-outgoing; Tue, 18 Nov 1997 01:31:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA07328 for ; Tue, 18 Nov 1997 01:31:45 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id EAA01111; Tue, 18 Nov 1997 04:31:04 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180931.EAA01111@dyson.iquest.net> Subject: Re: Optimizing HD I/O. What size to use to read/write? In-Reply-To: <199711180759.XAA20331@super.zippo.com> from Francisco Reyes at "Nov 18, 97 02:59:09 am" To: reyesf@super.zippo.com Date: Tue, 18 Nov 1997 04:31:04 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Francisco Reyes said: > I am going to start working on a program which will be heavy on I/O. > I was wondering what would be a good size to read/write at a time. > > What is the minimun block size FreeBSD allocates? 4K? 8K? Is it HD > dependent? > Depends on the filesystem configuration. On a 8K filesystem with 1K fragments, the filesystem will normally allocate 8K blocks, except for the last one, which will be some number of fragments. The kind of I/O dictates the blocksize that you want to use. There is generally little use of using more than a (8K:1K or 16K:2K) filesystem. The clustering code takes care of changing small sequential transfers into larger (up to 64K for now) device I/O. If you are talking about random I/O, in a database type situation, you might want to bypass filesystems all together. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Tue Nov 18 01:32:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA07495 for hackers-outgoing; Tue, 18 Nov 1997 01:32:35 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA07484 for ; Tue, 18 Nov 1997 01:32:30 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.5) id EAA01115; Tue, 18 Nov 1997 04:32:24 -0500 (EST) From: "John S. Dyson" Message-Id: <199711180932.EAA01115@dyson.iquest.net> Subject: Re: Optimizing HD I/O. What size to use to read/write? In-Reply-To: <199711180759.XAA20331@super.zippo.com> from Francisco Reyes at "Nov 18, 97 02:59:09 am" To: reyesf@super.zippo.com Date: Tue, 18 Nov 1997 04:32:24 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Francisco Reyes said: > I am going to start working on a program which will be heavy on I/O. > I was wondering what would be a good size to read/write at a time. > > What is the minimun block size FreeBSD allocates? 4K? 8K? Is it HD > dependent? > One more comment, if you are doing sequential I/O, you really don't want to do read/writes less than 4K-8K. You are likely into diminishing returns beyond 8K. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Tue Nov 18 02:45:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA12331 for hackers-outgoing; Tue, 18 Nov 1997 02:45:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA12303 for ; Tue, 18 Nov 1997 02:45:12 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA14244; Tue, 18 Nov 1997 04:44:00 -0600 Message-Id: <3.0.3.32.19971118043736.006d7d48@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 18 Nov 1997 04:37:36 -0600 To: Jonathan Mini From: Tony Overfield Subject: Re: >64MB Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:58 AM 11/10/97 -0800, Jonathan Mini wrote: > 1) The boot blocks are a part of the boot process, meaning that > they should function in real mode (being part of initializing the > processor) and the sole function of this code is to load the kernel > into memory. (this is bogus, IMO) Well, I don't think it's bogus, and Terry seems to want this one, if I haven't mistaken his statements. This has certain ideological advantages with respect to portability and multiple platform development. > 2) The boot blocks are a small microkernel who's sole purpose is to > load the main kernel (or possible a second micro-kernel which handles > config : read three stage boot) into memory and give it control. To > do this, it needs to have two contexts : > a) a protected context with mappings for the kernel, and > b) a vm86 context for talking to the BIOS. Yes, this is one possible approach, but I still think it offers no extra value over what we have now. Please don't assume I don't understand these issues. Regardless, I don't really care what approach is taken, so long as it is implemented correctly. Also remember that I'm referring to boot time code only. > The boot blocks shouldn't be constantly hopping from Real Mode to Protected >Mode over and over again! This is insane, No, this is done all the time. Switching between modes is fast, small and easy (excluding the '286, of course). >and the processor (especially on a >P/Pro system) will be spending more time jumping in and out of Real Mode than >it will spend loading the kernel from disk. This is absurd on its face (at least it should be) and it's very easy to _prove_ as much. I'm not sure why you want to repeat this error. >it would break most DPMI or EMS servers, most >notably being Microsoft's EMM386 and Quarterdeck's QEMM. If the BIOS _did_ try >and mess with the machine state it wuold break Windows 95 and most people >running DOS. Somehow I doubt someone would break the spec in this way. I'm quite familiar with the various things in a BIOS that can break Windows 95, DOS, QEMM, EMM386, etc. Real mode has PE=0, so code that wants to hijack the processor state can know that "ring 0 run state" is irrelevant. I did say that I knew of no BIOS that does this, but it is possible, without breaking any of the programs you mentioned, except for, possibly, the "big limits" code which started all of this. Fortunately, there's nothing to be gained by adding "big limits" code into a bootloader, so that whole discussion is tangential, unnecessary, and uninteresting. BTW, I assume the "spec" that you speak of is the defacto (and imaginary) "must run all code without bugs" spec that I am forced to use (among the many others that do exist). ;-) >> I have seen instances where a timer or an asynchronous disk interrupt >> (yes, in DOS) has occurred that resulted in a "real-mode" task-switch >> and an interrupt-time reentry into INT 13h. If the INT 13h function >> were to reload the descriptors before returning, you would lose your >> big limits at an essentially unpredictable time. (NCACHE.EXE for you >> die-hard types.) > > Hello, we're not running DOS. We're talking about boot code from the >BIOS. Not TSR's or DOS device drivers here. (just us chickens) Umm, no need to condescend, I can follow all the details. I was stating generic, additional reasons to avoid the "big limits" real mode. I chose an actual, verifiable example in an effort to avoid speculation. I can speculate with high confidence, but to be sure, I often choose to use actual facts, even when they aren't identical to the topic at hand. >> I simply don't believe 1) that the booloader does enough of these to >> matter, and 2) that anyone really cares about the performance of code >> that runs for less than one second per boot (on my systems, at least). >> On every system I've seen, the bootloader spends most of that second >> either waiting for I/O, or doing I/O. > > The point isn't really performance, but rather that we should be running in >protected mode ASAP. Especially since we don't have a 16bit compiler. But it already goes into protected mode ASAP. A 16-bit compiler is not needed, though the code could be a little smaller if we had one. >> > There are four reasons : >> >> [Four good, irrelevant, and deleted reasons...] > > These reasons _AREN'T_ irrelevent, simply because they are the major >reasons for having a PROTECTED mode in the first place. Which makes those >reasons solely good and deleted. Yay. All four points are good, as I noted, but they just don't apply. Reason 1 is irrelevant because there's no VM in the bootloader. Reason 2 is irrelevant because the bootloader doesn't take over the hardware IRQ's from the BIOS. Reason 3 is irrelevant because the bootloader doesn't make, or need to make, multiple concurrent BIOS calls. Reason 4 is irrelevant because the claim that the BIOS is untrustworthy during boot time is ridiculous and not even worthy of debate, IMHO. > THe VM86 facility you are talking about will ONLY exist after the kernel >has 'taken over' the machine's state. So here you finally agree with me? Like I said, don't use vm86() mode until the kernel takes over. Use real mode and protected mode, as appropriate, until the kernel takes over. >> After the bootloader loads the kernel into memory, it jumps into it. >> The part that bothers me is that people want that instant in time to be >> a magical instant where you cannot call the BIOS in real mode anymore >> after having done so several thousands of times up to that point. Just >> because it's now running the "kernel" doesn't mean anything other than >> a jump (lret, in this case) has actually occurred. I was arguing that >> there is no reason for things to work differently (i.e. no real need >> for vm86()), until after the booting process has been completed and the >> kernel "proper" begins execution. > > Several 'magical' things HAVE happened to the machine at this point. One >of the most important is that the system has 'assumed' control of the ENTIRE >machine at this point in time. All IRQ's all memory mappings, and the status >of all devices. (read: probe pass will come soon, if it hasn't already >happened) No. Read my stuff again. You don't seem to see it. The kernel doesn't instantly take off probing devices, running tasks, and dispatching cron jobs the instant you first jump into it. There's a significant amount of code that runs, just as the bootloader does, before the magical point where the kernel actually takes over. > You are saying that after having spent all of the time up to this point >setting this situation up, that we should _give_ _up_ control and return it >to the BIOS temporarily? No, not at all. I'm just saying that we should spend a few more cycles "setting this situation up". Don't take over all control until it's appropriate and we don't urgently need anything else from the real-mode BIOS. In this $(subject) topic, the kernel would like to know how much extended memory is present so that it can use it. Why not call the extended memory map BIOS functions as the last several BIOS calls before taking over the system? After all, we just called it a few thousand times to get the kernel into memory. What's a few more going to hurt? Then, the kernel can take over, use all the memory, start probing and attaching devices, and ultimately create a vm86() for those fancy things that need it after the kernel is running. > This I don't understand. I hope it's more clear now. - Tony From owner-freebsd-hackers Tue Nov 18 02:45:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA12344 for hackers-outgoing; Tue, 18 Nov 1997 02:45:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA12308 for ; Tue, 18 Nov 1997 02:45:15 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA14257; Tue, 18 Nov 1997 04:44:10 -0600 Message-Id: <3.0.3.32.19971118044330.0071582c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 18 Nov 1997 04:43:30 -0600 To: Jonathan Mini From: Tony Overfield Subject: Re: >64MB Cc: hackers@freebsd.org In-Reply-To: <19971110022540.34863@micron.mini.net> References: <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> <199711070205.MAA00455@word.smith.net.au> <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:25 AM 11/10/97 -0800, Jonathan Mini wrote: >Tony Overfield stands accused of saying: >> At 12:34 PM 11/7/97 +1030, Mike Smith wrote: >> >The kernel is loaded above 1M, so you would have to be careful to make >> >sure that your BIOS calls came out of the lowest 64K. That could be >> >done with a dispatcher in locore.s though. >> >> I assume you mean the lowest 640K. But yes, a dispatcher would have >> to exist down there, with a buffer large enough for your INT 13h calls >> and etc. > > THat's not true, the call needs to come from the lower 1087K, or the lower >1024K (1M) if you want to be really nice. The nominal term "lowest 640K" is often used to refer to this real-mode accessible user memory. In the context of this discussion, he could have meant either the "lowest 640K" or the lower 64K of the second MB. I guessed that he probably just dropped a zero from the 640K, when in fact he was talking about the other. It makes no difference, the important point was that the address needs to be real-mode compatible. >(calculate the linear adress for >FFFF:FFFF - it's (64K - 1) above 1M) "THat's not true." To be correct, you should have said "(64K - 16)." Yes, that's picky, but I though you were being picky too. ;-) >> If you can't trust the BIOS after the kernel is in memory, how can you >> trust it to load the kernel into memory? While the kernel is still >> "booting...", the BIOS should be safe enough to call in real-mode. > > The reason you can't trust the BIOS always is because once FreeBSD touches a >device, the BIOS doesn't know it and might assume that the device is in a >different state than it really is. The solution to this is to ensure that the >BIOS and FreeBSD never touch the same devices. > The only real way to ensure this is if FreeBSD doesn't touch devices, or >the BIOS doesn't touch devices. Of course I can't fault the simple logic of this answer, but if you had read my questions more carefully, you should have realized that I'm talking strictly about the time _before_ FreeBSD touches the devices. Once again, there's a certain time before the devices are touched and after the bootloader jumps into the kernel where it would be advantageous to make a few BIOS calls. I simply suggested doing so then, while it's still easy to do and while it can't possibly conflict with anything that FreeBSD has done up to that point. As an added bonus, when it is done at this certain time, it doesn't increase space consumption by the bootloader, which is a very important consideration. That's my last attempt. I apologize for not giving up sooner. I simply can't tolerate the unusual level of effort that seems to be required to be properly understood around here. - Tony From owner-freebsd-hackers Tue Nov 18 02:45:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA12358 for hackers-outgoing; Tue, 18 Nov 1997 02:45:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA12304 for ; Tue, 18 Nov 1997 02:45:13 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA14260; Tue, 18 Nov 1997 04:44:10 -0600 Message-Id: <3.0.3.32.19971118043753.0071582c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 18 Nov 1997 04:37:53 -0600 To: Terry Lambert From: Tony Overfield Subject: Re: >64MB Cc: hackers@FreeBSD.ORG In-Reply-To: <199711101908.MAA11282@usr05.primenet.com> References: <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 07:08 PM 11/10/97 +0000, Terry Lambert wrote: >> If you can't trust the BIOS after the kernel is in memory, how can you >> trust it to load the kernel into memory? While the kernel is still >> "booting...", the BIOS should be safe enough to call in real-mode. > >Three problems: > >1) You can't trust a *user process* to call the BIOS (it's not > the sword that's the problem, it's what the peasent *does* > with the sword that makes us make them illegal for everyone > but the knights and the king). I didn't realize the bootloader had user processes. >2) The BIOS INT 13 code has a 2G limit on partition size, unless > you can guarantee all the devices in your machine support > LBA mode (even then the limit on LBA is lower than the limit > in FreeBSD... 64bits >> 32 bits). This appears to be completely wrong. First, I'm talking about bootloaders. I assume you agree that the bootloader should use INT 13. Second, the INT 13 interface (without LBA mode) is limited to 8.4 GB, not 2 GB. Third, the limit for LBA INT 13 is 64-bits worth of sectors, or 2^73 bytes. This should last us for several more years. >3) Gate A20 (now you will argue that Dell hardware doesn't use > BIOS code that expects a wrap in memory). Of course I will! I doubt any BIOS has ever been made that needs it. You'll no doubt cite some heap-o-crud(tm), obsolete system made by some long defunct company, probably with some ironic name like "Leading Edge" or something.... ;-) - Tony, who disclaims any proprietary interest in the marks and names of others. From owner-freebsd-hackers Tue Nov 18 02:45:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA12374 for hackers-outgoing; Tue, 18 Nov 1997 02:45:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA12328 for ; Tue, 18 Nov 1997 02:45:20 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA14263; Tue, 18 Nov 1997 04:44:12 -0600 Message-Id: <3.0.3.32.19971118043823.0071582c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Tue, 18 Nov 1997 04:38:23 -0600 To: Terry Lambert From: Tony Overfield Subject: Re: >64MB Cc: hackers@FreeBSD.ORG In-Reply-To: <199711102016.NAA13623@usr05.primenet.com> References: <3.0.3.32.19971110035805.006cab94@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 08:16 PM 11/10/97 +0000, Terry Lambert wrote: >> No, it's not impossible to do, it's just useless to do, IMHO, for the >> job at hand. I don't see any reason to turn the bootloader into a >> vm86() program that plays games like this just to copy to memory above >> 1 MB, since it's far easier to just switch modes and copy it directly. > >I think you are missing the point. There's no argument that the boot >loader should be a vm86() program. Ok, but it sure seemed like some people were arguing for this... >> 2) The boot blocks are a small microkernel who's sole purpose is to >> load the main kernel (or possible a second micro-kernel which handles >> config : read three stage boot) into memory and give it control. To >> do this, it needs to have two contexts : >> a) a protected context with mappings for the kernel, and >> b) a vm86 context for talking to the BIOS. >The only argument is that it should >do the minimum possible work that can possibly be done before handing >the machine over to the kernel. I agree with this, but change "minimum possible" to "minimum necessary." >This is because the more the boot loader does, the more you will have >to rewrite for each new platform you port to, and the less it does, the >less you will have to rewrite. Well, where ever it's written, it will need rewriting. It's still system-dependant code, even if it lives in the kernel. I do understand that most folks would rather hack kernel code than bootloader code, however. >The point of accessing system information from the kernel where possible >is to make the boot-loader/kernel interconnect as architecturally >abstract as it can possibly be, so that the majority of the startup >code can be shared between architectures. The procedural abstraction, >if not the functional. Your kernel could obtain it from the bootinfo struct, if that's appropriate for the platform. It's still "obtained" by the kernel. >> >There are several other you can do using suspend/resume instructions and >> >similar tricks >> >> Suspend instruction? I could have sworn I knew them all by heart. > >There are "ICEBP" equivalents on non-Intel processors to do register >and processor state saves and restores; typically, they are used by >laptops for thjings like "suspend to disk" modes. Right, no such instruction for 94.736% (irresponsible, wild guess) of the CPU's in the world. Nice to know you're thinking about compatibility and portability. ;-) ;-) Actually, a laptop BIOS will simply poke itself into SMI mode to accomplish these things. It's much simpler that way, and it works on Intel's CPU's and many others. At least that's what I've always done. - Tony From owner-freebsd-hackers Tue Nov 18 03:03:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA13465 for hackers-outgoing; Tue, 18 Nov 1997 03:03:50 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA13459 for ; Tue, 18 Nov 1997 03:03:42 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id DAA25120; Tue, 18 Nov 1997 03:03:09 -0800 (PST) Message-ID: <19971118030308.27709@micron.mini.net> Date: Tue, 18 Nov 1997 03:03:08 -0800 From: Jonathan Mini To: Tony Overfield Cc: Jonathan Mini , hackers@freebsd.org Subject: Re: >64MB Reply-To: Jonathan Mini References: <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> <199711070205.MAA00455@word.smith.net.au> <3.0.3.32.19971110034509.0069e370@bugs.us.dell.com> <19971110022540.34863@micron.mini.net> <3.0.3.32.19971118044330.0071582c@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <3.0.3.32.19971118044330.0071582c@bugs.us.dell.com>; from Tony Overfield on Tue, Nov 18, 1997 at 04:43:30AM -0600 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tony Overfield stands accused of saying: [ ... snip ... ] > The nominal term "lowest 640K" is often used to refer to this real-mode > accessible user memory. In the context of this discussion, he could have > meant either the "lowest 640K" or the lower 64K of the second MB. I > guessed that he probably just dropped a zero from the 640K, when in fact > he was talking about the other. It makes no difference, the important > point was that the address needs to be real-mode compatible. Point taken, but I wanted to stress that any memory address readable from the classic 'real mode' addressing method is valid. > >(calculate the linear adress for > >FFFF:FFFF - it's (64K - 1) above 1M) > > "THat's not true." To be correct, you should have said "(64K - 16)." > Yes, that's picky, but I though you were being picky too. ;-) Ooops. :) Actually. If you want to be REALLY picky, it's (64K - 1) - 16, but hey... > >> If you can't trust the BIOS after the kernel is in memory, how can you > >> trust it to load the kernel into memory? While the kernel is still > >> "booting...", the BIOS should be safe enough to call in real-mode. > > > > The reason you can't trust the BIOS always is because once FreeBSD touches a > >device, the BIOS doesn't know it and might assume that the device is in a > >different state than it really is. The solution to this is to ensure that the > >BIOS and FreeBSD never touch the same devices. > > The only real way to ensure this is if FreeBSD doesn't touch devices, or > >the BIOS doesn't touch devices. > > Of course I can't fault the simple logic of this answer, but if you had > read my questions more carefully, you should have realized that I'm talking > strictly about the time _before_ FreeBSD touches the devices. In which case, my answer still stands : Until FreeBSD touches a device, the BIOS is a safe method of accessing it. > Once again, there's a certain time before the devices are touched and after > the bootloader jumps into the kernel where it would be advantageous to make > a few BIOS calls. I simply suggested doing so then, while it's still > easy to do and while it can't possibly conflict with anything that FreeBSD > has done up to that point. As an added bonus, when it is done at this > certain time, it doesn't increase space consumption by the bootloader, > which is a very important consideration. I agree -- In fact, I am a STRONG proponent of using the BIOS for various serives until the FreeBSD drivers can 'take over.' It makes sense for loading the kernel, it makes sense for a mutli-stage dynamically configured kernel (Something which I persoanlly need, and I know would be benificial to many other people as well), and it makes sense for a lot of other things, one example being the system console. If you ever want to see a cheap hack in the FreeBSD kernel, look to the system console code. It's a device, only it's probed and attached right off the bat, but only specific devices are probed there, which is defined by a C file rather than the kernel config. And to make things better, the device is probed and attached TWICE, rather than once. :) But wait! It gets BETTER! Not only does the kernel do a special probe/attach run for the system console, but it also creates a device major/minor for it! (look at /dev/cons :) ) But.. it's not a tty front-end for the kernel's entry point into the console, it's just a wrapper around the (assumed valid) tty interface from the console driver! (e.g. syscons) Which means that it doesn't have an independant tty struct. This is bad mana. The system console is an excellent example of how the BIOS services should be used to access a device before the FreeBSD device gets probed and attached in its proper order. If FreeBSD's special console code simply acted as a wrapper around the kernel's entry-point into the system console driver, and used the BIOS (or some code from the bootloader, to appease those of you who are now screaming 'but what about serial consoles?') for console I/O until the much-better-and-more-robust system console driver comes online. (Personally, I think that the system console behaviour should be layered, so as to remove a lot of these problems. Come on guys, the 'system console' is not ONE, but two or often THREE devices, and we need to treat it that way) > That's my last attempt. I apologize for not giving up sooner. > I simply can't tolerate the unusual level of effort that seems > to be required to be properly understood around here. I know the feeling... :( -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Tue Nov 18 03:24:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA14395 for hackers-outgoing; Tue, 18 Nov 1997 03:24:34 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14390 for ; Tue, 18 Nov 1997 03:24:30 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id DAA25156; Tue, 18 Nov 1997 03:23:54 -0800 (PST) Message-ID: <19971118032353.57770@micron.mini.net> Date: Tue, 18 Nov 1997 03:23:53 -0800 From: Jonathan Mini To: Tony Overfield Cc: Jonathan Mini , hackers@freebsd.org Subject: Re: >64MB Reply-To: Jonathan Mini References: <3.0.3.32.19971118043736.006d7d48@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <3.0.3.32.19971118043736.006d7d48@bugs.us.dell.com>; from Tony Overfield on Tue, Nov 18, 1997 at 04:37:36AM -0600 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tony Overfield stands accused of saying: > At 02:58 AM 11/10/97 -0800, Jonathan Mini wrote: > > 1) The boot blocks are a part of the boot process, meaning that > > they should function in real mode (being part of initializing the > > processor) and the sole function of this code is to load the kernel > > into memory. (this is bogus, IMO) > > Well, I don't think it's bogus, and Terry seems to want this one, if I > haven't mistaken his statements. This has certain ideological advantages > with respect to portability and multiple platform development. Hmm. As I read his reply, he seemed to be a proponent of setting up a vm86 TSS for the real mode code. > > 2) The boot blocks are a small microkernel who's sole purpose is to > > load the main kernel (or possible a second micro-kernel which handles > > config : read three stage boot) into memory and give it control. To > > do this, it needs to have two contexts : > > a) a protected context with mappings for the kernel, and > > b) a vm86 context for talking to the BIOS. > > Yes, this is one possible approach, but I still think it offers no extra > value over what we have now. Please don't assume I don't understand these > issues. Regardless, I don't really care what approach is taken, so long > as it is implemented correctly. Also remember that I'm referring to boot > time code only. I understand, but your second statement eludes me. You say that you don't care what approach is taken, as long as the code is implementd properly? But the approach taken to the solution is half of the implementation. A hack is still a hack, even if it is the most beutiful code within itself. > > The boot blocks shouldn't be constantly hopping from Real Mode to Protected > >Mode over and over again! This is insane, > > No, this is done all the time. Switching between modes is fast, small and > easy (excluding the '286, of course). Whether or not something is 'done all the time' is not an issue, it is still insane. > [ ... snip ... ] > I'm quite familiar with the various things in a BIOS that can break > Windows 95, DOS, QEMM, EMM386, etc. Real mode has PE=0, so code that > wants to hijack the processor state can know that "ring 0 run state" > is irrelevant. I did say that I knew of no BIOS that does this, but > it is possible, without breaking any of the programs you mentioned, > except for, possibly, the "big limits" code which started all of this. Then you should know that Win 95, QEMM, EMM386, and OS/2 (to name a few) run the processor in a vm86 task the whole time, to maintain their virtual memory mappings. (and EMS emulation) -- even when calling the BIOS. > Fortunately, there's nothing to be gained by adding "big limits" code > into a bootloader, so that whole discussion is tangential, unnecessary, > and uninteresting. In essence, you are right. This discussion is besides the point, and boring. Whether or not anything would be gained was the topic of debate, so I have to disagree. I would come up with convincing evidence, but I prefer to drop this debate. > BTW, I assume the "spec" that you speak of is the defacto (and > imaginary) "must run all code without bugs" spec that I am forced > to use (among the many others that do exist). ;-) Yes and no. THe 'spec' I speak of is from several specifications, which all boil down to the fact that once the BIOS gives the processor to the OS, it doesn't get to play hanky-panky with the machine state. > [ ... snip ... ] > >> I simply don't believe 1) that the booloader does enough of these to > >> matter, and 2) that anyone really cares about the performance of code > >> that runs for less than one second per boot (on my systems, at least). > >> On every system I've seen, the bootloader spends most of that second > >> either waiting for I/O, or doing I/O. > > > > The point isn't really performance, but rather that we should be running in > >protected mode ASAP. Especially since we don't have a 16bit compiler. > > But it already goes into protected mode ASAP. A 16-bit compiler is not > needed, though the code could be a little smaller if we had one. Ahh, but we do : /pub/FreeBSD/FreeBSD-current/ports/devel/bcc It's not that great, but it does work. > >> > There are four reasons : > >> > >> [Four good, irrelevant, and deleted reasons...] > > > > These reasons _AREN'T_ irrelevent, simply because they are the major > >reasons for having a PROTECTED mode in the first place. Which makes those > >reasons solely good and deleted. Yay. > > All four points are good, as I noted, but they just don't apply. > > Reason 1 is irrelevant because there's no VM in the bootloader. > Reason 2 is irrelevant because the bootloader doesn't take over the > hardware IRQ's from the BIOS. > Reason 3 is irrelevant because the bootloader doesn't make, or need to > make, multiple concurrent BIOS calls. > Reason 4 is irrelevant because the claim that the BIOS is untrustworthy > during boot time is ridiculous and not even worthy of debate, IMHO. I must have made that statement back when I thought that we were still talking about after-the-kernel-has-taken-control-of-the-system stage of boot, or later, such as while running the scheduler. > > THe VM86 facility you are talking about will ONLY exist after the kernel > >has 'taken over' the machine's state. > > So here you finally agree with me? Like I said, don't use vm86() mode until > the kernel takes over. Use real mode and protected mode, as appropriate, > until the kernel takes over. Why do you keep putting paren's around vm86? Are you referring to the VM86() functionality that Mike Smith is working on, or are you referring to a TSS with the vm86 adressing model? > [ ... much argument which arose from you and I thinking of different stages > of the boot provess deleted ... ] -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Tue Nov 18 05:25:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA20815 for hackers-outgoing; Tue, 18 Nov 1997 05:25:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA20810 for ; Tue, 18 Nov 1997 05:25:29 -0800 (PST) (envelope-from jamie@itribe.net) Message-Id: <199711181325.IAA24163@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Tue, 18 Nov 1997 08:23:56 -0500 (EST) From: Jamie Bowden To: chuckr@glue.umd.edu cc: hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <199711180211.VAA18014@earth.mat.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 17 Nov 1997 chuckr@glue.umd.edu wrote: > Absolutely no sarcasm here, I'm honestly curious why you'd want to have > so many filesystems. I would think that (unless you were a major > invoestor in a drive manufacturer) you'd be exaggerating the chance of > having one be overloaded, and then need to either reformat or swap out > to another, bigger disk, much more often than I. > > A friend who programs a lot shocked me by saying that she regularly > installs just one big partition, for /,/usr/ the whole works. I'd > never done that myself, but I've been trying to come up with some solid > reason why it's a bad idea. For a personal system it's fine. For a server machine, you don't want to worry about filling up /, and having everything die due to lack of disk space. On my machine at home I usually use two partitions (mostly because I have to drives). 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) From owner-freebsd-hackers Tue Nov 18 08:19:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02262 for hackers-outgoing; Tue, 18 Nov 1997 08:19:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02253 for ; Tue, 18 Nov 1997 08:19:37 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id LAA09202 for ; Tue, 18 Nov 1997 11:19:34 -0500 (EST) Date: Tue, 18 Nov 1997 11:19:33 -0500 (EST) From: Snob Art Genre To: hackers@freebsd.org Subject: Apollo Domain 660 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would anyone like an Apollo Domain 660? All you have to do is pick it up in New York City. Sorry for the off-topic post, but I wanted this community to have first crack at it. Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Tue Nov 18 08:20:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02436 for hackers-outgoing; Tue, 18 Nov 1997 08:20:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from albert.osu.cz (albert.osu.cz [195.113.106.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02251 for ; Tue, 18 Nov 1997 08:19:31 -0800 (PST) (envelope-from belkovic@albert.osu.cz) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id RAA03200 for ; Tue, 18 Nov 1997 17:20:22 +0100 (MET) Date: Tue, 18 Nov 1997 17:20:22 +0100 (MET) From: Josef Belkovics To: hackers@FreeBSD.ORG Subject: snmp agent/manager (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I look for some snmp agent and, mainly, manager. Both under FreeBSD. Manager at level as optivity. Some advice? Josef Belkovics From owner-freebsd-hackers Tue Nov 18 08:40:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03806 for hackers-outgoing; Tue, 18 Nov 1997 08:40:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03797 for ; Tue, 18 Nov 1997 08:40:52 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.7) with ESMTP id IAA17710; Tue, 18 Nov 1997 08:40:40 -0800 (PST) (envelope-from jdp) Message-Id: <199711181640.IAA17710@austin.polstra.com> To: kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: cvsup glitch In-Reply-To: <199711180804.JAA18647@gil.physik.rwth-aachen.de> References: <199711180804.JAA18647@gil.physik.rwth-aachen.de> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Tue, 18 Nov 1997 08:40:39 -0800 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199711180804.JAA18647@gil.physik.rwth-aachen.de>, Christoph Kukulies wrote: > > Running a cvsup gave me a mysterious error: > > TreeList failed: Error in "/usr/sup/src-all/checkouts.cvs:.": 19769: Invalid modTime That means that your "checkouts.cvs:." file is corrupted. It might be a good idea to run fsck soon. :-) > # cd /usr/sup/src-all > # ls -l > total 2800 > -rw-r--r-- 1 root wheel 819244 Nov 11 04:37 #cvs.cvsup-27653.0 > -rw-rw-r-- 1 root wheel 2020310 Nov 18 08:53 checkouts.cvs:. > # > > Well, I removed both files. Probably not a good idea. The one beginning with "#" is a temporary file, so don't worry about it. Since the "checkouts.cvs:." file was corrupted, you didn't have much choice but to delete it. You might possibly have fixed it with an editor, but that's not always possible if the file is badly corrupted. > Now cvsup is taking a deep breath for a while. I suspect it's > fetching everything now. It's checksumming your files in order to figure out which versions you have. It won't fetch everything again. > Anyway, what should I do in case this happens again? Next time, please save the corrupted file so that I can look at it. Every time I have seen this problem, it's been caused by a disk error or an untimely system crash or possibly a kernel bug. The corrupted files invariably have a big chunk of some completely unrelated file splatted into them, at an offset that's a multiple of the sector size. By the way, is your CVSup the latest version (15.2)? The text of the error message makes me suspect that you're running a version that's pretty old. If so, please consider upgrading. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Nov 18 09:02:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA05260 for hackers-outgoing; Tue, 18 Nov 1997 09:02:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA05250; Tue, 18 Nov 1997 09:01:57 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id JAA01396; Tue, 18 Nov 1997 09:01:56 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 18 Nov 1997 09:01:55 -0800 (PST) From: Doug White Reply-To: Doug White To: FreeBSD Questions , hackers@freebsd.org Subject: Re: FreeBSD 2.2.2 Won't Boot (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! For those of you running System Commander, here's the problem. To the boot block bashers, is there a way we can work around this? SysCommander is a pretty popular boot manager. We could either disable the partition type check or also make 0xB5 a valid system type. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major ---------- Forwarded message ---------- Date: Tue, 18 Nov 1997 01:55:12 -0500 From: Bryan Batten To: Doug White Subject: Re: FreeBSD 2.2.2 Won't Boot I last communicated with you about six weeks ago about boot problems installing FreeBSD on the 3rd primary partition on drive 0 of a 2 drive layout, using V Communications' System Commander (V2.24) as a boot manager. On Fri, 26 Sep 1997, Doug White wrote: > You're digging much deeper than I could. I think you're on your way to a solution here. Unfortunately I'm out of ideas, you're in over my > head. > > Since all Booteasy does is transfer control to another bootstrap > > program,I > > guess the next item would be to see what kind of boot program > > FreeBSD sets up in it's own partition. Any pointers to source? > > If you have the full source it's in /usr/src/mdec, or > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/boot/biosboot/ Remember that? It turns out that others are having the same problem; see the thread "System Commander problems" in newsgroup comp.unix.bsd.freebsd.misc. Anyway, here's what I've found out: After installing Free BSD 2.2.2, all attempts to boot the newly installed OS using System Commander fail with a "No bootable partition" message. I then de- installed System Commander, and re- installed FreeBSD, this time using its "Install MBR" option ... and it worked! I could boot FreeBSD. However, when I re- installed System Commander and tried to boot my newly installed FreeBSD using that, I was once again back to the "No bootable partition" message. Now, System Commander has a bad habit of ****ing around with the System Indicator byte in partition table entries (it loves to set bit 4), with the result that what was 0x09 becomes 0x19, what was 0xA5 becomes 0xB5, etc. - but that doesn't seem to bother any other OS I'm running - Linux, OS/2 Warp, MSDOS, and SCO. System Commander also provides a "Boot through MBR" option in which a file containing MBR data is read into memory, and control transfers to that. I had saved the MBR containing "Booteasy" and tried that. Sure enough, I could select it from System Commander's menu, and FreeBSD would boot. However, on rebooting, SC was out of the picture, and I was once again back to Booteasy. Thanks to help from Doug White (dwhite@resnet.uoregon.edu), I was able to find the applicable sources and identify the cause of the problems. I looked into Booteasy and found that it writes itself "back" to the boot sector on the first drive each time it's invoked so's to save the (possibly) new default boot selection. This explains why System Commander so quickly disappears without a trace when its "Load using MBR" option is selected. The second thing I observe about "Booteasy" is that all it really does (after writing itself back to the first block of the first drive) is load one block from a specified partition - or load the MBR of the second drive - and transfer control to it. Patching the saved "Booteasy" MBR so that it didn't write itself back to disk returned me to the "No bootable partition" problem - but did prevent SC from disappearing. The next part of the problem was found by examining the function boot1 in an assembly source file called start.S contained in the directory /pub/FreeBSD/FreeBSD-stable/src/sys/i386/boot/biosboot. This is the code that is loaded by the MBR code. boot1 reads the MBR record and scans the partition table for a System Indicator byte of type 0xA5. If one is found, additional boot code is read in from that partition. If one is not found, the "No bootable partition" message is issued and processing halts. (A potential problem here is that the search stops at the 1st BSD partition - apparently precluding booting from another BSD partition on the same drive.) To see if SC's modified boot indicator was the problem, I once more tried to boot Free BSD through SC, got the "No bootable partition" message, then rebooted Linux from a floppy and used fdisk to see the partitions. Sure enough, /dev/hda3 (3rd partition drive 0), was showing a type code of 0xB5. There is really a two part problem here: One is due to a characteristic of the "Booteasy" code in the MBR, and the other is what I consider to be a bug in System Commander: i.e. it sometimes sets bit 4 of the System Indicator byte. Booteasy: My suggestion for Booteasy is to modify it so that it doesn't write itself back to disk. This has the disadvantage of no longer being able to change the default boot drive selection, but the advantage is that interoperability with other products (e.g. System Commander) is improved. It might also be a good idea to look at start.S with respect to the single bootable partition problem. Can you pass this on? Or, can I impose on you enough to ask for pointers as to how I can pass this on? System Commander: With respect to System Commander, I think V Communications should fix it so's not to muck around with the System Indicator byte. Whatever that bit is being used for can be duplicated by using other storage ins its (required) DOS partition. I've been trying unsuccessfully to contact V Communications thru their Compuserve address about this, but I don't get any answers to my mail. From owner-freebsd-hackers Tue Nov 18 09:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06170 for hackers-outgoing; Tue, 18 Nov 1997 09:12:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA06155 for ; Tue, 18 Nov 1997 09:12:49 -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 RAA20871; Tue, 18 Nov 1997 17:05:45 +0100 From: Luigi Rizzo Message-Id: <199711181605.RAA20871@labinfo.iet.unipi.it> Subject: multiple instances of the same files... To: hackers@freebsd.org Date: Tue, 18 Nov 1997 17:05:44 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well I have the following problem (derived from the sound driver) the file "soundcard.h" is replicated three times: 1. /usr/include/machine/soundcard.h 2. /sys/i386/include/soundcard.h 3. /sys/i386/isa/snd/soundcard.h The first copy is normally used by application programs (some even use, erroneously, /usr/include/sys/soundcard.h ). The second copy is used in the kernel sources. The third copy has been introduced, somewhat arbitrarily, by myself in order to make the sound distribution self-contained. Other drivers have a similar problem, with copy #3 being part of the driver's distribution. I wonder if it would be possible to make, for all drivers, copy #2 a symlink to the include file located in the same place as the driver file. Many files in /sys/i386/include would deserve this, e.g.: asc.h -> /sys/i386/isa/ cpu.h -> /sys/i386/i386/ lpt.h -> /sys/i386/isa/ mouse.h -> /sys/i386/isa/ pcaudioio.h -> /sys/i386/isa/ soundcard.h -> /sys/i386/isa/[sound|snd]/ speaker.h -> /sys/i386/isa/ ultrasound.h -> /sys/i386/isa/sound/ and probably many others. BTW i also notice (at least in my copy of 2.2.1) some inconsistent use of include directories. At times the file is included as at other times it is included as Is there any rule about this ? Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Tue Nov 18 10:22:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10907 for hackers-outgoing; Tue, 18 Nov 1997 10:22:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10726; Tue, 18 Nov 1997 10:20:00 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id KAA27588; Tue, 18 Nov 1997 10:19:11 -0800 (PST) Message-ID: <19971118101910.03616@micron.mini.net> Date: Tue, 18 Nov 1997 10:19:10 -0800 From: Jonathan Mini To: Doug White Cc: FreeBSD Questions , hackers@FreeBSD.ORG Subject: Re: FreeBSD 2.2.2 Won't Boot (fwd) Reply-To: Jonathan Mini References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Doug White on Tue, Nov 18, 1997 at 09:01:55AM -0800 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [ ... much snipped ... ] > boot1 reads the MBR record and scans the partition table for a System > Indicator byte of type 0xA5. If one is found, additional boot code is read > in from that partition. If one is not found, the "No bootable partition" > message is issued and processing halts. (A potential problem here is that > the search stops at the 1st BSD partition - apparently precluding booting > from another BSD partition on the same drive.) Actually, it doesn't, since all boot1 is doing is trying to find a copy of boot2 to boot. (the second stage of the bootloader) and the boot blocks are present on every FFS ever made. > To see if SC's modified boot indicator was the problem, I once more tried > to boot Free BSD through SC, got the "No bootable partition" message, then > rebooted Linux from a floppy and used fdisk to see the partitions. Sure > enough, /dev/hda3 (3rd partition drive 0), was showing a type code of 0xB5. > > There is really a two part problem here: One is due to a characteristic of > the "Booteasy" code in the MBR, and the other is what I consider to be a > bug in System Commander: i.e. it sometimes sets bit 4 of the System > Indicator byte. > > Booteasy: > > My suggestion for Booteasy is to modify it so that it doesn't write itself > back to disk. This has the disadvantage of no longer being able to change > the default boot drive selection, but the advantage is that > interoperability with other products (e.g. System Commander) is improved. Modifying Booteasy to fix a bug in System Commander is a Bad Idea. There is no reason why you should be using both System Command and Booteasy at the same time. > It might also be a good idea to look at start.S with respect to the single > bootable partition problem. There is not single bootable parition problem. In fact, if you'd had multiple FreeBSD partitions here, the system would have booted. Unfortunalty for you, FreeBSD usually puts itself into one slice (partition in DOS parlance) and partitions that out to itself internally. > System Commander: > > With respect to System Commander, I think V Communications should fix it > so's not to muck around with the System Indicator byte. Whatever that bit > is being used for can be duplicated by using other storage ins its > (required) DOS partition. I've been trying unsuccessfully to contact V > Communications thru their Compuserve address about this, but I don't get > any answers to my mail. -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Tue Nov 18 10:51:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12697 for hackers-outgoing; Tue, 18 Nov 1997 10:51:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12684 for ; Tue, 18 Nov 1997 10:51:17 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.7.3) id TAA02345; Tue, 18 Nov 1997 19:48:14 +0100 (MET) Message-Id: <199711181848.TAA02345@sos.freebsd.dk> Subject: Re: multiple instances of the same files... In-Reply-To: <199711181605.RAA20871@labinfo.iet.unipi.it> from Luigi Rizzo at "Nov 18, 97 05:05:44 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Tue, 18 Nov 1997 19:48:08 +0100 (MET) Cc: hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Luigi Rizzo who wrote: > Well I have the following problem (derived from the sound driver) > > the file "soundcard.h" is replicated three times: > > 1. /usr/include/machine/soundcard.h > 2. /sys/i386/include/soundcard.h Erhm 1 should be an installed copy of 2, so they are actually the same file. > 3. /sys/i386/isa/snd/soundcard.h This one is new, but you know that :) > BTW i also notice (at least in my copy of 2.2.1) some inconsistent use > of include directories. At times the file is included as > at other times it is included as Well, gives the same file (given the sources are the same as the installed system), but userlevel progs should use . > Is there any rule about this ? Se above :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Tue Nov 18 10:59:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13399 for hackers-outgoing; Tue, 18 Nov 1997 10:59:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA13385 for ; Tue, 18 Nov 1997 10:59:40 -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 SAA21234; Tue, 18 Nov 1997 18:51:27 +0100 From: Luigi Rizzo Message-Id: <199711181751.SAA21234@labinfo.iet.unipi.it> Subject: Re: multiple instances of the same files... To: julian@whistle.com (Julian Elischer) Date: Tue, 18 Nov 1997 18:51:27 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <3471E066.446B9B3D@whistle.com> from "Julian Elischer" at Nov 18, 97 10:37:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Luigi Rizzo wrote: > > > > Well I have the following problem (derived from the sound driver) > > > > the file "soundcard.h" is replicated three times: > no you have 2 > > > > > 1. /usr/include/machine/soundcard.h > > 2. /sys/i386/include/soundcard.h > > 3. /sys/i386/isa/snd/soundcard.h > > /usr/include/machine is supposed to be a symlink (or copy) of > /sys/i386/include unfortunately it is a copy, because not everybody has kernel sources installed so they might miss #2. Having a copy instead of a symlink is boring since when you do development you might make changes to #2 and forget to update #1. generally, I manually make #1 a symlink to #2. The problem now is if you distribute updates of a kernel package (typical with experimental device drivers), it is easier to have all things in one place (hence the existence of #3) rather than having pieces scattered around. This is not only my problem: the meteor and bt848 drivers had the same problem with ioctl_{meteor|bt848}.h being in a different directory; and even the guspnp code distributed by amancio has the same problem (to the point that his distribution does not even have soundcard.h into it!) Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Tue Nov 18 12:37:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA20747 for hackers-outgoing; Tue, 18 Nov 1997 12:37:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA20736 for ; Tue, 18 Nov 1997 12:36:58 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.7/8.8.7) id UAA06458; Tue, 18 Nov 1997 20:34:17 GMT Message-ID: <19971118203415.35527@pavilion.net> Date: Tue, 18 Nov 1997 20:34:15 +0000 From: Josef Karthauser freebsd@atipa.com, cmott@srv.net, hackers@FreeBSD.ORG Subject: Re: IDT processors? References: <199711092054.WAA17476@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199711092054.WAA17476@shadows.aeon.net>; from mika ruohotie on Sun, Nov 09, 1997 at 10:54:43PM +0200 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; On Sun, Nov 09, 1997 at 10:54:43PM +0200, mika ruohotie wrote: > > ALPHA, get that freebsd port done! > > why would anyone want to use anything else than r10000? > > now, _that_ would be a port i'd like to see, freebsd on SGI platform. > > how likely is it? I'm currently working on some emulation stuff that could bring it slightly closer to reality. Who know, maybe by the turn of the century :) Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Tue Nov 18 13:02:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA22717 for hackers-outgoing; Tue, 18 Nov 1997 13:02:35 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA22686 for ; Tue, 18 Nov 1997 13:02:08 -0800 (PST) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.8/8.8.8) id PAA08706 for freebsd-hackers@freebsd.org; Tue, 18 Nov 1997 15:01:36 -0600 (CST) Date: Tue, 18 Nov 1997 15:01:36 -0600 (CST) From: Mark Tinguely Message-Id: <199711182101.PAA08706@plains.NoDak.edu> Subject: whistle article in InternetWeek Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; FYI: This is prob. old news to most people, but Whistle Communication (and their FreeBSD product) is featured on page 55 of the Nov 10, 1997 Internet Week (http://techweb.cmp.com/internetwk/reviews/rev1110.htm). --mark. From owner-freebsd-hackers Tue Nov 18 13:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA24153 for hackers-outgoing; Tue, 18 Nov 1997 13:20:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from heron.doc.ic.ac.uk (xfCmqaPwKVp4iApb1fupiKxCLTlqmjAY@heron.doc.ic.ac.uk [146.169.2.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA24147 for ; Tue, 18 Nov 1997 13:20:31 -0800 (PST) (envelope-from njs3@doc.ic.ac.uk) Received: from oak47.doc.ic.ac.uk [146.169.16.21] ([XCeo4G+g+SBQDVgPQct2czMPYTvaegj6]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0xXv5o-0001wo-00; Tue, 18 Nov 1997 21:21:56 +0000 Received: from njs3 by oak47.doc.ic.ac.uk with local (Exim 1.62 #3) id 0xXv44-0000Ay-00; Tue, 18 Nov 1997 21:20:08 +0000 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Tue, 18 Nov 1997 21:20:08 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) Subject: Re: Optimizing HD I/O What size to use? Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; Francisco Reyes said: > I am going to start working on a program which will be heavy on I/O. > I was wondering what would be a good size to read/write at a time. > > What is the minimun block size FreeBSD allocates? 4K? 8K? Is it HD > dependent? The default blocksize used by newfs(8) is 8192 bytes, your program could use some multiple of this size. (I checked the source in -current for this, it doesn't seem to be documented in the man page) However a better way to determine the optimum block size for I/O to a file is to f?stat(2) it and look at the st_blksize member. I've attached a program which takes a list of filenames and prints out the optimum I/O block size for them. Heres some sample output: [nsmart@caligula nsmart]$ uname -r 2.2.2-RELEASE [nsmart@caligula nsmart]$ ./a.out / /usr/bin/xargs /tmp/fifo /proc . /: (directory) 8192 bytes optimal blocksize /usr/bin/xargs: (regular) 8192 bytes optimal blocksize /tmp/fifo: (FIFO) 8192 bytes optimal blocksize /proc: (directory) 4096 bytes optimal blocksize .: (directory) 8192 bytes optimal blocksize Interestingly enough (or not) Solaris returns 1092 bytes as the optimum I/O blocksize on procfs, 5120 for a FIFO and 4096 for swapfs. To reduce the amount of system calls necessary you should use some (integer) multiple of the optimum I/O block size. Here's some sample times for a program that reads from stdin and writes to stdout in blocks whose size is specified on the command line: [nsmart@caligula nsmart]$ dd if=/dev/urandom of=temp bs=1024 count=1024 1024+0 records in 1024+0 records out 1048576 bytes transferred in 3.326055 secs (315261 bytes/sec) [nsmart@caligula nsmart]$ for i in 32768 16384 8192 4096 128 10 8 5 1; do > rm -f temp2 > time ./a.out $i < temp > temp2 > done 0.21 real 0.00 user 0.06 sys 0.21 real 0.00 user 0.06 sys 0.23 real 0.00 user 0.07 sys 0.23 real 0.00 user 0.07 sys 0.64 real 0.01 user 0.33 sys 3.75 real 0.18 user 3.27 sys 4.68 real 0.14 user 4.19 sys 7.30 real 0.32 user 6.57 sys 34.36 real 1.68 user 31.87 sys You pay a big performance hit if your blocksize is too small. There is an even faster way of performing I/O, mmap(2). By using mmap() you avoid the buffer copying that is implied in the read() and write() functions. Heres some sample times for the above program versus one which uses mmap(): [nsmart@caligula nsmart]$ for i in 1 2 3 4 5; do > rm -f temp2 > time ./mmap_cp < temp 1<>temp2 > rm -f temp2 > time ./rw_cp 8192 < temp >temp2 > echo > done 0.26 real 0.13 user 0.07 sys 1.04 real 0.00 user 0.32 sys 0.21 real 0.13 user 0.06 sys 1.00 real 0.00 user 0.36 sys 0.21 real 0.10 user 0.10 sys 1.18 real 0.00 user 0.33 sys 0.21 real 0.11 user 0.08 sys 0.98 real 0.01 user 0.28 sys 0.21 real 0.12 user 0.08 sys 1.07 real 0.00 user 0.37 sys Evidently, mmap() rocks. Source code is appended, Regards, Niall ==> common.c - some common stuff :) <== #include #include #include #include /* * Older systems don't have strerror, this version of it * will do for them. You may have to modify or remove * the declarations of sys_nerr and sys_nerrlist */ #ifdef NEED_STRERROR char* strerror(int errnum); extern int sys_nerr; extern char* sys_errlist[]; char* strerror(int errnum) { if (errnum > 0 && errnum < sys_nerr) return sys_errlist[errnum]; else return "Unknown error"; } #endif /* * Some utility functions for printing error messages */ extern char* prog_name; /* argv[0] */ void sys_err(char* fmt, ...) { int e = errno; va_list va; fprintf(stderr, "%s: ", prog_name); va_start(va, fmt); vfprintf(stderr, fmt, va); va_end(va); fprintf(stderr, "%s\n", strerror(e)); } void prog_err(char* fmt, ...) { va_list va; fprintf(stderr, "%s: ", prog_name); va_start(va, fmt); vfprintf(stderr, fmt, va); va_end(va); fputc('\n', stderr); } ==> common.h - the interface to common.c <== #ifndef __COMMON_H__ #define __COMMON_H__ #ifdef NEED_STRERROR char* strerror(int errnum); #endif void sys_err(char* fmt, ...); void prog_err(char* fmt, ...); #endif ==> mmap_copy.c - copy stdin to stdout using mmap() <== #include #include #include #include #include #include "common.h" char* prog_name; int main(int argc, char** argv) { struct stat st; caddr_t in_buf; caddr_t out_buf; prog_name = argv[0]; if (argc != 1) { prog_err("I don't take any arguments!"); exit(1); } if (fstat(STDIN_FILENO, &st) == -1) { sys_err("could not stat stdin: "); exit(1); } if ((in_buf = mmap((caddr_t) 0, st.st_size, PROT_READ, MAP_SHARED, STDIN_FILENO, 0)) == MAP_FAILED) { sys_err("could not mmap stdin: "); exit(1); } lseek(STDOUT_FILENO, st.st_size - 1, SEEK_SET); write(STDOUT_FILENO, "", 1); if ((out_buf = mmap((caddr_t) 0, st.st_size, PROT_READ | PROT_WRITE, MAP_SHARED, STDOUT_FILENO, 0)) == MAP_FAILED) { sys_err("could not mmap stdout: "); exit(1); } memcpy(out_buf, in_buf, st.st_size); munmap(in_buf, st.st_size); munmap(out_buf, st.st_size); if (ftruncate(STDOUT_FILENO, st.st_size) == -1) { sys_err("could not truncate stdout: "); } return 0; } ==> st_blksize.c - print out the st_blksize info for a file <== #include #include #include #include #include #include "common.h" /* * Some systems don't support AF_UNIX domain sockets */ #ifndef S_ISSOCK #define S_ISSOCK(x) 0 #endif char* prog_name; int main(int argc, char** argv) { struct stat st; char* file_type; prog_name = argv[0]; if (argc == 1) { fprintf(stderr, "Usage: %s filename [filename...]\n", prog_name); exit(1); } for(argv++; *argv != NULL; argv++) { if (stat(*argv, &st) == -1) { sys_err("%s: ", *argv); } else { file_type = NULL; if (S_ISDIR(st.st_mode)) file_type = "directory"; if (S_ISCHR(st.st_mode)) file_type = "character special"; if (S_ISBLK(st.st_mode)) file_type = "block special"; if (S_ISREG(st.st_mode)) file_type = "regular"; if (S_ISSOCK(st.st_mode)) file_type = "socket"; if (S_ISFIFO(st.st_mode)) file_type = "FIFO"; if (file_type == NULL) file_type = "unknown"; printf("%s: (%s) %ld bytes optimal blocksize\n", \ *argv, file_type, (long) st.st_blksize); } } return 0; } ==> vary_blk.c - copy stdin to stdout using read/write using varying block sizes <== #include #include #include #include "common.h" char* prog_name; int main(int argc, char** argv) { int blk_size; void* buf; int b; prog_name = *argv; if (argc != 2) { fprintf(stderr, "Usage: %s blocksize\n", prog_name); exit(1); } if ((blk_size = atoi(argv[1])) <= 0) { prog_err("Invalid blocksize: %d (%s)", blk_size, argv[1]); exit(1); } buf = malloc(blk_size); while ((b = read(STDIN_FILENO, buf, blk_size)) > 0) if (write(STDOUT_FILENO, buf, b) < b) { sys_err("write: "); exit(1); } if (b == -1) { sys_err("read: "); exit(1); } return 0; } From owner-freebsd-hackers Tue Nov 18 13:52:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26644 for hackers-outgoing; Tue, 18 Nov 1997 13:52:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26632 for ; Tue, 18 Nov 1997 13:52:31 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA23167; Tue, 18 Nov 1997 14:51:06 -0700 (MST) From: Terry Lambert Message-Id: <199711182151.OAA23167@usr01.primenet.com> Subject: Re: >64MB To: j_mini@efn.org Date: Tue, 18 Nov 1997 21:51:00 +0000 (GMT) Cc: tony@dell.com, hackers@freebsd.org In-Reply-To: <19971118032353.57770@micron.mini.net> from "Jonathan Mini" at Nov 18, 97 03:23:53 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > 1) The boot blocks are a part of the boot process, meaning that > > > they should function in real mode (being part of initializing the > > > processor) and the sole function of this code is to load the kernel > > > into memory. (this is bogus, IMO) > > > > Well, I don't think it's bogus, and Terry seems to want this one, if I > > haven't mistaken his statements. This has certain ideological advantages > > with respect to portability and multiple platform development. > > Hmm. As I read his reply, he seemed to be a proponent of setting up a vm86 > TSS for the real mode code. I can put my own feet in my mouth without help, thanks. 8-). 1) I want the boot blocks to run in real mode, and switch to protected mode before starting the kernel. The function of the boot blocks it to get the kernel loaded, not to do machine specific initialization. 2) I want the machine specific initialization to occur in the protected mode kernel, utilizing a VM86 TSS if it is necessary to do so (right now, it is, mostly because machine vendors don't care about protected mode code being able to call their BIOS). These goals aren't incompatible or mutually exclusive. > > > 2) The boot blocks are a small microkernel who's sole purpose is to > > > load the main kernel (or possible a second micro-kernel which handles > > > config : read three stage boot) into memory and give it control. To > > > do this, it needs to have two contexts : > > > a) a protected context with mappings for the kernel, and > > > b) a vm86 context for talking to the BIOS. > > > > Yes, this is one possible approach, but I still think it offers no extra > > value over what we have now. Please don't assume I don't understand these > > issues. Regardless, I don't really care what approach is taken, so long > > as it is implemented correctly. Also remember that I'm referring to boot > > time code only. > > I understand, but your second statement eludes me. You say that you don't > care what approach is taken, as long as the code is implementd properly? But > the approach taken to the solution is half of the implementation. A hack is > still a hack, even if it is the most beutiful code within itself. "Correctly" in this case means not implementing a VM86() mechanism twice. Since FreeBSD itself needs this mechanism for BIOS based hardware initialization, as well as for possible future "fallback" drivers, the place to implement it is as part of a HAL. This is because VM86() is one of the services a HAL can provide on an x86 family processors. > > > The boot blocks shouldn't be constantly hopping from Real Mode > > > to Protected Mode over and over again! This is insane, > > > > No, this is done all the time. Switching between modes is fast, small and > > easy (excluding the '286, of course). > > Whether or not something is 'done all the time' is not an issue, it is still > insane. The boot blocks are the *only* place where this type of insanity is even mildly tolerable (IMO). The fact is, we need to know some things that the hardware specific BIOS knows, and which we can't know ourselves without calling the hardware specific BIOS, without becoming hardware specific too. Since it's unacceptable for us to be hardware specific, then we need to know where we can put code that is platform specific (ie: it assumes the existance of a BIOS and a mechanism to call it) without putting the burden in the boot blocks. The reason it can't go in the bootblocks is twofold: 1) The space available to the boot blocks is already too low to allow adding this kind of extension. 2) When porting to a new platform, I can hard-code the information I would get from the HAL interface for obtaining machine specific information. I can do this without having to make it work, initially. The boot code approach would require that I make everything work initially, and this means more work for a minimally functional "first pass" at a port... making ports less likely. They are already unlikely enough. 8-(. > > So here you finally agree with me? Like I said, don't use vm86() mode > > until the kernel takes over. Use real mode and protected mode, as > > appropriate, until the kernel takes over. > > Why do you keep putting paren's around vm86? Are you referring to the VM86() > functionality that Mike Smith is working on, or are you referring to a TSS > with the vm86 adressing model? That's my convention. The reason I use it is to distinguish a functional interface whereby protected mode code can call real mode code to get a result (like a BIOS function call effect) and have the results returned to the protected mode caller. A non-procedural VM86() implies the ability to run a real mode OS in a protected environment, but says nothing about the ability of the protected mode code to use the virtual machine for it's own ends (like making the BIOS call to ask the memory size). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Nov 18 13:52:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26682 for hackers-outgoing; Tue, 18 Nov 1997 13:52:50 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26663 for ; Tue, 18 Nov 1997 13:52:43 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id NAA12010 for ; Tue, 18 Nov 1997 13:52:40 -0800 (PST) Date: Tue, 18 Nov 1997 13:52:35 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Just a note of appreciation... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just wanted to thank everybody going through and cleaning up the tree with the -Wformat, Wunused, and all those thingies. I appreciate that sometimes it's boring. It gives me a warm fuzzy to have warning-free builds... Now if somebody wanted to dig deep into libc and fix those in there, buildworld could border on an orgiastic experience... From owner-freebsd-hackers Tue Nov 18 14:03:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27397 for hackers-outgoing; Tue, 18 Nov 1997 14:03:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27392; Tue, 18 Nov 1997 14:03:01 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA24807; Tue, 18 Nov 1997 15:02:38 -0700 (MST) From: Terry Lambert Message-Id: <199711182202.PAA24807@usr01.primenet.com> Subject: Re: FreeBSD 2.2.2 Won't Boot (fwd) To: j_mini@efn.org Date: Tue, 18 Nov 1997 22:02:36 +0000 (GMT) Cc: dwhite@resnet.uoregon.edu, questions@freebsd.org, hackers@freebsd.org In-Reply-To: <19971118101910.03616@micron.mini.net> from "Jonathan Mini" at Nov 18, 97 10:19:10 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > My suggestion for Booteasy is to modify it so that it doesn't write itself > > back to disk. This has the disadvantage of no longer being able to change > > the default boot drive selection, but the advantage is that > > interoperability with other products (e.g. System Commander) is improved. > > Modifying Booteasy to fix a bug in System Commander is a Bad Idea. There > is no reason why you should be using both System Command and Booteasy at > the same time. V Communications is Frank Van Gilluwe's company. This is the company of the person who wrote "The Undocumented PC" book (a standard reference work used by the BSD community). Clearly, it's depending on the idea that a BIOS drive ID maps to a primary parittion ID, and assuming that FreeBSD will use the %dl value instead of relying on searching the partiton table, yet again, for the ID. This works for Linux because Linux doesn't have to deal with a "dangerously dedicated" mode -- and fails for FreeBSD for the same reason. Arguably, FreeBSD is correct; use of a partition table places an 8G limit on the drive size, and FreeBSD's method means that it does not suffer this restriction (of course, LBA mode would do the same thing, yielding 32 bits * 512 bytes per sector as a limit). I believe "system commander" does this twiddle to "remember" which partition was booted last. You seeing this problem is probably endemic to your use of a third primary parition for FreeBSD: BIOS does not support more than two primary partitions reported (0x80, 0x81) in %dl. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Nov 18 14:12:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28264 for hackers-outgoing; Tue, 18 Nov 1997 14:12:36 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28259 for ; Tue, 18 Nov 1997 14:12:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id OAA00302; Tue, 18 Nov 1997 14:12:30 -0800 (PST) Message-Id: <199711182212.OAA00302@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org cc: sos@freebsd.dk Subject: syscons and VC? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Nov 1997 14:12:29 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Background: I am trying to get glquake going on FreeBSD. glquake uses Mesa/Glide for 3d hardware support and svgalib for mouse and keyboard input. No jokes please about svgalib for mouse and keyboard thats the way that glquake and qtest2 (Quake2) are currently implemented for linux. Should anyone be interested on Mesa/Glide support you can download Mesa-2.5b6 from: ftp://iris.ssec.wisc.edu/pub/Mesa/beta/ You can get the glide library from : http://www.3dfx.com And there is lots of info on glide at www.3dfx.com My 3d board is a Diamond Monsted 3D which is a Voodoo chipset based board. My vga adapter is a Matrox millenium so for more info on Voodoo based boards or technology please visit wwww.3dfx.com Does anyone have a good example on how to switch VCs for FreeBSD? I have implemented the hooks on the linux emulation layer so it shouldn't be a problem to tranlate the linux ioctls to FreeBSD equivalent. Worst case scenarion we can modify svgalib-1.2.11 to fit our OS. glquake so far in demo mode seems to work okay so if get over this technical problem we will have glquake for FreeBSD 8) All my work is for 3.0 -current. --- this is what svgalib-1.2.11 does to aquire a VC: void __svgalib_open_devconsole(void) { struct vt_mode vtm; struct vt_stat vts; struct stat sbuf; char fname[30]; if (__svgalib_tty_fd >= 0) return; /* * Now, it would be great if we could use /dev/tty and see what it is connected to. * Alas, we cannot find out reliably what VC /dev/tty is bound to. Thus we parse * stdin through stderr for a reliable VC */ for (__svgalib_tty_fd = 0; __svgalib_tty_fd < 3; __svgalib_tty_fd++) { if (fstat(__svgalib_tty_fd, &sbuf) < 0) continue; if (ioctl(__svgalib_tty_fd, VT_GETMODE, &vtm) < 0) continue; if ((sbuf.st_rdev & 0xff00) != 0x400) continue; if (!(sbuf.st_rdev & 0xff)) continue; svgalib_vc = sbuf.st_rdev & 0xff; return; /* perfect */ } if ((__svgalib_tty_fd = open("/dev/ttyv0", O_RDWR)) < 0) { printf("svgalib: can't open /dev/console \n"); exit(1); } if (ioctl(__svgalib_tty_fd, VT_OPENQRY, &svgalib_vc) < 0) { printf("svgalib VT_OPENQRY 1 \n"); goto error; } if (svgalib_vc <= 0) { printf(" vc number %d \n", svgalib_vc); goto error; } sprintf(fname, "/dev/ttyv%d", svgalib_vc); close(__svgalib_tty_fd); /* change our control terminal: */ setsid(); printf(" about to open %s \n", fname ); /* We must use RDWR to allow for output... */ if (((__svgalib_tty_fd = open(fname, O_RDWR)) >= 0) && (ioctl(__svgalib_tty_fd, VT_GETSTATE, &vts) >= 0)) { if (!check_owner(vts.v_active)) { printf(" i am not the owner \n"); goto error; } /* success, redirect all stdios */ if (DREP) printf("[svgalib: allocated virtual console #%d]\n", svgalib_vc); fflush(stdin); fflush(stdout); fflush(stderr); close(0); close(1); close(2); dup(__svgalib_tty_fd); dup(__svgalib_tty_fd); dup(__svgalib_tty_fd); /* clear screen and switch to it */ fwrite("\e[H\e[J", 6, 1, stderr); fflush(stderr); if (svgalib_vc != vts.v_active) { startup_vc = vts.v_active; ioctl(__svgalib_tty_fd, VT_ACTIVATE, svgalib_vc); __svgalib_waitvtactive(); } } else { error: if (__svgalib_tty_fd > 2) printf("__svgalib_tty_fd %d \n", __svgalib_tty_fd); close(__svgalib_tty_fd); __svgalib_tty_fd = - 1; printf("Not running in a graphics capable console,\n" "and unable to find one.\n"); } } ----- afterwards the keyboard init routine does: ioctl(__svgalib_kbd_fd, KDSKBMODE, K_MEDIUMRAW); And I am not sure whats the FreeBSD equivalent for K_MEDIUMRAW. Tnks, Amancio From owner-freebsd-hackers Tue Nov 18 14:26:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29371 for hackers-outgoing; Tue, 18 Nov 1997 14:26:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA29363 for ; Tue, 18 Nov 1997 14:26:22 -0800 (PST) (envelope-from devet@adv.IAEhv.nl) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 17997 on Tue, 18 Nov 1997 22:26:14 GMT; id WAA17997 efrom: devet@adv.IAEhv.nl; eto: hackers@freebsd.org Received: (from devet@localhost) by adv.IAEhv.nl (8.8.7/8.8.6) id XAA14266 for hackers@freebsd.org; Tue, 18 Nov 1997 23:25:47 +0100 (CET) From: Arjan de Vet Message-Id: <199711182225.XAA14266@adv.IAEhv.nl> Subject: caching only directory disk blocks To: hackers@freebsd.org Date: Tue, 18 Nov 1997 23:25:47 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would it be possible to create a mount option (or something else) which would only cache disk blocks from directories and not disk blocks from 'normal' files? Or give the former precedence over the latter for staying in the buffer cache? The reason why I'm asking this? I'm currently playing with the Squid proxy-cache to improve its usage of the file system cache. For applications like Squid it's very important to keep as much directory blocks in the buffer cache as possible. Caching of 'normal' files doesn't make any sense because Squid has its own hot-object cache and most file access is too random anyway in order for the buffer cache to be useful. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.IAEhv.nl/users/devet/ for PGP key: finger devet@IAEhv.nl From owner-freebsd-hackers Tue Nov 18 15:01:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02561 for hackers-outgoing; Tue, 18 Nov 1997 15:01:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02551 for ; Tue, 18 Nov 1997 15:01:40 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id PAA26344; Tue, 18 Nov 1997 15:01:32 -0800 (PST) Date: Tue, 18 Nov 1997 15:01:32 -0800 (PST) From: Jaye Mathisen To: Arjan de Vet cc: hackers@FreeBSD.ORG Subject: Re: caching only directory disk blocks In-Reply-To: <199711182225.XAA14266@adv.IAEhv.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Not sure how useful this would be. If the object is hot, who cares if it's directory blocks or file data blocks? It's just important that it be in RAM, and not on disk. Although it might be an interesting tweak. On Tue, 18 Nov 1997, Arjan de Vet wrote: > Would it be possible to create a mount option (or something else) which > would only cache disk blocks from directories and not disk blocks from > 'normal' files? Or give the former precedence over the latter for staying > in the buffer cache? > > The reason why I'm asking this? I'm currently playing with the Squid > proxy-cache to improve its usage of the file system cache. For > applications like Squid it's very important to keep as much directory > blocks in the buffer cache as possible. Caching of 'normal' files doesn't > make any sense because Squid has its own hot-object cache and most file > access is too random anyway in order for the buffer cache to be useful. > > Arjan > > -- > Arjan de Vet, Eindhoven, The Netherlands > URL: http://www.IAEhv.nl/users/devet/ for PGP key: finger devet@IAEhv.nl > From owner-freebsd-hackers Tue Nov 18 16:10:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA07597 for hackers-outgoing; Tue, 18 Nov 1997 16:10:27 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from chain.freebsd.os.org.za (BgN0bjdlGs83eCxGxDcHk2ii70ehg6Qy@chain.iafrica.com [196.7.74.174]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA07590 for ; Tue, 18 Nov 1997 16:10:18 -0800 (PST) (envelope-from khetan@chain.iafrica.com) Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.8.8/8.8.8) with SMTP id CAA26887 for ; Wed, 19 Nov 1997 02:10:08 +0200 (SAT) Date: Wed, 19 Nov 1997 02:10:08 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@chain Reply-To: Khetan Gajjar To: hackers@freebsd.org Subject: WordPerfect 7.0 for SCO Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I've bought myself a copy of WordPerfect 7.0 for SCO OpenServer 5. I was wondering if it was possible to install this - I've tried the GUI installation, but it just core dumps (bus error), and the text version mutters about incorrect terminal emulation. gdb on the core file says Program terminated with signal 10, Bus error. #0 0x119e68 in ?? () Anybody got this working yet ? TIA. --- Khetan Gajjar - whois kg1779 | khetan@iafrica.com or khetan@os.org.za http://chain.iafrica.com/~khetan | PGPKey : finger khetan@chain.iafrica.com UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org Unix is user friendly; it's just selective about who it calls a friend! From owner-freebsd-hackers Tue Nov 18 16:40:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA09385 for hackers-outgoing; Tue, 18 Nov 1997 16:40:12 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA09375 for ; Tue, 18 Nov 1997 16:40:02 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (ts1port5d.masternet.it [194.184.65.245]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id BAA01128; Wed, 19 Nov 1997 01:44:06 +0100 (MET) Message-ID: <347243BA.36DA3B42@giovannelli.it> Date: Wed, 19 Nov 1997 01:41:14 +0000 From: Gianmarco Giovannelli Reply-To: gmarco@giovannelli.it X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Amancio Hasty CC: hackers@FreeBSD.ORG Subject: Re: syscons and VC? References: <199711182212.OAA00302@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty wrote: > > Hi, > > Background: > > I am trying to get glquake going on FreeBSD. glquake uses Mesa/Glide > for 3d hardware support and svgalib for mouse and keyboard input. > No jokes please about svgalib for mouse and keyboard thats the > way that glquake and qtest2 (Quake2) are currently implemented for > linux. > > Should anyone be interested on Mesa/Glide support you can > download Mesa-2.5b6 from: > > ftp://iris.ssec.wisc.edu/pub/Mesa/beta/ > > You can get the glide library from : http://www.3dfx.com > And there is lots of info on glide at www.3dfx.com > > My 3d board is a Diamond Monsted 3D which is a Voodoo chipset based board. > My vga adapter is a Matrox millenium so for more info on > Voodoo based boards or technology please visit wwww.3dfx.com > > Does anyone have a good example on how to switch VCs for FreeBSD? > > I have implemented the hooks on the linux emulation layer so it shouldn't > be a problem to tranlate the linux ioctls to FreeBSD equivalent. > > Worst case scenarion we can modify svgalib-1.2.11 to fit our OS. > > glquake so far in demo mode seems to work okay so if get over this > technical problem we will have glquake for FreeBSD 8) > > All my work is for 3.0 -current. > Please let me know if you succeded... glquake and glqwcl are the only things that are saving win95 from a brutal format ... -- Regards... Gianmarco "Unix expert since yesterday" http://www2.masternet.it From owner-freebsd-hackers Tue Nov 18 16:50:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA10310 for hackers-outgoing; Tue, 18 Nov 1997 16:50:58 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from gwu.ericy.com (gwu.ericy.com [208.196.3.162]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA10305 for ; Tue, 18 Nov 1997 16:50:54 -0800 (PST) (envelope-from euswdwj@exu.ericsson.se) Received: from mr3.exu.ericsson.se ([138.85.11.55]) by gwu.ericy.com (8.8.8/8.8.8) with ESMTP id SAA04446 for ; Tue, 18 Nov 1997 18:43:47 -0600 (CST) Received: from newman.exu.ericsson.se (newman.exu.ericsson.se [138.85.10.50]) by mr3.exu.ericsson.se (8.8.8/8.8.8) with ESMTP id SAA29472 for ; Tue, 18 Nov 1997 18:50:12 -0600 (CST) Received: from b04h32.exu.ericsson.se (euswdwj@b04h32 [138.85.55.132]) by newman.exu.ericsson.se (8.7.5/8.7.3) with ESMTP id SAA19440; Tue, 18 Nov 1997 18:50:03 -0600 (CST) From: "William D. Ward" Received: (euswdwj@localhost) by b04h32.exu.ericsson.se (8.7.6/8.6.12) id SAA02814; Tue, 18 Nov 1997 18:42:58 -0600 (CST) Message-Id: <199711190042.SAA02814@b04h32.exu.ericsson.se> Subject: PCNet-32: back for more To: hackers@FreeBSD.org Date: Tue, 18 Nov 1997 18:42:58 -0600 (CST) X-Mailer: ELM [version 2.4 PL0] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Maybe this is a bit old but I would like get started on it again. The difficulty is with a Compaq Deskpro XL 590 and the ethernet interface. Ifconfigging lnc1 results in: lnc1: Initialization failed It the interface appears to be failing a test in lnc_init() from /sys/i386/isa/if_lnc.c. Here: if (read_csr(sc, CSR0) & IDON) { ... } else log(LOG_ERR, "lnc%d: Initialisation failed\n", sc->arpcom.ac_if.if_unit); read_csr(sc, CSR0) returns 0x8881. According to the specs on the AMD79C970, this indicates ERR & MISS & INTR & INIT. Perhaps this is bogus information? Would this the correct data sheet (lnc1 probe message below)? Based on Whitaly's message, it might not be. Witaly Kurakolow: > AM79C974KC - dual PCI Ethernet/SCSI chip > where : > Ethernet part similar to AMD79C970 > this chip have 2 modes > 16 bit - compatible with old ISA AMD chips > 32 bit - not compatible lnc1 rev 2 int b irq 10 on pci0:11 mapreg[10] type=1 addr=00007000 size=0020. lnc1: PCnet-32 VL-Bus address 00:80:5f:f4:70:6d ^^ this means it is in 32 bit mode? If so then what options are available? > SCSI part similar to AMD53C974 > > FreeBSD 2.2.x use pci wrapper for ethernet half of this card, > and card detected as lnc1 and work in 16 bit mode > > !!! Use ifconfig lnc1 !!!! > > P.S. > On my work we have COMPAQ Prosignia-500 with same Ethernet adapter > and running FreeBSD-2.2.2 Any help with this would be greatly appreciated. The hardware is here and it would be no problem for me to try out any patches or suggestions. Would anybody be interested if I come up with a solution other than plugging in an extra ethernet card? Just hearing the cold winds blow in a desolate, lonely existence. Such is life. P.S. I'm running 2.2.5 now. From owner-freebsd-hackers Tue Nov 18 16:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA10680 for hackers-outgoing; Tue, 18 Nov 1997 16:54:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA10664 for ; Tue, 18 Nov 1997 16:54:39 -0800 (PST) (envelope-from fhackers@jraynard.demon.co.uk) Received: from jraynard.demon.co.uk ([158.152.42.77]) by post.mail.demon.net id aa2017996; 19 Nov 97 0:44 GMT Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.8.8/8.8.7) id XAA09641; Tue, 18 Nov 1997 23:33:03 GMT (envelope-from fhackers) Message-ID: <19971118233302.07610@jraynard.demon.co.uk> Date: Tue, 18 Nov 1997 23:33:02 +0000 From: James Raynard To: Jaye Mathisen Cc: freebsd-hackers@freebsd.org Subject: Re: Just a note of appreciation... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Jaye Mathisen on Tue, Nov 18, 1997 at 01:52:35PM -0800 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Nov 18, 1997 at 01:52:35PM -0800, Jaye Mathisen wrote: > > I just wanted to thank everybody going through and cleaning up the tree > with the -Wformat, Wunused, and all those thingies. I appreciate that > sometimes it's boring. Only sometimes? :-) > Now if somebody wanted to dig deep into libc and fix those in there, Well, I spent quite a lot of time last year going through libc with an amazingly stringent set of options (*) and fixing a lot of these, mainly in stdio and gen. The only response was a couple of (reasonably constructive, to be fair) critical emails, so I gave up. Since then, I've noticed a lot more have crept in :-( Bear in mind that this the kind of job people would avoid like the plague even if they were being paid for it... (*) If anyone's sufficiently masochi^H^H^H^H^H^H^Hinterested, they are -Wall -Wbad-function-cast \ -Wcast-align -Wcast-qual \ -Wchar-subscripts -Wconversion \ -Winline -Wmissing-declarations \ -Wmissing-prototypes -Wnested-externs \ -Wpointer-arith -Wredundant-decls \ -Wshadow -Wstrict-prototypes \ -Wwrite-strings (snipped from a bde posting some time ago). -- In theory, theory is better than practice. In practice, it isn't. James Raynard, Edinburgh, Scotland. http://www.freebsd.org/~jraynard/ From owner-freebsd-hackers Tue Nov 18 17:53:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14700 for hackers-outgoing; Tue, 18 Nov 1997 17:53:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14695 for ; Tue, 18 Nov 1997 17:53:25 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA06870; Wed, 19 Nov 1997 01:52:45 GMT Date: Wed, 19 Nov 1997 10:52:45 +0900 (JST) From: Michael Hancock To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Just a note of appreciation... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, Jaye Mathisen wrote: > I just wanted to thank everybody going through and cleaning up the tree > with the -Wformat, Wunused, and all those thingies. I appreciate that > sometimes it's boring. I saw some statistics done by ATT or someone like that where they found that code with a lot of unused variables was significantly more likely to have bugs than code without unused variables. > It gives me a warm fuzzy to have warning-free builds... Right! You don't get the feeling the code is being neglected. > Now if somebody wanted to dig deep into libc and fix those in there, > buildworld could border on an orgiastic experience... From owner-freebsd-hackers Tue Nov 18 19:28:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21293 for hackers-outgoing; Tue, 18 Nov 1997 19:28:58 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21287 for ; Tue, 18 Nov 1997 19:28:55 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id TAA00180 for ; Tue, 18 Nov 1997 19:28:42 -0800 (PST) Date: Tue, 18 Nov 1997 19:28:41 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: vnode.h and IO_NDELAY (help!!) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't find a single code fragment in any device driver that checks ioflags in the read routine to see if IO_NDELAY is set. My driver implements two distinct read modes: blocking and non-blocking. I need to check the ioflags passed to the read routine. I assume i would just #include and check up against IO_NDELAY, why can't I find any examples in a device driver of this being done? Am I going about the whole problem the wrong way? Specifically if a user issues a read on an aiox device opened with the O_NONBLOCK flag, or later performs an fcntl on the descriptor to make it non-blocking I want to detect that when they come into the read routine. If the vnode is blocking, I am allowed to tsleep on the fifo to complete the uio otherwise just get what is available and return. Am I making some grave mistake in how I am handling this??? From owner-freebsd-hackers Tue Nov 18 20:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA23847 for hackers-outgoing; Tue, 18 Nov 1997 20:04:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA23833 for ; Tue, 18 Nov 1997 20:04:33 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xY1Fy-0006jX-00; Tue, 18 Nov 1997 19:56:50 -0800 Date: Tue, 18 Nov 1997 19:56:48 -0800 (PST) From: Tom To: Terry Lambert cc: craig@ProGroup.COM, hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <199711181937.MAA08908@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, Terry Lambert wrote: > This is really bogus reasoning. The / partition will never fill up > because only root can fill it up, and there is a 10% reserve for root > to use. You can fit a lot of password file entries into 3M of a 30M FS. syslog runs as root, and it is big source of filled filesystems. Certainly not bogus reasoning. Tom From owner-freebsd-hackers Tue Nov 18 20:12:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24439 for hackers-outgoing; Tue, 18 Nov 1997 20:12:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24434 for ; Tue, 18 Nov 1997 20:12:11 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id XAA24391; Tue, 18 Nov 1997 23:11:57 -0500 (EST) Date: Tue, 18 Nov 1997 23:11:56 -0500 (EST) From: "Matthew N. Dodd" To: Arjan de Vet cc: hackers@FreeBSD.ORG Subject: Re: caching only directory disk blocks In-Reply-To: <199711182225.XAA14266@adv.IAEhv.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, Arjan de Vet wrote: > Would it be possible to create a mount option (or something else) which > would only cache disk blocks from directories and not disk blocks from > 'normal' files? Or give the former precedence over the latter for staying > in the buffer cache? Have you looked at the output of `vmstat -s` and looked at the name lookup statistics? I believe there is a sysctl that allows you to tune how much memory you allow the name cache to use, but I can't remember what it is right now. > The reason why I'm asking this? I'm currently playing with the Squid > proxy-cache to improve its usage of the file system cache. For > applications like Squid it's very important to keep as much directory > blocks in the buffer cache as possible. Caching of 'normal' files doesn't > make any sense because Squid has its own hot-object cache and most file > access is too random anyway in order for the buffer cache to be useful. I'm not sure how squid works, but in my world it would save the files in wire format, open, mmap, close (to cut down on FDs used) and just write the whole thing when someone asks for it. The cache would optimally keep track of the highest hit pages and use madvise to insure that they are or aren't cached. I would check the source to see if squid doesn't already do something like this. Have a good one. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Tue Nov 18 20:14:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24564 for hackers-outgoing; Tue, 18 Nov 1997 20:14:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from onyx.atipa.com (user18676@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA24555 for ; Tue, 18 Nov 1997 20:14:02 -0800 (PST) (envelope-from freebsd@atipa.com) Received: (qmail-queue invoked by uid 1018); 19 Nov 1997 04:19:06 -0000 Date: Tue, 18 Nov 1997 21:19:06 -0700 (MST) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Amancio Hasty cc: Julian Elischer , hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: FreeBSD based box wins prize at COMDEX! In-Reply-To: <199711172253.OAA03988@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 17 Nov 1997, Amancio Hasty wrote: > > Most Cool!!!! > > I feel like going home and opening a bottle of champagne 8) > > Amancio You mean instead of beer? :) Don't lose your roots! Kevin From owner-freebsd-hackers Tue Nov 18 20:30:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA25449 for hackers-outgoing; Tue, 18 Nov 1997 20:30:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA25443 for ; Tue, 18 Nov 1997 20:30:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id UAA01277; Tue, 18 Nov 1997 20:30:16 -0800 (PST) Message-Id: <199711190430.UAA01277@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Atipa cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: FreeBSD based box wins prize at COMDEX! In-reply-to: Your message of "Tue, 18 Nov 1997 21:19:06 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Nov 1997 20:30:15 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It is my other good -- half, Bettina, she is French !! Cheers, Amancio > > > On Mon, 17 Nov 1997, Amancio Hasty wrote: > > > > > Most Cool!!!! > > > > I feel like going home and opening a bottle of champagne 8) > > > > Amancio > > You mean instead of beer? :) > Don't lose your roots! > > Kevin From owner-freebsd-hackers Tue Nov 18 20:35:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA25646 for hackers-outgoing; Tue, 18 Nov 1997 20:35:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA25641; Tue, 18 Nov 1997 20:35:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id UAA01294; Tue, 18 Nov 1997 20:35:09 -0800 (PST) Message-Id: <199711190435.UAA01294@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: multimedia@freebsd.org cc: hackers@freebsd.org Subject: warning : upcoming glquake!! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Nov 1997 20:35:09 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, For those interested I managed to get glquake going over here . A little bit more hacking and I will never run glquake on Win95 !! The problem is syscons which does not have the equivalent of linux's keyboard mode K_MEDIUMRAW . A bit of hacking on syscons and we will be all set. glquake --- without mouse just keyboard input seems to work over here Will release what I have later on tonite so others can pitchin on the hacking 8) Oh, on the mini release is going to be hackerware use at your own risk . Enjoy, Amancio From owner-freebsd-hackers Wed Nov 19 05:20:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14891 for hackers-outgoing; Wed, 19 Nov 1997 05:20:58 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14886 for ; Wed, 19 Nov 1997 05:20:54 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA06385 for hackers@freebsd.org; Wed, 19 Nov 1997 11:01:02 +0100 (MET) (envelope-from sos) Message-Id: <199711191001.LAA06385@sos.freebsd.dk> Subject: Mail spam, sigh... To: hackers@freebsd.org (FreeBSD hackers) Date: Wed, 19 Nov 1997 11:01:01 +0100 (MET) From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If any of you gets a message back from my system claiming you should be shot or something to that extent, well, I'm sorry. The amount of JUNKmail recently has demanded that I enable my hysteric mail filter again, and its pretty harsh (one unsolicited mail, and that doamin is toast). Sorry for any inconvinience, but the filter stays this time... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Nov 19 05:34:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA16217 for hackers-outgoing; Wed, 19 Nov 1997 05:34:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA16182 for ; Wed, 19 Nov 1997 05:34:12 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.7/8.8.5) with SMTP id RAA09466 for ; Wed, 19 Nov 1997 17:58:20 +0600 (NS) Date: Wed, 19 Nov 1997 17:58:20 +0600 (NS) From: Ustimenko Semen To: hackers@freebsd.org Subject: SMC9432TX Fast Ethernet driver for FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, HACKERS... Alpha version of driver lies at: (Possibly it works not only on my machine) http://iclub.nsu.ru/~semen/smc9432tx.html Bye... From owner-freebsd-hackers Wed Nov 19 06:20:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA18473 for hackers-outgoing; Wed, 19 Nov 1997 06:20:43 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA18462; Wed, 19 Nov 1997 06:20:35 -0800 (PST) (envelope-from pete@sms.fi) Received: from omnip (silver.sms.fi [194.111.122.17]) by silver.sms.fi (8.8.7/8.7.3) with SMTP id QAA16018; Wed, 19 Nov 1997 16:20:10 +0200 (EET) From: "Petri Helenius" To: , "Amancio Hasty" Cc: Subject: Re: warning : upcoming glquake!! Date: Wed, 19 Nov 1997 14:53:02 +0200 Message-ID: <01bcf4ea$125de800$337dc5c2@omnip> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA18469 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Hi, > >For those interested I managed to get glquake going over here . >A little bit more hacking and I will never run glquake on Win95 !! > Any idea if you're going to get the mouse to work ? It's kind of boring to play with the keyboard since you'll get shot all the time because you cannot just move fast enough... Pete From owner-freebsd-hackers Wed Nov 19 08:04:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA25311 for hackers-outgoing; Wed, 19 Nov 1997 08:04:51 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from grunt.vl.net.ua (grunt.vl.net.ua [193.124.76.209]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA25187 for ; Wed, 19 Nov 1997 08:03:32 -0800 (PST) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 1.73 #4) id 0xYCaC-0000Ap-00; Wed, 19 Nov 1997 18:02:29 +0200 To: freebsd-hackers@freebsd.org Subject: No buffer space available. Date: 19 Nov 1997 18:02:27 +0200 Message-ID: <64v2ij$kq$1@grunt.vl.net.ua> X-Newsreader: TIN [UNIX 1.3 unoff BETA 970930; i386 FreeBSD 2.2.5-RELEASE] X-Via: News-To-Mail v1.0 From: Vladimir Litovka Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! Oftenly I see in system log message: 'No buffer space available'. Manual says, that there is full queue on the interface or no available buffers. Where located number of buffers for sending data? Can help increasing this number? -- Vladimir Litovka , hostmaster of vl.net.ua ======== Don't trouble trouble until trouble troubles you. From owner-freebsd-hackers Wed Nov 19 08:13:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA25949 for hackers-outgoing; Wed, 19 Nov 1997 08:13:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA25942 for ; Wed, 19 Nov 1997 08:13:11 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [204.141.95.138]) by etinc.com (8.8.3/8.6.9) with SMTP id LAA10578 for ; Wed, 19 Nov 1997 11:18:16 -0500 (EST) Message-Id: <3.0.32.19971119111515.00ce9100@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 19 Nov 1997 11:15:16 -0500 To: hackers@freebsd.org From: dennis Subject: Re: Twice as many OS/2 as FreeBSD ??? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:29 PM 11/16/97 +0100, you wrote: >In message , Alex writ >es: >> >> >>On Sun, 16 Nov 1997, Poul-Henning Kamp wrote: >> >>> >>> If you think this is embarrasing for FreeBSD: >>> >>> http://rc5stats.distributed.net/oslist.html >>> >>> How about joining "Team FreeBSD" and improving the number ? >> >>Or how bout making your own team, so you could collect the whole prize if >>you win? ;-) We've completed more blocks than Open or NetBSD however. > >One team is plenty. I'm not in it for the money... > >Open & Net BSD are not competition, but that OS/2 should be above us is >more than I can accept... I doubt that this is valid info. Most FreeBSD users don't purchase or register their product (or tell anyone how many copies they are using), so its rather impossible for anyone to really know how many people use it. Dennis From owner-freebsd-hackers Wed Nov 19 09:10:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA00512 for hackers-outgoing; Wed, 19 Nov 1997 09:10:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA00500; Wed, 19 Nov 1997 09:09:52 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id JAA01030; Wed, 19 Nov 1997 09:09:40 -0800 (PST) Message-Id: <199711191709.JAA01030@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Petri Helenius" cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: warning : upcoming glquake!! In-reply-to: Your message of "Wed, 19 Nov 1997 14:53:02 +0200." <01bcf4ea$125de800$337dc5c2@omnip> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Nov 1997 09:09:40 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, The mouse works. Cheers, Amancio From owner-freebsd-hackers Wed Nov 19 09:59:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA05210 for hackers-outgoing; Wed, 19 Nov 1997 09:59:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA05197 for ; Wed, 19 Nov 1997 09:59:06 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id KAA15592; Wed, 19 Nov 1997 10:59:01 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd015580; Wed Nov 19 10:58:52 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id KAA11740; Wed, 19 Nov 1997 10:58:47 -0700 (MST) From: Terry Lambert Message-Id: <199711191758.KAA11740@usr05.primenet.com> Subject: Re: Partitioning suggestions? To: tom@sdf.com (Tom) Date: Wed, 19 Nov 1997 17:58:47 +0000 (GMT) Cc: tlambert@primenet.com, craig@ProGroup.COM, hackers@freebsd.org In-Reply-To: from "Tom" at Nov 18, 97 07:56:48 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This is really bogus reasoning. The / partition will never fill up > > because only root can fill it up, and there is a 10% reserve for root > > to use. You can fit a lot of password file entries into 3M of a 30M FS. > > syslog runs as root, and it is big source of filled filesystems. > > Certainly not bogus reasoning. This is why newsyslog was committed: it can rotate logs by itself and ensure that a given log file will never exceed a certain amount of space (size + count of previous versions). Use newsyslog instead. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 10:05:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA05965 for hackers-outgoing; Wed, 19 Nov 1997 10:05:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA05959; Wed, 19 Nov 1997 10:05:48 -0800 (PST) (envelope-from itojun@itojun.org) Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.5/3.6Wbeta6) with ESMTP id DAA19881; Thu, 20 Nov 1997 03:00:47 +0900 (JST) To: Ruslan Ermilov cc: itojun@freebsd.org, hackers@freebsd.org In-reply-to: ru's message of Mon, 17 Nov 1997 14:22:38 +0200. <199711171222.OAA14473@relay.ucb.crimea.ua> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPSec and 2.2-STABLE From: Jun-ichiro itojun Itoh Date: Thu, 20 Nov 1997 03:00:46 +0900 Message-ID: <19877.879962446@coconut.itojun.org> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What is the general state of IPSec for FreeBSD? We, WIDE project IPv6 working group is working on IPv6/IPsec extension for FreeBSD. As for IPsec we support both rfc182* and draft-ietf-*. ESP Transport mode is working very well. ESP Tunnel mode is yet to be done. See http://www.v6.wide.ad.jp/ for more info. >Can I use it with post-2.2.5-RELEASE (i.e. 2.2-STABLE)? We use 2.2.5-RELEASE as base version but I believe our patch can easily be applied. itojun From owner-freebsd-hackers Wed Nov 19 10:06:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA06043 for hackers-outgoing; Wed, 19 Nov 1997 10:06:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA06036 for ; Wed, 19 Nov 1997 10:06:37 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id LAA07936; Wed, 19 Nov 1997 11:06:37 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd007882; Wed Nov 19 11:06:31 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA12806; Wed, 19 Nov 1997 11:06:14 -0700 (MST) From: Terry Lambert Message-Id: <199711191806.LAA12806@usr05.primenet.com> Subject: Re: Partitioning suggestions? To: tom@sdf.com (Tom) Date: Wed, 19 Nov 1997 18:06:14 +0000 (GMT) Cc: Don.Lewis@tsc.tdk.com, tlambert@primenet.com, craig@ProGroup.COM, hackers@freebsd.org In-Reply-To: from "Tom" at Nov 18, 97 11:02:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > } On Tue, 18 Nov 1997, Terry Lambert wrote: > > } > > } > This is really bogus reasoning. The / partition will never fill up > > } > because only root can fill it up, and there is a 10% reserve for root > > } > to use. You can fit a lot of password file entries into 3M of a 30M FS. > > } > > } syslog runs as root, and it is big source of filled filesystems. > > > > The log files are stored in /var/log. I always make /var a separate > > partition. > > Yes, that is whole point. Separate comparments for everything is good. > Terry seems to believe otherwise. Wrong. I gave ten good reasons why you would want things seperate, whereas the original poster gave one bad one. You can't argue "filling the disk up". It's a bogus argument: I) Filling the disk up should not be catastrophic, even if it does occur. II) Only root processes can override the reserve. This means pilot error in the most general sense. Pilot error can also write over the front of a raw disk; how does the software prevent one kind of pilot error, but not the other? It can't. III) If you have a root process which is a daemon, good sense dictates that the process will have its own controls to prevent overriding the reserve. The syslog argument remains bogus, since you should use newsyslog instead, and avoid the issue. For each example of badly behaved software you can come up with, I will either point to a well behaved piece of software, or I will simply say "then fix it". The FreeBSD penchant for destroying passwd files when the disk is full is an *error* in FreeBSD, and should be corrected. Then I can point at (I) above, and state "so what? So the disk is full...". > > The only file in my root partition that has been modified in the last > > week is /etc/dumpdates. > > And that might be a debatable location for that file. It is nice have / > as static as possible. Some other things: /etc/aliases, > /etc/master.passwd I definitely agree with this. / should be read-only. So should /usr, if you want to get down to it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 10:22:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA07685 for hackers-outgoing; Wed, 19 Nov 1997 10:22:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA07678 for ; Wed, 19 Nov 1997 10:22:53 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id LAA17051; Wed, 19 Nov 1997 11:22:51 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd017031; Wed Nov 19 11:22:41 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA14282; Wed, 19 Nov 1997 11:22:39 -0700 (MST) From: Terry Lambert Message-Id: <199711191822.LAA14282@usr05.primenet.com> Subject: Re: >64MB To: tony@dell.com (Tony Overfield) Date: Wed, 19 Nov 1997 18:22:39 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.3.32.19971118043753.0071582c@bugs.us.dell.com> from "Tony Overfield" at Nov 18, 97 04:37:53 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >1) You can't trust a *user process* to call the BIOS (it's not > > the sword that's the problem, it's what the peasent *does* > > with the sword that makes us make them illegal for everyone > > but the knights and the king). > > I didn't realize the bootloader had user processes. This is in the general sense of a callable VM86() interface. This assumes the kernel is up. > >2) The BIOS INT 13 code has a 2G limit on partition size, unless > > you can guarantee all the devices in your machine support > > LBA mode (even then the limit on LBA is lower than the limit > > in FreeBSD... 64bits >> 32 bits). > > This appears to be completely wrong. > > First, I'm talking about bootloaders. I assume you agree that the > bootloader should use INT 13. > > Second, the INT 13 interface (without LBA mode) is limited > to 8.4 GB, not 2 GB. A DOS partition (assuming we use the DOS MBR and aren't idiots, we are tied to the DOS partition table) is limited to C/H/S values. You have tha ability to map an 8G space with four descriptors. > Third, the limit for LBA INT 13 is 64-bits worth of sectors, or > 2^73 bytes. This should last us for several more years. The LBA limit is irrelevant. It's not usable, so it might as well be fiction. > >3) Gate A20 (now you will argue that Dell hardware doesn't use > > BIOS code that expects a wrap in memory). > > Of course I will! I doubt any BIOS has ever been made that needs > it. You'll no doubt cite some heap-o-crud(tm), obsolete system made > by some long defunct company, probably with some ironic name like > "Leading Edge" or something.... ;-) Yep. Right where I was going... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 10:28:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08440 for hackers-outgoing; Wed, 19 Nov 1997 10:28:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08434 for ; Wed, 19 Nov 1997 10:28:38 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA10944; Wed, 19 Nov 1997 11:28:36 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA05551; Wed, 19 Nov 1997 11:28:34 -0700 Date: Wed, 19 Nov 1997 11:28:34 -0700 Message-Id: <199711191828.LAA05551@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: sos@FreeBSD.dk Cc: hackers@FreeBSD.ORG (FreeBSD hackers) Subject: Re: Mail spam, sigh... In-Reply-To: <199711191001.LAA06385@sos.freebsd.dk> References: <199711191001.LAA06385@sos.freebsd.dk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If any of you gets a message back from my system claiming you > should be shot or something to that extent, well, I'm sorry. > The amount of JUNKmail recently has demanded that I enable > my hysteric mail filter again, and its pretty harsh (one > unsolicited mail, and that doamin is toast). > Sorry for any inconvinience, but the filter stays this time... What I've done is setup my filter to only accept email from known mailing lists, etc..., and also accept mail directly addressed to me. Everything else goes into 'junk' which is 99.99% of the junk mail that I receive, with .01% of it not being junk. Every once in a while I go look in my junk folder for 'valid' email, but otherwise it tends to do it's job well, and still not get rid of 'previously unknown by desired' email. Nate From owner-freebsd-hackers Wed Nov 19 10:31:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08684 for hackers-outgoing; Wed, 19 Nov 1997 10:31:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from www.communique.no (www.communique.no [193.212.204.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA08678 for ; Wed, 19 Nov 1997 10:31:42 -0800 (PST) (envelope-from are@communique.no) Received: (qmail 23716 invoked by uid 1001); 19 Nov 1997 18:38:20 -0000 Date: Wed, 19 Nov 1997 19:38:20 +0100 (CET) From: Are Bryne To: FreeBSD hackers list cc: Are Bryne Subject: NOT READY asc:4,1 error messages... (fwd) Message-ID: Organization: Communique DA MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried sending this to questions first, but no reply was forthcoming. [please keep me cc'd] ----------- forwarded message below Hi, I got this after a mysterious machine hang: (using verbose boot) WARNING: / was not properly dismounted. swapon: adding /dev/sd0s1b as swap device Automatic reboot in progress... /dev/rsd0a: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0a: 859 files, 12393 used, 19382 free (158 frags, 2403 blocks, 0.5% fragmentation) /dev/rsd0s1f: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s1f: 47652 files, 413623 used, 180152 free (6048 frags, 21763 blocks, 1.0% fragmentation) /dev/rsd0s1e: UNREF FILE I=72 OWNER=root MODE=100644 /dev/rsd0s1e: SIZE=0 MTIME=Oct 23 23:01 1997 (CLEARED) /dev/rsd0s1e: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rsd0s1e: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rsd0s1e: SUMMARY INFORMATION BAD (SALVAGED) /dev/rsd0s1e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s1e: 596 files, 2864 used, 26863 free (175 frags, 3336 blocks, 0.6% fragmentation) sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready, retries:4 sd0(ahc0:0:0): SCB 0x1 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0x177 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x3 Ordered Tag queued sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready, retries:4 Ordered Tag sent sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready, retries:4 sd0(ahc0:0:0): SCB 0x1 - timed out in message in phase, SCSISIGI == 0xe6 SEQADDR = 0x15b SCSISEQ = 0x12 SSTAT0 = 0x6 SSTAT1 = 0x3 sd0(ahc0:0:0): abort message in message buffer ahc0:A:0: Missed busfree. sd0(ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xb6 SEQADDR = 0x6 SCSISEQ = 0x5a SSTAT0 = 0x7 SSTAT1 = 0x13 ahc0: Issued Channel A Bus Reset. 4 SCBs aborted Clearing bus reset Clearing 'in-reset' flag sd0(ahc0:0:0): no longer in timeout sd0(ahc0:0:0): no longer in timeout ahc0: target 0 synchronous at 5.0MHz, offset = 0xc sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred, retries:2 Doing initial network setup: hostname. [normal from here on ...] Any ideas as to what this is? Flaky scsi-disk? Something else? Thanks in advance. (I am cc'ed as freebsd-questions takes up too much space and bandwith, IMO :) Are Bryne From owner-freebsd-hackers Wed Nov 19 10:32:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08869 for hackers-outgoing; Wed, 19 Nov 1997 10:32:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA08842 for ; Wed, 19 Nov 1997 10:32:48 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYEj9-00078B-00; Wed, 19 Nov 1997 10:19:51 -0800 Date: Wed, 19 Nov 1997 10:19:49 -0800 (PST) From: Tom To: Terry Lambert cc: Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <199711191806.LAA12806@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Terry Lambert wrote: > > > The log files are stored in /var/log. I always make /var a separate > > > partition. > > > > Yes, that is whole point. Separate comparments for everything is good. > > Terry seems to believe otherwise. > > Wrong. I gave ten good reasons why you would want things seperate, > whereas the original poster gave one bad one. > > You can't argue "filling the disk up". It's a bogus argument: > > I) Filling the disk up should not be catastrophic, even if it > does occur. How can it not be catastrophic? Think about a mail server. It will have to refuse e-mail, if there is no spool space. That is catastrophic. > II) Only root processes can override the reserve. This means pilot > error in the most general sense. Pilot error can also write > over the front of a raw disk; how does the software prevent > one kind of pilot error, but not the other? It can't. Who cares? Many process run as root, so they are all competing for the reserve. Also, non-root processes can be critical too. > III) If you have a root process which is a daemon, good sense > dictates that the process will have its own controls to > prevent overriding the reserve. The syslog argument > remains bogus, since you should use newsyslog instead, > and avoid the issue. newsyslog can limit logs to a particular size. It has no idea of how much space might actually be available. It can not avoid the issue, perhaps only limit it. It is only guarrenteed to avoid the issue, if /var/log is a separate filesystem. > For each example of badly behaved software you can come up with, I > will either point to a well behaved piece of software, or I will > simply say "then fix it". Please, let me use your magic wand on my software. I have no idea on how applications might continue to work without impairment with full filesystems. Seems to defy the laws of this uniserve. > The FreeBSD penchant for destroying passwd files when the disk is full > is an *error* in FreeBSD, and should be corrected. Then I can point > at (I) above, and state "so what? So the disk is full...". Who said it destroyed the passwd file? It just attempts to build new files, it it runs out of storage, it aborts, leaving the original passwd file. It kinda leaves you in lurch though, because you can't make any changes to it. > > > The only file in my root partition that has been modified in the last > > > week is /etc/dumpdates. > > > > And that might be a debatable location for that file. It is nice have / > > as static as possible. Some other things: /etc/aliases, > > /etc/master.passwd > > I definitely agree with this. / should be read-only. So should /usr, > if you want to get down to it. /usr is considerable easier to make ro than /. /etc/ is abused. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom From owner-freebsd-hackers Wed Nov 19 10:45:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10099 for hackers-outgoing; Wed, 19 Nov 1997 10:45:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10092 for ; Wed, 19 Nov 1997 10:45:37 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id TAA07286; Wed, 19 Nov 1997 19:45:56 +0100 (MET) (envelope-from sos) Message-Id: <199711191845.TAA07286@sos.freebsd.dk> Subject: Re: Mail spam, sigh... In-Reply-To: <199711191828.LAA05551@mt.sri.com> from Nate Williams at "Nov 19, 97 11:28:34 am" To: nate@mt.sri.com (Nate Williams) Date: Wed, 19 Nov 1997 19:45:56 +0100 (MET) Cc: sos@FreeBSD.dk, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.dk X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Nate Williams who wrote: > > If any of you gets a message back from my system claiming you > > should be shot or something to that extent, well, I'm sorry. > > The amount of JUNKmail recently has demanded that I enable > > my hysteric mail filter again, and its pretty harsh (one > > unsolicited mail, and that doamin is toast). > > Sorry for any inconvinience, but the filter stays this time... > > What I've done is setup my filter to only accept email from known > mailing lists, etc..., and also accept mail directly addressed to me. > Everything else goes into 'junk' which is 99.99% of the junk mail that I > receive, with .01% of it not being junk. Every once in a while I go > look in my junk folder for 'valid' email, but otherwise it tends to do > it's job well, and still not get rid of 'previously unknown by desired' > email. Well, I do the same thing, but have added rules to reject mail from a list of hostile sites/domans. I've encountered lots of mail that's addressed directly to my mail address, and that is stopped effectively now, I only get one junk email, and they are on the list :), together with sites on the "official" spam lists -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Nov 19 11:16:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA13538 for hackers-outgoing; Wed, 19 Nov 1997 11:16:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ccsales.ccsales.com (ccsales.ccsales.com [207.137.172.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA13529; Wed, 19 Nov 1997 11:16:20 -0800 (PST) (envelope-from randyk@ccsales.com) Date: Wed, 19 Nov 1997 11:20:39 -0800 (PST) From: Randy Katz To: WUSTL ListProc cc: hackers@freebsd.org Subject: strange things...HELP!!! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I tried to find out how this hacker is doing it on an ISP list and they said I was a hacker...HELP!!! The hacker ftp's into our server as a valid user (we will cancel him as soon as we know how to keep him out). Hacker copies /etc/master.passwd to his home directory. Hacker modified master.passwd. Hacker copies it back to /etc/master.passwd. How is he doing this? He does it fast (1 min. max). /etc/master.passwd is root/wheel 600. The hacker's account is not grouped under wheel. /etc/ is root/wheel 755. Is there something I'm doing wrong??? He can do it on any machine in our network. Don't try ccsales.com it's an old 2.1.0 FreeBSD box which I just use for personal mail. He has hacked it on FreeBSD 2.2.2 running wu-ftpd (BETA-13,14 & 15). HELP!!! Thanx, Randy Katz From owner-freebsd-hackers Wed Nov 19 11:53:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA18219 for hackers-outgoing; Wed, 19 Nov 1997 11:53:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from area51.stjohns.edu (area51.stjohns.edu [149.68.19.239]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA18212; Wed, 19 Nov 1997 11:53:19 -0800 (PST) (envelope-from lefty@area51.stjohns.edu) Received: from localhost (lefty@localhost) by area51.stjohns.edu (8.8.5/8.7.3) with SMTP id PAA00315; Wed, 19 Nov 1997 15:54:21 -0500 Date: Wed, 19 Nov 1997 15:54:21 -0500 (EST) From: "Lefty G." To: freebsd-questions@freebsd.org cc: freebsd-hackers@freebsd.org Subject: unsubscribe In-Reply-To: <19877.879962446@coconut.itojun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Wed Nov 19 12:06:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19983 for hackers-outgoing; Wed, 19 Nov 1997 12:06:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.5.84]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19971 for ; Wed, 19 Nov 1997 12:06:11 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.7/8.8.7) id NAA24046; Wed, 19 Nov 1997 13:06:10 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd024032; Wed Nov 19 13:05:57 1997 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA19787; Wed, 19 Nov 1997 13:05:53 -0700 (MST) From: Terry Lambert Message-Id: <199711192005.NAA19787@usr08.primenet.com> Subject: Re: Partitioning suggestions? To: tom@sdf.com (Tom) Date: Wed, 19 Nov 1997 20:05:53 +0000 (GMT) Cc: tlambert@primenet.com, Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@freebsd.org In-Reply-To: from "Tom" at Nov 19, 97 10:19:49 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I) Filling the disk up should not be catastrophic, even if it > > does occur. > > How can it not be catastrophic? Think about a mail server. It will > have to refuse e-mail, if there is no spool space. That is catastrophic. This is a graceful failure. The mail remains enqueued on the system attempting to deliver the mail; it's not lost. If you use the SMTP DSN extension, then you are even better off, but you don't *have* to in order for the failure to be graceful. Sendmail already has space limitation capabilities. The "-ob[/]" option allows refusal of messages when there are less than blocks available on the queue FS. If the "/" is specified, it will limit the maximum input message size to bytes, as well (and will refuse based on the SMTP "SIZE" extension if present, or after the terminating "." for the "DATA" command, if not). > > II) Only root processes can override the reserve. This means pilot > > error in the most general sense. Pilot error can also write > > over the front of a raw disk; how does the software prevent > > one kind of pilot error, but not the other? It can't. > > Who cares? Many process run as root, so they are all competing for the > reserve. Also, non-root processes can be critical too. Set quotas. The failure to set quotas is pilot error. > > III) If you have a root process which is a daemon, good sense > > dictates that the process will have its own controls to > > prevent overriding the reserve. The syslog argument > > remains bogus, since you should use newsyslog instead, > > and avoid the issue. > > newsyslog can limit logs to a particular size. It has no idea of how > much space might actually be available. It can not avoid the issue, > perhaps only limit it. It is only guarrenteed to avoid the issue, if > /var/log is a separate filesystem. That doesn't guarantee it. What if your FS fills up with PID files? You *must* be able to gracefuly fail on a resource failure; in other words, you must be able to handle any system call returning any error message which the system call may return based on the way you are using the call. > > For each example of badly behaved software you can come up with, I > > will either point to a well behaved piece of software, or I will > > simply say "then fix it". > > Please, let me use your magic wand on my software. I have no idea on > how applications might continue to work without impairment with full > filesystems. Seems to defy the laws of this uniserve. The *can't* continue to work; your wanting them to do so is what defies the laws of nature. What they *can* do (and *should* do) is fail gracefully. Do you think that any putative fix for the password file truncation bug can do anything *other* than fail gracefully? You expect it to allow the transaction on the theory it should grow more disk space to accommodate it? > > The FreeBSD penchant for destroying passwd files when the disk is full > > is an *error* in FreeBSD, and should be corrected. Then I can point > > at (I) above, and state "so what? So the disk is full...". > > Who said it destroyed the passwd file? It just attempts to build new > files, it it runs out of storage, it aborts, leaving the original passwd > file. It kinda leaves you in lurch though, because you can't make any > changes to it. So do three things: 1) Run as few things as possible as root; people bitch about the security implications all the time anyway. 2) Log in as root and delete things in excess of the reserve so you are no longer "in the lurch". 3) Up the reserve space to be back where it should be instead of the default FreeBSD picks to make owners of large disks happy; it was a bad political decision in the first place. Then you can be sure that you won't have to do #2 as frequently. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 12:22:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22218 for hackers-outgoing; Wed, 19 Nov 1997 12:22:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA22202 for ; Wed, 19 Nov 1997 12:21:59 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYGV8-0007Cm-00; Wed, 19 Nov 1997 12:13:30 -0800 Date: Wed, 19 Nov 1997 12:13:20 -0800 (PST) From: Tom To: Terry Lambert cc: Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <199711192005.NAA19787@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Terry Lambert wrote: > > > I) Filling the disk up should not be catastrophic, even if it > > > does occur. > > > > How can it not be catastrophic? Think about a mail server. It will > > have to refuse e-mail, if there is no spool space. That is catastrophic. > > This is a graceful failure. The mail remains enqueued on the I can't accept that idea of a "graceful" failure. I don't know if there are any "catastrophic" (ie. eaten e-mail, destroyed password files, etc) failures in FreeBSD, due to full filesystems. But the so-called graceful failures are the real essence of this thread. How do you avoid them in the first place? You probably do not realize that most SMTP sending software lacks auto retry. As soon as Sendmail starts refusing connections because of lack of space, expect your helpdesk to light up like a christmas tree. ... > > Who cares? Many process run as root, so they are all competing for the > > reserve. Also, non-root processes can be critical too. > > Set quotas. The failure to set quotas is pilot error. Quotas don't apply to root. > > newsyslog can limit logs to a particular size. It has no idea of how > > much space might actually be available. It can not avoid the issue, > > perhaps only limit it. It is only guarrenteed to avoid the issue, if > > /var/log is a separate filesystem. > > That doesn't guarantee it. What if your FS fills up with PID files? What would be creating pid files in /var/log? Tom From owner-freebsd-hackers Wed Nov 19 12:28:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22752 for hackers-outgoing; Wed, 19 Nov 1997 12:28:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22738 for ; Wed, 19 Nov 1997 12:28:04 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.7/8.8.7) id MAA14215; Wed, 19 Nov 1997 12:28:03 -0800 (PST) (envelope-from sef) Date: Wed, 19 Nov 1997 12:28:03 -0800 (PST) From: Sean Eric Fagan Message-Id: <199711192028.MAA14215@kithrup.com> To: hackers@freebsd.org Subject: Re: Mail spam, sigh... In-Reply-To: <199711191845.TAA07286.kithrup.freebsd.hackers@sos.freebsd.dk> References: <199711191828.LAA05551@mt.sri.com> from Nate Williams at "Nov 19, 97 11:28:34 am" Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Along this vein... I'd like to suggest adding the RBL support to the default sendmail file (freebsd.mc). This way, all FreeBSD systems would, by default, drop SMTP connections from the sites on the blacklist. I'd also like to add the anti-relay code to the file, but that's a bit trickier, I'm afraid (too easy to get wrong and screw things up). From owner-freebsd-hackers Wed Nov 19 12:31:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA23163 for hackers-outgoing; Wed, 19 Nov 1997 12:31:01 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from athena.veritas.com (athena.veritas.com [192.203.46.191]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA23148 for ; Wed, 19 Nov 1997 12:30:57 -0800 (PST) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com by athena.veritas.com with smtp (Smail3.1.29.0 #9) id m0xYGlp-000iwDC; Wed, 19 Nov 97 12:30 PST Received: from sigma.veritas.com by megami.veritas.com with smtp (Smail3.1.29.0 #7) id m0xYGlp-0000CuC; Wed, 19 Nov 97 12:30 PST Message-Id: From: Aaron Smith To: hackers@freebsd.org Subject: MFS /tmp oddness Date: Wed, 19 Nov 1997 12:30:39 -0800 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i'm having this problem where a boot-time-mounted MFS ends up being sized to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was the problem, i upped MAX and DFLDSIZ to 256M, but no dice. does anybody know why i'm getting such a tiny MFS? we tried using the -s option too but that didn't work either. sorry if this is a FAQ, i searched the mailing list archives to no avail. aaron On Mon, 17 Nov 1997 22:22:10 PST, John-Mark Gurney writes: >but be careful... normally you can only have a 64meg mfs unless you >increase the datasize limit to be larger than 64megs... I build my >kernel with: >options "MAXDSIZ=(512*1024*1024)" >options "DFLDSIZ=(512*1024*1024)" > >so that I can have: >Filesystem 1K-blocks Used Avail Capacity Mounted on >mfs:26 254319 62731 171243 27% /tmp > >note that the -s option specifies the size of the fs in 512byte blocks... >there is an option to have the mfs /tmp backed by a file (so if you >reboot your machine, your /tmp contents are saved, not sure if this >hurts performane or not) which helps prevents lose of data... From owner-freebsd-hackers Wed Nov 19 12:45:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA24827 for hackers-outgoing; Wed, 19 Nov 1997 12:45:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA24813 for ; Wed, 19 Nov 1997 12:45:22 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id MAA00371 for ; Wed, 19 Nov 1997 12:30:34 -0800 (PST) Date: Wed, 19 Nov 1997 12:30:33 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: Artificial Lifeform? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any artificial life programs for freebsd? Or easily portable. From owner-freebsd-hackers Wed Nov 19 12:52:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA25605 for hackers-outgoing; Wed, 19 Nov 1997 12:52:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA25595 for ; Wed, 19 Nov 1997 12:52:50 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA24569; Wed, 19 Nov 1997 15:52:35 -0500 (EST) Date: Wed, 19 Nov 1997 15:52:35 -0500 (EST) From: Snob Art Genre To: Tom cc: hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Tom wrote: > I can't accept that idea of a "graceful" failure. I don't know if there > are any "catastrophic" (ie. eaten e-mail, destroyed password > files, etc) failures in FreeBSD, due to full filesystems. But the > so-called graceful failures are the real essence of this thread. How do > you avoid them in the first place? Well, at first you don't. Then you learn how to estimate your disk space needs effectively. Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Wed Nov 19 13:39:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA01023 for hackers-outgoing; Wed, 19 Nov 1997 13:39:48 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA01008 for ; Wed, 19 Nov 1997 13:39:43 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (tc-if2-17.ida.net [208.141.171.74]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id OAA23804 for ; Wed, 19 Nov 1997 14:39:40 -0700 Date: Wed, 19 Nov 1997 14:39:05 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: hackers@FreeBSD.ORG Subject: Re: Mail spam, sigh... In-Reply-To: <199711192028.MAA14215@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Sean Eric Fagan wrote: > Along this vein... I'd like to suggest adding the RBL support to the default > sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > default, drop SMTP connections from the sites on the blacklist. > > I'd also like to add the anti-relay code to the file, but that's a bit > trickier, I'm afraid (too easy to get wrong and screw things up). > Would this cause problems for home networks which are only intermittently connected to the network? Charles Mott From owner-freebsd-hackers Wed Nov 19 13:41:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA01309 for hackers-outgoing; Wed, 19 Nov 1997 13:41:11 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA01303 for ; Wed, 19 Nov 1997 13:41:09 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA26782; Wed, 19 Nov 1997 13:41:03 -0800 Date: Wed, 19 Nov 1997 13:41:02 -0800 (PST) From: "Brian N. Handy" To: Sean Eric Fagan Cc: hackers@FreeBSD.ORG Subject: Re: Mail spam, sigh... In-Reply-To: <199711192028.MAA14215@kithrup.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Along this vein... I'd like to suggest adding the RBL support to the default >sendmail file (freebsd.mc). This way, all FreeBSD systems would, by >default, drop SMTP connections from the sites on the blacklist. > >I'd also like to add the anti-relay code to the file, but that's a bit >trickier, I'm afraid (too easy to get wrong and screw things up). I'd also like an easy-drop-in-way to drop email from sites that don't show up in the nameserver. (Maybe this is easy, I haven't done my research.) Brina From owner-freebsd-hackers Wed Nov 19 13:49:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA02475 for hackers-outgoing; Wed, 19 Nov 1997 13:49:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA02407 for ; Wed, 19 Nov 1997 13:49:18 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id QAA15622; Wed, 19 Nov 1997 16:47:20 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Wed, 19 Nov 1997 16:47:19 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "Jamil J. Weatherbee" cc: hackers@FreeBSD.ORG Subject: Re: Artificial Lifeform? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Jamil J. Weatherbee wrote: > > Are there any artificial life programs for freebsd? > Or easily portable. > /usr/ports/games/xlife. > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Nov 19 14:08:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA04756 for hackers-outgoing; Wed, 19 Nov 1997 14:08:11 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from garman.dyn.ml.org (pm106-01.dialip.mich.net [192.195.231.203]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA04732 for ; Wed, 19 Nov 1997 14:08:07 -0800 (PST) (envelope-from garman@earthling.net) Received: (qmail 2096 invoked by uid 1000); 19 Nov 1997 22:07:41 -0000 Message-ID: Date: Wed, 19 Nov 1997 17:07:40 -0500 From: garman@phs.k12.ar.us To: khetan@iafrica.com (Khetan Gajjar) Cc: hackers@freebsd.org Subject: Re: WordPerfect 7.0 for SCO References: X-Mailer: Mutt 0.58 Mime-Version: 1.0 Reply-To: garman@earthling.net X-Phase-Of-Moon: The Moon is Waning Gibbous (70% of Full) X-Operating-System: FreeBSD/i386 2.2-STABLE In-Reply-To: ; from Khetan Gajjar on Nov 19, 1997 02:10:08 +0200 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Khetan Gajjar writes: > Hi. > > I've bought myself a copy of WordPerfect 7.0 for SCO OpenServer 5. > I was wondering if it was possible to install this - I've tried the > GUI installation, but it just core dumps (bus error), and the text version > mutters about incorrect terminal emulation. > you can run the Linux version of WP7.0 with no problem on FreeBSD (I have it open right now). Never tried the SCO version. To make sure, you can download an "evaluation" copy from their site. it is in ftp.turbolinux.com:/pub/linux/corelwp if i remember correctly. enjoy, -- Jason Garman http://garman.home.ml.org/ Student, University of Maryland garman@earthling.net "A friend in Campus Parking is a True Friend Indeed." -- me From owner-freebsd-hackers Wed Nov 19 14:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08150 for hackers-outgoing; Wed, 19 Nov 1997 14:51:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08129 for ; Wed, 19 Nov 1997 14:50:52 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA10527; Wed, 19 Nov 1997 22:50:45 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA27441; Wed, 19 Nov 1997 23:50:45 +0100 (MET) Date: Wed, 19 Nov 1997 23:50:45 +0100 (MET) Message-Id: <199711192250.XAA27441@bitbox.follo.net> From: Eivind Eklund To: Randy Katz CC: wu-ftpd@wugate.wustl.edu, hackers@FreeBSD.ORG In-reply-to: Randy Katz's message of Wed, 19 Nov 1997 11:20:39 -0800 (PST) Subject: Re: strange things...HELP!!! References: Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hello, > > I tried to find out how this hacker is doing it on an ISP list and they > said I was a hacker...HELP!!! > > The hacker ftp's into our server as a valid user (we will cancel him as > soon as we know how to keep him out). Hacker copies /etc/master.passwd to > his home directory. Hacker modified master.passwd. Hacker copies it back > to /etc/master.passwd. > > How is he doing this? I don't know, but if this is happening repeatedly I'd try using ktrace to find out what happens. It definitely sound like a wu-ftpd bug which happens before it drops privileges (or possibly a combination of a bug that happens after dropping privileges and a root exploit, e.g. the /proc exploit (fixed in -stable somewhat pre-2.2.5) or the open() problem (fixed in -stable a day or two post-2.2.5). Eivind. From owner-freebsd-hackers Wed Nov 19 14:57:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08790 for hackers-outgoing; Wed, 19 Nov 1997 14:57:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08784; Wed, 19 Nov 1997 14:57:34 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA02140; Wed, 19 Nov 1997 14:57:03 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002136; Wed Nov 19 14:56:55 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id OAA26978; Wed, 19 Nov 1997 14:56:55 -0800 (PST) From: Archie Cobbs Message-Id: <199711192256.OAA26978@bubba.whistle.com> Subject: Re: IPSec and 2.2-STABLE In-Reply-To: <19877.879962446@coconut.itojun.org> from Jun-ichiro itojun Itoh at "Nov 20, 97 03:00:46 am" To: itojun@itojun.org (Jun-ichiro itojun Itoh) Date: Wed, 19 Nov 1997 14:56:55 -0800 (PST) Cc: ru@ucb.crimea.ua, itojun@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jun-ichiro itojun Itoh writes: > >What is the general state of IPSec for FreeBSD? > > We, WIDE project IPv6 working group is working on IPv6/IPsec > extension for FreeBSD. As for IPsec we support both rfc182* > and draft-ietf-*. ESP Transport mode is working very well. > ESP Tunnel mode is yet to be done. > See http://www.v6.wide.ad.jp/ for more info. > > >Can I use it with post-2.2.5-RELEASE (i.e. 2.2-STABLE)? > > We use 2.2.5-RELEASE as base version but I believe our patch > can easily be applied. Also, when I get around to it I'm going to make a port of Sun's SKIP package for FreeBSD 2.2-stable (it definitely requires some patching). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Wed Nov 19 15:01:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA09215 for hackers-outgoing; Wed, 19 Nov 1997 15:01:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA09207 for ; Wed, 19 Nov 1997 15:01:30 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA06547; Wed, 19 Nov 1997 16:00:39 -0700 (MST) From: Terry Lambert Message-Id: <199711192300.QAA06547@usr01.primenet.com> Subject: Re: Partitioning suggestions? To: tom@sdf.com (Tom) Date: Wed, 19 Nov 1997 23:00:36 +0000 (GMT) Cc: tlambert@primenet.com, Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@FreeBSD.ORG In-Reply-To: from "Tom" at Nov 19, 97 12:13:20 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can't accept that idea of a "graceful" failure. I don't know if there > are any "catastrophic" (ie. eaten e-mail, destroyed password > files, etc) failures in FreeBSD, due to full filesystems. But the > so-called graceful failures are the real essence of this thread. How do > you avoid them in the first place? By not engaging in sysadm pilot error that results in filled drives. > You probably do not realize that most SMTP sending software lacks auto > retry. As soon as Sendmail starts refusing connections because of lack of > space, expect your helpdesk to light up like a christmas tree. The better to encourage you to correct your pilot error after the fact. I don't have a problem with this feedback loop. If user complaints are more of a problem than reacting to the complaint (ie: possible loss of sales, etc.), then that's yet another feedback loop, one that encourages you to be proactive instead of reactive. These are all good things, since they force people out of denial about the way the universe works. 8-). > > > Who cares? Many process run as root, so they are all competing for the > > > reserve. Also, non-root processes can be critical too. > > > > Set quotas. The failure to set quotas is pilot error. > > Quotas don't apply to root. "Doctor, it hurts when I run as root...". As you pointed out before (and I pointed out before), if running as root is a problem, then fix that problem instead of kludging hard group quotas by limiting FS size. > > > newsyslog can limit logs to a particular size. It has no idea of how > > > much space might actually be available. It can not avoid the issue, > > > perhaps only limit it. It is only guarrenteed to avoid the issue, if > > > /var/log is a separate filesystem. > > > > That doesn't guarantee it. What if your FS fills up with PID files? > > What would be creating pid files in /var/log? In /var. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 15:02:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA09336 for hackers-outgoing; Wed, 19 Nov 1997 15:02:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA09315 for ; Wed, 19 Nov 1997 15:02:35 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA02174 for ; Wed, 19 Nov 1997 15:02:03 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma002171; Wed Nov 19 15:01:55 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id PAA27018 for hackers@freebsd.org; Wed, 19 Nov 1997 15:01:55 -0800 (PST) From: Archie Cobbs Message-Id: <199711192301.PAA27018@bubba.whistle.com> Subject: test email To: hackers@freebsd.org Date: Wed, 19 Nov 1997 15:01:55 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk test email From owner-freebsd-hackers Wed Nov 19 15:22:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA11701 for hackers-outgoing; Wed, 19 Nov 1997 15:22:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA11690 for ; Wed, 19 Nov 1997 15:22:33 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA09195; Wed, 19 Nov 1997 16:22:24 -0700 (MST) From: Terry Lambert Message-Id: <199711192322.QAA09195@usr01.primenet.com> Subject: Re: Mail spam, sigh... To: sef@kithrup.com (Sean Eric Fagan) Date: Wed, 19 Nov 1997 23:22:22 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199711192028.MAA14215@kithrup.com> from "Sean Eric Fagan" at Nov 19, 97 12:28:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Along this vein... I'd like to suggest adding the RBL support to the default > sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > default, drop SMTP connections from the sites on the blacklist. > > I'd also like to add the anti-relay code to the file, but that's a bit > trickier, I'm afraid (too easy to get wrong and screw things up). I have yet to see a clean way to make this work with a transiently connected system. I'd guess that the majority of users are on transiently connected systems (note: I did not say the majority of FreeBSD boxes). We need to start thinking about a set of "out of the box" configurations: o Not connected to the Internet at all o Transiently connected (ie: dialup async/ISDN) o Batch outgoing mail o Connect and send outgoing mail immediately o Permananetly connected That's enough for now, anyway... I'd like to see mobile/docked, moble/undocked/disconnected, and mobile/undocked/connected configurations as well (get your email using the phone on the Airplane, at the hotel, etc.), but first things first. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Nov 19 15:37:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13259 for hackers-outgoing; Wed, 19 Nov 1997 15:37:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from postman.opengroup.org (postman.opengroup.org [130.105.1.152]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13239 for ; Wed, 19 Nov 1997 15:37:14 -0800 (PST) (envelope-from louis@opengroup.org) Received: from opengroup.org (fireball.camb.opengroup.org [130.105.3.34]) by postman.opengroup.org (8.8.6/8.8.6) with ESMTP id SAA24946; Wed, 19 Nov 1997 18:35:54 -0500 (EST) Message-Id: <199711192335.SAA24946@postman.opengroup.org> To: Sean Eric Fagan cc: hackers@freebsd.org Subject: Re: Mail spam, sigh... In-reply-to: Message from Sean Eric Fagan <199711192028.MAA14215@kithrup.com> . X-uri: http://www.osf.org/~louis/ X-attribution: louis X-author: Louis Theran Date: Wed, 19 Nov 1997 18:35:53 -0500 From: Louis Theran Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "sef" == Sean Eric Fagan writes: sef> Along this vein... I'd like to suggest adding the RBL support sef> to the default sendmail file (freebsd.mc). This way, all sef> FreeBSD systems would, by default, drop SMTP connections from sef> the sites on the blacklist. I don't think that this is a very good idea. For most sites the RBL is way too restrictive in what it blackholes. I have played around with it a bit using qmail, and I noticed that ISPs like erols and concentric were making it into the RBL. Both of those have pretty good anti-spam AUPs, but more importantly they are both big enough that you will start bouncing a lot of mail from legitimate users, which is really not acceptable in most places. I think that the RBL gets too many false positives to be useful for most people, unfortunately. sef> I'd also like to add the anti-relay code to the file, but sef> that's a bit trickier, I'm afraid (too easy to get wrong and sef> screw things up). I'm all for this, but as you say, it is easy to screw up with sendmail, and there is also no one solution to this problem that works everywhere. Why not just ship the system with sendmail's SMTP daemon turned off? All that is required is a simple change of "YES" to "NO" in rc.conf. Anybody who needs it turned on should be smart enough to know what other things they have to do in terms of their sendmail.cf file to prevent their host from being hijacked by a spammer, etc. Empirical evidence would suggest that this assertion is incorrect, as there doesn't seem to be a shortage of open sendmail relays on the net, but anything that makes admins think before they enable relaying is probably a good thing. Personally I am waiting for Eric Allman to do the responsible thing and disable relaying in the official sendmail distribution. Something that I think that could be done pretty easily, though, would be to disable the various address forms that nobody really needs any more, such as the percent hack and the multiple '@' hack. Can anybody think of a reason why we need these by default in 1997? ^Louis From owner-freebsd-hackers Wed Nov 19 15:42:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13617 for hackers-outgoing; Wed, 19 Nov 1997 15:42:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13610 for ; Wed, 19 Nov 1997 15:42:13 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id SAA06732; Wed, 19 Nov 1997 18:42:07 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711192342.SAA06732@dyson.iquest.net> Subject: Re: MFS /tmp oddness In-Reply-To: from Aaron Smith at "Nov 19, 97 12:30:39 pm" To: aaron@veritas.com (Aaron Smith) Date: Wed, 19 Nov 1997 18:42:07 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Aaron Smith said: > i'm having this problem where a boot-time-mounted MFS ends up being sized > to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was > the problem, i upped MAX and DFLDSIZ to 256M, but no dice. > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > option too but that didn't work either. > > sorry if this is a FAQ, i searched the mailing list archives to no avail. > This is in my fstab and works. (note that the -b=16384,-f=2048 options are eccentric, but this is copied directly.) swap /tmp mfs rw,-s=210000,-b=16384,-f=2048 0 0 -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Wed Nov 19 16:02:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15024 for hackers-outgoing; Wed, 19 Nov 1997 16:02:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from pobox.com (ott-on1-15.netcom.ca [207.181.90.79]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15013 for ; Wed, 19 Nov 1997 16:02:05 -0800 (PST) (envelope-from brianc@pobox.com) Received: (from brianc@localhost) by pobox.com (8.8.7/8.8.7) id TAA07567; Wed, 19 Nov 1997 19:01:17 -0500 (EST) (envelope-from brianc) Message-ID: <19971119190117.04396@pobox.com> Date: Wed, 19 Nov 1997 19:01:17 -0500 From: Brian Campbell To: hackers@FreeBSD.ORG Subject: Re: MFS /tmp oddness References: <199711192342.SAA06732@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199711192342.SAA06732@dyson.iquest.net>; from John S. Dyson on Wed, Nov 19, 1997 at 06:42:07PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Nov 19, 1997 at 06:42:07PM -0500, John S. Dyson wrote: > Aaron Smith said: > > i'm having this problem where a boot-time-mounted MFS ends up being sized > > to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was > > the problem, i upped MAX and DFLDSIZ to 256M, but no dice. > > > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > > option too but that didn't work either. > > > > sorry if this is a FAQ, i searched the mailing list archives to no avail. > > > This is in my fstab and works. (note that the -b=16384,-f=2048 options > are eccentric, but this is copied directly.) > > swap /tmp mfs rw,-s=210000,-b=16384,-f=2048 0 0 Did you have to modify login.conf (or something else) to make this work? Mine specfies -s262000 but only manages to get 32M From owner-freebsd-hackers Wed Nov 19 16:10:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15769 for hackers-outgoing; Wed, 19 Nov 1997 16:10:11 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15738 for ; Wed, 19 Nov 1997 16:10:00 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id QAA26606; Wed, 19 Nov 1997 16:09:51 -0800 (PST) Message-ID: <19971119160950.02862@hydrogen.nike.efn.org> Date: Wed, 19 Nov 1997 16:09:50 -0800 From: John-Mark Gurney To: Aaron Smith Cc: hackers@FreeBSD.ORG Subject: Re: MFS /tmp oddness Reply-To: John-Mark Gurney References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Aaron Smith on Wed, Nov 19, 1997 at 12:30:39PM -0800 Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Aaron Smith scribbled this message on Wed, Nov 19, 1997 at 12:30 -0800: > i'm having this problem where a boot-time-mounted MFS ends up being sized > to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was > the problem, i upped MAX and DFLDSIZ to 256M, but no dice. > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > option too but that didn't work either. > > sorry if this is a FAQ, i searched the mailing list archives to no avail. sounds like you need to add a ulimit -d or increase the daemon data size in your /etc/login.conf... basicly the inital data size is to small for your config.. I'm still running 2.2.1-R so that I don't have that problem with login.conf.. ttyl.. > On Mon, 17 Nov 1997 22:22:10 PST, John-Mark Gurney writes: > >but be careful... normally you can only have a 64meg mfs unless you > >increase the datasize limit to be larger than 64megs... I build my > >kernel with: > >options "MAXDSIZ=(512*1024*1024)" > >options "DFLDSIZ=(512*1024*1024)" > > > >so that I can have: > >Filesystem 1K-blocks Used Avail Capacity Mounted on > >mfs:26 254319 62731 171243 27% /tmp > > > >note that the -s option specifies the size of the fs in 512byte blocks... > >there is an option to have the mfs /tmp backed by a file (so if you > >reboot your machine, your /tmp contents are saved, not sure if this > >hurts performane or not) which helps prevents lose of data... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Nov 19 16:25:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA16835 for hackers-outgoing; Wed, 19 Nov 1997 16:25:35 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16812 for ; Wed, 19 Nov 1997 16:25:22 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id SAA06978 for ; Wed, 19 Nov 1997 18:25:13 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma006931; Wed, 19 Nov 97 18:24:48 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id SAA21582 for ; Wed, 19 Nov 1997 18:24:48 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Wed, 19 Nov 1997 18:24:47 -0600 (CST) From: Kyle Mestery To: freebsd-hackers@freebsd.org Subject: Is my drive bad? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tried this on hardware last week, thought I would see if anyone on this list has some ideas. Any help appreciated! ---------- Forwarded message ---------- Date: Thu, 13 Nov 1997 21:40:46 -0600 (CST) From: Kyle Mestery To: freebsd-hardware@FreeBSD.ORG Subject: Is my drive bad? Hi, I have the following drive exhibiting the following problems, and was wondering if the drive is bad, like I suspect. Here is the drive: wd2: 1040MB (2130912 sectors), 2114 cyls, 16 heads, 63 S/T, 512 B/S And, here is what happens when I try to mount the drive: wd2c: reverting to PIO mode writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2 : status 71 error 4 wd2c: hard error writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2: status 71 error 4 wd2c: reverting to non-multi sector mode writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2: status 71 error 4 I manage to get a couple of those, depending on what partition I try and mount. The drive was on a machine about 6 months ago running 2.2, and I am trying to mount the partitions on a 3.0 machine. Also, attempting to use /stand/sysinstall instead of doing disklabel/newfs by hand results in the errors above and sysinstall exiting. The reason I am asking if the drive is going bad is because all partitions on it pass a fsck. Any ideas? Kyle Mestery StorageTek's Network Systems Group 7600 Boone Ave. N., Minneapolis, MN 55428 mesteka@anubis.network.com, mestery@winternet.com "You do not greet Death, you punch him in the throat repeatedly until he drags you away." --No Fear From owner-freebsd-hackers Wed Nov 19 16:48:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA18681 for hackers-outgoing; Wed, 19 Nov 1997 16:48:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cleopatra.ultra.net (cleopatra.ultra.net [199.232.56.35]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18661 for ; Wed, 19 Nov 1997 16:48:49 -0800 (PST) (envelope-from moncrg@ma.ultranet.com) Received: from moncrg (d69.b66.cmb.ma.ultra.net [209.6.66.69]) by cleopatra.ultra.net (8.8.5/ult1.05) with SMTP id TAA03486 for ; Wed, 19 Nov 1997 19:48:37 -0500 (EST) From: "Gregory D Moncreaff" To: "Hackers FreeBSD" Subject: 2.2.5, cvs, recommended development organization? Date: Wed, 19 Nov 1997 19:48:48 -0500 Message-ID: <01bcf54e$10138460$454206d1@moncrg> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0009_01BCF524.273D7C60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0009_01BCF524.273D7C60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Just got the 2.2.5 4 disk set with the cvs disk, since xemacs won't let me do anyhing with source code because of the cvs tags was wonderring what the recommended way of laying out the disks, repository, etc are? btw, I am a complete newbie to cvs. I did look at the man page, and the info file [which was not in the info title page btw] but there info was rather theoretical, and I was looking for an example the enviornment would have 2-4 developers, not on the internet, connected via a local ethernet lan. 1-2 doing kernel source work, others working on utilities, etc. could I do this with one repository? would each kernel deveolper need an entire local source tree checked out for `make world` how much disk space is involved? [source, build, etc] how long would it take to build? any pratical info, observations, etc will be appreciated -g ------=_NextPart_000_0009_01BCF524.273D7C60 Content-Type: text/x-vcard; name="Gregory Donald Moncreaff.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Gregory Donald Moncreaff.vcf" BEGIN:VCARD N:Moncreaff;Gregory;Donald FN:Gregory Donald Moncreaff EMAIL;PREF;INTERNET:moncrg@ma.ultranet.com END:VCARD ------=_NextPart_000_0009_01BCF524.273D7C60-- From owner-freebsd-hackers Wed Nov 19 16:56:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19154 for hackers-outgoing; Wed, 19 Nov 1997 16:56:08 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-12.ix.netcom.com [207.93.143.140]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19149 for ; Wed, 19 Nov 1997 16:56:05 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id QAA01272; Wed, 19 Nov 1997 16:55:55 -0800 (PST) Date: Wed, 19 Nov 1997 16:55:55 -0800 (PST) Message-Id: <199711200055.QAA01272@silvia.HIP.Berkeley.EDU> To: jamil@trojanhorse.ml.org CC: hackers@FreeBSD.ORG In-reply-to: (jamil@trojanhorse.ml.org) Subject: Re: Artificial Lifeform? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Are there any artificial life programs for freebsd? jkh is one. Satoshi :> From owner-freebsd-hackers Wed Nov 19 16:58:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19304 for hackers-outgoing; Wed, 19 Nov 1997 16:58:58 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19292 for ; Wed, 19 Nov 1997 16:58:53 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA01022; Wed, 19 Nov 1997 19:58:30 -0500 (EST) Date: Wed, 19 Nov 1997 19:58:29 -0500 (EST) From: Snob Art Genre To: John-Mark Gurney cc: Aaron Smith , hackers@freebsd.org Subject: Re: MFS /tmp oddness In-Reply-To: <19971119160950.02862@hydrogen.nike.efn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, John-Mark Gurney wrote: > sounds like you need to add a > ulimit -d > > or increase the daemon data size in your /etc/login.conf... basicly > the inital data size is to small for your config.. I'm still running > 2.2.1-R so that I don't have that problem with login.conf.. This latter fixed it for me just now . . . thanks! Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Wed Nov 19 17:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21011 for hackers-outgoing; Wed, 19 Nov 1997 17:16:22 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20990 for ; Wed, 19 Nov 1997 17:16:16 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id RAA00544 for ; Wed, 19 Nov 1997 17:16:05 -0800 (PST) Date: Wed, 19 Nov 1997 17:16:05 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: Need suggestions for a Name change Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have named my driver "aiox" for the: Industrial Computer Source AIO8-P 12 bit 8 channel analog board however it was mentioned that aiox was very much like asynchronous i/o and not analog io, I am asking for suggestions on a better name to avoid confusion with this. Thanks. From owner-freebsd-hackers Wed Nov 19 17:27:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22115 for hackers-outgoing; Wed, 19 Nov 1997 17:27:07 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cam.grad.kiev.ua ([195.5.25.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22097 for ; Wed, 19 Nov 1997 17:27:00 -0800 (PST) (envelope-from Ruslan@Shevchenko.kiev.ua) Received: from Shevchenko.kiev.ua (localhost [127.0.0.1]) by cam.grad.kiev.ua (8.8.7/8.8.5) with ESMTP id BAA27881 for ; Thu, 20 Nov 1997 01:26:23 GMT Message-ID: <347391BA.2E7168CC@Shevchenko.kiev.ua> Date: Thu, 20 Nov 1997 01:26:18 +0000 From: Ruslan Shevchenko X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: rebuilding of whatis database does not care about setting in /etc/manpath.conf Content-Type: multipart/mixed; boundary="------------C9117B100BBA79E6F6BDF7AF" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------C9117B100BBA79E6F6BDF7AF Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Rebuilding of whatis database in /etc/wheecly use static MANPATH, so, if I change mypath in /etc/manpath.conf (for example, to add manuals to perl5), whatis database is not build for it => apropos not work for manuals in this path. The fix is trivial (see in attachment). I write to hackers, with hope, that somebody quickly correct this. Or it is nessesory to interact with commiters via send-pr ? --------------C9117B100BBA79E6F6BDF7AF Content-Type: text/plain; charset=koi8-r; name="etc-wheekly-path" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="etc-wheekly-path" --- /etc/weekly.old Thu Nov 20 01:13:25 1997 +++ /etc/weekly Thu Nov 20 01:17:05 1997 @@ -52,11 +52,10 @@ echo "" echo "Rebuilding whatis database:" -if [ -d /usr/X11R6/man ] +MANPATH=`/usr/bin/manpath` +if [ "x$MANPATH" = "x" ] then -MANPATH=${MANPATH:-/usr/share/man:/usr/X11R6/man:/usr/local/man} -else -MANPATH=${MANPATH:-/usr/share/man:/usr/local/man} + echo 'some bad with you manpath' fi makewhatis.local "${MANPATH}" --------------C9117B100BBA79E6F6BDF7AF-- From owner-freebsd-hackers Wed Nov 19 17:35:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23106 for hackers-outgoing; Wed, 19 Nov 1997 17:35:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23095; Wed, 19 Nov 1997 17:35:17 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id BAA14119; Thu, 20 Nov 1997 01:35:13 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711200135.BAA14119@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jonathan M. Bresler" cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@freebsd.org Subject: Re: /etc/mail filters in 2.2.5 In-reply-to: Your message of "Sun, 16 Nov 1997 06:46:03 PST." <199711161446.GAA24588@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Nov 1997 01:35:13 +0000 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Brian Somers wrote: > > > > > Brian, > > > there are a couple issues here: > > > > > > Brian Somers wrote: > > > > I installed the /etc/mail stuff a few days ago, and added a few sites > > > > to domains.txt, specifically: > > > > > > > > BIGFOOT.DALTEK.NET^M #blocked. contact postmaster > > > > > > first, that "^M" is it in the file? > > > is so please delete it. > > > after deleting the "^M" > > > cd /etc/mail; make install > > > > Hmm, the domains.txt I got with the ``make'' had 'em in, so I figured > > they were meant to be :-I > > ahh.....did you use DOS! > "^M" is teh DOS extra end-of-line character. > DOS uses both and to indicate and end-of-line. > Unix uses only one, the Mac uses the other. > > > > > second, the way i wrote the rules, they block mail > > > from a domain, hence the file is called domains.txt ;) > > > bigfoot.daltek.net is a host, rather than a domain. > > > you can change the entry domains.txt to "daltek.net". > > > that will block mail from all of daltek.net. or you can > > > use the amended rules below to block mail from both > > > hosts and domains. then you can use entries like > > > "bigfoot.daltek.net" in domains.txt. > > > > > > add the rules below that are *not* preceded by a ">" > > > at the start of the line ;) > > > > Ok, done - thanks. I'll keep an eye on things. > > cool....let me know if there are any problems. [.....] > jmb Oh joy ! I had my first bounced (by me) mail today :-) Thanks. -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Wed Nov 19 17:42:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23698 for hackers-outgoing; Wed, 19 Nov 1997 17:42:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23680 for ; Wed, 19 Nov 1997 17:42:22 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA15015; Thu, 20 Nov 1997 01:41:36 GMT Date: Thu, 20 Nov 1997 10:41:36 +0900 (JST) From: Michael Hancock To: Gregory D Moncreaff cc: Hackers FreeBSD Subject: Re: 2.2.5, cvs, recommended development organization? In-Reply-To: <01bcf54e$10138460$454206d1@moncrg> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="----=_NextPart_000_0009_01BCF524.273D7C60" Content-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ------=_NextPart_000_0009_01BCF524.273D7C60 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-ID: On Wed, 19 Nov 1997, Gregory D Moncreaff wrote: > btw, I am a complete newbie to cvs. I did look at the man page, > and the info file [which was not in the info title page btw] but there > info was rather theoretical, and I was looking for an example Try http://www.cs.utah.edu/csinfo/texinfo/cvs/cvs_toc.html. Regards, Mike Hancock ------=_NextPart_000_0009_01BCF524.273D7C60-- From owner-freebsd-hackers Wed Nov 19 17:53:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24536 for hackers-outgoing; Wed, 19 Nov 1997 17:53:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24520 for ; Wed, 19 Nov 1997 17:53:03 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id UAA06472; Wed, 19 Nov 1997 20:51:03 -0500 (EST) Date: Wed, 19 Nov 1997 20:51:02 -0500 (EST) From: "Matthew N. Dodd" To: Tom cc: Terry Lambert , Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@FreeBSD.ORG Subject: Re: Partitioning suggestions? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Tom wrote: > You probably do not realize that most SMTP sending software lacks auto > retry. As soon as Sendmail starts refusing connections because of lack of > space, expect your helpdesk to light up like a christmas tree. If you're worried about QOS for your users have at least 2 machines in a DNS rotary for users to use for sending their mail (smtp.foo.com). These machines only need have a small amount of disk space. These 'smtp' machines speak -only- to your relay boxes. Boxes that speak to users shouldn't be attempting delivery. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Wed Nov 19 17:56:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24802 for hackers-outgoing; Wed, 19 Nov 1997 17:56:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24797 for ; Wed, 19 Nov 1997 17:56:51 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id UAA08628; Wed, 19 Nov 1997 20:56:33 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711200156.UAA08628@dyson.iquest.net> Subject: Re: Is my drive bad? In-Reply-To: from Kyle Mestery at "Nov 19, 97 06:24:47 pm" To: mestery@winternet.com (Kyle Mestery) Date: Wed, 19 Nov 1997 20:56:33 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kyle Mestery said: > > Tried this on hardware last week, thought I would see if anyone on this > list has some ideas. Any help appreciated! > > > wd2: 1040MB (2130912 sectors), 2114 cyls, 16 heads, 63 S/T, 512 B/S > > And, here is what happens when I try to mount the drive: > wd2c: reverting to PIO mode writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn > 0)wd2 > : status 71 error 4 > wd2c: hard error writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2: > status 71 > error 4 > wd2c: reverting to non-multi sector mode writing fsbn 0 of 0-15 (wd2 bn 0; > cn 0 > tn 0 sn 0)wd2: status 71 error 4 > Those errors are not the typical ones that I see when a drive has gone bad. You might want to rebuild to kernel to run in non-multi-sector mode. I have never tried to run multi-sector mode on a drive that fails doing it. Are you using an old drive? -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Wed Nov 19 17:57:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24851 for hackers-outgoing; Wed, 19 Nov 1997 17:57:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24844 for ; Wed, 19 Nov 1997 17:57:43 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id UAA08633; Wed, 19 Nov 1997 20:57:36 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711200157.UAA08633@dyson.iquest.net> Subject: Re: MFS /tmp oddness In-Reply-To: <19971119190117.04396@pobox.com> from Brian Campbell at "Nov 19, 97 07:01:17 pm" To: brianc@pobox.com (Brian Campbell) Date: Wed, 19 Nov 1997 20:57:36 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Campbell said: > On Wed, Nov 19, 1997 at 06:42:07PM -0500, John S. Dyson wrote: > > Aaron Smith said: > > > i'm having this problem where a boot-time-mounted MFS ends up being sized > > > to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was > > > the problem, i upped MAX and DFLDSIZ to 256M, but no dice. > > > > > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > > > option too but that didn't work either. > > > > > > sorry if this is a FAQ, i searched the mailing list archives to no avail. > > > > > This is in my fstab and works. (note that the -b=16384,-f=2048 options > > are eccentric, but this is copied directly.) > > > > swap /tmp mfs rw,-s=210000,-b=16384,-f=2048 0 0 > > Did you have to modify login.conf (or something else) to make this work? > Mine specfies -s262000 but only manages to get 32M > I changed my login.conf a long time ago. I didn't even think of it. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Wed Nov 19 17:58:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24922 for hackers-outgoing; Wed, 19 Nov 1997 17:58:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24917 for ; Wed, 19 Nov 1997 17:58:22 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id UAA06558; Wed, 19 Nov 1997 20:58:00 -0500 (EST) Date: Wed, 19 Nov 1997 20:58:00 -0500 (EST) From: "Matthew N. Dodd" To: "Brian N. Handy" cc: Sean Eric Fagan , hackers@freebsd.org Subject: Re: Mail spam, sigh... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Brian N. Handy wrote: > I'd also like an easy-drop-in-way to drop email from sites that don't show > up in the nameserver. (Maybe this is easy, I haven't done my research.) Svalid_host # check for valid domain name R$* $: $>3 $1 R $* < @ $+ . > $: $1 @ $2 R $* < @ $+ > $#error $@ 4.5.1 $: "451 Domain must resolve" I'm still working on one that checks forward and reverse and fusses if they do not match. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Wed Nov 19 18:07:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25455 for hackers-outgoing; Wed, 19 Nov 1997 18:07:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25443 for ; Wed, 19 Nov 1997 18:07:51 -0800 (PST) (envelope-from mouth@ibm.net) Received: from slip129-37-53-101.ca.us.ibm.net (slip129-37-53-101.ca.us.ibm.net [129.37.53.101]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id CAA151046; Thu, 20 Nov 1997 02:07:24 GMT From: mouth@ibm.net (John Kelly) To: Bruce Evans Cc: hackers@freebsd.org Subject: Re: Status of 650 UART support Date: Thu, 20 Nov 1997 03:08:34 GMT Message-ID: <34739fe9.22409@smtp-gw01.ny.us.ibm.net> References: <199711150553.QAA31140@godzilla.zeta.org.au> In-Reply-To: <199711150553.QAA31140@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.01/16.397 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA25451 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 15 Nov 1997 16:53:53 +1100, Bruce Evans wrote: >> not sure how to calculate the time required for the 8-bit bus cycles. > Each i/o takes about 1 usec on an 8MHz ISA bus (perhaps >125 nsec more or less) I tried some timing tests and measured almost 2 usec for one 8MHz ISA bus I/O on a 486 DX4-100. I used the following real-mode Turbo C DOS ISR with a dummy loop to repeat reading the UART line status register a million times. The rest of the program (not shown) is a simple terninal program where I can type characters which are sent to the modem and echoed back. The ISR grabs the incoming echoed characters and puts them in a buffer. The difference between the start and end time (also not shown) is reported outside the ISR. Only one "inportb(testbase)" line was present during the first timing run, while the second run had two. The difference between runs was 1.923 seconds, giving 1.923 usec for a single read from the UART line status register. >void interrupt com_int(void) { > > start = clock(); > testbase = portbase + LSR; > for (x = 1000000; x > 0; x--) { > > inportb(testbase); > inportb(testbase); /* ONLY PRESENT DURING SECOND RUN */ > > if ((inportb(portbase + IIR) & RX_MASK) == RX_ID) { > while (inportb(portbase + LSR) & RCVRDY) { > ccbuf[endbuf++] = inportb(portbase + RXR); > endbuf &= (SBUFSIZ - 1); > if (endbuf == startbuf) { > SError = BUFOVFL; > startbuf++; > startbuf &= (SBUFSIZ - 1); > } > } > } > } > > end = clock(); > > /* Tell PIC End-Of-Interrupt */ > outportb(ICR, EOI); >} From owner-freebsd-hackers Wed Nov 19 18:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25868 for hackers-outgoing; Wed, 19 Nov 1997 18:12:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25863 for ; Wed, 19 Nov 1997 18:12:54 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id CAA15191 for ; Thu, 20 Nov 1997 02:12:21 GMT Date: Thu, 20 Nov 1997 11:12:21 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: FreeBSD Hackers Subject: Re: Mail spam, sigh... In-Reply-To: <199711192028.MAA14215@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Sean Eric Fagan wrote: > Along this vein... I'd like to suggest adding the RBL support to the default > sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > default, drop SMTP connections from the sites on the blacklist. > > I'd also like to add the anti-relay code to the file, but that's a bit > trickier, I'm afraid (too easy to get wrong and screw things up). > Spammers started using our sendmail 8.8.5 to relay "Enter the Zone" crap all over the world. It appears that many spammers are looking for relay hosts in asia. I setup 8.8.8 with the anti-relay stuff to quench this spam. Sigh, it does gives you more work because you have to manage a list of hosts or domains to grant them the right to relay mail. Mike From owner-freebsd-hackers Wed Nov 19 18:25:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26709 for hackers-outgoing; Wed, 19 Nov 1997 18:25:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26700 for ; Wed, 19 Nov 1997 18:25:43 -0800 (PST) (envelope-from mouth@ibm.net) Received: from slip129-37-53-101.ca.us.ibm.net (slip129-37-53-101.ca.us.ibm.net [129.37.53.101]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id CAA246922; Thu, 20 Nov 1997 02:25:32 GMT From: mouth@ibm.net (John Kelly) To: Bruce Evans Cc: hackers@freebsd.org Subject: Re: Status of 650 UART support Date: Thu, 20 Nov 1997 03:26:42 GMT Message-ID: <3474ab40.2923767@smtp-gw01.ny.us.ibm.net> References: <199711150553.QAA31140@godzilla.zeta.org.au> In-Reply-To: <199711150553.QAA31140@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.01/16.397 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA26702 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 15 Nov 1997 16:53:53 +1100, Bruce Evans wrote: >is approximately 8 ports saturated with 32 bytes of input, 32 bytes >of output and a modem status change. This takes about 2*32 + 1*32 + 5 >i/o's per port. Each i/o takes about 1 usec on an 8MHz ISA bus (perhaps >125 nsec more or less). Altogether, it takes about 8*101 = 808. usec. >Altogether, with saturated input and no output it takes at least about >8*37 = 296 usec. Where you say 2*32 + 1*32 +5, I thought you meant two I/O for each input byte and one I/O for each output byte. But later you say 37 (32 + 5) I/O for saturated input, which would mean only one I/O for each input byte, so now I wonder if you meant the opposite -- two I/O for each output byte and one I/O for each input byte. But that doesn't sound right -- don't I need to read bit 0 of the line status register before trying to read a byte from the receiver FIFO, so that I'll know when I've emptied the receiver FIFO? That would give two I/O per input byte. John From owner-freebsd-hackers Wed Nov 19 18:54:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29342 for hackers-outgoing; Wed, 19 Nov 1997 18:54:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA29336 for ; Wed, 19 Nov 1997 18:54:38 -0800 (PST) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA14547; Thu, 20 Nov 97 03:56:35 +0100 Date: Thu, 20 Nov 97 03:56:35 +0100 Message-Id: <9711200256.AA14547@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: asami@cs.berkeley.edu Cc: jamil@trojanhorse.ml.org, hackers@freebsd.org In-Reply-To: <199711200055.QAA01272@silvia.HIP.Berkeley.EDU> (asami@cs.berkeley.edu) Subject: Re: Artificial Lifeform? X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Satoshi Asami writes: > * Are there any artificial life programs for freebsd? > jkh is one. But it dies very rapidly: $ /usr/local/bin/jkh Segmentation fault (core dumped) :-> Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr From owner-freebsd-hackers Wed Nov 19 18:58:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29691 for hackers-outgoing; Wed, 19 Nov 1997 18:58:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA29680 for ; Wed, 19 Nov 1997 18:58:50 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYMhg-0007OG-00; Wed, 19 Nov 1997 18:50:52 -0800 Date: Wed, 19 Nov 1997 18:50:16 -0800 (PST) From: Tom To: Terry Lambert cc: Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@freebsd.org Subject: Re: Partitioning suggestions? In-Reply-To: <199711192300.QAA06547@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Terry Lambert wrote: > > I can't accept that idea of a "graceful" failure. I don't know if there > > are any "catastrophic" (ie. eaten e-mail, destroyed password > > files, etc) failures in FreeBSD, due to full filesystems. But the > > so-called graceful failures are the real essence of this thread. How do > > you avoid them in the first place? > > By not engaging in sysadm pilot error that results in filled drives. In what universe is this? Point me to a mail server that you use, and I will fill one or more filesystems for you. Then when done, I will blame it on your pilot error. > > > That doesn't guarantee it. What if your FS fills up with PID files? > > > > What would be creating pid files in /var/log? > > In /var. The original poster, said to make /var/log a separate filesystem. This goes along with my point, because it would eliminate the problem. Tom From owner-freebsd-hackers Wed Nov 19 19:09:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA00652 for hackers-outgoing; Wed, 19 Nov 1997 19:09:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA00645 for ; Wed, 19 Nov 1997 19:09:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id TAA03632 for ; Wed, 19 Nov 1997 19:08:54 -0800 (PST) Message-Id: <199711200308.TAA03632@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: PCI Video capture for $77 8) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Nov 1997 19:08:53 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Fry's in California has a Bt848 based board which sells for $77!! So for $77 you can turn your PC into a TV, for more info on the Bt848 project see our bt848 web page: http://www.freebsd.org/~ahasty/Bt848.html Enjoy, Amancio From owner-freebsd-hackers Wed Nov 19 19:54:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA03493 for hackers-outgoing; Wed, 19 Nov 1997 19:54:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-12.ix.netcom.com [207.93.143.140]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03486 for ; Wed, 19 Nov 1997 19:54:41 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id TAA03168; Wed, 19 Nov 1997 19:54:19 -0800 (PST) Date: Wed, 19 Nov 1997 19:54:19 -0800 (PST) Message-Id: <199711200354.TAA03168@silvia.HIP.Berkeley.EDU> To: jmz@cabri.obs-besancon.fr CC: jamil@trojanhorse.ml.org, hackers@FreeBSD.ORG In-reply-to: <9711200256.AA14547@cabri.obs-besancon.fr> (message from Jean-Marc Zucconi on Thu, 20 Nov 97 03:56:35 +0100) Subject: Re: Artificial Lifeform? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * But it dies very rapidly: * $ /usr/local/bin/jkh * Segmentation fault (core dumped) Really? IIRC he used to be a perl script, maybe he didn't survive the upgrade to perl5? :) Satoshi From owner-freebsd-hackers Wed Nov 19 20:01:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04008 for hackers-outgoing; Wed, 19 Nov 1997 20:01:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03996 for ; Wed, 19 Nov 1997 20:01:31 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id BAA14262; Thu, 20 Nov 1997 01:43:27 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711200143.BAA14262@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: sef@kithrup.com (Sean Eric Fagan), hackers@freebsd.org Subject: Re: Mail spam, sigh... In-reply-to: Your message of "Wed, 19 Nov 1997 23:22:22 GMT." <199711192322.QAA09195@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Nov 1997 01:43:26 +0000 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Along this vein... I'd like to suggest adding the RBL support to the default > > sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > > default, drop SMTP connections from the sites on the blacklist. > > > > I'd also like to add the anti-relay code to the file, but that's a bit > > trickier, I'm afraid (too easy to get wrong and screw things up). > > I have yet to see a clean way to make this work with a transiently > connected system. I'd guess that the majority of users are on > transiently connected systems (note: I did not say the majority of > FreeBSD boxes). I'm on a `transiently connected' system and now happily use the stuff in /etc/mail (introduced for 2.2.5). My objective is to figure out the HACK()s (Mike Burgett has already shown me some examples) and put 'em in the FAQ - unless someone gets there in front of me (I've got lots of other stuff to keep be busy with at the moment too). > We need to start thinking about a set of "out of the box" configurations: [.....] I'm not sure I understand the rationale here. What's the difference between a ``permanent'' and ``sometimes'' link (unless you're subtly referring to the fact that most if not all of these rules are done in the canonification stage, and many ``sometimes'' sites have FEATURE(nocanonify)) ? If we get something working for the ``sometimes'' sites, why wouldn't it also work with the ``permanent'' sites ? > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Wed Nov 19 20:14:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04784 for hackers-outgoing; Wed, 19 Nov 1997 20:14:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04771 for ; Wed, 19 Nov 1997 20:14:22 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id UAA00361; Wed, 19 Nov 1997 20:13:21 -0800 (PST) Message-ID: <19971119201321.31590@micron.mini.net> Date: Wed, 19 Nov 1997 20:13:21 -0800 From: Jonathan Mini To: Jean-Marc Zucconi Cc: asami@cs.berkeley.edu, jamil@trojanhorse.ml.org, hackers@FreeBSD.ORG Subject: Re: Artificial Lifeform? Reply-To: Jonathan Mini References: <199711200055.QAA01272@silvia.HIP.Berkeley.EDU> <9711200256.AA14547@cabri.obs-besancon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <9711200256.AA14547@cabri.obs-besancon.fr>; from Jean-Marc Zucconi on Thu, Nov 20, 1997 at 03:56:35AM +0100 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jean-Marc Zucconi stands accused of saying: > >>>>> Satoshi Asami writes: > > > * Are there any artificial life programs for freebsd? > > jkh is one. > > But it dies very rapidly: > $ /usr/local/bin/jkh > Segmentation fault (core dumped) Yeah, but you know what's more fun? $ gdb /usr/local/bin/jhk GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... (gdb) print jhk_create_rant("Terry Lambert") :) :) It's more fun than fortune. > > :-> > > Jean-Marc > _____________________________________________________________________________ > Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex > PGP Key: finger jmz@cabri.obs-besancon.fr -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Wed Nov 19 21:26:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA08930 for hackers-outgoing; Wed, 19 Nov 1997 21:26:02 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from atohasi.mickey.ai.kyutech.ac.jp (atohasi.mickey.ai.kyutech.ac.jp [131.206.21.80]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA08907 for ; Wed, 19 Nov 1997 21:25:47 -0800 (PST) (envelope-from ohashi@mickey.ai.kyutech.ac.jp) Received: (from ohashi@localhost) by atohasi.mickey.ai.kyutech.ac.jp (8.8.7/3.4Wbeta6) id OAA07410; Thu, 20 Nov 1997 14:23:34 +0900 (JST) Date: Thu, 20 Nov 1997 14:23:34 +0900 (JST) Message-Id: <199711200523.OAA07410@atohasi.mickey.ai.kyutech.ac.jp> To: semen@iclub.nsu.ru Cc: hackers@freebsd.org Subject: Re: SMC9432TX Fast Ethernet driver for FreeBSD In-Reply-To: Your message of "Wed, 19 Nov 1997 17:58:20 +0600 (NS)". From: ohashi@mickey.ai.kyutech.ac.jp (Takeshi Ohashi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk semen>>Hello, HACKERS... semen>> semen>>Alpha version of driver lies at: semen>>(Possibly it works not only on my machine) semen>> semen>>http://iclub.nsu.ru/~semen/smc9432tx.html semen>> semen>>Bye... God job. The driver is working fine on our FreeBSD-2.2.5 box. Thanks. -- Takeshi OHASHI ohashi@mickey.ai.kyutech.ac.jp From owner-freebsd-hackers Wed Nov 19 22:11:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA12246 for hackers-outgoing; Wed, 19 Nov 1997 22:11:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA12238 for ; Wed, 19 Nov 1997 22:11:36 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id HAA25272 for hackers@freebsd.org; Thu, 20 Nov 1997 07:00:16 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id GAA02288; Thu, 20 Nov 1997 06:30:14 +0100 (CET) (envelope-from andreas) Message-ID: <19971120063014.22538@klemm.gtn.com> Date: Thu, 20 Nov 1997 06:30:14 +0100 From: Andreas Klemm To: hackers@freebsd.org Subject: Are we missing NFS with file locking ? Heard that NetBSD 1.3 should have Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! tron@lyssa.owl.de (Matthias Scheler) claimed on de.comp.os.unix that NetBSD 1.3 came with true NFS file locking support. Wasn't it something we are still missing, or am I wrong ? Should it be true, perhaps someone who has access to NetBSD sources could take a closer look into this ?! Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' From owner-freebsd-hackers Wed Nov 19 22:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA13993 for hackers-outgoing; Wed, 19 Nov 1997 22:42:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA13983 for ; Wed, 19 Nov 1997 22:42:49 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA01668; Thu, 20 Nov 1997 07:42:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id MAA27004; Wed, 19 Nov 1997 12:36:21 +0100 (MET) Message-ID: <19971119123620.RJ44811@uriah.heep.sax.de> Date: Wed, 19 Nov 1997 12:36:20 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: archer@lucky.net (Alexander Litvin) Subject: Re: 2.2-stable, panic References: <19971113004848.26628@grape.carrier.kiev.ua> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19971113004848.26628@grape.carrier.kiev.ua>; from Alexander Litvin on Nov 13, 1997 00:48:48 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Alexander Litvin wrote: > It's not the first time I'm asking here for some help. > Though before I haven't received substantial assistance, > where else can I ask for it? That's most likely not for being ignored, but since nobody has an apparent and quick answer for you. (I don't have either, sorry.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Nov 19 22:43:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14018 for hackers-outgoing; Wed, 19 Nov 1997 22:43:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA14009 for ; Wed, 19 Nov 1997 22:42:56 -0800 (PST) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.8/8.6.9) with SMTP id XAA00738; Wed, 19 Nov 1997 23:40:40 -0800 Date: Wed, 19 Nov 1997 23:40:39 -0800 (PST) From: Alex Belits To: Satoshi Asami cc: jamil@trojanhorse.ml.org, hackers@FreeBSD.ORG Subject: Re: Artificial Lifeform? In-Reply-To: <199711200055.QAA01272@silvia.HIP.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Satoshi Asami wrote: > * Are there any artificial life programs for freebsd? > > jkh is one. > > Satoshi :> ...after long and painful upgrade sysadmin brings his box up, installs jkh port on it and shows just how much he likes new installer... -- Alex From owner-freebsd-hackers Wed Nov 19 22:44:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14174 for hackers-outgoing; Wed, 19 Nov 1997 22:44:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA14169 for ; Wed, 19 Nov 1997 22:44:06 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA01818; Thu, 20 Nov 1997 07:44:05 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id TAA27758; Wed, 19 Nov 1997 19:31:41 +0100 (MET) Message-ID: <19971119193141.NY02422@uriah.heep.sax.de> Date: Wed, 19 Nov 1997 19:31:41 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: luomat+freebsd+hackers@luomat.peak.org (Timothy J Luoma) Subject: Re: NBQ: Why partitioning? (was: Re: Partitioning suggestions?) References: <199711180019.TAA01983@dyson.iquest.net> <199711180202.VAA04479@luomat.peak.org> <19971117192532.37475@micron.mini.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19971117192532.37475@micron.mini.net>; from Jonathan Mini on Nov 17, 1997 19:25:32 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jonathan Mini wrote: > There are your reasons. :) I'm sure there are probably more. Well, having installed a new central server in our company last weekend, i had to find that i ran out of partition slots on the first disk to satisfy all my wishes. ;-) I've solved the problem by making /tmp not a separate disk filesystem, but MFS instead. (I'm not very fond of MFS, for a number of reasons.) I wished we would support 16 partition slots at least as an alternative to the backwards-compatible 8 slot model. The main reason for having multiple filesystems is that the unix kernel decides many things on a per-filesystem basis: mount flags describing the basic properties of the filesystem (read/only vs. read/write, async metadata updates, allowed to execute something at all, allowed to have /dev nodes, allowed to execute setuid binaries, etc. pp.), and NFS exportation come to mind. I understand that this is just a kernel optimization. It's sheer impossible inside the kernel, to find out for a particular vnode whether it's the part of a given tree subhierarchy. However, finding out about which filesystem you're mounted from is very simple. So if something like the mentioned features are to be applied to a particular subtree, binding them to a filesystem seems to be the best compromise given the historical structure of the unix filesystem. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Nov 19 22:47:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14441 for hackers-outgoing; Wed, 19 Nov 1997 22:47:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA14414 for ; Wed, 19 Nov 1997 22:47:31 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA02390; Thu, 20 Nov 1997 07:47:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id MAA27073; Wed, 19 Nov 1997 12:56:16 +0100 (MET) Message-ID: <19971119125616.CS64559@uriah.heep.sax.de> Date: Wed, 19 Nov 1997 12:56:16 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.org Cc: cao@bus.net (Chuck O'Donnell) Subject: Re: /dev/speaker References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tim Vanderhoek on Nov 14, 1997 20:12:45 -0500 Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Tim Vanderhoek wrote: > On Thu, 13 Nov 1997, Jamil J. Weatherbee wrote: > > > printf "\a" > > /dev/console > > with appropriate privs, of course. /dev/console is a poor choice, it could be a serial console, redirected to an xconsole, or dropped entirely. /dev/ttyv0 is a better choice. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Nov 19 22:47:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14482 for hackers-outgoing; Wed, 19 Nov 1997 22:47:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA14474 for ; Wed, 19 Nov 1997 22:47:46 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA02482 for hackers@FreeBSD.org; Thu, 20 Nov 1997 07:47:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id OAA27195; Wed, 19 Nov 1997 14:27:30 +0100 (MET) Message-ID: <19971119142730.OZ52645@uriah.heep.sax.de> Date: Wed, 19 Nov 1997 14:27:30 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.org Subject: Re: Need some input re: named pipes References: <199711141434.JAA01323@dyson.iquest.net> <199711142357.QAA18184@usr06.primenet.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199711142357.QAA18184@usr06.primenet.com>; from Terry Lambert on Nov 14, 1997 23:57:07 +0000 Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > Could anyone give me some feedback on an idea of making our pipe > code (fast) > used for named pipes? I don't think that it is hard > to implement, but > do people usually use the socket ioctl's for > named pipes? Many of those > would go-away when moving to the pipe > code. > Wouldn't this break X? Of course not. X is using sockets, not pipes. j@uriah 208% ls -l /tmp/.X11-unix/ total 0 srwxrwxrwx 1 root wheel 0 Nov 14 00:02 X0= srwxrwxrwx 1 root wheel 0 Nov 14 00:04 X1= These should be in /var/run, of course. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Nov 19 23:14:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA16053 for hackers-outgoing; Wed, 19 Nov 1997 23:14:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA16038 for ; Wed, 19 Nov 1997 23:14:51 -0800 (PST) (envelope-from max@iclub.nsu.ru) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.7/8.8.5) with SMTP id NAA17316 for ; Thu, 20 Nov 1997 13:15:32 +0600 (NS) Date: Thu, 20 Nov 1997 13:15:32 +0600 (NS) From: Max Khon To: freebsd-hackers@freebsd.org Subject: IBM PC 350 P100 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, there! i've got several IBM PC 350 P100 workstations (P100, 82437FX (Triton), S3 Trio 64V+ onboard, 16(32)M, PS/2 mouse, PS/2 kbd, AMD PCNet/PCI based network card) 3.0-CURRENT: everything works fine (raw ftp ~900-950K/s) 2.2.5-STABLE: - cannot shutdown properly (do not sync disks) - KBD_BROKEN_RESET does not help - raw ftp throughput is about 20-30K/s. lnc driver works with AMD PCNet/PCI cards in 16-bit mode. i wrote device driver which works with AMD PCNet/PCI in 32-bit mode - does not help. this is not BOUNCE_BUFFERS problem as someone noticed earlier, because 1) i tried this on workstations with 16M 2) on workstations with 32M i tried both lnc with 'option BOUNCE_BUFFERS' in kernel config and my own driver which does not need BOUNCE_BUFFERS any comments? /max PS with both 2.2.5-STABLE and 3.0-CURRENT sometimes monitor looses sync while booting (IBM G50) From owner-freebsd-hackers Wed Nov 19 23:42:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17954 for hackers-outgoing; Wed, 19 Nov 1997 23:42:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA17943 for ; Wed, 19 Nov 1997 23:42:00 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id SAA28030; Thu, 20 Nov 1997 18:37:00 +1100 Date: Thu, 20 Nov 1997 18:37:00 +1100 From: Bruce Evans Message-Id: <199711200737.SAA28030@godzilla.zeta.org.au> To: bde@zeta.org.au, mouth@ibm.net Subject: Re: Status of 650 UART support Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Altogether, with saturated input and no output it takes at least about >>8*37 =3D 296 usec.=20 > >Where you say 2*32 + 1*32 +5, I thought you meant two I/O for each >input byte and one I/O for each output byte. But later you say 37 (32 Right. >+ 5) I/O for saturated input, which would mean only one I/O for each >input byte, so now I wonder if you meant the opposite -- two I/O for >each output byte and one I/O for each input byte. I mean 2*16 + 5. This assumes a trigger level of 16. There will always be 16 bytes for saturated input and no interrupts except for input. There may be up to 16 more bytes if we can barely keep up. >But that doesn't sound right -- don't I need to read bit 0 of the line >status register before trying to read a byte from the receiver FIFO, >so that I'll know when I've emptied the receiver FIFO? That would >give two I/O per input byte. I think you can actually ready bit 7 to see if there is a full fifo (with no parity/framing/overrun errors) and, if it is set, read the entire fifo before reading the LSR again. This gives close to one I/O per input byte. It is a bit tricky to handle error cases and quitting properly - we don't want to fall back to two I/O's per input byte. Another character may have arrived, and if the fifo is larger than we know about, there may be many more characters to process. ISTR that there is more setup overhead but can't see it now. Bruce From owner-freebsd-hackers Thu Nov 20 00:21:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA20282 for hackers-outgoing; Thu, 20 Nov 1997 00:21:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA20269 for ; Thu, 20 Nov 1997 00:21:26 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA06210 for hackers@freebsd.org; Thu, 20 Nov 1997 09:21:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id JAA01342; Thu, 20 Nov 1997 09:06:11 +0100 (MET) Message-ID: <19971120090611.FW37911@uriah.heep.sax.de> Date: Thu, 20 Nov 1997 09:06:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: vnode.h and IO_NDELAY (help!!) References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jamil J. Weatherbee on Nov 18, 1997 19:28:41 -0800 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jamil J. Weatherbee wrote: > I can't find a single code fragment in any device driver that checks > ioflags in the read routine to see if IO_NDELAY is set. That's work-in-progress, but i know the non-delay stuff does what it's supposed to do: static int rtcread(dev_t dev, struct uio *uio, int flag) { int rv = 0; size_t amnt; if (flag & IO_NDELAY) { /* O_NONBLOCK requests to pull previous data if available */ if ((rtc_softc.sc_flags & RTC_UPDATED) == 0) rv = EWOULDBLOCK; } else { rv = tsleep((caddr_t)&rtc_softc, RTCPRI | PCATCH, "rtc", 0); if (rv == ERESTART) rv = EINTR; } if (rv == 0) { amnt = MIN(uio->uio_resid, RTC_DATALEN); rv = uiomove((caddr_t)&rtc_softc.sc_data, amnt, uio); } return rv; } Also, don't forget that you need to allow the FIONBIO ioctl command. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Nov 20 00:30:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA20885 for hackers-outgoing; Thu, 20 Nov 1997 00:30:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA20871 for ; Thu, 20 Nov 1997 00:30:29 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA24216; Thu, 20 Nov 1997 00:30:38 -0800 (PST) To: asami@cs.berkeley.edu (Satoshi Asami) cc: jamil@trojanhorse.ml.org, hackers@FreeBSD.ORG Subject: Re: Artificial Lifeform? In-reply-to: Your message of "Wed, 19 Nov 1997 16:55:55 PST." <199711200055.QAA01272@silvia.HIP.Berkeley.EDU> Date: Thu, 20 Nov 1997 00:30:38 -0800 Message-ID: <24212.880014638@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * Are there any artificial life programs for freebsd? > > jkh is one. > > Satoshi :> Hey, you know, I really resent these baseless insinuations that I^\Quit (core dumped) From owner-freebsd-hackers Thu Nov 20 00:36:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA21181 for hackers-outgoing; Thu, 20 Nov 1997 00:36:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA21175 for ; Thu, 20 Nov 1997 00:36:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA24358; Thu, 20 Nov 1997 00:35:14 -0800 (PST) To: Ruslan Shevchenko cc: hackers@FreeBSD.ORG Subject: Re: rebuilding of whatis database does not care about setting in /etc/manpath.conf In-reply-to: Your message of "Thu, 20 Nov 1997 01:26:18 GMT." <347391BA.2E7168CC@Shevchenko.kiev.ua> Date: Thu, 20 Nov 1997 00:35:13 -0800 Message-ID: <24355.880014913@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Or it is nessesory to interact with commiters via send-pr ? Yes, please. Mail to -hackers simply gets assumed that "someone else" will handle it. Jordan From owner-freebsd-hackers Thu Nov 20 00:53:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22072 for hackers-outgoing; Thu, 20 Nov 1997 00:53:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA22066 for ; Thu, 20 Nov 1997 00:53:04 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id TAA31061; Thu, 20 Nov 1997 19:46:56 +1100 Date: Thu, 20 Nov 1997 19:46:56 +1100 From: Bruce Evans Message-Id: <199711200846.TAA31061@godzilla.zeta.org.au> To: bde@zeta.org.au, mouth@ibm.net Subject: Re: Status of 650 UART support Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Each i/o takes about 1 usec on an 8MHz ISA bus (perhaps >>125 nsec more or less) >I tried some timing tests and measured almost 2 usec for one 8MHz ISA >bus I/O on a 486 DX4-100. The difference is partly due to the difference between real/VM86 and protected mode. Here are the best-case cycle times for inb, at least on plain 486's: pm (CPL <= IOPL): 8 real: 14 VM86: 27 pm (CPL > IOPL): 28 27 - 8 only accounts for 0.19 usec per i/o at 100 MHz. >I used the following real-mode Turbo C DOS ISR with a dummy loop to >repeat reading the UART line status register a million times. The I used to use throwaway test programs under DOS to determine i/o timing. Now I use throwaway LKMs under FreeBSD. The easiest method is to take one of the examples in /usr/share/exemples/lkm and put `... microtime(&start); test_code(); microtime(&finish); printf(...);' in the startup code. Then loading the module runs the test. Bruce From owner-freebsd-hackers Thu Nov 20 01:33:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA23890 for hackers-outgoing; Thu, 20 Nov 1997 01:33:07 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from chouette.inria.fr (chouette.inria.fr [138.96.24.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA23851 for ; Thu, 20 Nov 1997 01:32:21 -0800 (PST) (envelope-from Emmanuel.Duros@sophia.inria.fr) Received: by chouette.inria.fr (8.8.6/8.8.5) id KAA07538; Thu, 20 Nov 1997 10:32:10 +0100 (MET) Date: Thu, 20 Nov 1997 10:32:10 +0100 (MET) Message-Id: <199711200932.KAA07538@chouette.inria.fr> From: Emmanuel Duros To: freebsd-hackers@freebsd.org Subject: My fbsd router looses packets ! Reply-to: Emmanuel.Duros@sophia.inria.fr Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My fbsd (2.2.2 release) router has two communication interfaces and when it routes packets between its interfaces, it looses lots of packets ! Here is the network configuration: --- --------- --- |A| | B | |C| --- --------- --- | (b1) | | (b2) | -------------------------- -------------------------- b1 is an Ethernet interface, b2 is a dvb interface, it is a satellite communication card (a send-only interface). I wrote the device driver for the latter. I have used a video conferencing application to verify the communication between the stations: 1) A generates a video stream to B up to several Mbps: NO LOSSES 2) B generates a video stream to C up to several Mbps: NO LOSSES 3) A generates a video stream to C at 100-200 kbps and I get 5 to 30 % loss rate 1) ensures that the connectivity between A and B is fine 2) ensures that the connectivity between B and C is fine 3) shows that there is a routing pb !!! Beside this, it is not the first time I have used this network configuration, it used to work very well on another a fbsd router running a one year old snapshot. I have got absolutely no idea where my pb comes from, I have checked IRQs, probable overlapping ports and everything looks fine to me. I do not think it comes from my driver because of 2) and because it used to work very well before I changed the PC and the fbsd OS version. I join the output of the dmesg in case this can help... Thanks a lot for any help! Emmanuel PS: For information the send-only interface (dvtx0) has an ISA bus and performs DMA transfers ------- Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #5: Wed Nov 19 21:10:31 GMT 1997 eduros@pacman.inria.fr:/usr/src/sys/compile/PACMAN_TX CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 62619648 (61152K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 1 int a irq 10 on pci0:17 de0 rev 17 int a irq 15 on pci0:18 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:6b:ea:df chip3 rev 1 on pci0:20:0 pci0:20:1: Intel Corporation, device=0x1960, class=memory (misc) int a irq 9 [no driver assigned] Probing for devices on PCI bus 1: ahc0 rev 0 int a irq 10 on pci1:1 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "CONNER CFP2107W 2.14GB 1524" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2048MB (4194304 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, ovlap, dma, iordis wcd0: 2066Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked dvtx0: 0.9b1 version - Probing... dvtx0 at 0x310 irq 11 drq 5 on isa npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers de0: enabling 10baseT port From owner-freebsd-hackers Thu Nov 20 01:44:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA24511 for hackers-outgoing; Thu, 20 Nov 1997 01:44:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from thorin.hway.ru (root@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA24503 for ; Thu, 20 Nov 1997 01:44:39 -0800 (PST) (envelope-from flash@hway.ru) Received: from flash.intech.hway.ru (flash.intech.hway.ru [192.168.1.16]) by thorin.hway.ru (8.8.6/8.8.6) with ESMTP id MAA05405; Thu, 20 Nov 1997 12:36:17 +0300 (MSK) Received: from localhost (flash@localhost) by flash.intech.hway.ru (8.8.7/8.8.7) with SMTP id MAA00652; Thu, 20 Nov 1997 12:37:46 +0300 (MSK) Date: Thu, 20 Nov 1997 12:37:46 +0300 (MSK) From: "Alexander V. Tischenko" To: Max Khon cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IBM PC 350 P100 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, Max Khon wrote: > Hi, there! > > i've got several IBM PC 350 P100 workstations (P100, 82437FX (Triton), S3 > Trio 64V+ onboard, 16(32)M, PS/2 mouse, PS/2 kbd, AMD PCNet/PCI based > network card) > > 3.0-CURRENT: > everything works fine (raw ftp ~900-950K/s) > > 2.2.5-STABLE: > - cannot shutdown properly (do not sync disks) - KBD_BROKEN_RESET does > not help > - raw ftp throughput is about 20-30K/s. lnc driver works with AMD > PCNet/PCI cards in 16-bit mode. i wrote device driver which works with AMD > PCNet/PCI in 32-bit mode - does not help. this is not BOUNCE_BUFFERS > problem as someone noticed earlier, because > 1) i tried this on workstations with 16M > 2) on workstations with 32M i tried both lnc with 'option BOUNCE_BUFFERS' > in kernel config and my own driver which does not need BOUNCE_BUFFERS > > any comments? > Concerning lnc: While in the age of 2.1-... i've got the PC-Net/PCI driver working (breed from linux of my own). The problem of working/notworking was purely in alignment (AMD's are a bit crazy on that, not bounce buffers. If you want to have a look, drop me a note, i'll give it to you. Also William D. Ward is investigating the problems with AMD drivers right now. Manuals on AMD chips you may get on AMD itself or http://www.hway.ru/~flash/amd/ > /max > > PS with both 2.2.5-STABLE and 3.0-CURRENT sometimes monitor looses sync > while booting (IBM G50) > > From owner-freebsd-hackers Thu Nov 20 01:59:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25272 for hackers-outgoing; Thu, 20 Nov 1997 01:59:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from intranet.blueberry.co.uk (intranet.blueberry.co.uk [195.129.9.107]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25260; Thu, 20 Nov 1997 01:59:00 -0800 (PST) (envelope-from keith@intranet.blueberry.co.uk) Received: (from keith@localhost) by intranet.blueberry.co.uk (8.8.7/8.8.7) id KAA02066; Thu, 20 Nov 1997 10:00:45 GMT (envelope-from keith) Message-ID: <19971120100045.64917@blueberry.co.uk> Date: Thu, 20 Nov 1997 10:00:45 +0000 From: Keith Jones To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: mountmsdosfs(): Warning: ...... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organization: Blueberry New Media Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I mount MSDOS partitions on to my FreeBSD system (2.2.5R) the following warning appears: mountmsdosfs(): Warning: root directory is not a multiple of the cluster- size in length This is expected; my DOS version is >3.3 and the man page is pretty clear about that. 3.0C apparently has the same problem (according to the manpage on www.freebsd.org). Is support for DOS >3.3 planned/is someone working on this/is a patch available? Keith -- v Keith Jones Systems Manager, Blueberry New Media Ltd. v | Postal Mail: 2/10 Harbour Yard, Chelsea Harbour, LONDON, UK. SW10 0XD | | Telephone: +44 (0)171 351 3313 Fax: +44 (0)171 351 2476 | ^ Email: Keith.Jones@blueberry.co.uk WWW: http://www.blueberry.co.uk/ ^ From owner-freebsd-hackers Thu Nov 20 02:00:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA25556 for hackers-outgoing; Thu, 20 Nov 1997 02:00:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA25545 for ; Thu, 20 Nov 1997 02:00:50 -0800 (PST) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id CAA26738; Thu, 20 Nov 1997 02:04:18 -0800 (PST) Date: Thu, 20 Nov 1997 02:04:18 -0800 (PST) From: Dmitry Kohmanyuk Message-Id: <199711201004.CAA26738@dog.farm.org> To: abelits@phobos.illtel.denver.co.us (Alex Belits) Cc: freebsd-hackers@freebsd.org Subject: Re: Artificial Lifeform? Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > On Wed, 19 Nov 1997, Satoshi Asami wrote: > > * Are there any artificial life programs for freebsd? > > > > jkh is one. > > > > Satoshi :> > ...after long and painful upgrade sysadmin brings his box up, installs jkh > port on it and shows just how much he likes new installer... only to find in next 2 hours that install of jkh screwed up his tcl/tk libraries completely so none of other ports work ;-)) -- It's awfully hard work doing nothing. However, I don't mind hard work when there is no definite object of any kind. -- Oscar Wilde, The Importance of Being Earnest From owner-freebsd-hackers Thu Nov 20 03:01:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA28736 for hackers-outgoing; Thu, 20 Nov 1997 03:01:58 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA28731 for ; Thu, 20 Nov 1997 03:01:51 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id IAA09842 for ; Thu, 20 Nov 1997 08:01:12 -0300 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256555.003C88A3 ; Thu, 20 Nov 1997 08:01:11 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: cmott@srv.net Message-ID: <03256555.003C32C5.01@papagaio.voga.com.br> Date: Thu, 20 Nov 1997 08:01:05 -0300 Subject: dial on demand with dynamic IP Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On successive dialups where different IPs are assigned, it is not possible > to maintain a continuous tcp connection from any computer on your network > - -- either the ppp host or any box which is being NAT'ed by ppp -alias. Well, that's not entirely correct. The PPP protocol let you negotiate an address. With ijPPP, for example, you can specify your address as x.y.z.w/0.0.0.0, and it will try to get you the x.y.z.w address, failing that accept anything. Now, you can do two things with that. You can change your PPP program so it will always try to get the last address it was using, or you can set up a fixed IP address for it to negotiate. Choose this address well and you will likely get it most of the time. From owner-freebsd-hackers Thu Nov 20 03:34:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA29867 for hackers-outgoing; Thu, 20 Nov 1997 03:34:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA29836 for ; Thu, 20 Nov 1997 03:34:07 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id IAA13742 for ; Thu, 20 Nov 1997 08:33:32 -0300 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256555.003F7B44 ; Thu, 20 Nov 1997 08:33:23 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: hackers@FreeBSD.ORG Message-ID: <03256555.003F5208.00@papagaio.voga.com.br> Date: Thu, 20 Nov 1997 08:33:18 -0300 Subject: Re: Virtual Intel Machines? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Of course, given that Intel chips work the way they do, it sounds > like it'd be pretty much impossible to do what I was hoping for. > Sigh. It was such a cool idea, too. Err, maybe. That depends on _what_ you want. See the FLUX/FLUKE project, for instance. They run virtual machines, but not like the old vm machines. And work over Intel. From owner-freebsd-hackers Thu Nov 20 03:35:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA29933 for hackers-outgoing; Thu, 20 Nov 1997 03:35:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA29924 for ; Thu, 20 Nov 1997 03:35:12 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id LAA18189; Thu, 20 Nov 1997 11:35:10 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id MAA29627; Thu, 20 Nov 1997 12:35:08 +0100 (MET) Date: Thu, 20 Nov 1997 12:35:08 +0100 (MET) Message-Id: <199711201135.MAA29627@bitbox.follo.net> From: Eivind Eklund To: "Gregory D Moncreaff" CC: hackers@FreeBSD.ORG In-reply-to: "Gregory D Moncreaff"'s message of Wed, 19 Nov 1997 19:48:48 -0500 Subject: Re: 2.2.5, cvs, recommended development organization? References: <01bcf54e$10138460$454206d1@moncrg> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Please disable vcards when sending to the mailing-lists - thanks! > Just got the 2.2.5 4 disk set with the cvs disk, > since xemacs won't let me do anyhing with source code > because of the cvs tags was wonderring what the recommended > way of laying out the disks, repository, etc are? Press Ctrl-x Ctrl-q and you can edit those files. If you'd read the on-line tutorial and checked the help for the active modes in those buffers, you'd know. This is freebsd-questions material. Eivind. From owner-freebsd-hackers Thu Nov 20 05:50:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05623 for hackers-outgoing; Thu, 20 Nov 1997 05:50:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from per.plex.nl (SPARCserver.plex.nl [193.67.154.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA05582 for ; Thu, 20 Nov 1997 05:50:07 -0800 (PST) (envelope-from jbackus@plex.nl) Received: from jos.mp-c.com (isdn-11h.plex.nl [194.229.212.49]) by per.plex.nl (SMI-8.6/SMI-SVR4) id OAA03748; Thu, 20 Nov 1997 14:43:51 +0100 X-Disclaimer: Plex is a public access Internet provider Received: (qmail 336 invoked by uid 1000); 20 Nov 1997 13:02:26 -0000 Message-ID: <19971120130226.335.qmail@jos.mp-c.com> To: hackers@FreeBSD.ORG cc: djb@koobera.math.uic.edu Subject: Re: Mail spam, sigh... In-reply-to: Your message of "Wed, 19 Nov 1997 18:35:53 EST." <199711192335.SAA24946@postman.opengroup.org> Reply-To: Jos Backus Date: Thu, 20 Nov 1997 14:02:26 +0100 From: Jos Backus Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The %-hack, source-routing and relaying are all disabled _by default_ in a standard qmail installation, by virtue of control/rcpthosts having sane contents and control/percenthack being absent. Groetjes, Jos -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ jbackus@plex.nl _/_/ _/_/_/ #include From owner-freebsd-hackers Thu Nov 20 05:50:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05701 for hackers-outgoing; Thu, 20 Nov 1997 05:50:52 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from per.plex.nl (SPARCserver.plex.nl [193.67.154.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA05696 for ; Thu, 20 Nov 1997 05:50:47 -0800 (PST) (envelope-from jbackus@plex.nl) Received: from jos.mp-c.com (isdn-11h.plex.nl [194.229.212.49]) by per.plex.nl (SMI-8.6/SMI-SVR4) id OAA03752; Thu, 20 Nov 1997 14:43:53 +0100 X-Disclaimer: Plex is a public access Internet provider Received: (qmail 372 invoked by uid 1000); 20 Nov 1997 13:10:21 -0000 Message-ID: <19971120131021.371.qmail@jos.mp-c.com> To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: Mail spam, sigh... In-reply-to: Your message of "Wed, 19 Nov 1997 23:22:22 GMT." <199711192322.QAA09195@usr01.primenet.com> Reply-To: Jos Backus Date: Thu, 20 Nov 1997 14:10:21 +0100 From: Jos Backus Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry, In message <199711192322.QAA09195@usr01.primenet.com> you wrote: >I have yet to see a clean way to make this work with a transiently connected >system. I'd guess that the majority of users are on transiently connected >systems (note: I did not say the majority of FreeBSD boxes). This is what my qmail home setup looks like: jos:/var/qmail/control% cat virtualdomains :alias-ppp jos:/var/qmail/alias% cat .qmail-ppp-default ./ppp/ jos:/var/qmail/alias% ls -ld ppp drwx------ 5 alias qmail 512 Nov 7 14:56 ppp jos:~alias% cat /usr/local/bin/send-mail #!/bin/sh export PATH=/usr/local/bin/serialmail:/var/qmail/bin:/usr/local/bin:/bin DIR=~alias/ppp PREFIX=alias-ppp- HOST=mailhost.plex.nl HELOHOST=`hostname` maildirsmtp $DIR $PREFIX $HOST $HELOHOST jos:/var/qmail/alias% ps axwww|grep smtp 190 con- I+ 0:00.01 tcpserver -R -u 71 -g 70 0 smtp /var/qmail/bin/qmail-smtpd Groetjes, Jos -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ jbackus@plex.nl _/_/ _/_/_/ #include From owner-freebsd-hackers Thu Nov 20 06:43:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA08799 for hackers-outgoing; Thu, 20 Nov 1997 06:43:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: (from jmb@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA08793; Thu, 20 Nov 1997 06:43:09 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199711201443.GAA08793@hub.freebsd.org> Subject: Re: Mail spam, sigh... To: sef@kithrup.com (Sean Eric Fagan) Date: Thu, 20 Nov 1997 06:43:08 -0800 (PST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199711192028.MAA14215@kithrup.com> from "Sean Eric Fagan" at Nov 19, 97 12:28:03 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sean Eric Fagan wrote: > > Along this vein... I'd like to suggest adding the RBL support to the default > sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > default, drop SMTP connections from the sites on the blacklist. > > I'd also like to add the anti-relay code to the file, but that's a bit > trickier, I'm afraid (too easy to get wrong and screw things up). > see /etc/mail/{README,sendmail.cf.additions,Makefile}. (both 2.2.5-RELEASE and -current) i will commit RBL support in the near future. we are using it on hub.freebsd.org, in addition to the check performed by /etc/mail/sendmail.cf.additions. RBL has yet to block any spam, the other checks seem to get all first. jmb From owner-freebsd-hackers Thu Nov 20 06:51:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA09194 for hackers-outgoing; Thu, 20 Nov 1997 06:51:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: (from jmb@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA09181; Thu, 20 Nov 1997 06:51:02 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199711201451.GAA09181@hub.freebsd.org> Subject: Re: Mail spam, sigh... To: handy@sag.space.lockheed.com (Brian N. Handy) Date: Thu, 20 Nov 1997 06:51:02 -0800 (PST) Cc: sef@kithrup.com, hackers@FreeBSD.ORG In-Reply-To: from "Brian N. Handy" at Nov 19, 97 01:41:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian N. Handy wrote: > > >Along this vein... I'd like to suggest adding the RBL support to the default > >sendmail file (freebsd.mc). This way, all FreeBSD systems would, by > >default, drop SMTP connections from the sites on the blacklist. > > > >I'd also like to add the anti-relay code to the file, but that's a bit > >trickier, I'm afraid (too easy to get wrong and screw things up). > > I'd also like an easy-drop-in-way to drop email from sites that don't show > up in the nameserver. (Maybe this is easy, I haven't done my research.) get 2.2.5-RELEASE or -current. cd /etc/mail make populate /etc/mail/denyip.local and /etc/mail/spamsites.local according to taste. use /etc/mail/ips.txt and /etc/mail/domains.txt as examples. add /etc/mail/sendmail.cf.additions to your .mc or .cf file kill -HUP `head -1 /var/run/sendmail.pid` cd /etc/mail; make install its all in the /etc/mail/README jmb From owner-freebsd-hackers Thu Nov 20 07:10:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA10243 for hackers-outgoing; Thu, 20 Nov 1997 07:10:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from heathers2.stdio.com (root@heathers2.stdio.com [204.152.114.165]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA10238 for ; Thu, 20 Nov 1997 07:10:19 -0800 (PST) (envelope-from lile@stdio.com) Received: from frog (socks6d.raleigh.ibm.com [204.146.167.238]) by heathers2.stdio.com (8.6.12/8.6.13) with SMTP id KAA13136 for ; Thu, 20 Nov 1997 10:08:15 -0500 Message-ID: <347452D3.41C6@stdio.com> Date: Thu, 20 Nov 1997 10:10:11 -0500 From: Larry Lile X-Mailer: Mozilla 3.01 (X11; I; AIX 1) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Problems mounting a cd-rom drive on 2.2_RELENG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I ran accros a very strange problem last night and I was wondering if someone could shed some light on this. I had a drive bay smoke a power supply and had to move the data from that drive to another, when I had the system rebuilt I became unable to mount a cdrom. When I try to mount the cdrom this is what happens: anarchy: # mount /cdrom cd9660: /dev/cd0a: Invalid argument here is the fstab entry: anarchy: # grep cd9660 /etc/fstab /dev/cd0a /cdrom cd9660 ro,noauto 0 0 and the boot messages for the cdrom drive are Nov 20 03:13:05 anarchy /kernel: (ncr0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 Nov 20 03:13:05 anarchy /kernel: cd0(ncr0:6:0): CD-ROM Nov 20 03:13:05 anarchy /kernel: cd0(ncr0:6:0): asynchronous. Nov 20 03:13:05 anarchy /kernel: can't get the size [ with FreeBSD 2.1.5 live filesystem cd in cd-drive yes, I opened it up and checked just to make sure i'm not losing my tiny little mind :) ] What is truly bizzare is that I do have a cd in the drive and if I boot kernel.GENERIC it reports the correct size of the cd and will allow me to mount the filesystems. Nov 20 03:11:13 anarchy /kernel.GENERIC: (ncr0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 Nov 20 03:11:13 anarchy /kernel.GENERIC: cd0(ncr0:6:0): CD-ROM Nov 20 03:11:13 anarchy /kernel.GENERIC: cd0(ncr0:6:0): asynchronous. Nov 20 03:11:14 anarchy /kernel.GENERIC: cd present [313642 x 2048 byte records] [ Same 2.1.5 cd in the drive ] I thought it might be bit-rot in the kernel so I rebuilt it from scratch, no dice. Then I thought maybe it was SCSI_DELAY so I made it 15, just like GENERIC, still no luck. I saw this problem on my other system and posted a question but got no really good answer and still cannot mount the cd on that system, it is 2.2.2 release. I'm stumped :( Currently I have cvsup'd the latest 2.2_RELENG sources and am running a make world, then I will rebuild my kernel and hope for the best. In the mean time, any ideas? Any help would be greatly appreciated. Larry Lile lile@stdio.com From owner-freebsd-hackers Thu Nov 20 07:10:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA10280 for hackers-outgoing; Thu, 20 Nov 1997 07:10:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA10266; Thu, 20 Nov 1997 07:10:33 -0800 (PST) (envelope-from ks@itp.ac.ru) Received: from speecart.chg.ru (speecart.chg.ru [193.233.46.2]) by itp.ac.ru (8.8.3/8.8.3) with SMTP id SAA25605; Thu, 20 Nov 1997 18:32:15 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 20 Nov 1996 17:54:02 +0300 (MSK) Organization: Landau Institute for Theoretical Physics From: "Sergey S. Kosyakov" To: freebsd-ports@freebsd.org, freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org Subject: Is gmake so buggy? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all! I'm trying to compile one packet (namely the last version of postgresql). The compilation needs gmake. The files tree have modification time = now (GMT + 3 + light saving time) and it seems to be that gmake do not undestand localtime - it tells that files have modification time in future. (May be I should establish some environmental variable for gmake?) I use FreeBSD-3.0-SNAP, computer's CMOS clock eq. localtime, timezone MSK PS. Please reply to: ks@itp.ac.ru (i'm subscribed freebsd-hardware only) --- ---------------------------------- Sergey Kosyakov Laboratory of Distributed Computing Department of High-Performance Computing and Applied Network Research Landau Institute for Theoretical Physics E-Mail: Sergey S. Kosyakov Date: 20-Nov-96 Time: 17:54:02 ---------------------------------- From owner-freebsd-hackers Thu Nov 20 08:30:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15741 for hackers-outgoing; Thu, 20 Nov 1997 08:30:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA15736 for ; Thu, 20 Nov 1997 08:30:29 -0800 (PST) (envelope-from mouth@ibm.net) Received: from slip129-37-53-69.ca.us.ibm.net (slip129-37-53-69.ca.us.ibm.net [129.37.53.69]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id QAA45008; Thu, 20 Nov 1997 16:30:07 GMT From: mouth@ibm.net (John Kelly) To: Bruce Evans Cc: hackers@freebsd.org Subject: Re: Status of 650 UART support Date: Thu, 20 Nov 1997 17:31:16 GMT Message-ID: <34746b1f.1864429@smtp-gw01.ny.us.ibm.net> References: <199711200737.SAA28030@godzilla.zeta.org.au> In-Reply-To: <199711200737.SAA28030@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.01/16.397 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA15737 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997 18:37:00 +1100, Bruce Evans wrote: >I think you can actually ready bit 7 to see if there is a full fifo >(with no parity/framing/overrun errors) and, if it is set, read the >entire fifo before reading the LSR again. This gives close to one I/O >per input byte. It is a bit tricky to handle error cases and quitting >properly - we don't want to fall back to two I/O's per input byte. The Startech databook makes no mention of LSR bit 7 indicating a full FIFO, only a dirty one. Same for all the literature I have on the NS 16550. Apparently you can use the FIFO trigger level to read a block of bytes without checking LSR bit 0 every time -- the Startech data book even suggests it. To handle all cases, especially multiport shared interrupt cards where you don't know which UART generated the receiver interrupt, you must first check the IIR (Startech calls it the ISR -- interrupt Status register) to see if the UART generated a received data interrupt. After emptying the block, you could leave any remaining characters in the FIFO, and simply get them on the next interrupt, avoiding the need of checking LSR bit 0 for bytes beyond the block size. John From owner-freebsd-hackers Thu Nov 20 08:31:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15785 for hackers-outgoing; Thu, 20 Nov 1997 08:31:07 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA15776 for ; Thu, 20 Nov 1997 08:31:00 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id IAA01413; Thu, 20 Nov 1997 08:25:49 -0800 (PST) Date: Thu, 20 Nov 1997 08:25:48 -0800 (PST) From: "Jamil J. Weatherbee" To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: vnode.h and IO_NDELAY (help!!) In-Reply-To: <19971120090611.FW37911@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk global, does not even show there being an rtcread on my system (maybye because it is -stable), there is an rtc.h though. Are you saying I should support the FIONBIO ioctl()? Where do I find the definition of that? Do you have an example? I had some problems with returning an error (EWOULDBLOCK) if I broke out because the I/O was going to block. Doesn't returing an error from your read routine make the users call to read(2) return -1 and errno set to your error? Anyway I thought that a non-blocking data source should just simply return 0 when it was no data, not an error. Because thats how I've seen read(2) used with select, basically select() catch a descriptor that is ready and exhaust that data source until it reads 0. -1 is really an error. Also according to the tsleep manpage, why do you only catch ERESTART and not EINTR, I found that that catching EINTR was important for me because if the user threw a huge buffer at me and the acquisition rate was down at 64 bytes/sec, It might take a while after pressing ctrl-C for the program to exit. So I catch anything non-zero and break out, without returning an error (except for timeout). The thing is that the uio structure might already contain some data, and I don't want to loose that normally. Unless there is something really wrong (timeout). I am afraid if I return an error than the user will not be able to get at whatever partial data was there. For instance they might want to have a signal catcher that catches SIGINT and shuts some things down. Once that exits I assume they would end up at the instruction after the read call and they could still get that final data from the interrupted read right? Anyway can you take a look at this and tell me how it should be? Also about how I implement (and why) the FIONBIO call? Here is my code fragment: -------------------------------------------------------- /* how to read from the board */ static int alog_read (dev_t dev, struct uio *uio, int ioflag) { int unit = UNIT(dev); int chan = CHANNEL(dev); talog_unit *info = alog_unit[unit]; int s, oldtrig, terr, toread, err = 0; s = spltty(); oldtrig = info->chan[chan].fifotrig; /* save official trigger value */ while (uio->uio_resid >= sizeof(u_short)) /* while uio has space */ { if (!info->chan[chan].fifosize) /* if we have an empty fifo */ { if (ioflag & IO_NDELAY) break; /* exit if we are non-blocking */ /* Start filling fifo on first blocking read */ if (info->chan[chan].status == STATUS_INIT) info->chan[chan].status = STATUS_INUSE; /* temporarily adjust the fifo trigger to be optimal size */ info->chan[chan].fifotrig = min (READMAXTRIG, uio->uio_resid / sizeof(u_short)); /* lets sleep until we have some io available or timeout */ terr = tsleep (&(info->chan[chan].fifo), READPRI | PCATCH, READMSG, info->chan[chan].fifotrig*READTIMO); if (terr == EWOULDBLOCK) { printf (DEVFORMAT ": read timeout\n", unit, 'a'+EMUX(chan), IMUX(chan)); err = ETIMEDOUT; break; /* were outta here */ } if (terr) break; /* if caught a signal then just break out */ } /* ok, now if we got here there is something to read from the fifo */ /* calculate how many entries we can read out from the fifostart * pointer */ toread = min (uio->uio_resid / sizeof(u_short), min (info->chan[chan].fifosize, FIFOSIZE - info->chan[chan].fifostart)); /* perform the move, if there is an error then exit */ if (err = uiomove((caddr_t) &(info->chan[chan].fifo[info->chan[chan].fifostart]), toread * sizeof(u_short), uio)) break; info->chan[chan].fifosize -= toread; /* fifo this much smaller */ info->chan[chan].fifostart += toread; /* we got this many more */ if (info->chan[chan].fifostart == FIFOSIZE) info->chan[chan].fifostart = 0; /* wrap around fifostart */ } info->chan[chan].fifotrig = oldtrig; /* restore trigger changes */ splx(s); return err; } From owner-freebsd-hackers Thu Nov 20 09:27:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA19711 for hackers-outgoing; Thu, 20 Nov 1997 09:27:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA19682; Thu, 20 Nov 1997 09:26:58 -0800 (PST) (envelope-from ks@itp.ac.ru) Received: from speecart.chg.ru (speecart.chg.ru [193.233.46.2]) by itp.ac.ru (8.8.3/8.8.3) with SMTP id UAA26176; Thu, 20 Nov 1997 20:48:31 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199711201707.LAA10964@unix.tfs.net> Date: Wed, 20 Nov 1996 20:15:12 +0300 (MSK) Organization: Landau Institute for Theoretical Physics From: "Sergey S. Kosyakov" To: jbryant@tfs.net Subject: Re: Is gmake so buggy? Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 20-Nov-97 Jim Bryant wrote: >In reply: >> Hi all! ....... >> >> PS. Please reply to: ks@itp.ac.ru (i'm subscribed freebsd-hardware only) > >hi, i haven't seen this one, but i will highly recommend that you >set the CMOS clock to UTC, and let FreeBSD handle timezone >conversions. this COULD be where the problem comes from, but don't >quote me on it... > >if you run WinBlowz, you will notice that MickeySoft cannot deal with >a CMOS clock set to UTC, but then the best way to fix that is: >`rm -rf /msdos`, and you CAN quote me on that! > yes, it is my the best dream - rm -rf /msdos /windows /winnt etc. But: there are still no (and will no be [I think]): Lotus Notes for FreeBSD (Why? So[p]laris and A[H]IX have?) Support for my Sony CDR Worm. Ok - it's just philosophy - commercial and public domain interaction. Anyway, thank you. --- ---------------------------------- Sergey Kosyakov Laboratory of Distributed Computing Department of High-Performance Computing and Applied Network Research Landau Institute for Theoretical Physics E-Mail: Sergey S. Kosyakov Date: 20-Nov-96 Time: 20:15:17 ---------------------------------- From owner-freebsd-hackers Thu Nov 20 09:54:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21597 for hackers-outgoing; Thu, 20 Nov 1997 09:54:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21590; Thu, 20 Nov 1997 09:54:05 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id MAA10107; Thu, 20 Nov 1997 12:52:33 -0500 (EST) Date: Thu, 20 Nov 1997 12:52:32 -0500 (EST) From: Jim Flowers To: Archie Cobbs cc: Jun-ichiro itojun Itoh , ru@ucb.crimea.ua, itojun@freebsd.org, hackers@freebsd.org Subject: Re: IPSec and 2.2-STABLE In-Reply-To: <199711192256.OAA26978@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have quite a bit of Skip-1.0 patched and running on 2.2.5 starting with Joe MacDonalds patches. Currently I'm working on eliminating warnings during compile and getting more functionality for skiptool under open windows. Most of the warnings are implicit declarations, unused variables and incompatable typing (about 70 involving 17 files). Works ok FreeBSD to FreeBSD but so far have not got the configuration right for W95 to FreeBSD (version 0 used although 2 configured). W95 to W95 works fine. Hope to have clean compile by end of next week. Any of this of any use to you? Jim Flowers #4 ISP on C|NET, #1 in Ohio On Wed, 19 Nov 1997, Archie Cobbs wrote: > Jun-ichiro itojun Itoh writes: > > >What is the general state of IPSec for FreeBSD? > > > > We, WIDE project IPv6 working group is working on IPv6/IPsec > > extension for FreeBSD. As for IPsec we support both rfc182* > > and draft-ietf-*. ESP Transport mode is working very well. > > ESP Tunnel mode is yet to be done. > > See http://www.v6.wide.ad.jp/ for more info. > > > > >Can I use it with post-2.2.5-RELEASE (i.e. 2.2-STABLE)? > > > > We use 2.2.5-RELEASE as base version but I believe our patch > > can easily be applied. > > Also, when I get around to it I'm going to make a port of Sun's SKIP > package for FreeBSD 2.2-stable (it definitely requires some patching). > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > From owner-freebsd-hackers Thu Nov 20 10:28:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24211 for hackers-outgoing; Thu, 20 Nov 1997 10:28:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24169 for ; Thu, 20 Nov 1997 10:28:02 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA09983; Thu, 20 Nov 1997 11:27:49 -0700 (MST) From: Terry Lambert Message-Id: <199711201827.LAA09983@usr01.primenet.com> Subject: Re: Mail spam, sigh... To: brian@awfulhak.org (Brian Somers) Date: Thu, 20 Nov 1997 18:27:47 +0000 (GMT) Cc: tlambert@primenet.com, sef@kithrup.com, hackers@freebsd.org In-Reply-To: <199711200143.BAA14262@awfulhak.demon.co.uk> from "Brian Somers" at Nov 20, 97 01:43:26 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have yet to see a clean way to make this work with a transiently > > connected system. I'd guess that the majority of users are on > > transiently connected systems (note: I did not say the majority of > > FreeBSD boxes). > > I'm on a `transiently connected' system and now happily use the stuff > in /etc/mail (introduced for 2.2.5). My objective is to figure out > the HACK()s (Mike Burgett has already shown me some examples) and put > 'em in the FAQ - unless someone gets there in front of me (I've got > lots of other stuff to keep be busy with at the moment too). > > > We need to start thinking about a set of "out of the box" configurations: > [.....] > > I'm not sure I understand the rationale here. What's the difference > between a ``permanent'' and ``sometimes'' link (unless you're subtly > referring to the fact that most if not all of these rules are done in > the canonification stage, and many ``sometimes'' sites have > FEATURE(nocanonify)) ? If we get something working for the > ``sometimes'' sites, why wouldn't it also work with the ``permanent'' > sites ? Because you can't do DNS lookups when your link is down, and using "fetchmail" or "qpopper" or "poplookup" to get your mail enqueues it locally instead of delivering it immediately, and by the time "sendmail -q" runs for queue processing, you have no way to do DNS lookups? Or that DNS lookups need to occur on local machines requesting to send email, but, again, your link may not be up if you are batching the mail to send it during a periodic connect, so you can't DNS lookup your local machines? Or you are acting as a "store-and-forward" site for a bunch of low cost (ie: local 28.8 phone calls) links (each site which the rules would require a DNS lookup on), and you yourself are transiently connected through a shared high cost (ie: PAC Bell or US West metered rate ISDN *and*/*or* long distance 28.8 toll call) link? Or you are connecteD 2B+d ISDN, and your 9600 baud channel is up for inbound connections, and outbound connection bring up the higher cost ISDN link, so you can get mail, but you can't do DNS lookups? There are others, like one FreeBSD box and the husband/wife/son/daugther's Windows 95 box using you as a "smarter host" -- ie: they are trying to relay through you. It's a bad idea to lock these out in the default configuration. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Nov 20 10:39:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25366 for hackers-outgoing; Thu, 20 Nov 1997 10:39:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from kcmain.skw-inc.com ([208.132.78.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25356 for ; Thu, 20 Nov 1997 10:39:03 -0800 (PST) (envelope-from root@kcmain.skw-inc.com) Received: (from root@localhost) by kcmain.skw-inc.com (8.8.7/8.8.8) id MAA18338 for hackers@freebsd.org; Thu, 20 Nov 1997 12:39:01 -0600 (CST) (envelope-from root) Date: Thu, 20 Nov 1997 12:39:01 -0600 (CST) From: Charlie Root Message-Id: <199711201839.MAA18338@kcmain.skw-inc.com> To: hackers@freebsd.org Subject: sendmail or nameserver configuration problem Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am setting up a new name server on the internet for a customers domain, and everything is working, except that when email is sent to anyone@skw-inc.com I get the following error: Nov 20 12:34:31 kcmain sendmail[18313]: MAA18311: SYSERR(root): skw-inc.com.skw-inc.com. config error: mail loops back to me (MX problem? I have the machine defined as skw-inc.com. in my nameserver files. It has 2 network cards, so I have an entry for both IP addresses. I have aCNAME setup as mail.skw-inc.com, which also failes. any ideas? brian From owner-freebsd-hackers Thu Nov 20 10:42:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25666 for hackers-outgoing; Thu, 20 Nov 1997 10:42:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25656 for ; Thu, 20 Nov 1997 10:42:26 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id LAA11374; Thu, 20 Nov 1997 11:42:08 -0700 (MST) From: Terry Lambert Message-Id: <199711201842.LAA11374@usr01.primenet.com> Subject: Re: Partitioning suggestions? To: tom@sdf.com (Tom) Date: Thu, 20 Nov 1997 18:42:06 +0000 (GMT) Cc: tlambert@primenet.com, Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@FreeBSD.ORG In-Reply-To: from "Tom" at Nov 19, 97 06:50:16 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I can't accept that idea of a "graceful" failure. I don't know if there > > > are any "catastrophic" (ie. eaten e-mail, destroyed password > > > files, etc) failures in FreeBSD, due to full filesystems. But the > > > so-called graceful failures are the real essence of this thread. How do > > > you avoid them in the first place? > > > > By not engaging in sysadm pilot error that results in filled drives. > > In what universe is this? Point me to a mail server that you use, and > I will fill one or more filesystems for you. Then when done, I will blame > it on your pilot error. It will start refusing your mail as originating from a mail bomber based on hueristics before that could happen. If this failed, and it didn't, then it would start refusing your mail on the basis of my account being over quota, since unlike stupid configurations, my mail server is set up to deliver mail directly to use accounts (and runs as the user to do so). If this failed (ie: I was so stupid as to overcommit my disk space), then it would begin refusing your mail as soon as there were less than some minimum number of blocks free on the FS to which it is spooling. In none of these cases is the failure triggered by the FS actually getting full. Are you trying to convinve me you can DOS attack me? I know that already. There are much more clever ways of doing that than you suggest, however, and therefore much more effective. I could make an smtp connection from a relatively large and geographically seperate number of locations, and do nothing with it (for example). I would send "NOP" requests to keep the sendmail up and sucking up virtual memory, as well as keeping the number of processes high enough that your memory overcommit based VM system would start "sniping" other processes. If you've intentionally limited the number of sendmail's that could run simultaneously, then at worst I can deny all other inbound connections. Denial of Service attacks are a problem. Handle them on a one-by-one basis, but please start in order of severity. The attack you have described is down in the noise, easily trackable, and easily (and cheaply) prosecuted in a local venue (ie: you can eat the travel costs to appear in my local jurisdiction's courtroom, or you can pay the summary judgement entered in after your failure to appear; in other words, you lose financially if you use that naieve an attack. > > > > That doesn't guarantee it. What if your FS fills up with PID files? > > > > > > What would be creating pid files in /var/log? > > > > In /var. > > The original poster, said to make /var/log a separate filesystem. > This goes along with my point, because it would eliminate the problem. You would still be able to deny service. You just wouldn't be able to deny logging. Luckily, you could force the logs to roll over in the available space, and thus obliterate whatever you wanted to obliterate from the logs, and *still* deny logging service. Denial of service is a blivit. No matter how you shovel, you can't fit 10 pounds of manure into a 5 pound sack. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Nov 20 11:21:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28117 for hackers-outgoing; Thu, 20 Nov 1997 11:21:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28112 for ; Thu, 20 Nov 1997 11:21:13 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21407; Thu, 20 Nov 1997 11:16:41 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd021401; Thu Nov 20 11:16:34 1997 Message-ID: <34748C15.794BDF32@whistle.com> Date: Thu, 20 Nov 1997 11:14:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Emmanuel.Duros@sophia.inria.fr CC: freebsd-hackers@FreeBSD.ORG Subject: Re: My fbsd router looses packets ! References: <199711200932.KAA07538@chouette.inria.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Emmanuel Duros wrote: > > My fbsd (2.2.2 release) router has two communication interfaces and when > it routes packets between its interfaces, it looses lots of packets ! > > Here is the network configuration: > > --- --------- --- > |A| | B | |C| > --- --------- --- > | (b1) | | (b2) | > -------------------------- -------------------------- > > b1 is an Ethernet interface, b2 is a dvb interface, it is a satellite > communication card (a send-only interface). I wrote the device > driver for the latter. > > I have used a video conferencing application to verify the communication > between the stations: > > 1) A generates a video stream to B up to several Mbps: NO LOSSES > 2) B generates a video stream to C up to several Mbps: NO LOSSES > 3) A generates a video stream to C at 100-200 kbps and I get 5 to > 30 % loss rate > > 1) ensures that the connectivity between A and B is fine > 2) ensures that the connectivity between B and C is fine > 3) shows that there is a routing pb !!! > > Beside this, it is not the first time I have used this network > configuration, it used to work very well on another a fbsd router > running a one year old snapshot. > > I have got absolutely no idea where my pb comes from, I have checked > IRQs, probable overlapping ports and everything looks fine to me. I do > not think it comes from my driver because of 2) and because it used to > work very well before I changed the PC and the fbsd OS version. > > I join the output of the dmesg in case this can help... > Thanks a lot for any help! > > Emmanuel > > PS: For information the send-only interface (dvtx0) has an ISA bus and > performs DMA transfers > > ------- > Copyright (c) 1992-1997 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > FreeBSD 2.2.2-RELEASE #5: Wed Nov 19 21:10:31 GMT 1997 > eduros@pacman.inria.fr:/usr/src/sys/compile/PACMAN_TX > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping=9 > Features=0xfbff,MTRR,PGE,MCA,CMOV> > real memory = 67108864 (65536K bytes) > avail memory = 62619648 (61152K bytes) > Probing for devices on PCI bus 0: > chip0 rev 2 on pci0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > vga0 rev 1 int a irq 10 on pci0:17 > de0 rev 17 int a irq 15 on pci0:18 > de0: 21041 [10Mb/s] pass 1.1 > de0: address 00:00:c0:6b:ea:df > chip3 rev 1 on pci0:20:0 > pci0:20:1: Intel Corporation, device=0x1960, class=memory (misc) int a irq 9 [no driver assigned] > Probing for devices on PCI bus 1: > ahc0 rev 0 int a irq 10 on pci1:1 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "CONNER CFP2107W 2.14GB 1524" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2048MB (4194304 512 byte sectors) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 72065B > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (atapi): , removable, ovlap, dma, iordis > wcd0: 2066Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray > wcd0: no disc inside, unlocked > dvtx0: 0.9b1 version - Probing... > dvtx0 at 0x310 irq 11 drq 5 on isa > npx0 on motherboard > npx0: INT 16 interface > ccd0-3: Concatenated disk drivers > de0: enabling 10baseT port An ISA bus can only really support 1 ethernet and still leave any CPU time for other actions. can you stream video from B tpo A and C at the same time? how about from A and C to B at the same time.? ISA is a hog. While th ISA cycle is proceding, the CPU can do nothing else. ISA I/O cycles are approximatly 1uSec long.. do the maths. If it's an 8-bit card, you lose.. 16 bit cards are 'close' (SOME ISA implementations are better than others) From owner-freebsd-hackers Thu Nov 20 11:30:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29013 for hackers-outgoing; Thu, 20 Nov 1997 11:30:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28991 for ; Thu, 20 Nov 1997 11:30:51 -0800 (PST) (envelope-from joes@shasta.wstein.com) Received: (from joes@localhost) by shasta.wstein.com (8.8.8/8.8.8) id LAA12994; Thu, 20 Nov 1997 11:29:24 -0800 (PST) From: Joseph Stein Message-Id: <199711201929.LAA12994@shasta.wstein.com> Subject: Re: Artificial Lifeform? In-Reply-To: <24212.880014638@time.cdrom.com> from "Jordan K. Hubbard" at "Nov 20, 97 00:30:38 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 20 Nov 1997 11:29:24 -0800 (PST) Cc: asami@cs.berkeley.edu, jamil@trojanhorse.ml.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 X-Loop: FreeBSD.org Precedence: bulk > Hey, you know, I really resent these baseless insinuations that I^\Quit (core dumped) > Anyone got a bucket so jkh can start over again? From owner-freebsd-hackers Thu Nov 20 12:13:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03409 for hackers-outgoing; Thu, 20 Nov 1997 12:13:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03402 for ; Thu, 20 Nov 1997 12:13:53 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA04095 for ; Thu, 20 Nov 1997 12:13:51 -0800 (PST) Date: Thu, 20 Nov 1997 12:13:51 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: When are login.conf limits honored? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are limits set by login.conf enforced for users no matter how their process starts? IE, if a person is gets a process started via apache under their uid, (so setuid() I assume), do the login.conf limits take affect? It doesn't appear to, but perhaps I'm doing something wrong. From owner-freebsd-hackers Thu Nov 20 12:17:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03703 for hackers-outgoing; Thu, 20 Nov 1997 12:17:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03687 for ; Thu, 20 Nov 1997 12:17:39 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA05088 for ; Thu, 20 Nov 1997 12:17:37 -0800 (PST) Date: Thu, 20 Nov 1997 12:17:36 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Serious performance issue with 2.2.5-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in July. Big mistake. The only update to take place was the make buildworld, make installworld, no other configuration files were modified, nor any changes to startup scripts, etc. I now get these weird pauses where everything on the machine just freezes for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. The system was a web server, and was happily serving up several hundred domains. Now with the upgrade, I'll be lucky to keep them. Not good. It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. Any ideas appreciated. I have built a new kernel from sources supped 11/7, but it doesn't seem to be any better. From owner-freebsd-hackers Thu Nov 20 12:20:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA04005 for hackers-outgoing; Thu, 20 Nov 1997 12:20:12 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03992 for ; Thu, 20 Nov 1997 12:20:05 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id LAA01891; Thu, 20 Nov 1997 11:41:25 -0800 (PST) Date: Thu, 20 Nov 1997 11:41:25 -0800 (PST) From: "Jamil J. Weatherbee" To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: vnode.h and IO_NDELAY (help!!) In-Reply-To: <19971120090611.FW37911@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Also, don't forget that you need to allow the FIONBIO ioctl command. Ok, sorry, I see what you are doing now. Your just hashing out the read function returning ERESTART and instead returing EINTR, since you have no way of restarting. I have done that also (it made sense). But about the FIONBIO call, I don't see what you are saying. Why would I need to support that, I thought that that would be intercepted at the vnode level? I see it defined in filio.h. By the way, how are you supposed to pick ioctl groups. I am currently using 'A', but i see 'D' being used also. Is there a list of which letter you should use. I assume lowercase are reserved for the system and you should always use uppercase in new drivers? From owner-freebsd-hackers Thu Nov 20 12:39:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA05444 for hackers-outgoing; Thu, 20 Nov 1997 12:39:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05429 for ; Thu, 20 Nov 1997 12:39:27 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA28828; Thu, 20 Nov 1997 15:36:18 -0500 (EST) Date: Thu, 20 Nov 1997 15:36:17 -0500 (EST) From: Snob Art Genre To: Charlie Root cc: hackers@FreeBSD.ORG Subject: Re: sendmail or nameserver configuration problem In-Reply-To: <199711201839.MAA18338@kcmain.skw-inc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yeah, you have to add the lines Cwskw-inc.com Cwmail.skw-inc.com to your sendmail.cf . . . this stuff should go to -questions btw. On Thu, 20 Nov 1997, Charlie Root wrote: > I am setting up a new name server on the internet for a customers > domain, and everything is working, except that when email is sent to > anyone@skw-inc.com I get the following error: > > Nov 20 12:34:31 kcmain sendmail[18313]: MAA18311: SYSERR(root): > skw-inc.com.skw-inc.com. config error: mail loops back to me (MX > problem? > > I have the machine defined as skw-inc.com. in my nameserver files. It > has 2 network cards, so I have an entry for both IP addresses. I have > a CNAME setup as mail.skw-inc.com, which also failes. > > any ideas? > > brian > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Thu Nov 20 13:34:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA09869 for hackers-outgoing; Thu, 20 Nov 1997 13:34:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA09861; Thu, 20 Nov 1997 13:34:53 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA10663; Thu, 20 Nov 1997 13:34:22 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma010661; Thu Nov 20 13:33:54 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id NAA04627; Thu, 20 Nov 1997 13:33:54 -0800 (PST) From: Archie Cobbs Message-Id: <199711202133.NAA04627@bubba.whistle.com> Subject: Re: IPSec and 2.2-STABLE In-Reply-To: from Jim Flowers at "Nov 20, 97 12:52:32 pm" To: jflowers@ezo.net (Jim Flowers) Date: Thu, 20 Nov 1997 13:33:53 -0800 (PST) Cc: archie@whistle.com, itojun@itojun.org, ru@ucb.crimea.ua, itojun@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jim Flowers writes: > > > Also, when I get around to it I'm going to make a port of Sun's SKIP > > package for FreeBSD 2.2-stable (it definitely requires some patching). > > I have quite a bit of Skip-1.0 patched and running on 2.2.5 starting > with Joe MacDonalds patches. Currently I'm working on eliminating warnings > during compile and getting more functionality for skiptool under open windows. > Most of the warnings are implicit declarations, unused variables and > incompatable typing (about 70 involving 17 files). Works ok FreeBSD > to FreeBSD but so far have not got the configuration right for W95 to > FreeBSD (version 0 used although 2 configured). W95 to W95 works fine. > Hope to have clean compile by end of next week. Any of this of any use > to you? Yes.. I'd like to see your patches. I've already patched it to compile and eliminate all warnings myself... I've tested it between two FreeBSD machines, but not otherwise. If you want to see my patches lemme know. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Nov 20 13:44:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10678 for hackers-outgoing; Thu, 20 Nov 1997 13:44:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from inertia.dfacades.com (inertia.dfacades.com [207.155.93.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10665 for ; Thu, 20 Nov 1997 13:44:37 -0800 (PST) (envelope-from dleeds@dfacades.com) Received: (from dleeds@localhost) by inertia.dfacades.com (8.8.7/8.8.7) id NAA00409 for hackers@freebsd.org; Thu, 20 Nov 1997 13:48:03 -0800 (PST) From: Daniel Leeds Message-Id: <199711202148.NAA00409@inertia.dfacades.com> Subject: vidcontrol questions To: hackers@freebsd.org Date: Thu, 20 Nov 1997 13:48:02 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL35 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i work on a laptop and use vidcontrol to set my screen background to blue and text to yellow. if i use lynx or some other programs it reverts back to black and white when i quit...is there some way to make yellow and blue the default so whe i boot its like that and it wont change if some program exits and resets the terminal as i assume its doing. thanks From owner-freebsd-hackers Thu Nov 20 13:49:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11010 for hackers-outgoing; Thu, 20 Nov 1997 13:49:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from cray-ymp.acm.stuorg.vt.edu (scott@cray-ymp.acm.stuorg.vt.edu [128.173.43.251]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10909 for ; Thu, 20 Nov 1997 13:47:58 -0800 (PST) (envelope-from scott@cray-ymp.acm.stuorg.vt.edu) Received: (from scott@localhost) by cray-ymp.acm.stuorg.vt.edu (8.8.7/8.8.5) id QAA27967 for freebsd-hackers@freebsd.org; Thu, 20 Nov 1997 16:47:46 -0500 (EST) From: Scott Gasch Message-Id: <199711202147.QAA27967@cray-ymp.acm.stuorg.vt.edu> Subject: Question about swapping To: freebsd-hackers@freebsd.org Date: Thu, 20 Nov 1997 16:47:46 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am running 3.0-CURRENT off of the most recent snapshot. I have a strange problem with swap -- maybe it's just me doing something dumb... Is it possible to swap on three partitions? There are three drives in the system and I set up a swap partition on each to improve interleved performance. But when I do a swapon -a it starts swapping on the first two (i.e. the first two entries in fstab) and says the third is an "invalid argument". Changing the order in fstab changes which two devices it swaps on. Did I miss something? Reading the swapinfo and swapon man pages led me to believe there was no two partition limit... Thanks for the help. Scott -- +------------+ hp +-----------------+ | Scott Gasch \ / scott@ | | Computer Sci \ ``All programmers are playwrights and / perl.guru.org | | Virginia Tech \ all computers are lousy actors'' / finger for PGP key | +----------------+ +---------------------+ From owner-freebsd-hackers Thu Nov 20 13:55:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11615 for hackers-outgoing; Thu, 20 Nov 1997 13:55:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11599 for ; Thu, 20 Nov 1997 13:55:46 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id QAA03288; Thu, 20 Nov 1997 16:55:38 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711202155.QAA03288@dyson.iquest.net> Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: from Jaye Mathisen at "Nov 20, 97 12:17:36 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 20 Nov 1997 16:55:38 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen said: > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > July. > > Big mistake. > > The only update to take place was the make buildworld, make installworld, > no other configuration files were modified, nor any changes to startup > scripts, etc. > > I now get these weird pauses where everything on the machine just freezes > for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > The system was a web server, and was happily serving up several hundred > domains. Now with the upgrade, I'll be lucky to keep them. Not good. > > It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > > Any ideas appreciated. I have built a new kernel from sources supped > 11/7, but it doesn't seem to be any better. > Try this patch. The change in vfs_bio from 2.2.2 to 2.2.5 appears to be incorrect, and subverts part of the functionality of what getnewbuf is supposed to do. (Sorry, the patch might be reversed.) Index: sys/kern/vfs_bio.c =================================================================== RCS file: /local/home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.104.2.7 retrieving revision 1.104.2.3 diff -C2 -r1.104.2.7 -r1.104.2.3 *** vfs_bio.c 1997/09/01 23:23:08 1.104.2.7 --- vfs_bio.c 1997/02/13 08:17:18 1.104.2.3 *************** *** 889,896 **** /* wait for a free buffer of any kind */ needsbuffer = 1; ! do ! tsleep(&needsbuffer, (PRIBIO + 1) | slpflag, "newbuf", ! slptimeo); ! while (needsbuffer); return (0); } --- 872,877 ---- /* wait for a free buffer of any kind */ needsbuffer = 1; ! tsleep(&needsbuffer, ! (PRIBIO + 1) | slpflag, "newbuf", slptimeo); return (0); } -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Thu Nov 20 14:00:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12023 for hackers-outgoing; Thu, 20 Nov 1997 14:00:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11978 for ; Thu, 20 Nov 1997 13:59:59 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id NAA02655; Thu, 20 Nov 1997 13:59:37 -0800 (PST) Message-ID: <19971120135937.07786@micron.mini.net> Date: Thu, 20 Nov 1997 13:59:37 -0800 From: Jonathan Mini To: "Jamil J. Weatherbee" Cc: Joerg Wunsch , hackers@freebsd.org Subject: Re: vnode.h and IO_NDELAY (help!!) Reply-To: Jonathan Mini References: <19971120090611.FW37911@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Jamil J. Weatherbee on Thu, Nov 20, 1997 at 11:41:25AM -0800 X-files: The Truth is Out There Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jamil J. Weatherbee stands accused of saying: > [ ... snip ... ] By the way, how are you supposed to pick > ioctl groups. I am currently using 'A', but i see 'D' being used also. > Is there a list of which letter you should use. I assume lowercase are > reserved for the system and you should always use uppercase in new > drivers? ioctl group ID's are local to each device driver. They are used soely for groupsing ioctl's into groups by your driver. For an example, look at machine/console.h, which defines the ioctls for syscons/pcvt. -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five." From owner-freebsd-hackers Thu Nov 20 14:28:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14176 for hackers-outgoing; Thu, 20 Nov 1997 14:28:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from unix.tfs.net (pm3-p44.tfs.net [206.154.183.236]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA14168 for ; Thu, 20 Nov 1997 14:28:50 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.7/8.8.5) id QAA11446; Thu, 20 Nov 1997 16:28:38 -0600 (CST) From: Jim Bryant Message-Id: <199711202228.QAA11446@unix.tfs.net> Subject: Re: vidcontrol questions In-Reply-To: <199711202148.NAA00409@inertia.dfacades.com> from Daniel Leeds at "Nov 20, 97 01:48:02 pm" To: dleeds@dfacades.com (Daniel Leeds) Date: Thu, 20 Nov 1997 16:28:37 -0600 (CST) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > i work on a laptop and use vidcontrol to set my screen background to > blue and text to yellow. > > if i use lynx or some other programs it reverts back to black and white > when i quit...is there some way to make yellow and blue the default so > whe i boot its like that and it wont change if some program exits > and resets the terminal as i assume its doing. > > thanks look in /usr/src/sys/i386/isa/syscons.c for user_default and kernel_default. one of the first things i always change, as i like cyan on black regular text, and yellow on black kernel messages... another thing to change would be in /usr/src/sys/i386/isa/syscons.h would be the HISTORY_SIZE if you like more scrollback buffering... 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+ From owner-freebsd-hackers Thu Nov 20 15:00:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16390 for hackers-outgoing; Thu, 20 Nov 1997 15:00:22 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16379 for ; Thu, 20 Nov 1997 15:00:12 -0800 (PST) (envelope-from byung@wam.umd.edu) Received: from rac3.wam.umd.edu (byung@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.8.8.Beta2/8.8.7) with ESMTP id SAA00151 for ; Thu, 20 Nov 1997 18:00:09 -0500 (EST) From: Byung Yang Received: (from byung@localhost) by rac3.wam.umd.edu (8.8.8/8.8.7) id SAA09764 for freebsd-hackers@freefall.cdrom.com; Thu, 20 Nov 1997 18:00:06 -0500 (EST) Date: Thu, 20 Nov 1997 18:00:06 -0500 (EST) Message-Id: <199711202300.SAA09764@rac3.wam.umd.edu> To: freebsd-hackers@freefall.FreeBSD.org Subject: about VoxWare.. Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am currently using FreeBSD 2.2.0 Release. In the kernel, I noticed that VoxWare Sound Driver: 3.0-beta-950506 was supported. Is there any recent version of this? I am using Turtle Beach TBS2000 and it's not supported by this driver. CS4232 driver also works with this card. Where can I find newer drivers? Thanks Byung From owner-freebsd-hackers Thu Nov 20 15:02:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16636 for hackers-outgoing; Thu, 20 Nov 1997 15:02:52 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from callisto.fortean.com (callisto.fortean.com [206.142.225.82]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16497; Thu, 20 Nov 1997 15:01:31 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.5/8.8.5) with SMTP id RAA08794; Thu, 20 Nov 1997 17:56:14 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Thu, 20 Nov 1997 17:56:14 -0500 (EST) From: "Bruce M. Walter" To: hackers@freebsd.org, questions@freebsd.org Subject: Ascend NetWarp 128 ISDN TA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all! Is anyone working on a driver for the Ascend NetWarp 128 ISDN Terminal Adapter? It is based on a network interface model rather than a comm port model so it should not suffer from all of the latency problems of a serial TA. Currently the card is selling for ~$175 US dollars and comes with Windoze95 and NT miniport drivers which back into the M$ ISDN accellerator interface. I have one of these cards and would be willing to port/write a driver for it if there's not one already in the works. - Bruce ======================================================================== || Bruce M. Walter || 107 Timber Hollow Court #335 || || Senior Network Consultant || Chapel Hill, NC 27514 || || Fortean Technologies, Inc. || Tel: 919-967-4766 || || Information Technology Consultants || Fax: 919-967-4395 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Thu Nov 20 15:29:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19019 for hackers-outgoing; Thu, 20 Nov 1997 15:29:50 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19007 for ; Thu, 20 Nov 1997 15:29:43 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id AAA03508 for hackers@FreeBSD.ORG; Fri, 21 Nov 1997 00:29:30 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA03705; Fri, 21 Nov 1997 00:20:01 +0100 (CET) (envelope-from roberto) Message-ID: <19971121002001.09565@keltia.freenix.fr> Date: Fri, 21 Nov 1997 00:20:01 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: NBQ: Why partitioning? (was: Re: Partitioning suggestions?) References: <199711180019.TAA01983@dyson.iquest.net> <199711180202.VAA04479@luomat.peak.org> <19971117192532.37475@micron.mini.net> <19971119193141.NY02422@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19971119193141.NY02422@uriah.heep.sax.de>; from J Wunsch on Wed, Nov 19, 1997 at 07:31:41PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3818 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > I wished we would support 16 partition slots at least as an > alternative to the backwards-compatible 8 slot model. Why not using a second FreeBSD slice ? I think it should work. I've tried it but intend to on my new 4.3 GB drive. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #49: Sat Nov 15 20:03:33 CET 1997 From owner-freebsd-hackers Thu Nov 20 15:31:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19194 for hackers-outgoing; Thu, 20 Nov 1997 15:31:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19183 for ; Thu, 20 Nov 1997 15:31:34 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id PAA15413; Thu, 20 Nov 1997 15:30:47 -0800 (PST) Date: Thu, 20 Nov 1997 15:30:47 -0800 (PST) From: Jaye Mathisen To: "John S. Dyson" cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711202155.QAA03288@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmmm, this patch fails either way I apply it. Can somebody mail me the 1.104.2.3 rev of this file? I tried to get to ftp.freebsd.org, but it's unavailable. Or the cvs command to extract it, my permutations have been less than successful getting the right version, although I have a cvs tree from cvsupd handy. On Thu, 20 Nov 1997, John S. Dyson wrote: > Jaye Mathisen said: > > > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > > July. > > > > Big mistake. > > > > The only update to take place was the make buildworld, make installworld, > > no other configuration files were modified, nor any changes to startup > > scripts, etc. > > > > I now get these weird pauses where everything on the machine just freezes > > for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > > > The system was a web server, and was happily serving up several hundred > > domains. Now with the upgrade, I'll be lucky to keep them. Not good. > > > > It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > > > > Any ideas appreciated. I have built a new kernel from sources supped > > 11/7, but it doesn't seem to be any better. > > > Try this patch. The change in vfs_bio from 2.2.2 to 2.2.5 appears to be > incorrect, and subverts part of the functionality of what getnewbuf is > supposed to do. (Sorry, the patch might be reversed.) > > > Index: sys/kern/vfs_bio.c > =================================================================== > RCS file: /local/home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.104.2.7 > retrieving revision 1.104.2.3 > diff -C2 -r1.104.2.7 -r1.104.2.3 > *** vfs_bio.c 1997/09/01 23:23:08 1.104.2.7 > --- vfs_bio.c 1997/02/13 08:17:18 1.104.2.3 > *************** > *** 889,896 **** > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! do > ! tsleep(&needsbuffer, (PRIBIO + 1) | slpflag, "newbuf", > ! slptimeo); > ! while (needsbuffer); > return (0); > } > --- 872,877 ---- > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! tsleep(&needsbuffer, > ! (PRIBIO + 1) | slpflag, "newbuf", slptimeo); > return (0); > } > > > -- > John > dyson@freebsd.org > jdyson@nc.com > From owner-freebsd-hackers Thu Nov 20 15:31:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19201 for hackers-outgoing; Thu, 20 Nov 1997 15:31:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rumor.research.att.com (rumor.research.att.com [192.20.225.9]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA19186 for ; Thu, 20 Nov 1997 15:31:35 -0800 (PST) (envelope-from ji@research.att.com) Received: from research.att.com ([135.207.30.100]) by rumor; Thu Nov 20 18:27:39 EST 1997 Received: from amontillado.research.att.com ([135.207.24.32]) by research-clone; Thu Nov 20 18:26:49 EST 1997 Received: from bual.research.att.com (bual.research.att.com [135.207.24.19]) by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id SAA15570; Thu, 20 Nov 1997 18:26:45 -0500 (EST) Received: (from ji@localhost) by bual.research.att.com (8.7.5/8.7) id SAA02346; Thu, 20 Nov 1997 18:26:44 -0500 (EST) Date: Thu, 20 Nov 1997 18:26:44 -0500 (EST) Message-Id: <199711202326.SAA02346@bual.research.att.com> From: John Ioannidis To: hackers@FreeBSD.ORG Cc: lile@stdio.com In-reply-to: <199711202155.NAA11629@hub.freebsd.org> (owner-hackers-digest@FreeBSD.ORG) Subject: Re: Problems mounting a cd-rom drive on 2.2_RELENG Reply-To: ji@research.att.com Organization: AT&T Labs - Research Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > anarchy: # mount /cdrom > cd9660: /dev/cd0a: Invalid argument Looks like your kernel and your /sbin/mount_cd9660 are not happy with each other. Make sure you run the mount program that goes with the kernel you are running. If you are tracking FreeBSD-current, make sure your mount_cd9660 is: "$Id: mount_cd9660.c,v 1.7.2.1 1997/08/17 13:30:23 joerg Exp$"; The mount program that comes with 2.2.2-RELEASE does not work. /ji From owner-freebsd-hackers Thu Nov 20 15:33:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19566 for hackers-outgoing; Thu, 20 Nov 1997 15:33:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19558 for ; Thu, 20 Nov 1997 15:33:27 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA27875; Thu, 20 Nov 1997 16:33:13 -0700 (MST) From: Terry Lambert Message-Id: <199711202333.QAA27875@usr02.primenet.com> Subject: Re: When are login.conf limits honored? To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 20 Nov 1997 23:33:12 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Nov 20, 97 12:13:51 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Are limits set by login.conf enforced for users no matter how their > process starts? IE, if a person is gets a process started via apache > under their uid, (so setuid() I assume), do the login.conf limits > take affect? > > It doesn't appear to, but perhaps I'm doing something wrong. man 3 login_class Apache doesn't call it. Hack apache to fix. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Nov 20 15:38:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA20183 for hackers-outgoing; Thu, 20 Nov 1997 15:38:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA20167; Thu, 20 Nov 1997 15:38:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA11660 (5.67b/IDA-1.5); Fri, 21 Nov 1997 00:38:03 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id AAA06703; Fri, 21 Nov 1997 00:17:10 +0100 (MET) From: Wilko Bulte Message-Id: <199711202317.AAA06703@yedi.iaf.nl> Subject: Re: need an Alpha-based machine To: tlambert@primenet.com (Terry Lambert) Date: Fri, 21 Nov 1997 00:17:10 +0100 (MET) Cc: sprice@hiwaay.net, alpha@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199711172043.NAA26135@usr07.primenet.com> from "Terry Lambert" at Nov 17, 97 08:43:15 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote... > > > Does anybody out there in FreeBSD-land have a spare > > Alpha-based machine that they would be willing to > > loan/sell? > > > > I want to contribute to getting the FreeBSD Alpha > > I'm using a Multia, and not the "official" porting platform (there > is no documentation for the "official" platform). > > You can obtain a Multia rather cheaply from www.onsale.com, if you > are willing to wait for the interest to wane (it gets bumped by > postings like this one -- might as well not compete with other > FreeBSD'ers. ;-)). You can also look at the PC64 boards, they sell here in Holland for US$ 175. See www.request.nl This mainboard, while not a speed daemon of any magnitude, at least holds a couple of PCI exp. cards. The Multia is limited to one short PCI slot. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix --Yoda From owner-freebsd-hackers Thu Nov 20 15:44:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA20788 for hackers-outgoing; Thu, 20 Nov 1997 15:44:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA20738 for ; Thu, 20 Nov 1997 15:44:00 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA28655; Thu, 20 Nov 1997 16:43:59 -0700 (MST) From: Terry Lambert Message-Id: <199711202343.QAA28655@usr02.primenet.com> Subject: Re: vidcontrol questions To: dleeds@dfacades.com (Daniel Leeds) Date: Thu, 20 Nov 1997 23:43:57 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199711202148.NAA00409@inertia.dfacades.com> from "Daniel Leeds" at Nov 20, 97 01:48:02 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i work on a laptop and use vidcontrol to set my screen background to > blue and text to yellow. > > if i use lynx or some other programs it reverts back to black and white > when i quit...is there some way to make yellow and blue the default so > whe i boot its like that and it wont change if some program exits > and resets the terminal as i assume its doing. There is a conflict between the ISO color sequences adjunct to ANS 3.64 and the use of attributes. What does reverse video mean? What does underline mean? In the monochrome days, underline meant "set this bit in display memory for all displayed characters". In the color days, there was no underline, only color attributes (and a blink bit that could be defined to blink on clock OR provide an additional bit selector for background color). An underlined word meant "dark blue on black" instead of "white on black" because of the 0-7 value assignments for the 4 bits. So when you select an attribute, you are selecting colors. How "esc [ 0 m" affects colors depends on whether the attributes are considered specific color combinations, modifications of the default color combinations (ie: "reverse = flip foreground/background", but "underine = ???" and "bold = ??? [flip bit 3?]", etc.). SCO has additional sequences in its console to allow selection of color pairs for attributes. But say I build a set of texts like: ,--------------------------. | most of the text | | | | | | ,-------------------. | | | Warning text | | | `-------------------' | | | | | | | `--------------------------' And I want to invert one word of the warning text. What is inverse now? The correct way to handle this is to change your bold, underline, and "attribute off" termcap entries to set the colors you want.. and the "off" means "set back to my preferred colors" instead of "off". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Nov 20 16:36:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24582 for hackers-outgoing; Thu, 20 Nov 1997 16:36:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from unix.tfs.net (node41.tfs.net [207.2.220.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24577 for ; Thu, 20 Nov 1997 16:36:18 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.7/8.8.5) id SAA11620; Thu, 20 Nov 1997 18:36:09 -0600 (CST) From: Jim Bryant Message-Id: <199711210036.SAA11620@unix.tfs.net> Subject: Re: vidcontrol questions In-Reply-To: <199711202343.QAA28655@usr02.primenet.com> from Terry Lambert at "Nov 20, 97 11:43:57 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 20 Nov 1997 18:36:09 -0600 (CST) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > There is a conflict between the ISO color sequences adjunct to ANS 3.64 A> and the use of attributes. > > What does reverse video mean? What does underline mean? [snip] terry, user_default and kernel_default were provided for the purpose the gentleman asked about. vidcontrol only operates on the console, thus the question was concerning the console. there is no need to mung up termcap by giving nonstandard definitions for standard items. also, check case 'm': in syscons.c... i believe it does follow the SCO standard for changing colors seperately from the attributes you mention. 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+ From owner-freebsd-hackers Thu Nov 20 16:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24755 for hackers-outgoing; Thu, 20 Nov 1997 16:38:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24742 for ; Thu, 20 Nov 1997 16:38:09 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA22144; Thu, 20 Nov 1997 17:38:03 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA12201; Thu, 20 Nov 1997 17:37:59 -0700 Date: Thu, 20 Nov 1997 17:37:59 -0700 Message-Id: <199711210037.RAA12201@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jaye Mathisen Cc: "John S. Dyson" , hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: References: <199711202155.QAA03288@dyson.iquest.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Can somebody mail me the 1.104.2.3 rev of this file? I tried to get to > ftp.freebsd.org, but it's unavailable. You don't want that rev, you just want the changes made that John pointed out. Try this with patch -R Nate ---------- =================================================================== RCS file: /home/CVS/src/sys/kern/vfs_bio.c,v retrieving revision 1.104.2.5 retrieving revision 1.104.2.6 diff -u -r1.104.2.5 -r1.104.2.6 --- vfs_bio.c 1997/05/31 10:36:23 1.104.2.5 +++ vfs_bio.c 1997/06/21 13:32:58 1.104.2.6 @@ -887,8 +887,10 @@ if (!bp) { /* wait for a free buffer of any kind */ needsbuffer = 1; - tsleep(&needsbuffer, - (PRIBIO + 1) | slpflag, "newbuf", slptimeo); + do + tsleep(&needsbuffer, (PRIBIO + 1) | slpflag, "newbuf", + slptimeo); + while (needsbuffer); return (0); } Index: vfs_bio.c From owner-freebsd-hackers Thu Nov 20 17:06:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA27088 for hackers-outgoing; Thu, 20 Nov 1997 17:06:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA27079 for ; Thu, 20 Nov 1997 17:05:59 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA06865; Thu, 20 Nov 1997 17:05:51 -0800 (PST) Date: Thu, 20 Nov 1997 17:05:49 -0800 (PST) From: Jaye Mathisen To: "John S. Dyson" cc: hackers@FreeBSD.ORG Subject: Nope, didn't fix it.Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711202155.QAA03288@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk OK, I handpatched the source, built a new kernel, and fired it up again. If anything, it's worse than before, hanging up within seconds of rebooting. I'm dropping back to the previous version for now, but this pretty well kills 2.2.5 for me for usability. I noticed that with this patch, I get very quick spikes in the la for the machine. Putting along around 3-3.5, then bam, spike to 15-20, then slowly comes back down. Yet top shows 52M Inact, 89M act, and only 195M swap used, out of a total of 744M. I notice now that a lot of processes seem to be in vmwait, when they didn't used to show it. Heck, I just had a la spike of 480. Machine kept running, but it was unable to serve files for 2-3 minutes. Help. On Thu, 20 Nov 1997, John S. Dyson wrote: > Jaye Mathisen said: > > > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > > July. > > > > Big mistake. > > > > The only update to take place was the make buildworld, make installworld, > > no other configuration files were modified, nor any changes to startup > > scripts, etc. > > > > I now get these weird pauses where everything on the machine just freezes > > for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > > > The system was a web server, and was happily serving up several hundred > > domains. Now with the upgrade, I'll be lucky to keep them. Not good. > > > > It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > > > > Any ideas appreciated. I have built a new kernel from sources supped > > 11/7, but it doesn't seem to be any better. > > > Try this patch. The change in vfs_bio from 2.2.2 to 2.2.5 appears to be > incorrect, and subverts part of the functionality of what getnewbuf is > supposed to do. (Sorry, the patch might be reversed.) > > > Index: sys/kern/vfs_bio.c > =================================================================== > RCS file: /local/home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.104.2.7 > retrieving revision 1.104.2.3 > diff -C2 -r1.104.2.7 -r1.104.2.3 > *** vfs_bio.c 1997/09/01 23:23:08 1.104.2.7 > --- vfs_bio.c 1997/02/13 08:17:18 1.104.2.3 > *************** > *** 889,896 **** > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! do > ! tsleep(&needsbuffer, (PRIBIO + 1) | slpflag, "newbuf", > ! slptimeo); > ! while (needsbuffer); > return (0); > } > --- 872,877 ---- > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! tsleep(&needsbuffer, > ! (PRIBIO + 1) | slpflag, "newbuf", slptimeo); > return (0); > } > > > -- > John > dyson@freebsd.org > jdyson@nc.com > From owner-freebsd-hackers Thu Nov 20 17:37:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29161 for hackers-outgoing; Thu, 20 Nov 1997 17:37:42 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA29141; Thu, 20 Nov 1997 17:37:35 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id BAA26182; Fri, 21 Nov 1997 01:36:51 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711210136.BAA26182@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Sergey S. Kosyakov" cc: freebsd-ports@freebsd.org, freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Is gmake so buggy? In-reply-to: Your message of "Wed, 20 Nov 1996 17:54:02 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 01:36:51 +0000 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hi all! > > I'm trying to compile one packet (namely the last version of postgresql). > The compilation needs gmake. The files tree have modification time = now > (GMT + 3 + light saving time) and it seems to be that gmake do not > undestand localtime - it tells that files have modification time in future. > (May be I should establish some environmental variable for gmake?) > > I use FreeBSD-3.0-SNAP, computer's CMOS clock eq. localtime, timezone MSK > > PS. Please reply to: ks@itp.ac.ru (i'm subscribed freebsd-hardware only) Is, perhaps, the date of your posting some indication that you have date problems on your machine ? Your posting date was: Date: Wed, 20 Nov 1996 17:54:02 +0300 (MSK) ^^^^ *grin* > --- > ---------------------------------- > Sergey Kosyakov > Laboratory of Distributed Computing > Department of High-Performance Computing and Applied Network Research > Landau Institute for Theoretical Physics > E-Mail: Sergey S. Kosyakov > Date: 20-Nov-96 > Time: 17:54:02 > ---------------------------------- -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Nov 20 17:45:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29921 for hackers-outgoing; Thu, 20 Nov 1997 17:45:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA29906 for ; Thu, 20 Nov 1997 17:45:31 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id SAA08710; Thu, 20 Nov 1997 18:45:30 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd008696; Thu Nov 20 18:45:22 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA19629; Thu, 20 Nov 1997 18:45:20 -0700 (MST) From: Terry Lambert Message-Id: <199711210145.SAA19629@usr05.primenet.com> Subject: Re: vidcontrol questions To: jbryant@unix.tfs.net Date: Fri, 21 Nov 1997 01:45:20 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@freebsd.org In-Reply-To: <199711210036.SAA11620@unix.tfs.net> from "Jim Bryant" at Nov 20, 97 06:36:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What does reverse video mean? What does underline mean? > [snip] > > terry, > > user_default and kernel_default were provided for the purpose the > gentleman asked about. > > vidcontrol only operates on the console, thus the question was > concerning the console. > > there is no need to mung up termcap by giving nonstandard definitions > for standard items. > > also, check case 'm': in syscons.c... i believe it does follow the > SCO standard for changing colors seperately from the attributes you mention. Yah. The point is that you aren't talking colors when you use "sticky" values for these things. He's confused sticky and non-sticky in his expectations, so the real bug is not in the software. As far as not hacking termcap: This presumes you are using the color console as a monochrome console, but with different definitions of "default", "reverse", "underline", "blink", "bold", and whatever other attributes you pretend to accept (ie: double wide, double high and wide, top half, double wide and high bottom half, etc.). If you want to use it as a color terminal, you shouldn't depend on "sticky" defaults. For example, how does a particular set of "sticky" defaults interact with colorls (answer: badly), and so on. So setting defaults is kind of mutually exclusive with treating it as a color console... if I select a foreground color of green in my color aware application, I'm pretty much screwed if the user has selected a "default backgound color" of green as well. I have no way of knowing this, as a color aware application. The SCO "setcolor" utility was really meant for changing defaults for monochrome-only aware apps. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Nov 20 18:24:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA02575 for hackers-outgoing; Thu, 20 Nov 1997 18:24:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA02567 for ; Thu, 20 Nov 1997 18:24:49 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id SAA20035; Thu, 20 Nov 1997 18:24:40 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Thu, 20 Nov 1997 18:24:40 -0800 (PST) From: Chris Timmons To: "John S. Dyson" cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711202155.QAA03288@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On around November 3, there was a thread here in -hackers of subject "FreeBSD shines" that mentioned a semaphore benchmarking program: "If anyone wants the code (and results for other OSes) see ftp://samba.anu.edu.au/pub/tridge/semspeed.c" Subsequent discussion pointed out that 2.2 was quite a bit faster than 2.2.5. Maybe a look at semspeed.c will provide some suggestions about where to look. I noticed similar symptoms on my ppro 200/128MB 2.2 based file server sometime in August - short hangs of 10-20 seconds under heavy file system load, nfs+cvsupd. For my system, switching from if_de hardware to if_fxp appeared to help a lot although I upgraded to more memory around the same time... so, no real clues just vague rambling. 2.2-STABLE FreeBSD 2.2-STABLE #0: Sun Sep 7 14:31:07 PDT 1997 with 256MB and maxvnodes=32768 works really, really well. -Chris On Thu, 20 Nov 1997, John S. Dyson wrote: > Jaye Mathisen said: > > > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > > July. > > > > Big mistake. > > > > The only update to take place was the make buildworld, make installworld, > > no other configuration files were modified, nor any changes to startup > > scripts, etc. > > > > I now get these weird pauses where everything on the machine just freezes > > for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > > > The system was a web server, and was happily serving up several hundred > > domains. Now with the upgrade, I'll be lucky to keep them. Not good. > > > > It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > > > > Any ideas appreciated. I have built a new kernel from sources supped > > 11/7, but it doesn't seem to be any better. > > > Try this patch. The change in vfs_bio from 2.2.2 to 2.2.5 appears to be > incorrect, and subverts part of the functionality of what getnewbuf is > supposed to do. (Sorry, the patch might be reversed.) > > > Index: sys/kern/vfs_bio.c > =================================================================== > RCS file: /local/home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.104.2.7 > retrieving revision 1.104.2.3 > diff -C2 -r1.104.2.7 -r1.104.2.3 > *** vfs_bio.c 1997/09/01 23:23:08 1.104.2.7 > --- vfs_bio.c 1997/02/13 08:17:18 1.104.2.3 > *************** > *** 889,896 **** > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! do > ! tsleep(&needsbuffer, (PRIBIO + 1) | slpflag, "newbuf", > ! slptimeo); > ! while (needsbuffer); > return (0); > } > --- 872,877 ---- > /* wait for a free buffer of any kind */ > needsbuffer = 1; > ! tsleep(&needsbuffer, > ! (PRIBIO + 1) | slpflag, "newbuf", slptimeo); > return (0); > } > > > -- > John > dyson@freebsd.org > jdyson@nc.com > From owner-freebsd-hackers Thu Nov 20 18:41:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA03505 for hackers-outgoing; Thu, 20 Nov 1997 18:41:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA03497 for ; Thu, 20 Nov 1997 18:41:15 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id VAA00867; Thu, 20 Nov 1997 21:41:10 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711210241.VAA00867@dyson.iquest.net> Subject: Re: Nope, didn't fix it.Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: from Jaye Mathisen at "Nov 20, 97 05:05:49 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Thu, 20 Nov 1997 21:41:10 -0500 (EST) Cc: toor@dyson.iquest.net, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen said: > > OK, I handpatched the source, built a new kernel, and fired it up again. > > If anything, it's worse than before, hanging up within seconds of > rebooting. > Hmmmm... The original modification of the code was a mistake. getnewbuf is supposed to return if it blocks. > > I'm dropping back to the previous version for now, but this pretty well > kills 2.2.5 for me for usability. > Ouch! At least you have a plan B. > > I notice now that a lot of processes seem to be in vmwait, when they > didn't used to show it. > > Heck, I just had a la spike of 480. Machine kept running, but it was > unable to serve files for 2-3 minutes. > Whoa!!! Bring in the vm_page fix from RELENG_2_2 !!! It could be another manifestation of the page queue management bug!!! John From owner-freebsd-hackers Thu Nov 20 19:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA05129 for hackers-outgoing; Thu, 20 Nov 1997 19:05:19 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [204.152.114.165]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA05124 for ; Thu, 20 Nov 1997 19:05:16 -0800 (PST) (envelope-from lile@heathers2.stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.6.12/8.6.13) id WAA21469; Thu, 20 Nov 1997 22:03:10 -0500 Date: Thu, 20 Nov 1997 22:03:09 -0500 (EST) From: "Larry S. Lile" To: hackers@freebsd.org cc: ji@research.att.com Subject: Re: Problems mounting a cd-rom drive on 2.2_RELENG In-Reply-To: <199711202326.SAA02346@bual.research.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, that certainly explains the problems I have been seeing with my router and could explain what happened on my main machine. After I sup'd and rebuilt the cdrom drive started working correctly again. Thanks for the info :) I must have missed it in the Errata for 2.2.2 when I installed it. Thanks Larry On Thu, 20 Nov 1997, John Ioannidis wrote: > > anarchy: # mount /cdrom > > cd9660: /dev/cd0a: Invalid argument > > Looks like your kernel and your /sbin/mount_cd9660 are not happy with > each other. Make sure you run the mount program that goes with the > kernel you are running. If you are tracking FreeBSD-current, make sure > your mount_cd9660 is: > "$Id: mount_cd9660.c,v 1.7.2.1 1997/08/17 13:30:23 joerg Exp$"; > The mount program that comes with 2.2.2-RELEASE does not work. > > /ji From owner-freebsd-hackers Thu Nov 20 19:19:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06086 for hackers-outgoing; Thu, 20 Nov 1997 19:19:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06077 for ; Thu, 20 Nov 1997 19:18:56 -0800 (PST) (envelope-from koshy@india.hp.com) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id TAA25525 for ; Thu, 20 Nov 1997 19:18:49 -0800 (PST) Message-Id: <199711210318.TAA25525@palrel1.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA023221934; Fri, 21 Nov 1997 08:42:14 +0530 To: freebsd-hackers@freebsd.org Subject: References for page coloring algorithms? Date: Fri, 21 Nov 1997 08:42:13 +0530 From: A Joseph Koshy Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does any literature exist on the page coloring algorithm used in FreeBSD? If so, I'd appreciate it if someone could forward/post references. I didn't find any previous discussion on this topic in the archives. I came across the following ACM paper on page coloring for direct mapped caches, but the schemes described there are substantially different from the FreeBSD code: R. E. Kessler and Mark D. Hill, Page Placement Algorithms for Large Real-Indexed Caches, ACM TOCS, Vol. 10, No. 4, November 1992, pp. 338-359. Thanks, Koshy #include STD_DISCLAIMER From owner-freebsd-hackers Thu Nov 20 19:46:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA07660 for hackers-outgoing; Thu, 20 Nov 1997 19:46:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA07655 for ; Thu, 20 Nov 1997 19:45:55 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYjuG-0000K6-00; Thu, 20 Nov 1997 19:37:24 -0800 Date: Thu, 20 Nov 1997 19:37:22 -0800 (PST) From: Tom To: Chris Timmons cc: "John S. Dyson" , Jaye Mathisen , hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, Chris Timmons wrote: > > On around November 3, there was a thread here in -hackers of subject > "FreeBSD shines" that mentioned a semaphore benchmarking program: > > "If anyone wants the code (and results for other OSes) see > ftp://samba.anu.edu.au/pub/tridge/semspeed.c" > > Subsequent discussion pointed out that 2.2 was quite a bit faster than > 2.2.5. Maybe a look at semspeed.c will provide some suggestions about > where to look. I recall this comparison was only for semaphore operations, which no part of FreeBSD uses (only some apps use it), and the comparison was made between 2.2 and current, and current was found to be quite slow. Tom From owner-freebsd-hackers Thu Nov 20 19:46:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA07734 for hackers-outgoing; Thu, 20 Nov 1997 19:46:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA07718 for ; Thu, 20 Nov 1997 19:46:40 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYjw9-0000KC-00; Thu, 20 Nov 1997 19:39:21 -0800 Date: Thu, 20 Nov 1997 19:39:20 -0800 (PST) From: Tom To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711202155.QAA03288@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, John S. Dyson wrote: > Jaye Mathisen said: > > > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > > July. Did you move to 2.2.5-stable or just to 2.2.5-RELEASE? Several patches have gone into 2.2.5 since the release. Tom From owner-freebsd-hackers Thu Nov 20 19:48:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA07895 for hackers-outgoing; Thu, 20 Nov 1997 19:48:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA07868 for ; Thu, 20 Nov 1997 19:48:01 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id TAA15677; Thu, 20 Nov 1997 19:47:41 -0800 (PST) Date: Thu, 20 Nov 1997 19:47:41 -0800 (PST) From: Jaye Mathisen To: Tom cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am cvsup'd as of 11/17 if I remember correctly. On Thu, 20 Nov 1997, Tom wrote: > > On Thu, 20 Nov 1997, John S. Dyson wrote: > > > Jaye Mathisen said: > > > > > > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > > > July. > > Did you move to 2.2.5-stable or just to 2.2.5-RELEASE? Several patches > have gone into 2.2.5 since the release. > > Tom > From owner-freebsd-hackers Thu Nov 20 20:25:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10490 for hackers-outgoing; Thu, 20 Nov 1997 20:25:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10483 for ; Thu, 20 Nov 1997 20:24:56 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id XAA01323; Thu, 20 Nov 1997 23:23:36 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711210423.XAA01323@dyson.iquest.net> Subject: Re: References for page coloring algorithms? In-Reply-To: <199711210318.TAA25525@palrel1.hp.com> from A Joseph Koshy at "Nov 21, 97 08:42:13 am" To: koshy@india.hp.com (A Joseph Koshy) Date: Thu, 20 Nov 1997 23:23:36 -0500 (EST) Cc: freebsd-hackers@freebsd.org Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A Joseph Koshy said: > > Does any literature exist on the page coloring algorithm used in FreeBSD? > If so, I'd appreciate it if someone could forward/post references. I > didn't find any previous discussion on this topic in the archives. > > I came across the following ACM paper on page coloring for direct mapped > caches, but the schemes described there are substantially different from > the FreeBSD code: > > R. E. Kessler and Mark D. Hill, > Page Placement Algorithms for Large Real-Indexed Caches, > ACM TOCS, Vol. 10, No. 4, November 1992, pp. 338-359. > That is the primary document that spurred me on, to write the coloring code. Our coloring code is a scheme that does not cause additional paging (note that another paper that they came up with showed that coloring can cause additional paging, or less efficient memory utlization.) The algorithm is my invention, so there are no explicit references. If you want, I can send you a userland simulation for the method (I used it to demonstrate correctness, and debug the algorithm.) If you notice (by running lat_mem_rd from lmbench), our coloring algorithm is practically 100% effective. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Thu Nov 20 20:43:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA11402 for hackers-outgoing; Thu, 20 Nov 1997 20:43:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA11388; Thu, 20 Nov 1997 20:43:18 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA01447; Thu, 20 Nov 1997 20:43:45 -0800 (PST) To: "Jonathan M. Bresler" cc: handy@sag.space.lockheed.com (Brian N. Handy), sef@kithrup.com, hackers@FreeBSD.ORG Subject: Re: Mail spam, sigh... In-reply-to: Your message of "Thu, 20 Nov 1997 06:51:02 PST." <199711201451.GAA09181@hub.freebsd.org> Date: Thu, 20 Nov 1997 20:43:44 -0800 Message-ID: <1443.880087424@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > add /etc/mail/sendmail.cf.additions to your .mc or .cf file > kill -HUP `head -1 /var/run/sendmail.pid` > cd /etc/mail; make install It sure would be nice if this specific aspect of it were improved! Even a simple grep-and-patch rule in the Makefile would be an improvement (look for preexisting patch, apply patch if not found). Even better, of course, would be to use the appropriate M4 macros for this in generating a sendmail.cf to order. This is another thing we really need a "setup wizard" type tool for. :( Jordan From owner-freebsd-hackers Thu Nov 20 21:36:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14792 for hackers-outgoing; Thu, 20 Nov 1997 21:36:27 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14786 for ; Thu, 20 Nov 1997 21:36:23 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA01929; Thu, 20 Nov 1997 21:36:41 -0800 (PST) To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Thu, 20 Nov 1997 12:17:36 PST." Date: Thu, 20 Nov 1997 21:36:41 -0800 Message-ID: <1925.880090601@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > July. > > Big mistake. Perhaps, though if any clear mistakes were made here, it was in the transition process itself, it still remaining for me to be convinced that 2.2.5 itself is the culprit or I think I'd be hearing a lot more reports like this, especially from the 2.2.5 based web sites at some of the various ISPs I help maintain directly myself. The clear mistake was in hot-upgrading a production machine rather than installing/upgrading a 2nd box (or, at the very minimum, a second disk with / and /usr on it) and doing the cut-over as a staged exercise. Then if you'd seen the 2.2.5 problem here, you'd have simply switched back to the previous setup and given yourself the breathing room to puzzle over the new problem scenario at your leisure. Doing it the way you just did it is, frankly, about as completely and utterly wrong as it's possible to do things in an ISP environment and various protruding parts of you now need to be slapped, if you have someone around to provide this helpful service for you, so that you don't do something this criminally stupid in a production environment again. :-) As for your "weird pauses", that's the first I've heard of any such symptoms and would strongly recommend that you start trying to collect data during those pauses as to whether it's the interface, DNS, routes, what exactly "hangs" at the lowest level of this. Jordan From owner-freebsd-hackers Thu Nov 20 22:08:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16494 for hackers-outgoing; Thu, 20 Nov 1997 22:08:10 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16489 for ; Thu, 20 Nov 1997 22:08:07 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id WAA00970 for ; Thu, 20 Nov 1997 22:07:57 -0800 (PST) Date: Thu, 20 Nov 1997 22:07:57 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: GNATS completely broken. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I haven't been able to get any new send-prs posted for the last 2 days. From owner-freebsd-hackers Thu Nov 20 22:11:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16658 for hackers-outgoing; Thu, 20 Nov 1997 22:11:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16650 for ; Thu, 20 Nov 1997 22:11:31 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id BAA01289; Fri, 21 Nov 1997 01:11:30 -0500 (EST) (envelope-from henrich) Date: Fri, 21 Nov 1997 01:11:30 -0500 (EST) From: Charles Henrich Message-Id: <199711210611.BAA01289@crh.cl.msu.edu> To: jkh@time.cdrom.com, freebsd-hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE Newsgroups: lists.freebsd.hackers References: <65378m$5qr$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >The clear mistake was in hot-upgrading a production machine rather >than installing/upgrading a 2nd box (or, at the very minimum, a second >disk with / and /usr on it) and doing the cut-over as a staged >exercise. Then if you'd seen the 2.2.5 problem here, you'd have >simply switched back to the previous setup and given yourself the >breathing room to puzzle over the new problem scenario at your >leisure. Doing it the way you just did it is, frankly, about as >completely and utterly wrong as it's possible to do things in an ISP >environment and various protruding parts of you now need to be >slapped, if you have someone around to provide this helpful service >for you, so that you don't do something this criminally stupid in a >production environment again. :-) Now Now, not all of us have spare hardware to throw around, besides I've done this on my production news server twice now :) It started life as a 2.2 alpha snap, then a few months back I installed 2.2.2-RELEASE on top of it, and just a few weeks ago 2.2.5 on top of that. So far, everythings been running peachy keen. Granted if I jump major OS revs (3.0) a complete from scratch start is in the plans. Although granted, I dont mind putting myself in situations where I have to completely rebuild a system from scratch in an hour or so, a little pressure never hurt anyone :) >As for your "weird pauses", that's the first I've heard of any such >symptoms and would strongly recommend that you start trying to collect >data during those pauses as to whether it's the interface, DNS, >routes, what exactly "hangs" at the lowest level of this. Same here.. I've been running 2.2.5 (installed ontop of a live filesystem that started life as above) on my very heavily beat news server with zilcho problems. Its been rocking as a matter of fact. I swapped out the de0 card in it just the other day to try out a fxp0 to see if it made any difference (it didnt) but the machine is still humming along great transferring a little over a million articles a day across a 12 disk CCD array across 4 adaptec 2940 scsi controllers. This machine (ALR Revolution MP-Pro) / OS combination is the best I've ever had the pleasure of working on. Everytime I have to go do something under solaris I whine for weeks about it :) [Course right about now flames should erupt from the disks, and the CPU should blast through the front of the case :)] So my rant ends in, again FreeBSD (And by the transitive property, its developers) is the most reliable, high performance, easiest to play with, and funnest (yea its a word, cause I said so :) to play with! Thanks mucho! -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Thu Nov 20 23:06:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18769 for hackers-outgoing; Thu, 20 Nov 1997 23:06:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18759 for ; Thu, 20 Nov 1997 23:06:08 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id XAA01060 for ; Thu, 20 Nov 1997 23:05:57 -0800 (PST) Date: Thu, 20 Nov 1997 23:05:57 -0800 (PST) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: SCSI Errors & CCD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I purchased two 4.3 gig IBM External Scsi drives and want to use ccd to make them mirrors of each other. I would like to install from my 2.2.5 cds onto these drives. Is there a way to set it up to install onto mirrored drives at install time or can I do this later? I want to be able to boot off of these ccd drives. What does the following mean: It appeared when I was trying to install 2.2.5 on my external IBM 4.3gig Ultra SCSI. I am using a 2940 ultra, and are properly active terminated externally. The adapter is set to use ultra mode(20mhz?) on this device which is id0. This is the only device external, and the only device period (3' cable). sd0(ahc0:0:0): parity error during data-in phase sd0(ahc0:0:0): ABORTED COMMAND sd0(ahc0:0:0): Initiator Detected error message received, retries: 2 sometimes retries were 1-4 here is my dmesg: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.5-STABLE #0: Thu Nov 20 20:52:17 PST 1997 root@shellx.acroal.com:/usr/src/sys/compile/SHELLX CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 62496768 (61032K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 2 int a irq 11 on pci0:15 ahc0 rev 1 int a irq 9 on pci0:16 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "IBM DCAS-34330 S60B" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:40:05:3c:8e:0f, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface 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: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 3815MB (7814016 sectors), 7752 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, dma, iordis wcd0: 689Kb/sec, 112Kb cache, audio play, 127 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa DEVFS: ready to run IP packet filtering initialized, divert enabled, logging disabled From owner-freebsd-hackers Thu Nov 20 23:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19319 for hackers-outgoing; Thu, 20 Nov 1997 23:20:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19314 for ; Thu, 20 Nov 1997 23:20:39 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id XAA28632; Thu, 20 Nov 1997 23:20:28 -0800 (PST) Date: Thu, 20 Nov 1997 23:20:28 -0800 (PST) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <1925.880090601@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pulleeze... I've been running practically every release of 2.2.x on almost 30 servers on a more regular basis than probably anybody. This is the only machine having the problem, and it ran 2.2.2 just yippee skippee. The problem started 10 minutes after 2.2.5 went in, and I'm having a hard time believing that it could be anything else, when there's no other failure mode (like smoke, disk problems, ethernet interface problems, or anything else). I have restored part of the backups to get to a usable 2.2.2, and it boots and runs just fine. Given that John even points out that there are bugs in the vfs_bio code that weren't in 2.2.2, I find it hard not to point the finger a bit at 2.2.5. In any case, I will try the 2 patches I got and see what happens. It definitely appears load related. From owner-freebsd-hackers Fri Nov 21 00:20:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22607 for hackers-outgoing; Fri, 21 Nov 1997 00:20:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA22557 for ; Fri, 21 Nov 1997 00:19:55 -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 HAA27101; Fri, 21 Nov 1997 07:49:49 +0100 From: Luigi Rizzo Message-Id: <199711210649.HAA27101@labinfo.iet.unipi.it> Subject: Re: about VoxWare.. To: byung@wam.umd.edu (Byung Yang) Date: Fri, 21 Nov 1997 07:49:49 +0100 (MET) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199711202300.SAA09764@rac3.wam.umd.edu> from "Byung Yang" at Nov 20, 97 05:59:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am currently using FreeBSD 2.2.0 Release. In the kernel, I noticed that > VoxWare Sound Driver: 3.0-beta-950506 was supported. > Is there any recent version of this? I am using Turtle Beach TBS2000 > and it's not supported by this driver. CS4232 driver also works with this card. > Where can I find newer drivers? maybe you can try my new audio driver http://www.iet.unipi.it/~luigi/FreeBSD.html (i have no idea which chipset does the TBS2000 use... but it is worth a try). cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Nov 21 00:22:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22734 for hackers-outgoing; Fri, 21 Nov 1997 00:22:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA22727 for ; Fri, 21 Nov 1997 00:21:59 -0800 (PST) (envelope-from tony@dell.com) Received: from ant.us.dell.com (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA24111; Fri, 21 Nov 1997 02:20:50 -0600 Message-Id: <3.0.3.32.19971121022045.00760330@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Fri, 21 Nov 1997 02:20:45 -0600 To: Terry Lambert From: Tony Overfield Subject: Re: >64MB Cc: hackers@freebsd.org In-Reply-To: <199711191822.LAA14282@usr05.primenet.com> References: <3.0.3.32.19971118043753.0071582c@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: >> >2) The BIOS INT 13 code has a 2G limit on partition size, unless >> > you can guarantee all the devices in your machine support >> > LBA mode (even then the limit on LBA is lower than the limit >> > in FreeBSD... 64bits >> 32 bits). >> >> Second, the INT 13 interface (without LBA mode) is limited >> to 8.4 GB, not 2 GB. > >A DOS partition (assuming we use the DOS MBR and aren't idiots, we >are tied to the DOS partition table) is limited to C/H/S values. A C/H/S value is limited to 8.4 GB, not 2 GB. There is no INT 13 limit anywhere near 2 GB. Your claim that "The BIOS INT 13 code has a 2G limit on partition size" is wrong. I have created many partitions larger than 2 GB, as have many other people. >You have tha ability to map an 8G space with four descriptors. Yes, and you can also map an 8G space with two 4G "descriptors," or one 8G "descriptor," or even sixteen .5G "descriptors." DOS ordinarily creates a primary partition and an optional extended partition. The extended partition can contain an unlimited number of secondary partitions. No matter how many partitions you create in DOS, you'll only use two of the four top-level partition entries. >> Third, the limit for LBA INT 13 is 64-bits worth of sectors, or >> 2^73 bytes. This should last us for several more years. > >The LBA limit is irrelevant. You claimed that LBA was limited to 32 bits and that's wrong. Suddenly deeming it irrelevant doesn't change that. >It's not usable, so it might as well be fiction. No. LBA mode _is_ usable. I use it every day, without any problems. - Tony From owner-freebsd-hackers Fri Nov 21 00:22:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22773 for hackers-outgoing; Fri, 21 Nov 1997 00:22:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA22757 for ; Fri, 21 Nov 1997 00:22:07 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA21827 for hackers@FreeBSD.ORG; Fri, 21 Nov 1997 09:22:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id JAA05285; Fri, 21 Nov 1997 09:07:58 +0100 (MET) Message-ID: <19971121090758.JM01376@uriah.heep.sax.de> Date: Fri, 21 Nov 1997 09:07:58 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: vnode.h and IO_NDELAY (help!!) References: <19971120090611.FW37911@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: hackers@FreeBSD.ORG In-Reply-To: ; from Jamil J. Weatherbee on Nov 20, 1997 11:41:25 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jamil J. Weatherbee wrote: > > Also, don't forget that you need to allow the FIONBIO ioctl command. > > ... But about the > FIONBIO call, I don't see what you are saying. Why would I need to > support that, I thought that that would be intercepted at the vnode level? You need to ensure that the ioctl routine of your driver doesn't reject this ioctl command, i.e. it must not return ENOTTY or another error for it. Here's mine from the future rtc.c: static int rtcioctl(dev_t dev, int cmd, caddr_t data, int flag, struct proc *p) { int rv = 0; switch (cmd) { case FIONBIO: break; default: rv = ENOTTY; } return rv; } -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Nov 21 00:38:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23457 for hackers-outgoing; Fri, 21 Nov 1997 00:38:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23439 for ; Fri, 21 Nov 1997 00:38:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA03061; Fri, 21 Nov 1997 00:38:26 -0800 (PST) To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Fri, 21 Nov 1997 01:11:30 EST." <199711210611.BAA01289@crh.cl.msu.edu> Date: Fri, 21 Nov 1997 00:38:25 -0800 Message-ID: <3057.880101505@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Now Now, not all of us have spare hardware to throw around, besides I've done Well, now hang on a second.. If you're going to be an ISP, at least one who takes himself and his services halfway seriously, then surely cost of an extra PC (or, as I noted, even just an extra *disk*) is going to pale in comparison to the cost of inflicting instability on your user base. I also wasn't really intending on beating up on Jaye, though it might have seemed like I did, so much as his statements accompanying the bug report which noted that he was going to have potentially hundreds of web customers and such going away as a result of the failed upgrade and, well, that just stuck in my craw as one of those "doctor, doctor, it hurts when I do *this*" sort of bug reports which indicated a far more serious degree of dysfunction elsewhere. > this on my production news server twice now :) It started life as a 2.2 alph a > snap, then a few months back I installed 2.2.2-RELEASE on top of it, and just > a few weeks ago 2.2.5 on top of that. So far, everythings been running peach y > keen. Granted if I jump major OS revs (3.0) a complete from scratch start is And if that's the case then you're one of the lucky ones. Does that make it excusable as a general operating principle? No. :-) > So my rant ends in, again FreeBSD (And by the transitive property, its > developers) is the most reliable, high performance, easiest to play with, and > funnest (yea its a word, cause I said so :) to play with! Thanks mucho! Well, thanks. Still, don't you think we should be trying to set a proper example for all those ISPs wandering around lost in the woods out there? ;) Jordan From owner-freebsd-hackers Fri Nov 21 00:40:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23555 for hackers-outgoing; Fri, 21 Nov 1997 00:40:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from localhost.umd.edu (root@annex12-3.dial.umd.edu [128.8.23.147]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23549 for ; Fri, 21 Nov 1997 00:39:56 -0800 (PST) (envelope-from byung@wam.umd.edu) Received: from localhost (byung@localhost) by localhost.umd.edu (8.8.5/8.8.5) with SMTP id DAA10596; Fri, 21 Nov 1997 03:02:45 -0500 (EST) X-Authentication-Warning: localhost.umd.edu: byung owned process doing -bs Date: Fri, 21 Nov 1997 03:02:43 -0500 (EST) From: Byung Yang X-Sender: byung@localhost To: Luigi Rizzo cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: about VoxWare. In-Reply-To: <199711210649.HAA27101@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk TBS2000 uses CS4232 chiset.. and I am sure your driver would work. Thank you for the info and the driver! :-) ------- Byung ------- > maybe you can try my new audio driver > > http://www.iet.unipi.it/~luigi/FreeBSD.html > > (i have no idea which chipset does the TBS2000 use... but it is worth a > try). > > cheers > luigi > > -----------------------------+-------------------------------------- > Luigi Rizzo | Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it | Universita' di Pisa > tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ > _____________________________|______________________________________ > > From owner-freebsd-hackers Fri Nov 21 01:11:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25532 for hackers-outgoing; Fri, 21 Nov 1997 01:11:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25527 for ; Fri, 21 Nov 1997 01:11:12 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA03375; Fri, 21 Nov 1997 01:11:31 -0800 (PST) To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Thu, 20 Nov 1997 23:20:28 PST." Date: Fri, 21 Nov 1997 01:11:30 -0800 Message-ID: <3371.880103490@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Pulleeze... > > I've been running practically every release of 2.2.x on almost 30 servers > on a more regular basis than probably anybody. Man 1: "Uh, I really hate to be a wuss about this, but it's raining heavily, those black thunderclouds look a little menacing and I've seen the tree in our front yard struck three times by lighting in the last 10 minutes. Are you *sure* we ought to be mounting this television antenna on the roof right now? It seems somewhat... imprudent..." Man 2: "Nonsense! Why, I've put up more television antennas during severe storms than practically anybody!" :-) Jordan From owner-freebsd-hackers Fri Nov 21 01:27:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA26435 for hackers-outgoing; Fri, 21 Nov 1997 01:27:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from meowy.angio.net (meowy.angio.net [206.197.119.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA26430 for ; Fri, 21 Nov 1997 01:27:41 -0800 (PST) (envelope-from angio@meowy.angio.net) Received: from meowy.angio.net (localhost.angio.net [127.0.0.1]) by meowy.angio.net (8.8.8/8.7.3) with ESMTP id CAA01468; Fri, 21 Nov 1997 02:25:18 -0700 (MST) Message-Id: <199711210925.CAA01468@meowy.angio.net> To: "Daniel Sobral" cc: hackers@freebsd.org Subject: Re: Virtual Intel Machines? In-reply-to: Your message of "Thu, 20 Nov 1997 08:33:18 -0300." <03256555.003F5208.00@papagaio.voga.com.br> Date: Fri, 21 Nov 1997 02:25:18 -0700 From: Dave Andersen Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: "Daniel Sobral" > > Of course, given that Intel chips work the way they do, it sounds > > like it'd be pretty much impossible to do what I was hoping for. > > Sigh. It was such a cool idea, too. > > Err, maybe. That depends on _what_ you want. See the FLUX/FLUKE project, > for instance. They run virtual machines, but not like the old vm machines. > And work over Intel. There are, however, some big differences between the "VM" provided by Fluke and the the VMs provided by machines like the IBM VM/370 (and between full virtual machine simulators). The major difference is that traditional virtual machine simulators of either flavor provide the operating system with what appears to it to be a direct hardware interface. In contrast, Fluke provides a set of low-level access routines that differ widely from the underlying hardware. The idea behind the recursive virtual machine support in Fluke is to provide an efficient mechanism for supporting relatively deep nested virtual machine hierarchies, _not_ to provide an environment where an operating system can run, unmodified, alongside another complete and unmodified operating system. (This is what the original poster was inquiring about). -Dave From owner-freebsd-hackers Fri Nov 21 02:40:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA29980 for hackers-outgoing; Fri, 21 Nov 1997 02:40:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA29967 for ; Fri, 21 Nov 1997 02:40:24 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id HAA02574; Fri, 21 Nov 1997 07:39:17 -0300 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256556.003A8597 ; Fri, 21 Nov 1997 07:39:12 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: angio@angio.net cc: hackers@freebsd.org Message-ID: <03256556.003A7018.00@papagaio.voga.com.br> Date: Fri, 21 Nov 1997 07:39:09 -0300 Subject: Re: Virtual Intel Machines? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > There are, however, some big differences between the "VM" provided > by Fluke and the the VMs provided by machines like the IBM VM/370 (and [etc] Yeah, I am aware of that. That's the reason I said "that depends on what you want". From owner-freebsd-hackers Fri Nov 21 04:39:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA04573 for hackers-outgoing; Fri, 21 Nov 1997 04:39:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA04568 for ; Fri, 21 Nov 1997 04:39:02 -0800 (PST) (envelope-from Daniel_Sobral@voga.com.br) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id JAA02160 for ; Fri, 21 Nov 1997 09:38:26 -0300 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256556.00456C1E ; Fri, 21 Nov 1997 09:38:16 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: hackers@freebsd.org Message-ID: <03256556.0044E942.00@papagaio.voga.com.br> Date: Fri, 21 Nov 1997 09:38:10 -0300 Subject: Artificial Life Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk First, this subject does not seem to belong to this list. Second, I had a link to the most famous Artificial Life work, but I lost it. I recall it used Unix, though, so it is probably relatively easy to port. I think this question can be found on comp.ai, and certainly the nice people at comp.ai.alife can help you... :-) From owner-freebsd-hackers Fri Nov 21 05:32:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA07458 for hackers-outgoing; Fri, 21 Nov 1997 05:32:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07452 for ; Fri, 21 Nov 1997 05:32:33 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA06157; Fri, 21 Nov 1997 13:32:28 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id OAA03173; Fri, 21 Nov 1997 14:32:26 +0100 (MET) Date: Fri, 21 Nov 1997 14:32:26 +0100 (MET) Message-Id: <199711211332.OAA03173@bitbox.follo.net> From: Eivind Eklund To: Jaye Mathisen CC: hackers@FreeBSD.ORG In-reply-to: Jaye Mathisen's message of Thu, 20 Nov 1997 12:17:36 -0800 (PST) Subject: Re: Serious performance issue with 2.2.5-RELEASE References: Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > July. > > Big mistake. > > The only update to take place was the make buildworld, make installworld, > no other configuration files were modified, nor any changes to startup > scripts, etc. > > I now get these weird pauses where everything on the machine just freezes > for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > The system was a web server, and was happily serving up several hundred > domains. Now with the upgrade, I'll be lucky to keep them. Not good. You've not had any problems with 2.2.2? We've been having problems with 4-5 seconds random hangs on our 2.2.2 webservers, which seems to occur mostly on static pages. I've not been able to find any clear pattern to when this happens; it is completely random, and seems to have be less often lately (but still happens in 1 of 100 cases or so). A previous comment to -hackers on this didn't given any reply, so it doesn't seem to be a common problem - but the problems are present on a lot of different machines, with almost all-different hardware (I think all of them have 2940s - but they don't emit any warning/error messages from the drivers). I have not been able to reproduce any delays in ssh or terminal modes on the same machines. Eivind. From owner-freebsd-hackers Fri Nov 21 06:20:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10663 for hackers-outgoing; Fri, 21 Nov 1997 06:20:10 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from eh.est.is (root@eh.est.is [194.144.208.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10651 for ; Fri, 21 Nov 1997 06:20:03 -0800 (PST) (envelope-from totii@est.is) Received: from didda.est.is (ppp-43.est.is [194.144.208.143]) by eh.est.is (8.8.5/8.8.7) with SMTP id OAA18646 for ; Fri, 21 Nov 1997 14:19:36 GMT (envelope-from totii@est.is) Message-ID: <34759882.41C67EA6@est.is> Date: Fri, 21 Nov 1997 14:19:46 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: syscons keyboard mapping 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 GAA10655 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been checking if there is possibility for 'dead key' in keyboard mapping of syscons. Icelandic has several characters with 'acute' on top and we enter the character by hitting 'dead acute' key and then the character that takes the 'acute'. I have already made keymap for syscons but without the ascended characters and also modified keymap file for XFree86 where the 'dead key' works exept in Netscape for BSDI 3.01, StarOffice for Linux 3.1, WordPerfect for Linux V7.0. For Me this is a kind of must, having the keyboard working both in X and syscons! -- Þórður Ívarsson Thordur Ivarsson Rafeindavirki Electronic technician Norðurgötu 30 Nordurgotu 30 Box 309 Box 309 602 Akureyri 602 Akureyri Ísland Iceland --------------------------------------------- FreeBSD has good features, Some others are full of unwanted features! --------------------------------------------- From owner-freebsd-hackers Fri Nov 21 07:24:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14466 for hackers-outgoing; Fri, 21 Nov 1997 07:24:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA14461 for ; Fri, 21 Nov 1997 07:24:34 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin2.anlw.anl.gov [141.221.254.102]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id IAA27957; Fri, 21 Nov 1997 08:24:30 -0700 Date: Fri, 21 Nov 1997 08:23:58 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Eivind Eklund cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711211332.OAA03173@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You've not had any problems with 2.2.2? We've been having problems > with 4-5 seconds random hangs on our 2.2.2 webservers, which seems to > occur mostly on static pages. If you're using the apache web server, it has some fairly elaborate pre-forking and process control. I wouldn't be entirely surprised to see it have delays if it were near the fork limit or that the number of spare processes waiting for requests is not large enough. Charles Mott From owner-freebsd-hackers Fri Nov 21 07:27:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14605 for hackers-outgoing; Fri, 21 Nov 1997 07:27:43 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14599 for ; Fri, 21 Nov 1997 07:27:33 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id PAA08127; Fri, 21 Nov 1997 15:27:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id QAA05098; Fri, 21 Nov 1997 16:27:18 +0100 (MET) Message-ID: <19971121162718.13505@bitbox.follo.net> Date: Fri, 21 Nov 1997 16:27:18 +0100 From: Eivind Eklund To: Charles Mott Cc: Eivind Eklund , hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE References: <199711211332.OAA03173@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from Charles Mott on Fri, Nov 21, 1997 at 08:23:58AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Nov 21, 1997 at 08:23:58AM -0700, Charles Mott wrote: > > You've not had any problems with 2.2.2? We've been having problems > > with 4-5 seconds random hangs on our 2.2.2 webservers, which seems to > > occur mostly on static pages. > > If you're using the apache web server, it has some fairly elaborate > pre-forking and process control. I wouldn't be entirely surprised to see > it have delays if it were near the fork limit or that the number of spare > processes waiting for requests is not large enough. Yes, it is with apache. It is running with no limits, and with MAXUSERS=100 (up from 10, which had the same problems). The same Apache config (exactly) under 2.1-STABLE showed no problems :-( Eivind. From owner-freebsd-hackers Fri Nov 21 08:03:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA17189 for hackers-outgoing; Fri, 21 Nov 1997 08:03:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA17182 for ; Fri, 21 Nov 1997 08:03:19 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin2.anlw.anl.gov [141.221.254.102]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id JAA28104; Fri, 21 Nov 1997 09:03:12 -0700 Date: Fri, 21 Nov 1997 09:02:39 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Eivind Eklund cc: Eivind Eklund , hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <19971121162718.13505@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Eivind Eklund wrote: > On Fri, Nov 21, 1997 at 08:23:58AM -0700, Charles Mott wrote: > > > You've not had any problems with 2.2.2? We've been having problems > > > with 4-5 seconds random hangs on our 2.2.2 webservers, which seems to > > > occur mostly on static pages. > > > > If you're using the apache web server, it has some fairly elaborate > > pre-forking and process control. I wouldn't be entirely surprised to see > > it have delays if it were near the fork limit or that the number of spare > > processes waiting for requests is not large enough. > > Yes, it is with apache. It is running with no limits, and with > MAXUSERS=100 (up from 10, which had the same problems). The same > Apache config (exactly) under 2.1-STABLE showed no problems :-( > If MinSpareServers is not large enough, there can be a one second delay in creating new processes, but this does not explain the 4-5 second delay you are experiencing. So I think you are seeing something interesting here. One thing to do is to put some debug lines in http_main.c, to see where it might be hanging up. I see three possible areas: (1) hangup at select(), (2) hangup due to advisory locking, or (3) new processes cannot be forked rapidly enough. [Note: I am not an expert in Apache and have no personal use for it, but I have been looking at the code to create a generic, semi-object oriented (C not C++) process management module. I'll e-mail it to anyone who is interested.] -- Charles Mott From owner-freebsd-hackers Fri Nov 21 08:22:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18484 for hackers-outgoing; Fri, 21 Nov 1997 08:22:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from kaiwan009.kaiwan.com (0@kaiwan009.kaiwan.com [198.178.203.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18451 for ; Fri, 21 Nov 1997 08:22:25 -0800 (PST) (envelope-from frank@exit.com) Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.8.8/8.8.8) with UUCP id HAA05105; Fri, 21 Nov 1997 07:51:22 -0800 (PST) Received: (from frank@localhost) by exit.com (8.8.7/8.7.3) id HAA00291; Fri, 21 Nov 1997 07:38:40 -0800 (PST) From: Frank Mayhar Message-Id: <199711211538.HAA00291@exit.com> Subject: Re: MFS /tmp oddness To: brianc@pobox.com (Brian Campbell) Date: Fri, 21 Nov 1997 07:38:39 -0800 (PST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19971119190117.04396@pobox.com> from Brian Campbell at "Nov 19, 97 07:01:17 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Campbell wrote: > On Wed, Nov 19, 1997 at 06:42:07PM -0500, John S. Dyson wrote: > > Aaron Smith said: > > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > > > option too but that didn't work either. > > This is in my fstab and works. (note that the -b=16384,-f=2048 options > > are eccentric, but this is copied directly.) > > swap /tmp mfs rw,-s=210000,-b=16384,-f=2048 0 0 > Did you have to modify login.conf (or something else) to make this work? > Mine specfies -s262000 but only manages to get 32M This is another metoo. I see exactly the same thing, with a specified size of 196608. I haven't yet tried changing the block and frag size to match John's; I'll do that today. -- Frank Mayhar frank@exit.com From owner-freebsd-hackers Fri Nov 21 08:52:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20747 for hackers-outgoing; Fri, 21 Nov 1997 08:52:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA20741 for ; Fri, 21 Nov 1997 08:52:23 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xYwBL-0000hh-00; Fri, 21 Nov 1997 08:43:51 -0800 Date: Fri, 21 Nov 1997 08:43:49 -0800 (PST) From: Tom To: "Jamil J. Weatherbee" cc: hackers@freebsd.org Subject: Re: SCSI Errors & CCD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, Jamil J. Weatherbee wrote: > I purchased two 4.3 gig IBM External Scsi drives and want to use ccd to > make them mirrors of each other. I would like to install from my 2.2.5 > cds onto these drives. Is there a way to set it up to install onto > mirrored drives at install time or can I do this later? > > I want to be able to boot off of these ccd drives. You can't boot off a ccd filesystem, as the BIOS doesn't know anything about ccd. You have to have a non-ccd root. > What does the following mean: > sd0(ahc0:0:0): parity error during data-in phase > sd0(ahc0:0:0): ABORTED COMMAND > sd0(ahc0:0:0): Initiator Detected error message received, retries: 2 SCSI uses parity on the bus. Apparently you suffered an error. That means that something on the cable is damaging your data. Replace cable, terminators, etc. Tom From owner-freebsd-hackers Fri Nov 21 09:00:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21566 for hackers-outgoing; Fri, 21 Nov 1997 09:00:55 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from super.zippo.com (perry.zippo.com [207.211.168.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21553 for ; Fri, 21 Nov 1997 09:00:50 -0800 (PST) (envelope-from reyesf@super.zippo.com) Received: (from reyesf@localhost) by super.zippo.com (8.8.6/8.8.7) id JAA17886; Fri, 21 Nov 1997 09:00:49 -0800 (PST) Message-Id: <199711211700.JAA17886@super.zippo.com> From: "Francisco Reyes" To: "hackers@FreeBSD.ORG" Date: Fri, 21 Nov 97 12:02:16 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.9 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Where sources for chpass? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I was looking for the sources for chpass and could not find them. During installation I said to include several group of sources (/usr/src/bin, /usr/src/sbin, etc..). Perhaps I missed one? How do I go about getting the sources for chpass? What is the easiest way to search for sources? Is there are relation between the location of the executable and the location of the sources? Looking at /usr/src/bin and /usr/src/sbin seemed like there are many sources missing from what I installed. From owner-freebsd-hackers Fri Nov 21 09:06:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21946 for hackers-outgoing; Fri, 21 Nov 1997 09:06:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from super.zippo.com (perry.zippo.com [207.211.168.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21940 for ; Fri, 21 Nov 1997 09:06:35 -0800 (PST) (envelope-from reyesf@super.zippo.com) Received: (from reyesf@localhost) by super.zippo.com (8.8.6/8.8.7) id JAA18286; Fri, 21 Nov 1997 09:06:34 -0800 (PST) Message-Id: <199711211706.JAA18286@super.zippo.com> From: "Francisco Reyes" To: "hackers@FreeBSD.ORG" Date: Fri, 21 Nov 97 12:08:01 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.9 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Is there a FreeBSD benchmark program? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I recently saw a message about someone upgrading from 2.2-stable to 2.2.5 and having serious performance degratation. I was wondering if there was any benchmark program for FreeBSD. This may help both users and kernel developers on checking whether a new kernel or configuration is better. From owner-freebsd-hackers Fri Nov 21 09:13:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22569 for hackers-outgoing; Fri, 21 Nov 1997 09:13:54 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22558 for ; Fri, 21 Nov 1997 09:13:47 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA27840; Fri, 21 Nov 1997 10:13:37 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA14398; Fri, 21 Nov 1997 10:13:34 -0700 Date: Fri, 21 Nov 1997 10:13:34 -0700 Message-Id: <199711211713.KAA14398@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Charles Henrich , freebsd-hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <3057.880101505@time.cdrom.com> References: <199711210611.BAA01289@crh.cl.msu.edu> <3057.880101505@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Now Now, not all of us have spare hardware to throw around, besides I've done > > Well, now hang on a second.. If you're going to be an ISP, at least > one who takes himself and his services halfway seriously, then surely > cost of an extra PC (or, as I noted, even just an extra *disk*) is > going to pale in comparison to the cost of inflicting instability > on your user base. In defense of Jaye, let's say he did bring in a spare PC, loaded it up with 2.2.5 and it worked fine in his 'fake' load environment. But, when he moved it into 'real' production use, it started seeing those kinds of problems. Would his problem be taken more seriously then? (He does seem to imply that it's load related, and as we all know it's difficult to simulate real-world load conditions everywhere except the real world.) Nate From owner-freebsd-hackers Fri Nov 21 09:15:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22785 for hackers-outgoing; Fri, 21 Nov 1997 09:15:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22779 for ; Fri, 21 Nov 1997 09:15:48 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id MAA03841; Fri, 21 Nov 1997 12:15:45 -0500 (EST) (envelope-from henrich) Message-ID: <19971121121545.44119@crh.cl.msu.edu> Date: Fri, 21 Nov 1997 12:15:45 -0500 From: Charles Henrich To: Nate Williams Cc: "Jordan K. Hubbard" , freebsd-hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE References: <199711210611.BAA01289@crh.cl.msu.edu> <3057.880101505@time.cdrom.com> <199711211713.KAA14398@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199711211713.KAA14398@mt.sri.com>; from Nate Williams on Fri, Nov 21, 1997 at 10:13:34AM -0700 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: Serious performance issue with 2.2.5-RELEASE, Nate Williams stated: > > > Now Now, not all of us have spare hardware to throw around, besides I've > > > done > > > > Well, now hang on a second.. If you're going to be an ISP, at least one > > who takes himself and his services halfway seriously, then surely cost of > > an extra PC (or, as I noted, even just an extra *disk*) is going to pale > > in comparison to the cost of inflicting instability on your user base. > > In defense of Jaye, let's say he did bring in a spare PC, loaded it up with > 2.2.5 and it worked fine in his 'fake' load environment. But, when he moved > it into 'real' production use, it started seeing those kinds of problems. > Would his problem be taken more seriously then? > > (He does seem to imply that it's load related, and as we all know it's > difficult to simulate real-world load conditions everywhere except the real > world.) Thats definatly true. Ideally I dont believe in upgrades, so a fresh install, fresh rebuild of everything, and fresh redeploy of everything is the best way to go. Im willing to do this under extreme duress (i.e. its all broken) but since I've hot-upgraded same major releases of FreeBSD dozens of times, and its never once failed.. Well, its worth the risk to me to save all that time. It is odd that his 2.2.5 system is behaving badly, when others seem to be going well. Perhaps its NFS related? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Nov 21 09:24:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA23652 for hackers-outgoing; Fri, 21 Nov 1997 09:24:46 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA23639 for ; Fri, 21 Nov 1997 09:24:36 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id MAA03923; Fri, 21 Nov 1997 12:24:32 -0500 (EST) (envelope-from henrich) Message-ID: <19971121122431.30389@crh.cl.msu.edu> Date: Fri, 21 Nov 1997 12:24:31 -0500 From: Charles Henrich To: "Jordan K. Hubbard" Cc: freebsd-hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE References: <199711210611.BAA01289@crh.cl.msu.edu> <3057.880101505@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <3057.880101505@time.cdrom.com>; from Jordan K. Hubbard on Fri, Nov 21, 1997 at 12:38:25AM -0800 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: Serious performance issue with 2.2.5-RELEASE, Jordan K. Hubbard stated: > Well, now hang on a second.. If you're going to be an ISP, at least one who > takes himself and his services halfway seriously, then surely cost of an > extra PC (or, as I noted, even just an extra *disk*) is going to pale in > comparison to the cost of inflicting instability on your user base. Well, that depends really. The cost of an extra PC in this case is an ALR Dual Revolution MP-Pro system, which if I just mirror the system is going to cost around $10k. I can rebuild the entire system in an hour when neccesary. It does depend on the function of the system, of course. If its an access authorization machine you have a much more critical system than say a news server. > stuck in my craw as one of those "doctor, doctor, it hurts when I do *this*" > sort of bug reports which indicated a far more serious degree of dysfunction > elsewhere. I understand that. Hot-Upgrading (by which I mean doing a complete OS install on top of my filesystem after booting from the install floppy) can cause strange problems that cease to exist if you clean upgrade... I havent run into a problem doing this with FreeBSD yet however.. Actually, if you want to be really frightened, I've upgraded entire operating systems from 2.1 to 2.1.7 including kernel while the system was running live (using sup), a quick reboot and we're now on 2.1.7 and it worked wonderfully well. Scary stuff maynard :) > And if that's the case then you're one of the lucky ones. Does that make it > excusable as a general operating principle? No. :-) Well, as long as when you do it you accept the fact that (and have the ability to) 1) It may break completely 2) You will have to rebuild from scratch in a very short time > Well, thanks. Still, don't you think we should be trying to set a proper > example for all those ISPs wandering around lost in the woods out there? ;) Maybe, maybe we should call this Extreme-Computing :) For me it always comes down to the critical nature of the system. If my entire business ceases because this system is down, I'll take an entirely different approach, than if a user cant read news for a few hours.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Nov 21 10:23:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28447 for hackers-outgoing; Fri, 21 Nov 1997 10:23:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28431 for ; Fri, 21 Nov 1997 10:22:54 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id NAA14703; Fri, 21 Nov 1997 13:23:22 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Fri, 21 Nov 1997 13:23:22 -0500 (EST) From: "David E. Cross" To: Francisco Reyes cc: "hackers@FreeBSD.ORG" Subject: Re: Is there a FreeBSD benchmark program? In-Reply-To: <199711211706.JAA18286@super.zippo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Francisco Reyes wrote: > I recently saw a message about someone upgrading from 2.2-stable to > 2.2.5 and having serious performance degratation. I was wondering if > there was any benchmark program for FreeBSD. This may help both users > and kernel developers on checking whether a new kernel or > configuration is better. /usr/ports/benchmarks -- David Cross From owner-freebsd-hackers Fri Nov 21 10:58:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01702 for hackers-outgoing; Fri, 21 Nov 1997 10:58:51 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA01692; Fri, 21 Nov 1997 10:58:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA22399 (5.67b/IDA-1.5); Fri, 21 Nov 1997 19:58:21 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id TAA02838; Fri, 21 Nov 1997 19:36:35 +0100 (MET) From: Wilko Bulte Message-Id: <199711211836.TAA02838@yedi.iaf.nl> Subject: Re: need an Alpha-based machine To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Fri, 21 Nov 1997 19:36:35 +0100 (MET) Cc: tlambert@primenet.com, sprice@hiwaay.net, alpha@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199711202317.AAA06703@yedi.iaf.nl> from "Wilko Bulte" at Nov 21, 97 00:17:10 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wilko Bulte wrote... > As Terry Lambert wrote... > > > > > Does anybody out there in FreeBSD-land have a spare > > > Alpha-based machine that they would be willing to > > > loan/sell? > > > > > > I want to contribute to getting the FreeBSD Alpha > > > > I'm using a Multia, and not the "official" porting platform (there > > is no documentation for the "official" platform). > > > > You can obtain a Multia rather cheaply from www.onsale.com, if you > > are willing to wait for the interest to wane (it gets bumped by > > postings like this one -- might as well not compete with other > > FreeBSD'ers. ;-)). > > You can also look at the PC64 boards, they sell here in Holland Eh, AXPpci33 that is... > for US$ 175. See www.request.nl This mainboard, while not a speed > daemon of any magnitude, at least holds a couple of PCI exp. > cards. The Multia is limited to one short PCI slot. _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix --Yoda From owner-freebsd-hackers Fri Nov 21 11:20:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03533 for hackers-outgoing; Fri, 21 Nov 1997 11:20:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from europa.com (root@thetics.europa.com [199.2.194.14]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA03524 for ; Fri, 21 Nov 1997 11:20:31 -0800 (PST) (envelope-from digitalmechanix.com!jimmy@europa.com) Received: from localhost (1030 bytes) by europa.com via rmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Fri, 21 Nov 1997 11:20:28 -0800 (PST) (Smail-3.2.0.98 1997-Oct-16 #2 built 1997-Oct-19) Received: from spot.digitalmechanix.com (spot.digitalmechanix.com [195.200.100.12]) by james.digitalmechanix.com (8.8.5/8.8.5) with SMTP id LAA02837 for ; Fri, 21 Nov 1997 11:20:48 -0800 (PST) Received: by spot.digitalmechanix.com with Microsoft Mail id <01BCF66F.7B626520@spot.digitalmechanix.com>; Fri, 21 Nov 1997 11:20:33 -0800 Message-ID: <01BCF66F.7B626520@spot.digitalmechanix.com> From: "James D. Fowler" To: "'freebsd-hackers@freebsd.org'" Subject: pnp Date: Fri, 21 Nov 1997 11:20:31 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there anything out there for enabling pnp on FreeBSD 2.2.1. I have a Boca modem that I would like to use. Thanks, Jim James D. Fowler Digital Mechanix 8937 N. Westanna #6 Portland Or. 97203 503.285.6843 From owner-freebsd-hackers Fri Nov 21 11:37:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA04954 for hackers-outgoing; Fri, 21 Nov 1997 11:37:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA04946 for ; Fri, 21 Nov 1997 11:37:30 -0800 (PST) (envelope-from cbray@best.com) Received: from curtis.creativedesign.com (host117.creativedesign.com [207.135.94.117]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id LAA01946; Fri, 21 Nov 1997 11:35:49 -0800 (PST) Message-ID: <3475E143.EE7AF250@best.com> Date: Fri, 21 Nov 1997 11:30:12 -0800 From: Curtis Bray Reply-To: cbray@best.com X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: malloc() problems in children after using rfork() X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm trying to use rfork(RFPROC | RFMEM) so that all the children can share the same address space with their parent. If I have multiple children issuing mallocs the children seem to core dump. Once I turn the RFMEM flag off I have no problem mallocing (but of course I loose the shared address space). Anyone know what I could be doing wrong here? Do I have to put semaphores around every malloc?? I hope that's not the case... Thanks in advance! Curtis From owner-freebsd-hackers Fri Nov 21 11:39:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05106 for hackers-outgoing; Fri, 21 Nov 1997 11:39:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05097 for ; Fri, 21 Nov 1997 11:39:12 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA06265; Fri, 21 Nov 1997 13:47:39 -0500 (EST) Date: Fri, 21 Nov 1997 13:47:38 -0500 (EST) From: Snob Art Genre To: Francisco Reyes cc: "hackers@FreeBSD.ORG" Subject: Re: Where sources for chpass? In-Reply-To: <199711211700.JAA17886@super.zippo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Did you try "locate chpass.c"? I just did, and got "/usr/src/usr.bin/chpass/chpass.c" as output. On Fri, 21 Nov 1997, Francisco Reyes wrote: > I was looking for the sources for chpass and could not find them. > During installation I said to include several group of sources > (/usr/src/bin, /usr/src/sbin, etc..). Perhaps I missed one? How do I > go about getting the sources for chpass? > > What is the easiest way to search for sources? Is there are relation > between the location of the executable and the location of the > sources? Looking at /usr/src/bin and /usr/src/sbin seemed like there > are many sources missing from what I installed. > > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Fri Nov 21 11:47:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05725 for hackers-outgoing; Fri, 21 Nov 1997 11:47:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05713 for ; Fri, 21 Nov 1997 11:47:09 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA19663; Fri, 21 Nov 1997 11:47:31 -0800 (PST) To: Nate Williams cc: Charles Henrich , freebsd-hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Fri, 21 Nov 1997 10:13:34 MST." <199711211713.KAA14398@mt.sri.com> Date: Fri, 21 Nov 1997 11:47:30 -0800 Message-ID: <19659.880141650@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In defense of Jaye, let's say he did bring in a spare PC, loaded it up > with 2.2.5 and it worked fine in his 'fake' load environment. But, when > he moved it into 'real' production use, it started seeing those kinds of > problems. Would his problem be taken more seriously then? His problem would be taken seriously in either case, but in the 2nd scenario we'd also have time to investigate it without having to listen to his dire predictions of impending business failure at the same time. :-) I understand that some problems don't show up until you load test, but at the same time you need to be able to service your customers on whatever platform *worked* last while you go back to the drawing board, so to speak, and try to figure out why your migration failed. Jordan From owner-freebsd-hackers Fri Nov 21 11:54:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06277 for hackers-outgoing; Fri, 21 Nov 1997 11:54:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06268 for ; Fri, 21 Nov 1997 11:54:12 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA19722; Fri, 21 Nov 1997 11:54:35 -0800 (PST) To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Fri, 21 Nov 1997 12:24:31 EST." <19971121122431.30389@crh.cl.msu.edu> Date: Fri, 21 Nov 1997 11:54:35 -0800 Message-ID: <19718.880142075@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, that depends really. The cost of an extra PC in this case is an ALR > Dual Revolution MP-Pro system, which if I just mirror the system is going to Well, as I've said 3 times now, if you can't afford a whole 'nother box, then at least buy another disk for / and /usr so that you can still switch back to the previous OS version in 10 minutes or less. Are you going to argue that *this* cost is too onerous to bear for an ISP? :) Jordan From owner-freebsd-hackers Fri Nov 21 11:57:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06603 for hackers-outgoing; Fri, 21 Nov 1997 11:57:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06588 for ; Fri, 21 Nov 1997 11:57:47 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id OAA00475; Fri, 21 Nov 1997 14:57:39 -0500 (EST) (envelope-from henrich) Message-ID: <19971121145739.63336@crh.cl.msu.edu> Date: Fri, 21 Nov 1997 14:57:39 -0500 From: Charles Henrich To: "Jordan K. Hubbard" Cc: freebsd-hackers@freebsd.org Subject: Re: Serious performance issue with 2.2.5-RELEASE References: <19971121122431.30389@crh.cl.msu.edu> <19718.880142075@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19718.880142075@time.cdrom.com>; from Jordan K. Hubbard on Fri, Nov 21, 1997 at 11:54:35AM -0800 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: Serious performance issue with 2.2.5-RELEASE, Jordan K. Hubbard stated: > > Well, that depends really. The cost of an extra PC in this case is an ALR > > Dual Revolution MP-Pro system, which if I just mirror the system is going > > to > > Well, as I've said 3 times now, if you can't afford a whole 'nother box, > then at least buy another disk for / and /usr so that you can still switch > back to the previous OS version in 10 minutes or less. Are you going to > argue that *this* cost is too onerous to bear for an ISP? :) Nah, but it certainly takes the fun out of upgrades :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Nov 21 11:58:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06668 for hackers-outgoing; Fri, 21 Nov 1997 11:58:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06657 for ; Fri, 21 Nov 1997 11:58:15 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id OAA01102; Fri, 21 Nov 1997 14:57:58 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711211957.OAA01102@dyson.iquest.net> Subject: Re: Is there a FreeBSD benchmark program? In-Reply-To: from "David E. Cross" at "Nov 21, 97 01:23:22 pm" To: dec@phoenix.its.rpi.edu (David E. Cross) Date: Fri, 21 Nov 1997 14:57:58 -0500 (EST) Cc: reyesf@super.zippo.com, hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David E. Cross said: > On Fri, 21 Nov 1997, Francisco Reyes wrote: > > > I recently saw a message about someone upgrading from 2.2-stable to > > 2.2.5 and having serious performance degratation. I was wondering if > > there was any benchmark program for FreeBSD. This may help both users > > and kernel developers on checking whether a new kernel or > > configuration is better. > > /usr/ports/benchmarks > I am usually very careful about maintaining performance in my area(s) (VM and sometimes VFS) code. I have some private benchmarks and use public benchmarks to verify performance. I think that BDE and PHK both are very careful also. Any time a new benchmark comes across the mailing lists, we usually grab onto them :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Fri Nov 21 12:19:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08438 for hackers-outgoing; Fri, 21 Nov 1997 12:19:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08420 for ; Fri, 21 Nov 1997 12:18:58 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA08833; Fri, 21 Nov 1997 12:18:52 -0800 (PST) Date: Fri, 21 Nov 1997 12:18:52 -0800 (PST) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <3371.880103490@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk All I meant was that 2.2.5 was in use on quite a few of my servers, and I felt comfortable with it's robustness and reliability. However, my webserver sees more load than any other server I have, so I don't see any way I could've predicted a failure. (The only other server I have that gets hammered on is my newsserver, but I upgraded it to 3.0 some time ago to get around the FS corruption problem that seemed to be plaguing it, me, and a few other users). On Fri, 21 Nov 1997, Jordan K. Hubbard wrote: > > Pulleeze... > > > > I've been running practically every release of 2.2.x on almost 30 servers > > on a more regular basis than probably anybody. > > Man 1: "Uh, I really hate to be a wuss about this, but it's raining > heavily, those black thunderclouds look a little menacing and I've > seen the tree in our front yard struck three times by lighting in the > last 10 minutes. Are you *sure* we ought to be mounting this > television antenna on the roof right now? It seems somewhat.... > imprudent..." > > Man 2: "Nonsense! Why, I've put up more television antennas during > severe storms than practically anybody!" > > :-) > Jordan > From owner-freebsd-hackers Fri Nov 21 12:19:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08449 for hackers-outgoing; Fri, 21 Nov 1997 12:19:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bb.cc.wa.us (root@[208.8.136.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08437 for ; Fri, 21 Nov 1997 12:19:08 -0800 (PST) (envelope-from chris@bb.cc.wa.us) Received: from localhost (chris@localhost) by bb.cc.wa.us (8.8.5/8.6.9) with SMTP id MAA11168; Fri, 21 Nov 1997 12:23:19 -0800 (PST) Date: Fri, 21 Nov 1997 12:23:18 -0800 (PST) From: Chris Coleman To: Francisco Reyes cc: "hackers@FreeBSD.ORG" Subject: Re: Where sources for chpass? In-Reply-To: <199711211700.JAA17886@super.zippo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Francisco Reyes wrote: > I was looking for the sources for chpass and could not find them. > During installation I said to include several group of sources > (/usr/src/bin, /usr/src/sbin, etc..). Perhaps I missed one? How do I > go about getting the sources for chpass? > > What is the easiest way to search for sources? Is there are relation > between the location of the executable and the location of the > sources? Looking at /usr/src/bin and /usr/src/sbin seemed like there > are many sources missing from what I installed. > > The sources for files is /usr/bin and /usr/sbin are located in: /usr/src/usr.bin and /usr/src/usr.sbin the files /usr/src/bin and /usr/src/sbin are for: /bin and /sbin executables. Happy Hacking. Christopher J. Coleman (chris@bb.cc.wa.us) Computer Support Analyst I (509)-766-8873 FreeBSD Book Project: http://www.vmunix.com/fbsd-book/ From owner-freebsd-hackers Fri Nov 21 12:58:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11261 for hackers-outgoing; Fri, 21 Nov 1997 12:58:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from shell5.ba.best.com (cbray@shell5.ba.best.com [206.184.139.136]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11255 for ; Fri, 21 Nov 1997 12:57:57 -0800 (PST) (envelope-from cbray@shell5.ba.best.com) Received: from localhost (cbray@localhost) by shell5.ba.best.com (8.8.7/8.7.3) with SMTP id MAA27537 for ; Fri, 21 Nov 1997 12:57:52 -0800 (PST) Date: Fri, 21 Nov 1997 12:57:52 -0800 (PST) From: Curtis Bray To: freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Curtis Bray wrote: > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > share the same address space with their parent. > > If I have multiple children issuing mallocs the children seem to > core > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > of course I loose the shared address space). Anyone know what I could > be doing wrong here? Do I have to put semaphores around every > malloc?? > I hope that's not the case... Thanks in advance! By the way, I am running on 2.2.5 (STABLE). After further examination I noticed that the segmentation fault only occurs if the child tries to read or write to the piece of memory that it allocated. For example: void child_proc(int procNum, int time) { char *buf; buf = (char *) malloc(255); printf("Child %d created...: buf = %p\n", procNum, buf); sleep(time); GlobalCount++; printf("%c\n", buf[0]); <<-- It will page fault here... printf("Freeing %p\n", buf); free(buf); exit(0); } Also if I run with only one child I don't have a problem. But if two children try to modify the their malloced space, then only one succeedes and the other faults. Here's the output from running the above with 2 children: --------------- Going to create 2 rfork() process Parent waiting for children. Child 0 (PID 8343) created...: buf = 0x15000 Child 1 (PID 8344) created...: buf = 0x15100 Freeing 0x15000 Parent woke up on wait for 8344 with status 139 (#0) 8344 : Signaled? 1 / SigNum 11 Parent woke up on wait for 8343 with status 0 (#1) 8343 : Signaled? 0 / SigNum 0 Parent exiting: Global Count: 2! --------------- The same problem occrurs even if I don't call free() in each child. Other ideas? Curtis From owner-freebsd-hackers Fri Nov 21 13:01:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA11569 for hackers-outgoing; Fri, 21 Nov 1997 13:01:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA11551 for ; Fri, 21 Nov 1997 13:01:13 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id QAA01392; Fri, 21 Nov 1997 16:01:06 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711212101.QAA01392@dyson.iquest.net> Subject: Re: malloc() problems in children after using rfork() In-Reply-To: <3475E143.EE7AF250@best.com> from Curtis Bray at "Nov 21, 97 11:30:12 am" To: cbray@best.com Date: Fri, 21 Nov 1997 16:01:06 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Curtis Bray said: > Hi, > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > share the same address space with their parent. > > If I have multiple children issuing mallocs the children seem to core > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > of course I loose the shared address space). Anyone know what I could > be doing wrong here? Do I have to put semaphores around every malloc?? > I hope that's not the case... Thanks in advance! > Aieee... rfork is very tricky to use. Take a look at the assembly code that I have included. Note the management of the stack. -- John dyson@freebsd.org jdyson@nc.com .file "rf.S" #include #include "DEFS.h" #include "SYS.h" #define KERNEL #include #undef KERNEL #undef DEBUG /* * 8 12 16 20 24 28 * _rfork(flags, stack, startrtn, startarg, userrtn, arg); * * flags: RF* flags for rfork in unistd.h. * subr: subroutine to run as a thread. * stack: top of stack for thread. * arg: argument to thread. */ .stabs "rf.S",100,0,0,Ltext0 .text Ltext0: .type _thrfork,@function .stabd 68,0,1 ENTRY(thrfork) pushl %ebp movl %esp, %ebp pushl %esi /* * Push thread info onto the new thread's stack */ movl 12(%ebp), %esi / get stack addr subl $4, %esi movl 28(%ebp), %eax / get user argument movl %eax, (%esi) subl $4, %esi movl 24(%ebp), %eax / get user thread address movl %eax, (%esi) subl $4, %esi movl 20(%ebp), %eax / get internal argument movl %eax, (%esi) subl $4, %esi movl 16(%ebp), %eax / get internal subroutine movl %eax, (%esi) .stabd 68,0,2 /* * Prepare and execute rfork */ pushl 8(%ebp) pushl %esi leal SYS_rfork, %eax KERNCALL jb 2f .stabd 68,0,3 /* * Check to see if we are in the parent or child */ cmpl $0, %edx jnz 1f addl $8, %esp popl %esi movl %ebp, %esp popl %ebp ret .p2align 2 /* * If we are in the child (new thread), then * set-up the call to the internal subroutine. If it * returns, then call __exit. */ .stabd 68,0,4 1: movl %esi,%esp #ifdef DEBUG movl %esp, _stackaddr movl (%esp), %eax movl %eax, _stack movl 4(%esp), %eax movl %eax,_stack+4 movl 8(%esp), %eax movl %eax,_stack+8 movl 12(%esp), %eax movl %eax,_stack+12 #endif popl %eax #ifdef DEBUG movl %eax,_fcn #endif call %eax addl $12, %esp /* * Exit system call */ pushl %eax pushl $SYS_exit call _syscall .stabd 68,0,5 2: movl $EAGAIN, _errno movl $-1, %eax leave ret .stabs "thrfork:f67",36,0,6,_thrfork Lfe1: .size _thrfork,Lfe1-_thrfork #ifdef DEBUG .data .globl _stack _stack: .long 0 .long 0 .long 0 .long 0 .long 0 .globl _stackaddr _stackaddr: .long 0 .globl _fcn _fcn: .long 0 #endif From owner-freebsd-hackers Fri Nov 21 13:10:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA12087 for hackers-outgoing; Fri, 21 Nov 1997 13:10:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA12039 for ; Fri, 21 Nov 1997 13:09:09 -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 VAA28755; Fri, 21 Nov 1997 21:02:31 +0100 From: Luigi Rizzo Message-Id: <199711212002.VAA28755@labinfo.iet.unipi.it> Subject: Re: pnp To: jimmy@digitalmechanix.com (James D. Fowler) Date: Fri, 21 Nov 1997 21:02:30 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <01BCF66F.7B626520@spot.digitalmechanix.com> from "James D. Fowler" at Nov 21, 97 11:20:12 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there anything out there for enabling pnp on FreeBSD 2.2.1. I have a Boca modem that I would like to use. > Thanks, see http://www.iet.unipi.it/~luigi/FreeBSD.html the relevant bits are also on the 2.2.5 cdrom under xperimnt/ cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Nov 21 13:22:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA13505 for hackers-outgoing; Fri, 21 Nov 1997 13:22:07 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA13489 for ; Fri, 21 Nov 1997 13:22:04 -0800 (PST) (envelope-from nash@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (nash@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id PAA06064; Fri, 21 Nov 1997 15:22:02 -0600 (CST) Received: from localhost (nash@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id PAA09561; Fri, 21 Nov 1997 15:22:01 -0600 (CST) Date: Fri, 21 Nov 1997 15:22:01 -0600 (CST) From: Alex Nash To: Curtis Bray cc: freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() In-Reply-To: <3475E143.EE7AF250@best.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Curtis Bray wrote: > Hi, > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > share the same address space with their parent. > > If I have multiple children issuing mallocs the children seem to core > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > of course I loose the shared address space). Anyone know what I could > be doing wrong here? Do I have to put semaphores around every malloc?? > I hope that's not the case... Thanks in advance! The only locking malloc() performs is pthread_mutex_lock/unlock in the libc_r version. The non-threaded version provides no locking at all. Alex From owner-freebsd-hackers Fri Nov 21 13:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16084 for hackers-outgoing; Fri, 21 Nov 1997 13:45:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from shell5.ba.best.com (cbray@shell5.ba.best.com [206.184.139.136]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16067 for ; Fri, 21 Nov 1997 13:45:01 -0800 (PST) (envelope-from cbray@shell5.ba.best.com) Received: from localhost (cbray@localhost) by shell5.ba.best.com (8.8.7/8.7.3) with SMTP id NAA15206; Fri, 21 Nov 1997 13:44:55 -0800 (PST) Date: Fri, 21 Nov 1997 13:44:53 -0800 (PST) From: Curtis Bray To: Alex Nash cc: Curtis Bray , freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Alex Nash wrote: > On Fri, 21 Nov 1997, Curtis Bray wrote: > > > Hi, > > > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > > share the same address space with their parent. > > > > If I have multiple children issuing mallocs the children seem to core > > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > > of course I loose the shared address space). Anyone know what I could > > be doing wrong here? Do I have to put semaphores around every malloc?? > > I hope that's not the case... Thanks in advance! > > The only locking malloc() performs is pthread_mutex_lock/unlock in the > libc_r version. The non-threaded version provides no locking at all. > I was hoping to avoid the pthread package because I need my threads (or children processes in this case) to perform a lot of file IO. I appears that since non-blocking file IO doesn't exist in 4.4BSD that this approach would cause all my threads to block while one of them is waiting for data off the disk. Obviously this defeats the purpose of a threaded app! From what I'd seen in the mail list archives, it appears the rfork() method may work better for these IO bound applications. I was assuming that once the RFMEM flag was set, then the VM system would respect multiple children sharing the same address space. That's what I've gotten from the man pages anyway: man 2 rfork: RFMEM If set, the kernel will force sharing of the entire ad- dress space. The child will then inherit all the shared segments the parent process owns. Other segment types will be unaffected. Subsequent forks by the parent will then propagate the shared data and bss between children. The stack segment is always split. May be set only with RFPROC. Am I mistaken in this approach? Curtis From owner-freebsd-hackers Fri Nov 21 13:46:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16241 for hackers-outgoing; Fri, 21 Nov 1997 13:46:40 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16236 for ; Fri, 21 Nov 1997 13:46:37 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA29657 for ; Fri, 21 Nov 1997 14:46:29 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15613; Fri, 21 Nov 1997 14:46:27 -0700 Date: Fri, 21 Nov 1997 14:46:27 -0700 Message-Id: <199711212146.OAA15613@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.org Subject: Getting ethernet packets content under FreeBSD? X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is it possible to easily? I'm trying to debug a protocol, and w/out the contents of the data being sent in the packets it's awful hard to do. Is there anyway of dumping out the actual packet contents somewhere instead of dumping out the packet headers, which are less than useful for upper-layer TCP/IP protocol debugging. (Yes, I understand the possibility of packet snooping for passwords, etc.. that can occur if this is possible, but I don't want to have to go by a packet analyzer of hack tcpdump if I don't have to.) Nate From owner-freebsd-hackers Fri Nov 21 13:56:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16959 for hackers-outgoing; Fri, 21 Nov 1997 13:56:37 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16954 for ; Fri, 21 Nov 1997 13:56:27 -0800 (PST) (envelope-from nash@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (nash@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id PAA08832; Fri, 21 Nov 1997 15:56:26 -0600 (CST) Received: from localhost (nash@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id PAA10215; Fri, 21 Nov 1997 15:56:26 -0600 (CST) Date: Fri, 21 Nov 1997 15:56:25 -0600 (CST) From: Alex Nash To: Curtis Bray cc: freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Curtis Bray wrote: > From what I'd seen in the mail list archives, it appears the rfork() > method may work better for these IO bound applications. I was assuming > that once the RFMEM flag was set, then the VM system would respect > multiple children sharing the same address space. That's what I've > gotten from the man pages anyway: The problem is not with the VM system, but with the C library's malloc() routine (lib/libc/stdlib/malloc.c). The malloc routines have several critical sections within them which are unprotected when using the single threaded library. Alex From owner-freebsd-hackers Fri Nov 21 14:03:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17400 for hackers-outgoing; Fri, 21 Nov 1997 14:03:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA17394 for ; Fri, 21 Nov 1997 14:03:30 -0800 (PST) (envelope-from jack@diamond.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.8.7/8.8.7) with SMTP id RAA14925 for ; Fri, 21 Nov 1997 17:03:31 -0500 (EST) Date: Fri, 21 Nov 1997 17:03:31 -0500 (EST) From: jack X-Sender: jack@germanium.xtalwind.net To: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Without getting into the religious sub-thread, I noticed the following difference between 2.2.1 and 2.2.5. With 2.2.1 on two boxs one running 30 instances of mgetty and the other running 64 at boot immediately after the date is displayed the login prompt and all the mgettys came right up. With 2.2.5 there is a several second delay before the login prompt and the start of the mgettys. Changing those ports from `off' to `on' in /etc/ttys and doing kill -HUP 1 shows the same behavior, 2.2.1 the modems show TR immediately with 2.2.5 it takes a few seconds. No biggie, we don't need to reboot too often. :) -------------------------------------------------------------------------- Jack O'Neill Finger jacko@diamond.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-hackers Fri Nov 21 14:28:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19668 for hackers-outgoing; Fri, 21 Nov 1997 14:28:38 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19662 for ; Fri, 21 Nov 1997 14:28:31 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.7/8.6.9) with ESMTP id XAA17154; Fri, 21 Nov 1997 23:28:24 +0100 (CET) Message-Id: <199711212228.XAA17154@peedub.muc.de> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bruce M. Walter" Cc: freebsd-hackers@freefall.FreeBSD.org, isdn-dev@hcs.de Subject: Re: Ascend NetWarp 128 ISDN TA Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 20 Nov 1997 17:56:14 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 23:28:24 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Bruce M. Walter" writes: >Hey all! > >Is anyone working on a driver for the Ascend NetWarp 128 ISDN Terminal >Adapter? It is based on a network interface model rather than a comm port >model so it should not suffer from all of the latency problems of a serial >TA. > >Currently the card is selling for ~$175 US dollars and comes with >Windoze95 and NT miniport drivers which back into the M$ ISDN accellerator >interface. > >I have one of these cards and would be willing to port/write a driver for >it if there's not one already in the works. > well, start writing. :) The only drivers for ISDN cards that are currently available (for FreeBSD) are for cards common in Europe. Which chipset does the card use ? There might be a driver for a card with the same chipset that you could start with. There are drivers for a number of passive cards which use the Siemens chips (ISAC and HSCX). You might also check out whether Linux already supports the card. If you get a driver working send a mail to isdn-dev@hcs.de. This is a group which is working on an ISDN package which will, hopefully, find its way into FreeBSD in the near future. For that matter, we might be able to help you out with the driver (answering questions, etc.). We can't write the driver since cards used in Europe don't include the NT-1. That's provided by the phone companies here. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com From owner-freebsd-hackers Fri Nov 21 14:34:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20165 for hackers-outgoing; Fri, 21 Nov 1997 14:34:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20152 for ; Fri, 21 Nov 1997 14:34:26 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA29984; Fri, 21 Nov 1997 15:34:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA15870; Fri, 21 Nov 1997 15:34:22 -0700 Date: Fri, 21 Nov 1997 15:34:22 -0700 Message-Id: <199711212234.PAA15870@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: bmah@CA.Sandia.GOV Cc: Nate Williams , hackers@freebsd.org Subject: Re: Getting ethernet packets content under FreeBSD? In-Reply-To: <199711212231.OAA18274@stennis.ca.sandia.gov> References: <199711212146.OAA15613@mt.sri.com> <199711212231.OAA18274@stennis.ca.sandia.gov> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Is it possible to easily? I'm trying to debug a protocol, and w/out the > > contents of the data being sent in the packets it's awful hard to do. > > Is there anyway of dumping out the actual packet contents somewhere > > instead of dumping out the packet headers, which are less than useful > > for upper-layer TCP/IP protocol debugging. > > Does "tcpdump -x -e -s 1500" not do what you want? Probably, I just couldn't figure out how do to it. :) > The tcpdump maintainers deliberately left out an ASCII packet-printer, but > coding one up is pretty easy if that's what you need. I can always run it through hexdump. :) Nate From owner-freebsd-hackers Fri Nov 21 14:38:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20482 for hackers-outgoing; Fri, 21 Nov 1997 14:38:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20464 for ; Fri, 21 Nov 1997 14:38:03 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.7/8.8.8) id RAA01688; Fri, 21 Nov 1997 17:37:47 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199711212237.RAA01688@dyson.iquest.net> Subject: Re: malloc() problems in children after using rfork() In-Reply-To: from Curtis Bray at "Nov 21, 97 01:44:53 pm" To: cbray@best.com (Curtis Bray) Date: Fri, 21 Nov 1997 17:37:47 -0500 (EST) Cc: nash@Mcs.Net, cbray@best.com, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Curtis Bray said: > > > On Fri, 21 Nov 1997, Alex Nash wrote: > > > On Fri, 21 Nov 1997, Curtis Bray wrote: > > > > > Hi, > > > > > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > > > share the same address space with their parent. > > > > > > If I have multiple children issuing mallocs the children seem to core > > > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > > > of course I loose the shared address space). Anyone know what I could > > > be doing wrong here? Do I have to put semaphores around every malloc?? > > > I hope that's not the case... Thanks in advance! > > > > The only locking malloc() performs is pthread_mutex_lock/unlock in the > > libc_r version. The non-threaded version provides no locking at all. > > > > I was hoping to avoid the pthread package because I need my threads (or > children processes in this case) to perform a lot of file IO. I appears > that since non-blocking file IO doesn't exist in 4.4BSD that this approach > would cause all my threads to block while one of them is waiting for data > off the disk. Obviously this defeats the purpose of a threaded app! > I should have the AIO stuff done soon... It will work on ANY filedescriptor. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-hackers Fri Nov 21 14:42:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20834 for hackers-outgoing; Fri, 21 Nov 1997 14:42:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from callisto.fortean.com (callisto.fortean.com [206.142.225.82]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20820 for ; Fri, 21 Nov 1997 14:42:40 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.5/8.8.5) with SMTP id RAA14383; Fri, 21 Nov 1997 17:38:31 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Fri, 21 Nov 1997 17:38:30 -0500 (EST) From: "Bruce M. Walter" To: Gary Jennejohn cc: freebsd-hackers@freefall.FreeBSD.org, isdn-dev@hcs.de Subject: Re: Ascend NetWarp 128 ISDN TA In-Reply-To: <199711212228.XAA17154@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gary, Thanks for the reply. > >Is anyone working on a driver for the Ascend NetWarp 128 ISDN Terminal > >Adapter? > > Which chipset does the card use ? There might be a driver for a card with > the same chipset that you could start with. There are drivers for a > number of passive cards which use the Siemens chips (ISAC and HSCX). Here's what I know: 1) It is a passive TA based on the Network Interface model rather than the Comm Interface model. This makes it an excellent choice to avoid the latency hit involved in Sync<->Async translation as well as the UART speed ceiling. 2) The card is PnP and based on the Siemens 2086/2091/82525 chipset. In fact, these are about the only chips on the card at all. 3) It claims to support National ISDN NI-1, AT&T 5ESS, NORTEL DMS-100, EDSI and INS-64 signaling protocols. > You might also check out whether Linux already supports the card. It currently doesn't, but I've checked out isdn4linux and the HiSax drivers and things look promising... So far as I can tell, from bisdn and HiSax, the isdn (B channel) driver should be ok as-is, but disdn (D channel) driver will need additions to support the US signaling protocols. Does that sound reasonable? As far as the actual card support goes, I'm not sure which european cards are closest to it. I've read the Niccy is ISAC/HCSX based, as well as the Teles. Is this the case? > If you get a driver working send a mail to isdn-dev@hcs.de. This is > a group which is working on an ISDN package which will, hopefully, > find its way into FreeBSD in the near future. For that matter, we > might be able to help you out with the driver (answering questions, > etc.). Absolutely. Thanks much! I've been in contact with Ascend and am waiting for more information from the Systems Engineers. I'll let you know what progress I make. Cheers! - Bruce ======================================================================== || Bruce M. Walter || 107 Timber Hollow Court #335 || || Senior Network Consultant || Chapel Hill, NC 27514 || || Fortean Technologies, Inc. || Tel: 919-967-4766 || || Information Technology Consultants || Fax: 919-967-4395 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Fri Nov 21 14:57:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21984 for hackers-outgoing; Fri, 21 Nov 1997 14:57:29 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA21964 for ; Fri, 21 Nov 1997 14:57:18 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 12899 invoked by uid 1001); 21 Nov 1997 22:56:43 +0000 (GMT) To: nate@mt.sri.com Cc: hackers@FreeBSD.ORG Subject: Re: Getting ethernet packets content under FreeBSD? In-Reply-To: Your message of "Fri, 21 Nov 1997 14:46:27 -0700" References: <199711212146.OAA15613@mt.sri.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Fri, 21 Nov 1997 23:56:43 +0100 Message-ID: <12897.880153003@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is it possible to easily? I'm trying to debug a protocol, and w/out the > contents of the data being sent in the packets it's awful hard to do. > Is there anyway of dumping out the actual packet contents somewhere > instead of dumping out the packet headers, which are less than useful > for upper-layer TCP/IP protocol debugging. libpcap is your friend. You need BPF in the kernel, of course. A good start would be ftp://ee.lbl.gov/pcapture-0.2.1.tar.Z, which is a program that uses libpcap to capture packets: DESCRIPTION Pcapture captures the last few packets that match the boolean expression. The packets are collected in a circu­ lar buffer; when a signal (TERM, INT, or HUP) is received, the are written out to the raw packet file. (Notice that a raw packet file must be specified using the -w flag.) Should be easy enough to modify to record the data continuously. Or you could just use 'tcpdump -w'. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Fri Nov 21 15:00:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22273 for hackers-outgoing; Fri, 21 Nov 1997 15:00:44 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from anlsun.ebr.anlw.anl.gov (anlsun.ebr.anlw.anl.gov [141.221.1.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA22265 for ; Fri, 21 Nov 1997 15:00:39 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (tc-if2-34.ida.net [208.141.171.91]) by anlsun.ebr.anlw.anl.gov (8.6.11/8.6.11) with SMTP id PAA28906; Fri, 21 Nov 1997 15:58:08 -0700 Date: Fri, 21 Nov 1997 15:57:29 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Curtis Bray cc: freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Curtis Bray wrote: > On Fri, 21 Nov 1997, Alex Nash wrote: > > On Fri, 21 Nov 1997, Curtis Bray wrote: > > > Hi, > > > > > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > > > share the same address space with their parent. > > > > > > If I have multiple children issuing mallocs the children seem to core > > > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > > > of course I loose the shared address space). Anyone know what I could > > > be doing wrong here? Do I have to put semaphores around every malloc?? > > > I hope that's not the case... Thanks in advance! > > > > The only locking malloc() performs is pthread_mutex_lock/unlock in the > > libc_r version. The non-threaded version provides no locking at all. > > > > I was hoping to avoid the pthread package because I need my threads (or > children processes in this case) to perform a lot of file IO. I appears > that since non-blocking file IO doesn't exist in 4.4BSD that this approach > would cause all my threads to block while one of them is waiting for data > off the disk. Obviously this defeats the purpose of a threaded app! > > From what I'd seen in the mail list archives, it appears the rfork() > method may work better for these IO bound applications. I was assuming > that once the RFMEM flag was set, then the VM system would respect > multiple children sharing the same address space. That's what I've > gotten from the man pages anyway: > > man 2 rfork: > > RFMEM If set, the kernel will force sharing of the entire ad- > dress space. The child will then inherit all the shared > segments the parent process owns. Other segment types > will be unaffected. Subsequent forks by the parent will > then propagate the shared data and bss between children. > The stack segment is always split. May be set only with > RFPROC. > > Am I mistaken in this approach? > > Curtis > I've been dealing a little with the same problem, and I decided to use regular forking and then to use mmap() to have a shared memory area between processes. I know threading is supposed to be great and all, but what I see is alot of minor dfferences between operating systems that make it difficult to be really portable. Often thread-safe libraries are missing on target systems or have slightly different function names (like Solaris). rfork() looks like an interesting function, but it doesn't seen widespread in Unix yet (I just checked for it on linux and OSF). I seem to remember Linus making a a big deal about a clone() call. Charles Mott From owner-freebsd-hackers Fri Nov 21 16:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27048 for hackers-outgoing; Fri, 21 Nov 1997 16:20:26 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27037 for ; Fri, 21 Nov 1997 16:20:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA04819; Fri, 21 Nov 1997 16:15:22 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd004816; Fri Nov 21 16:15:18 1997 Message-ID: <34762398.1CFBAE39@whistle.com> Date: Fri, 21 Nov 1997 16:13:12 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Alex Nash CC: Curtis Bray , freebsd-hackers@freebsd.org Subject: Re: malloc() problems in children after using rfork() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alex Nash wrote: > > On Fri, 21 Nov 1997, Curtis Bray wrote: > > > Hi, > > > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > > share the same address space with their parent. > > > > If I have multiple children issuing mallocs the children seem to core > > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > > of course I loose the shared address space). Anyone know what I could > > be doing wrong here? Do I have to put semaphores around every malloc?? > > I hope that's not the case... Thanks in advance! > > The only locking malloc() performs is pthread_mutex_lock/unlock in the > libc_r version. The non-threaded version provides no locking at all. > > Alex I just saw the other email he's using 2.2.5 rfmem don't work in 2.2.x. well it DOES but it only shares EXISTING memory. new allocations are not shared.. From owner-freebsd-hackers Fri Nov 21 16:20:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27057 for hackers-outgoing; Fri, 21 Nov 1997 16:20:28 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27042 for ; Fri, 21 Nov 1997 16:20:24 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA04927; Fri, 21 Nov 1997 16:18:42 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd004918; Fri Nov 21 16:18:38 1997 Message-ID: <34762460.3F54BC7E@whistle.com> Date: Fri, 21 Nov 1997 16:16:32 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Curtis Bray CC: Alex Nash , freebsd-hackers@FreeBSD.ORG Subject: Re: malloc() problems in children after using rfork() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Curtis Bray wrote: > > On Fri, 21 Nov 1997, Alex Nash wrote: > > > On Fri, 21 Nov 1997, Curtis Bray wrote: > > > > > Hi, > > > > > > I'm trying to use rfork(RFPROC | RFMEM) so that all the children can > > > share the same address space with their parent. > > > > > > If I have multiple children issuing mallocs the children seem to core > > > dump. Once I turn the RFMEM flag off I have no problem mallocing (but > > > of course I loose the shared address space). Anyone know what I could > > > be doing wrong here? Do I have to put semaphores around every malloc?? > > > I hope that's not the case... Thanks in advance! > > > > The only locking malloc() performs is pthread_mutex_lock/unlock in the > > libc_r version. The non-threaded version provides no locking at all. > > > > I was hoping to avoid the pthread package because I need my threads (or > children processes in this case) to perform a lot of file IO. I appears > that since non-blocking file IO doesn't exist in 4.4BSD that this approach > would cause all my threads to block while one of them is waiting for data > off the disk. Obviously this defeats the purpose of a threaded app! > > From what I'd seen in the mail list archives, it appears the rfork() > method may work better for these IO bound applications. I was assuming > that once the RFMEM flag was set, then the VM system would respect > multiple children sharing the same address space. That's what I've > gotten from the man pages anyway: > > man 2 rfork: > > RFMEM If set, the kernel will force sharing of the entire ad- > dress space. The child will then inherit all the shared > segments the parent process owns. Other segment types > will be unaffected. Subsequent forks by the parent will > then propagate the shared data and bss between children. > The stack segment is always split. May be set only with > RFPROC. > > Am I mistaken in this approach? > > Curtis you WOULD be correct, except that RFMEM is only partially implemented for 2.2.x New allocations from the kernel (done after the rfork) are not shared.. this was fixed in -current but I'm pretty sure john has not back-ported it. From owner-freebsd-hackers Fri Nov 21 17:19:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01317 for hackers-outgoing; Fri, 21 Nov 1997 17:19:50 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01309 for ; Fri, 21 Nov 1997 17:19:44 -0800 (PST) (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id CAA28277; Sat, 22 Nov 1997 02:06:25 +0100 (MET) From: Wolfgang Helbig Message-Id: <199711220106.CAA28277@rvc1.informatik.ba-stuttgart.de> Subject: Re: Where sources for chpass? In-Reply-To: <199711211700.JAA17886@super.zippo.com> from Francisco Reyes at "Nov 21, 97 12:02:16 pm" To: reyesf@super.zippo.com Date: Sat, 22 Nov 1997 02:06:24 +0100 (MET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was looking for the sources for chpass and could not find them. > During installation I said to include several group of sources > (/usr/src/bin, /usr/src/sbin, etc..). Perhaps I missed one? How do I > go about getting the sources for chpass? > > What is the easiest way to search for sources? Is there are relation > between the location of the executable and the location of the > sources? Looking at /usr/src/bin and /usr/src/sbin seemed like there > are many sources missing from what I installed. Use whereis(1), locate(1) or find(1). Wolfgang From owner-freebsd-hackers Fri Nov 21 17:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03850 for hackers-outgoing; Fri, 21 Nov 1997 17:58:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA03839 for ; Fri, 21 Nov 1997 17:58:14 -0800 (PST) (envelope-from alex@zen.nash.org) Received: (from alex@localhost) by zen.nash.org (8.8.8/8.8.7) id TAA05968; Fri, 21 Nov 1997 19:54:54 -0600 (CST) (envelope-from alex) Message-Id: <199711220154.TAA05968@zen.nash.org> Date: Fri, 21 Nov 1997 19:54:53 -0600 (CST) From: nash@mcs.net Reply-To: nash@mcs.com Subject: Re: malloc() problems in children after using rfork() To: julian@whistle.com cc: cbray@best.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <34762398.1CFBAE39@whistle.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 21 Nov, Julian Elischer wrote: >> The only locking malloc() performs is pthread_mutex_lock/unlock in the >> libc_r version. The non-threaded version provides no locking at all. [...] > I just saw the other email > > he's using 2.2.5 > rfmem don't work in 2.2.x. > well it DOES but it only shares EXISTING memory. > new allocations are not shared.. and in a subsequent email... > New allocations from the kernel (done after the rfork) > are not shared.. > this was fixed in -current but I'm pretty sure john has not back-ported > it. Unless I'm missing something, even if the fix was brought into -stable it still won't allow multiple rforked(RFMEM|RFPROC) processes to malloc out of a shared data segment (without locking, of course). Alex From owner-freebsd-hackers Fri Nov 21 18:58:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06806 for hackers-outgoing; Fri, 21 Nov 1997 18:58:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06801 for ; Fri, 21 Nov 1997 18:58:31 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id SAA00308; Fri, 21 Nov 1997 18:57:40 -0800 (PST) Date: Fri, 21 Nov 1997 18:57:39 -0800 (PST) From: Jaye Mathisen To: Frank Mayhar cc: Brian Campbell , hackers@freebsd.org Subject: Re: MFS /tmp oddness In-Reply-To: <199711211538.HAA00291@exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had to modify the rc/daemon entry in login.conf to get a MFS bigger than 32. Seems bogus. On Fri, 21 Nov 1997, Frank Mayhar wrote: > Brian Campbell wrote: > > On Wed, Nov 19, 1997 at 06:42:07PM -0500, John S. Dyson wrote: > > > Aaron Smith said: > > > > does anybody know why i'm getting such a tiny MFS? we tried using the -s > > > > option too but that didn't work either. > > > This is in my fstab and works. (note that the -b=16384,-f=2048 options > > > are eccentric, but this is copied directly.) > > > swap /tmp mfs rw,-s=210000,-b=16384,-f=2048 0 0 > > Did you have to modify login.conf (or something else) to make this work? > > Mine specfies -s262000 but only manages to get 32M > > This is another metoo. I see exactly the same thing, with a specified > size of 196608. I haven't yet tried changing the block and frag size to > match John's; I'll do that today. > -- > Frank Mayhar frank@exit.com > From owner-freebsd-hackers Fri Nov 21 21:35:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13819 for hackers-outgoing; Fri, 21 Nov 1997 21:35:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from seidata.com (seidata.com [206.160.242.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA13814 for ; Fri, 21 Nov 1997 21:35:53 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by seidata.com (8.8.7/8.8.5) with SMTP id AAA17014; Sat, 22 Nov 1997 00:35:15 -0500 (EST) Date: Sat, 22 Nov 1997 00:35:15 -0500 (EST) From: Mike To: Josef Belkovics cc: hackers@FreeBSD.ORG Subject: Re: snmp agent/manager (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, Josef Belkovics wrote: > I look for some snmp agent and, mainly, manager. Both under FreeBSD. > Manager at level as optivity. Some advice? It seems like this post and my reply should be in "questions" and not "hackers"... anyway, what type of snmp hardware are you using? We use Cisco and USR snmp devices and we have experimented with "total control" packages from both vendors. I believe Cisco makes a "Unix" version of their software, but I am not sure about USR... the effectiveness of snmp software, to a large extent, is dependant upon the availability of MIBs. I would advise snooping around the Cisco and USR web sites. --- Mike Hoskins SEI Data Network Services, Inc. mike@seidata.com From owner-freebsd-hackers Sat Nov 22 00:44:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23128 for hackers-outgoing; Sat, 22 Nov 1997 00:44:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23096 for ; Sat, 22 Nov 1997 00:44:00 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: (from uucp@localhost) by DNS.Lamb.net (8.8.6/8.8.6) id AAA02444 for ; Sat, 22 Nov 1997 00:44:09 -0800 (PST) Received: from gatekeeper.Alameda.net(207.90.181.2) via SMTP by DNS.Lamb.net, id smtpd002442; Sat Nov 22 00:44:01 1997 Received: (from ulf@localhost) by Gatekeeper.Alameda.net (8.8.6/8.7.6) id AAA12866 for hackers@freebsd.org; Sat, 22 Nov 1997 00:43:51 -0800 (PST) From: Ulf Zimmermann Message-Id: <199711220843.AAA12866@Gatekeeper.Alameda.net> Subject: Upgrade function of 2.2.5R To: hackers@freebsd.org Date: Sat, 22 Nov 1997 00:43:51 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmmm, has anyone seen this ? I just used the upgrade function of 2.2.5R and the system came up fine, but with the 2.2.2R kernel. Everything else seems to be 2.2.5, even the kernel source. Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-hackers Sat Nov 22 00:48:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23579 for hackers-outgoing; Sat, 22 Nov 1997 00:48:14 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23569 for ; Sat, 22 Nov 1997 00:48:10 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: (from uucp@localhost) by DNS.Lamb.net (8.8.6/8.8.6) id AAA02454 for ; Sat, 22 Nov 1997 00:48:19 -0800 (PST) Received: from gatekeeper.Alameda.net(207.90.181.2) via SMTP by DNS.Lamb.net, id smtpd002452; Sat Nov 22 00:48:09 1997 Received: (from ulf@localhost) by Gatekeeper.Alameda.net (8.8.6/8.7.6) id AAA12954 for hackers@freebsd.org; Sat, 22 Nov 1997 00:47:59 -0800 (PST) From: Ulf Zimmermann Message-Id: <199711220847.AAA12954@Gatekeeper.Alameda.net> Subject: Upgrade function and root dir To: hackers@freebsd.org Date: Sat, 22 Nov 1997 00:47:59 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would it be possible to change the upgrade function, so that is not necessary overwrites the dot files in /root ? I always save it, but it would be one step less ;-) Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-hackers Sat Nov 22 01:00:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA24157 for hackers-outgoing; Sat, 22 Nov 1997 01:00:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA24152 for ; Sat, 22 Nov 1997 01:00:46 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA21215 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Sat, 22 Nov 1997 10:01:11 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id AAA06628 for FreeBSD-hackers@freebsd.org; Sat, 22 Nov 1997 00:25:59 +0100 (MET) From: Wilko Bulte Message-Id: <199711212325.AAA06628@yedi.iaf.nl> Subject: volume control on SCSI Toshiba CDdrive To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sat, 22 Nov 1997 00:25:59 +0100 (MET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just changed my old 4x Toshiba cdrom to a 12x Toshiba. To be precise, it is a TOSHIBA CD-ROM XM-5701TA 3136. The 4x Toshiba audio volume was controllable using the WorkMan 'slide'. It seems that the 12x Toshiba does not respond to this. AFAIK the volume stuff is part of the SCSI standard these days. Any comments of fellow XM5701 owners? _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix --Yoda From owner-freebsd-hackers Sat Nov 22 01:21:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25323 for hackers-outgoing; Sat, 22 Nov 1997 01:21:32 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA25318 for ; Sat, 22 Nov 1997 01:21:28 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA10780; Sat, 22 Nov 1997 10:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id KAA08829; Sat, 22 Nov 1997 10:01:02 +0100 (MET) Message-ID: <19971122100101.ND15465@uriah.heep.sax.de> Date: Sat, 22 Nov 1997 10:01:01 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (hackers@FreeBSD.ORG) Cc: reyesf@super.zippo.com (Francisco Reyes) Subject: Re: Where sources for chpass? References: <199711211700.JAA17886@super.zippo.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199711211700.JAA17886@super.zippo.com>; from Francisco Reyes on Nov 22, 1997 05:21:38 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Francisco Reyes wrote: > What is the easiest way to search for sources? j@uriah 276% whereis -s chpass chpass: /usr/src/usr.bin/chpass -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Nov 22 01:52:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA26568 for hackers-outgoing; Sat, 22 Nov 1997 01:52:51 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA26563 for ; Sat, 22 Nov 1997 01:52:47 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA25099; Sat, 22 Nov 1997 01:53:16 -0800 (PST) To: Ulf Zimmermann cc: hackers@FreeBSD.ORG Subject: Re: Upgrade function of 2.2.5R In-reply-to: Your message of "Sat, 22 Nov 1997 00:43:51 PST." <199711220843.AAA12866@Gatekeeper.Alameda.net> Date: Sat, 22 Nov 1997 01:53:16 -0800 Message-ID: <25095.880192396@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a bug which I fixed in the 2.2.5-stable sysinstall. It's also fixed in the ftp://freebsd.org/pub/jkh/225upgrade.tgz package, which upgrades /stand/sysinstall to the latest before launching it in upgrade mode (which, if you're only after the upgrading of sysinstall, you can always say "No" to). Jordan > Hmmm, has anyone seen this ? I just used the upgrade function > of 2.2.5R and the system came up fine, but with the 2.2.2R kernel. > Everything else seems to be 2.2.5, even the kernel source. > > Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-hackers Sat Nov 22 02:02:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA27041 for hackers-outgoing; Sat, 22 Nov 1997 02:02:25 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA27036 for ; Sat, 22 Nov 1997 02:02:19 -0800 (PST) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0xZCO1-0032bjC; Sat, 22 Nov 97 11:02 MET Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Sat, 22 Nov 1997 10:15:08 +0100 (MET) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for walter@fortean.com; Sat, 22 Nov 1997 10:06:51 +0100 (CET) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Ascend NetWarp 128 ISDN TA In-Reply-To: from "Bruce M. Walter" at "Nov 21, 97 05:38:30 pm" To: walter@fortean.com (Bruce M. Walter) Date: Sat, 22 Nov 1997 10:06:51 +0100 (CET) Cc: garyj@muc.de, freebsd-hackers@freefall.FreeBSD.org, isdn-dev@hcs.de Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce M. Walter wrote: > > >Is anyone working on a driver for the Ascend NetWarp 128 ISDN Terminal > > >Adapter? [i'm rearranging the order of your mail a bit] > 2) The card is PnP and based on the Siemens 2086/2091/82525 chipset. In > fact, these are about the only chips on the card at all. The 2086 is the ISAC, it is used to interface the ISDN line with the rest of the system, the 2091 is an Echo Cancellation Circuit, no idea what it is used for here and the 82525 is the HSCX used to interface to the B channel. Databooks for these chips are available from: http://www.siemens.de/Semiconductor/products/ICs/33/33036.htm All passive cards currently supported by bisdn and the upcoming isdn4bsd are based on the Siemens HSCX/ISAC combination, so once you know how the interfacing of the chips to the ISA/EISA/PCI bus is done, you are done. Bisdn and isdn4bsd do _not_ support any protocols other than DSS1 (EuroISDN) (and the old 1TR6 in case of bisdn) yet, and this will be most of the work to make the card usable outside Europe. > 3) It claims to support National ISDN NI-1, AT&T 5ESS, NORTEL DMS-100, > EDSI and INS-64 signaling protocols. Yes, this is the same as if a manufacturer of cars would write in it's specs: "This car supports driving on every road in the world" :-) The chipset in question does support the hardware access to the line in order to support the above mentioned protocols, but the protocol support itself will have to be written by someone. I guess, that this card comes with some sort of support software for DOS or Windows or so, and the whole (which is _much_!) protocol handling then is done in this software. You have to write this support from scratch when you want to use this card under another than the supported OS'ses. Since the D channel is 3-layerd, it might be possible to reuse some of the existing protocol support from DSS1 for the US protocols (it basically has 3 layers, in Europe is it I.430, Q.921 and Q.931 - Layer 1 seems to have some differences for the US being "not quite" I.430, Layer 2 seems to be the same but layer 3 has to be written; the difficulty seems that there is not a single protocol but different phone companies with different switches seem to have different protocols in the US). The B channel stays the same everywhere. > 1) It is a passive TA based on the Network Interface model rather than the > Comm Interface model. This makes it an excellent choice to avoid the > latency hit involved in Sync<->Async translation as well as the UART speed > ceiling. It looks like this "interface model" is entirely implemented in the accom- panied software. It is - once the whole protocol support is written for the M$DOS world - very easy to interface the result to a TTY or a network interface inside the hosting OS, but for passive cards this is done in soft- ware. In case you have an active card, the host OS can be presented a _hardware_ interface which look like an UART or a network chip like the ones found on NE2000 or WD/SMC cards, then this interface model is transportable across OS platforms, but this does not seem to be true in your case, since this would require not only the chips you have found on your card, but at least a microprocessor, RAM, ROM and support chips. Hope this helps, hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe "Those who can, do. Those who can't, talk. And those who can't talk, talk about talking." (B. Shaw) From owner-freebsd-hackers Sat Nov 22 02:23:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA27790 for hackers-outgoing; Sat, 22 Nov 1997 02:23:05 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA27785 for ; Sat, 22 Nov 1997 02:23:02 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA00464 for hackers@FreeBSD.ORG; Sat, 22 Nov 1997 11:23:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id LAA09192; Sat, 22 Nov 1997 11:12:53 +0100 (MET) Message-ID: <19971122111253.HK34127@uriah.heep.sax.de> Date: Sat, 22 Nov 1997 11:12:53 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: NBQ: Why partitioning? (was: Re: Partitioning suggestions?) References: <199711180019.TAA01983@dyson.iquest.net> <199711180202.VAA04479@luomat.peak.org> <19971117192532.37475@micron.mini.net> <19971119193141.NY02422@uriah.heep.sax.de> <19971121002001.09565@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19971121002001.09565@keltia.freenix.fr>; from Ollivier Robert on Nov 21, 1997 00:20:01 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > I wished we would support 16 partition slots at least as an > > alternative to the backwards-compatible 8 slot model. > > Why not using a second FreeBSD slice ? I happen to hate slices, ya know? :-) I wanna be able to use my disk on any potential controller, disregarding any geometry hassles. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Nov 22 05:52:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA06491 for hackers-outgoing; Sat, 22 Nov 1997 05:52:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iq.org (proff@profane.iq.org [203.4.184.222]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA06458 for ; Sat, 22 Nov 1997 05:51:57 -0800 (PST) (envelope-from proff@iq.org) Received: (qmail 3910 invoked by uid 110); 22 Nov 1997 13:50:23 -0000 Date: 22 Nov 1997 13:50:23 -0000 Message-ID: <19971122135023.3909.qmail@iq.org> From: Julian Assange To: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Subject: cryptographic filing system alpha Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A few people have been pestering me for an alpha snapshot, so without futher ado: http://underground.org/book/marutukku.tgz This is fully functional, but the build system and documentation is still in state of transition. It has only been tested so far on FreeBSD2.2.2. It is *NOT* user-friendly at this stage. And should *NOT* be distributed. This is not beta software. This is alpha software. Caveat Emptor It comes with rc16, cast-128, idea and blowfish, but will pull in DES, tripple DES, rc4, rc2 and faster versions of the internal ciphers if you have SSLeay installed (which you can find in /usr/ports/security). Compile under freebsd: $ make depend $ make # modload mkernel/maru_mod.o $ cd msetkey # ./mcreate # ./mnewiv # ./maset # newfs /dev/maru0 # mkdir /maru # mount /dev/maru0 /maru $ cd /maru $ ls -la ; whatever $ cd / # umount /maru # cd (wherever)/msetkey # ./mdetach # modunload -n maru_mod man pages (quite brief ones at the moment) are in doc/ you can view these with: make pagename.less I've included two man pages below, which will give you some idea of what is involved. -- Prof. Julian Assange |"Don't worry about people stealing your ideas. If your | Ideas are any good, you'll have to ram them down proff@iq.org | people's throats." -- Stolen quote from Howard Aiken proff@gnu.ai.mit.edu | http://underground.org/book mnewiv(1) mnewiv(1) NAME mnewiv -- Create a new Rubberhose ciphertext descriptor SYNOPSIS mnewiv [-1 key_cipher] [-2 lattice_cipher] [-3 block_cipher] [-b fs_blocksize] [-D depth] [-f] [-d debug_lvl] [maru.iv] DESCRIPTION Create a new maru.iv file. When complete, this file con- tains o Major and minor version numbers, for chronologically shifted compatibility o Cipher description numbers for the Key, Lattice and Block ciphers o Master Key agitation count o File system blocksize (-b) o Depth of the block key generator lattice (-D) o Header checksum before decryption o Master Key agitation checksum o MAX_PASSPHRASE bytes of passphrase salt o MAX_KEY bytes of Master Key salt o Salt for the left and right lattice keys o Initialisation vectors for the lattice o Initialisation vectors for each cryptographic block within the file-system block OPTIONS -1 key_cipher Cipher used for pass-phrase `hashing', master- key decryption and lattice key/table generation. Defaults to rc16 -2 lattice_cipher Cipher used for generating file-system block keys from the lattice. Defaults to CAST-128 -3 block_cipher Cipher used for the encryption and decryption of disk blocks. Defaults to CAST-128 1 mnewiv(1) mnewiv(1) -b fs_blocksize Sets the file-system block size. Ideally this value should exactly equal the bdevsw strategy read/write size as passed in from the calling filesystem. A reasonable value is chosen by default (2048 under FreeBSD), and should be only changed with care. -D depth Specify the depth of the subkey-generation lat- tice. File system block keys are generated from the lattice, such that a lattice of depth n can produce 2^n blockeys. Lattice depth defaults to n = 32, which is acceptable for cipher extents upto 4294967296 file system blocks in size. -d debug_lvl Set the debug level. Level 0 produces no status information ("quiet"), level 1 produces minimal status informatio. Level 2 and above produce additional debugging information. At debugging levels two or greater, the anti-core-dumping and memory-wiping-on-exit features of rubberhose are disabled in other to facilitate post crash anal- ysis. -f Force contiuation on error (where possible, e.g over-write pre-existing files instead of abort- ing). EXAMPLE Example mnewiv $ mnewiv -1 rc16 -2 ssl-des-ede3-cbc -3 ssl-des-ede3-cbc mysexy.iv rubberhose (0.5) (c) 1997 Julian Assange MARUTUKKU truly is the refuge of his land, city, and people. Unto him shall the people give praise forever. Enter new passphrase (128 significant characters): Confirm passphrase: Confirm passphrase (again): Generating 128 pseudo cryptographically random bytes for passphrase salt Generating 256 cryptographically random bytes for maru master key Agitating rc16 key generator state for 5 seconds... 32405 rc16 agitations (6481 per second) Generating 32 pseudo cryptographically random bytes for primary lattice key salt's Generating 512 pseudo cryptographically random bytes for subkey lattice IV's Generating 2048 pseudo cryptographically random bytes for master block IV array Clearing key artifacts Maru IV extent header generation complete. Saving Maru SALT/IV extent header as "mysexy.iv" * MAKE AT LEAST TWO BACKUPS of this file. If a single bit sells out to the dark forces of entropy, your entire maru ciphertext extent will follow suit ENVIROMENT 2 mnewiv(1) mnewiv(1) MARU_PASSPHRASE Use the contents of this variable instead of prompting for a pass-phrase. COPYRIGHT Copyright 1997 Julian Assange , All rights reserved. AUTHOR Julian Assange . SEE ALSO hose(1), mnewiv(1), mcreate(1), mwipe(1), mattach(1), maset(1), msetkey(1), mclearkey(1), mdetach(1), mdecrypt(1), mgetopt(1), msetopt(1), mstats(1), minfo(1), mlist(1). mlist(1) mlist(1) NAME mlist -- List available ciphers SYNOPSIS mlist [-d debug_lvl] [-f] DESCRIPTION List available ciphers OPTIONS -d debug_lvl Set the debug level. Level 0 produces no status information ("quiet"), level 1 produces minimal status informatio. Level 2 and above produce additional debugging information. At debugging levels two or greater, the anti-core-dumping and memory-wiping-on-exit features of rubberhose are disabled in other to facilitate post crash anal- ysis. -f Force contiuation on error (where possible, e.g over-write pre-existing files instead of abort- ing). EXAMPLE Example mlist $ mlist rubberhose (0.5) (c) 1997 Julian Assange Remember - it's called ``Rubber-hose'', but it's pronounced ``Maru-tuk-ku''. name xor cipher_num 13 key_size 128 bits block_size 64 bits state/ksch 4 bytes name idea-cbc cipher_num 2 key_size 128 bits block_size 64 bits state/ksch 432 bytes name cast-cbc cipher_num 1 key_size 128 bits block_size 64 bits state/ksch 132 bytes name ssl-rc2-cbc cipher_num 11 key_size 128 bits block_size 64 bits state/ksch 8196 bytes name ssl-blowfish-cbc cipher_num 5 key_size 448 bits block_size 64 bits 1 mlist(1) mlist(1) state/ksch 8196 bytes name ssl-rc4 cipher_num 12 key_size 2048 bits block_size 0 bits (stream cipher) state/ksch 8196 bytes name ssl-idea-cbc cipher_num 10 key_size 128 bits block_size 64 bits state/ksch 8196 bytes name ssl-des-cbc cipher_num 6 key_size 64 bits (56 bits real) block_size 64 bits state/ksch 8196 bytes name ssl-des-ede-cbc cipher_num 7 key_size 128 bits (112 bits real) block_size 64 bits state/ksch 8196 bytes name ssl-des-ede3-cbc cipher_num 8 key_size 192 bits (168 bits real) block_size 64 bits state/ksch 8196 bytes name ssl-desx-cbc cipher_num 9 key_size 192 bits (168 bits real) block_size 64 bits state/ksch 8196 bytes name rc16 cipher_num 3 key_size 2048 bits block_size 0 bits (stream cipher) state/ksch 131080 bytes ENVIROMENT MARU_PASSPHRASE Use the contents of this variable instead of prompting for a pass-phrase. COPYRIGHT Copyright 1997 Julian Assange , All rights reserved. AUTHOR Julian Assange . SEE ALSO hose(1), mnewiv(1), mcreate(1), mwipe(1), mattach(1), maset(1), msetkey(1), mclearkey(1), mdetach(1), mdecrypt(1), mgetopt(1), msetopt(1), 2 mlist(1) mlist(1) mstats(1), minfo(1), mlist(1). From owner-freebsd-hackers Sat Nov 22 07:02:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA09362 for hackers-outgoing; Sat, 22 Nov 1997 07:02:27 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from callisto.fortean.com (callisto.fortean.com [206.142.225.82]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA09355 for ; Sat, 22 Nov 1997 07:02:21 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.5/8.8.5) with SMTP id JAA20695; Sat, 22 Nov 1997 09:58:13 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Sat, 22 Nov 1997 09:58:12 -0500 (EST) From: "Bruce M. Walter" To: Hellmuth Michaelis cc: garyj@muc.de, freebsd-hackers@freefall.FreeBSD.org, isdn-dev@hcs.de Subject: Re: Ascend NetWarp 128 ISDN TA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hellmuth Michaelis writes: > All passive cards currently supported by bisdn and the upcoming isdn4bsd > are based on the Siemens HSCX/ISAC combination, so once you know how the > interfacing of the chips to the ISA/EISA/PCI bus is done, you are done. This part is almost done. Just one or two little bits of info from the card's system engineer are still needed. Is isdn4bsd available yet as a snapshot? If it's replacing bisdn, I'd love to start there instead of having to port my updates into it. > Since the D channel is 3-layerd, it might be possible to reuse some of the > existing protocol support from DSS1 for the US protocols (it basically has > 3 layers, in Europe is it I.430, Q.921 and Q.931 - Layer 1 seems to have > some differences for the US being "not quite" I.430, Layer 2 seems to be > the same but layer 3 has to be written; the difficulty seems that there is > not a single protocol but different phone companies with different switches > seem to have different protocols in the US). You're right on the money here. From what I've been finding at least National N1 and N2 are closely based on Q.931, in fact N1 is a superset of Q.931 by a mere 5 messages. (aside from a few minor implementation differences) As for I.430, I've not been able to find the official ITU spec, so I'm shooting in the dark for now. My current plan of attack is: 1) Get the teles driver talking to the TA... I figure if I can document the differences it shouldn't be too hard to backfit everything into isdn4bsd when it's out. 2) Get all of the ITU specs and contrast them with the US specs... I have Q.921 and Q.931, as well as various US specs. Once I find the differences, I can build off the existing code. Does isdn4bsd use the same disdn pseudo-device model for D channels as bisdn? 3) Add the support code into the disdn driver... 4) Relax and get a life. Reasonable? > Hope this helps, > hellmuth It does... Much! Many Thanks! - Bruce ======================================================================== || Bruce M. Walter || 107 Timber Hollow Court #335 || || Senior Network Consultant || Chapel Hill, NC 27514 || || Fortean Technologies, Inc. || Tel: 919-967-4766 || || Information Technology Consultants || Fax: 919-967-4395 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Sat Nov 22 10:14:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17768 for hackers-outgoing; Sat, 22 Nov 1997 10:14:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17763 for ; Sat, 22 Nov 1997 10:14:50 -0800 (PST) (envelope-from batie@agora.rdrop.com) Received: (from batie@localhost) by agora.rdrop.com (8.8.5/8.8.5) id KAA29003; Sat, 22 Nov 1997 10:14:47 -0800 (PST) Message-ID: <19971122101447.61698@agora.rdrop.com> Date: Sat, 22 Nov 1997 10:14:47 -0800 From: Alan Batie To: hackers@freebsd.org Subject: Hot upgrades Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=EJdfMPwZcMS1vKFf X-Mailer: Mutt 0.76 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --EJdfMPwZcMS1vKFf Content-Type: text/plain; charset=us-ascii > From: Charles Henrich > Date: Fri, 21 Nov 1997 12:24:31 -0500 > Subject: Re: Serious performance issue with 2.2.5-RELEASE > > I understand that. Hot-Upgrading (by which I mean doing a complete OS install > on top of my filesystem after booting from the install floppy) can cause > strange problems that cease to exist if you clean upgrade... I havent run into > a problem doing this with FreeBSD yet however.. I just hot-upgraded my laptop from 2.1-PAO to 2.2.5, and now it's off the net --- it seems that the pccard driver no longer accepts "default" and "any" for interrupts and memory locations, but wants specific numbers. Which seems like a big step backwards if you ask me, but I haven't yet gotten a chance to track down what's going on, so don't consider this a bug report or a complaint yet (unless you know for sure that this was what was supposed to happen :-) ). On a production system, I would never hot upgrade... -- Alan Batie ______ It's not my fault! It's some guy batie@agora.rdrop.com \ / named "General Protection"! +1 503 452-0960 \ / --Ratbert PGP FP: DE 3C 29 17 C0 49 \/ 7A 27 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. --EJdfMPwZcMS1vKFf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNHchFov4wNua7QglAQExjwP/dXJhYhWvRIEGMiHF+7xCzasNCeHzvQSp ZNl5Yb0NiQ8j1egcWZWL+BvMKRHbdGF/qAAv0HRKMM9PNHRInz1kK+8Kmu8VQQOy 4i3mwA8y+q593Y9y6JpN+Y13++f7pcjw23EsN2gdNA12dXER3qWRugMHl7ydXJB8 3Q26Bt1l1mc= =4FMo -----END PGP SIGNATURE----- --EJdfMPwZcMS1vKFf-- From owner-freebsd-hackers Sat Nov 22 13:19:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26843 for hackers-outgoing; Sat, 22 Nov 1997 13:19:15 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26835 for ; Sat, 22 Nov 1997 13:19:12 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA02229; Sat, 22 Nov 1997 14:19:03 -0700 (MST) From: Terry Lambert Message-Id: <199711222119.OAA02229@usr01.primenet.com> Subject: Re: Upgrade function and root dir To: ulf@Alameda.net (Ulf Zimmermann) Date: Sat, 22 Nov 1997 21:19:02 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199711220847.AAA12954@Gatekeeper.Alameda.net> from "Ulf Zimmermann" at Nov 22, 97 00:47:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Would it be possible to change the upgrade function, so that is not > necessary overwrites the dot files in /root ? I always save it, but > it would be one step less ;-) Don't modify root's .-files. Modify the .-files as another user and su instead. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Nov 22 13:38:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA27978 for hackers-outgoing; Sat, 22 Nov 1997 13:38:48 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA27970 for ; Sat, 22 Nov 1997 13:38:45 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09250; Sat, 22 Nov 1997 13:40:53 -0800 (PST) Message-Id: <199711222140.NAA09250@implode.root.com> To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-reply-to: Your message of "Thu, 20 Nov 1997 12:17:36 PST." From: David Greenman Reply-To: dg@root.com Date: Sat, 22 Nov 1997 13:40:53 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in >July. > >Big mistake. > >The only update to take place was the make buildworld, make installworld, >no other configuration files were modified, nor any changes to startup >scripts, etc. > >I now get these weird pauses where everything on the machine just freezes >for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > >The system was a web server, and was happily serving up several hundred >domains. Now with the upgrade, I'll be lucky to keep them. Not good. > >It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > >Any ideas appreciated. I have built a new kernel from sources supped >11/7, but it doesn't seem to be any better. Is it possible that the slowness could actually be a network related problem involving the updated 'de' driver in 2.2.5? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Nov 22 14:37:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA00866 for hackers-outgoing; Sat, 22 Nov 1997 14:37:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA00861 for ; Sat, 22 Nov 1997 14:37: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 <53141(1)>; Sat, 22 Nov 1997 14:36:02 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Sat, 22 Nov 1997 14:35:38 -0800 To: Nate Williams cc: bmah@ca.sandia.gov, hackers@freebsd.org Subject: Re: Getting ethernet packets content under FreeBSD? In-reply-to: Your message of "Fri, 21 Nov 97 14:34:22 PST." <199711212234.PAA15870@mt.sri.com> Date: Sat, 22 Nov 1997 14:35:23 PST From: Bill Fenner Message-Id: <97Nov22.143538pst.177476@crevenia.parc.xerox.com> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I usually just use this perl script, which I call "tcpdumpscii". Then run "tcpdumpscii -s 1500 -x [other tcpdump args]". Bill #!/import/misc/bin/perl # # open(TCPDUMP,"tcpdump -l @ARGV|"); while () { if (/^\s+(\S\S)+/) { $sav = $_; $asc = ""; while (s/\s*(\S\S)\s*//) { $i = hex($1); if ($i < 32 || $i > 126) { $asc .= "."; } else { $asc .= pack(C,hex($1)); } } $foo = "." x length($asc); $_ = $sav; s/\t/ /g; s/^$foo/$asc/; } print; } From owner-freebsd-hackers Sat Nov 22 16:20:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06339 for hackers-outgoing; Sat, 22 Nov 1997 16:20:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA06322 for ; Sat, 22 Nov 1997 16:20:10 -0800 (PST) (envelope-from mburgett@dragon.awen.com) Received: (from mburgett@localhost) by dragon.awen.com (8.8.8/8.8.7) id QAA00917; Sat, 22 Nov 1997 16:20:09 -0800 (PST) Message-Id: <199711230020.QAA00917@dragon.awen.com> From: "Mike Burgett" To: "hackers@freebsd.org" Date: Sat, 22 Nov 97 16:20:08 -0800 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: 3Com info source? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking for programming information from 3com, specifically about the Cardbus Etherlink XL 10/100 (3C575) card. (Information that can be used to write a device driver for this card) I've tried contacting 3com tech support, but haven't heard anything back in about 10 days... I hope someone on this list has a contact that might be able to get the information, or knows were I might start digging/poking/prodding... Thanks, Mike From owner-freebsd-hackers Sat Nov 22 19:42:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA15349 for hackers-outgoing; Sat, 22 Nov 1997 19:42:16 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA15343 for ; Sat, 22 Nov 1997 19:42:13 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id TAA28948; Sat, 22 Nov 1997 19:42:10 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sat, 22 Nov 1997 19:42:09 -0800 (PST) From: Chris Timmons To: Mike Burgett cc: "hackers@freebsd.org" Subject: Re: 3Com info source? In-Reply-To: <199711230020.QAA00917@dragon.awen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Find the number for their faxback service. Look for the document which allows you to request developer information, get that, and then complete it and send it back. In the past 3com has been very cooperative, but you have to find the right people. I just about gave up on their tech support people once and on a whim wrote to a .3com.com person I saw in a newsgroup. Sure enough, they do have a standard procedure for this but it is buried. Hope this helps, -Chris On Sat, 22 Nov 1997, Mike Burgett wrote: > I'm looking for programming information from 3com, specifically about the > Cardbus Etherlink XL 10/100 (3C575) card. (Information that can be used to > write a device driver for this card) > > I've tried contacting 3com tech support, but haven't heard anything back in > about 10 days... > > I hope someone on this list has a contact that might be able to get the > information, or knows were I might start digging/poking/prodding... > > Thanks, > Mike > > From owner-freebsd-hackers Sat Nov 22 22:08:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA21528 for hackers-outgoing; Sat, 22 Nov 1997 22:08:13 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from super.zippo.com (perry.zippo.com [207.211.168.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA21523 for ; Sat, 22 Nov 1997 22:08:11 -0800 (PST) (envelope-from reyesf@super.zippo.com) Received: (from reyesf@localhost) by super.zippo.com (8.8.6/8.8.7) id WAA10580; Sat, 22 Nov 1997 22:08:05 -0800 (PST) Message-Id: <199711230608.WAA10580@super.zippo.com> From: "Francisco Reyes" To: "hackers@FreeBSD.ORG" Date: Sun, 23 Nov 97 01:07:37 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Thanks for the code! (was optimizing HD I/O) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Date: Tue, 18 Nov 1997 21:20:08 +0000 >Subject: Re: Optimizing HD I/O What size to use? Thanks much fo the info and code regarding optimizing disk I/O. From owner-freebsd-hackers Sat Nov 22 22:34:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA22490 for hackers-outgoing; Sat, 22 Nov 1997 22:34:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from lupo.thebarn.com (lupo.lcse.umn.edu [128.101.182.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA22485 for ; Sat, 22 Nov 1997 22:34:52 -0800 (PST) (envelope-from cattelan@lupo.thebarn.com) Received: (from cattelan@localhost) by lupo.thebarn.com (8.8.8/8.8.5) id AAA01033; Sun, 23 Nov 1997 00:34:43 -0600 (CST) Date: Sun, 23 Nov 1997 00:34:43 -0600 (CST) Message-Id: <199711230634.AAA01033@lupo.thebarn.com> From: Russell Cattelan MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@freebsd.org Subject: New VoxWare not working with mpeg players X-Mailer: VM 6.34 under 20.3 "Istanbul" XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently brought my FreeBSD install up to "current" and the new voxware drivers are not working with any of the mpeg players "mpg123" "maplay". I have a Prosonic Jazz16 card, the kernel recognizes the card and but when I try to play music I get patterned static. Jazz16: No MPU401 devices configured - MIDI port not initialized sb0 at 0x220 irq 7 drq 1 on isa NOTE! SB Pro support required with your soundcard! snd0: The only "error" messages I get is on the console: dsp_speed 8000 dsp_speed done 8000 dsp_speed 44100 dsp_speed done 43478 I'm not sure what this means but it does suggest the speed is incorrect. (note the 44100 is correct) Note: the voxware driver was working with 3.0-current as of a early oct build. From owner-freebsd-hackers Sat Nov 22 22:51:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23348 for hackers-outgoing; Sat, 22 Nov 1997 22:51:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23337 for ; Sat, 22 Nov 1997 22:51:49 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id WAA27340; Sat, 22 Nov 1997 22:51:34 -0800 (PST) Date: Sat, 22 Nov 1997 22:51:33 -0800 (PST) From: Jaye Mathisen To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <199711222140.NAA09250@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I do not believe so. What ever it is definitely appears related to swapping/paging somehow. I get these LA spikes in the several hundreds, the disk light is on solid for 2-3 minutes, then it all goes away. System accounting doesn't show any unusual pattern of apps being run. The vast majority are perl scripts. There's about 1100 processes on the machine, give or take a few, with about 80MB RAM free. NFS is compiled in, but not used. I have also disabled ntpd thinking something was hanging there, but no dice. On Sat, 22 Nov 1997, David Greenman wrote: > >I upgraded my web server to 2.2.5 from 2.2.2-stable, dated sometime in > >July. > > > >Big mistake. > > > >The only update to take place was the make buildworld, make installworld, > >no other configuration files were modified, nor any changes to startup > >scripts, etc. > > > >I now get these weird pauses where everything on the machine just freezes > >for 30-40 seconds, sometimes longer. NFS is compiled in, but not in use. > > > >The system was a web server, and was happily serving up several hundred > >domains. Now with the upgrade, I'll be lucky to keep them. Not good. > > > >It's a Super Micro P6, 384MB RAM, 2 SCSI disks off a bus-logic controller. > > > >Any ideas appreciated. I have built a new kernel from sources supped > >11/7, but it doesn't seem to be any better. > > Is it possible that the slowness could actually be a network related > problem involving the updated 'de' driver in 2.2.5? > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > From owner-freebsd-hackers Sat Nov 22 23:38:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25163 for hackers-outgoing; Sat, 22 Nov 1997 23:38:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25158 for ; Sat, 22 Nov 1997 23:38:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.5) with ESMTP id XAA03851; Sat, 22 Nov 1997 23:38:40 -0800 (PST) Message-Id: <199711230738.XAA03851@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Russell Cattelan cc: freebsd-hackers@freebsd.org Subject: Re: New VoxWare not working with mpeg players In-reply-to: Your message of "Sun, 23 Nov 1997 00:34:43 CST." <199711230634.AAA01033@lupo.thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Nov 1997 23:38:39 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The printf messages are just debugging messages which I just nuked. Will work tonite to figured out how to properly handle your card. Amancio From owner-freebsd-hackers Sat Nov 22 23:42:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25411 for hackers-outgoing; Sat, 22 Nov 1997 23:42:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25402 for ; Sat, 22 Nov 1997 23:42:03 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id SAA19794; Sun, 23 Nov 1997 18:39:28 +1100 Date: Sun, 23 Nov 1997 18:39:28 +1100 From: Bruce Evans Message-Id: <199711230739.SAA19794@godzilla.zeta.org.au> To: bde@zeta.org.au, mouth@ibm.net Subject: Re: Status of 650 UART support Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I think you can actually ready bit 7 to see if there is a full fifo >>(with no parity/framing/overrun errors) and, if it is set, read the >>entire fifo before reading the LSR again. This gives close to one I/O >>per input byte. It is a bit tricky to handle error cases and quitting >>properly - we don't want to fall back to two I/O's per input byte. > >The Startech databook makes no mention of LSR bit 7 indicating a full >=46IFO, only a dirty one. Same for all the literature I have on the NS >16550. Oops. It actually gives a summary of the errors in the fifo. This is necessary for avoiding reads of the LSR when the fifo is read all at once. The LSR must still be read before each byte if LSR bit 7 indicates an error. >Apparently you can use the FIFO trigger level to read a block of bytes >without checking LSR bit 0 every time -- the Startech data book even >suggests it. To handle all cases, especially multiport shared >interrupt cards where you don't know which UART generated the receiver >interrupt, you must first check the IIR (Startech calls it the ISR -- >interrupt Status register) to see if the UART generated a received >data interrupt. sio attempts to minimise reads of the IIR, so fitting this in cleanly is tricky. OTOH, the read of the MSR can be avoided if the IIR can be trusted (the current code is designed to avoid IIR bugs in 8250s and 16450s without much cost if the IIR actually works). I was thinking of an extra read of the IIR when I mentioned tricky error handling. The simplest approach leads to 3 i/o's per byte of input instead of 2 (IIR, LSR, RXDATA) instrad of (LSR, RXDATA). >After emptying the block, you could leave any remaining characters in >the FIFO, and simply get them on the next interrupt, avoiding the need >of checking LSR bit 0 for bytes beyond the block size. Here is some (low quality, old and unfinished) code for doing this. It has some interface changes (void *vcom, and siointr1() called directly from XintrN()) that won't work in -current. The behaviour is controlled by global variables sio_iir and sio_stream. Setting sio_iir gives more use of the IIR and setting sio_stream gives bulk processing of the input fifo. sio_iir is probably required if sio_stream is used and is probably a pessimization otherwise. Bruce diff -c2 sio.c~ sio.c *** sio.c~ Fri Nov 21 19:36:47 1997 --- sio.c Fri Nov 21 19:36:49 1997 *************** *** 1407,1421 **** } ! void ! siointr(unit) ! int unit; { ! #ifndef COM_MULTIPORT ! COM_LOCK(); ! siointr1(com_addr(unit)); ! COM_UNLOCK(); ! #else /* COM_MULTIPORT */ ! struct com_s *com; bool_t possibly_more_intrs; /* --- 1423,1436 ---- } ! #ifdef COM_MULTIPORT ! static void ! siointr(vcom) ! void *vcom; { ! struct com_s *com; bool_t possibly_more_intrs; + int unit; + + com = vcom; /* *************** *** 1440,1444 **** != IIR_NOPEND) { siointr1(com); ! possibly_more_intrs = TRUE; } /* XXX COM_UNLOCK(); */ --- 1455,1460 ---- != IIR_NOPEND) { siointr1(com); ! if (!siointr1_looping) ! possibly_more_intrs = TRUE; } /* XXX COM_UNLOCK(); */ *************** *** 1446,1470 **** } while (possibly_more_intrs); COM_UNLOCK(); - #endif /* COM_MULTIPORT */ } static void ! siointr1(com) ! struct com_s *com; { u_char line_status; u_char modem_status; u_char *ioptr; u_char recv_data; while (TRUE) { line_status = inb(com->line_status_port); /* input event? (check first to help avoid overruns) */ while (line_status & LSR_RCV_MASK) { /* break/unnattached error bits or real input? */ if (!(line_status & LSR_RXRDY)) recv_data = 0; else recv_data = inb(com->data_port); if (line_status & (LSR_BI | LSR_FE | LSR_PE)) { --- 1462,1527 ---- } while (possibly_more_intrs); COM_UNLOCK(); } + #endif /* COM_MULTIPORT */ static void ! siointr1(vcom) ! void *vcom; { + struct com_s *com; + u_char iir; u_char line_status; u_char modem_status; u_char *ioptr; u_char recv_data; + int streaming; + + com = vcom; + /* + * siointr1_looping is used to determine if siointr1() is looping + * without doing anything. If COM_MULTIPORT then assume we + * would loop if nothing is done since we only run through + * once and can not detect it ourselves. + */ + #ifdef COM_MULTIPORT + siointr1_looping = TRUE; + #else + siointr1_looping = FALSE; + #endif + if (sio_iir) { + iir = inb(com->int_id_port) & IIR_IMASK; + if (iir == IIR_RXTOUT) + goto rxrdy; + if (iir == IIR_RXRDY) + goto rxrdy; + if (iir == IIR_RLS) + goto rxrdy; + goto mlsc; + } while (TRUE) { + rxrdy: line_status = inb(com->line_status_port); + streaming = 0; /* input event? (check first to help avoid overruns) */ while (line_status & LSR_RCV_MASK) { + int i; + + for (i = 0; i < fifo_delay; ++i) + inb(com->data_port + 7); + siointr1_looping = FALSE; + if (sio_stream && streaming == 0 && com->hasfifo + && !(line_status & LSR_RCV_FIFO)) { + if (!sio_iir) + iir = inb(com->int_id_port) & IIR_IMASK; + if (iir == IIR_RXRDY) + streaming = 14; + } /* break/unnattached error bits or real input? */ if (!(line_status & LSR_RXRDY)) recv_data = 0; else + more_rx: recv_data = inb(com->data_port); if (line_status & (LSR_BI | LSR_FE | LSR_PE)) { *************** *** 1527,1530 **** --- 1584,1591 ---- } cont: + if (streaming != 0 && --streaming != 0) + goto more_rx; + if (sio_iir) + goto loop; /* * "& 0x7F" is to avoid the gcc-1.40 generating a slow *************** *** 1534,1540 **** --- 1595,1603 ---- } + mlsc: /* modem status change? (always check before doing output) */ modem_status = inb(com->modem_status_port); if (modem_status != com->last_modem_status) { + siointr1_looping = FALSE; if (com->do_dcd_timestamp && !(com->last_modem_status & MSR_DCD) *************** *** 1564,1570 **** --- 1627,1635 ---- } + txrdy: /* output queued and everything ready? */ if (line_status & LSR_TXRDY && com->state >= (CS_BUSY | CS_TTGO | CS_ODEVREADY)) { + siointr1_looping = FALSE; ioptr = com->obufq.l_head; if (com->tx_fifo_size > 1) { *************** *** 1600,1613 **** com_events += LOTS_OF_EVENTS; com->state |= CS_ODONE; ! setsofttty(); /* handle at high level ASAP */ } } } /* finished? */ #ifndef COM_MULTIPORT if ((inb(com->int_id_port) & IIR_IMASK) == IIR_NOPEND) - #endif /* COM_MULTIPORT */ return; } } --- 1665,1706 ---- com_events += LOTS_OF_EVENTS; com->state |= CS_ODONE; ! ! /* handle at high level ASAP */ ! setsofttty(); } } } + loop: + if (sio_iir) { + iir = inb(com->int_id_port) & IIR_IMASK; + if (iir == IIR_NOPEND) + return; + if (iir == IIR_RXTOUT) + goto rxrdy; + if (iir == IIR_RXRDY) + goto rxrdy; + if (iir == IIR_RLS) + goto rxrdy; + if (iir == IIR_MLSC) + goto mlsc; + if (iir == IIR_TXRDY) + goto txrdy; + } + /* finished? */ #ifndef COM_MULTIPORT if ((inb(com->int_id_port) & IIR_IMASK) == IIR_NOPEND) return; + /* + * If the device says we should be doing something but we + * aren't, exit or else we may never return. + */ + if (sio_loop_test && siointr1_looping) + return; + siointr1_looping = TRUE; + #else + return; + #endif } }