From owner-freebsd-current Sun Jul 5 07:39:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11104 for freebsd-current-outgoing; Sun, 5 Jul 1998 07:39:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11096 for ; Sun, 5 Jul 1998 07:39:28 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id AAA24273 for ; Mon, 6 Jul 1998 00:09:28 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA16289; Mon, 6 Jul 1998 00:09:27 +0930 Date: Mon, 6 Jul 1998 00:09:27 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: current@FreeBSD.ORG Subject: inetd problems Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting the following on my smtp port when I connect to it: [morden|kkenn] 0:05 ~ telnet localhost smtp Trying 127.0.0.1... Connected to localhost.rebel.net.au. Escape character is '^]'. inetd in realloc(): warning: junk pointer, too low to make sense. 220 morden.net.au ESMTP I recall noticing this some time ago as well, but didnt look into it any further - but I'm currently having intermittent problems delivering messages via smtp, and this is possibly related. [morden|kkenn] 0:08 ~ ls -l /usr/sbin/inetd -r-xr-xr-x 1 bin bin 24576 Jun 21 22:18 /usr/sbin/inetd* (A diff between this and a copy compiled from current sources shows no differences) Any ideas? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 09:34:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19924 for freebsd-current-outgoing; Sun, 5 Jul 1998 09:34:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eecis.udel.edu (ren.eecis.udel.edu [128.175.7.13]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA19919 for ; Sun, 5 Jul 1998 09:34:26 -0700 (PDT) (envelope-from <@eecis.udel.edu:alexandr@ren.eecis.udel.edu>) Date: Sun, 5 Jul 1998 09:34:26 -0700 (PDT) From: "<"<@eecis.udel.edu:alexandr@ren.eecis.udel.edu> Message-Id: <199807051634.JAA19919@hub.freebsd.org> Received: from localhost by eecis.udel.edu id aa07502; 5 Jul 1998 12:34 EDT To: John Birrell Cc: Open Systems Networking , freebsd-current@FreeBSD.ORG Subject: RE: Ports breakage. Organization: Mos Eisley Candy Store Reply-To: alexandr@louie.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Sun, 05 Jul 1998 08: 56:09 +1000 Date: Sun, 05 Jul 1998 12:34:14 -0400 From: Jerry Alexandratos Message-ID: <199807051234.aa07502@eecis.udel.edu> John Birrell says: : Open Systems Networking wrote: : > : > Im gonna get fried for this but some of the ports for me are breaking like : > xpilot with: [stuff deleted] : Check if you've got an old libc in /usr/lib and the new one in /usr/lib/aout. : I've seen this sort of thing when a port compiles against the new headers, : but links against the old libc due to the configure script "searching" : /usr/lib. So what's the best way to clean up /usr/lib if it's got the old versions in there? Is there some option that can be used during a "make world"? Thanks in advance. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 09:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21150 for freebsd-current-outgoing; Sun, 5 Jul 1998 09:46:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21142 for ; Sun, 5 Jul 1998 09:46:10 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA06364; Mon, 6 Jul 1998 02:46:00 +1000 Date: Mon, 6 Jul 1998 02:46:00 +1000 From: Bruce Evans Message-Id: <199807051646.CAA06364@godzilla.zeta.org.au> To: mike@smith.net.au, netchild@wurzelausix.cs.uni-sb.de Subject: Re: Kernel panic, solved! + question Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've solved my problem, I had >> config kernel swap on generic >> in my kernel, after changing it to >> config kernel root on sd0s2 >> the new kernel bootet without a panic. >> >> Q: Why did my old kernel boot, and the new one didn't? > >'on generic' is Evil. I always use it. It works fine, but has no effect unless you boot with -a or the kernel can't find a root device in the normal way (when it would panic outside of setconf()). Are you using any other nonstandard options? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 09:52:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02328 for freebsd-current-outgoing; Sun, 5 Jul 1998 09:52:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27296 for ; Sun, 5 Jul 1998 09:52:31 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id MAA27365; Sun, 5 Jul 1998 12:45:52 -0400 (EDT) Date: Sun, 5 Jul 1998 12:52:27 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: alexandr@louie.udel.edu cc: freebsd-current@FreeBSD.ORG Subject: RE: Ports breakage. In-Reply-To: <199807051627.MAA25236@mail.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Jul 1998, < wrote: > So what's the best way to clean up /usr/lib if it's got the old versions > in there? Is there some option that can be used during a "make world"? Move all the /usr/lib libraries into /usr/lib/old in case the ports break and you need them. I was told. And once ELF is finished the ELF libs will go into /usr/lib and everything will be 100% peachy again. It's just a transistional phase right now. I got bit cause I have not done a make world in a LONG time in "current time". And that is what bit me. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 09:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19810 for freebsd-current-outgoing; Sun, 5 Jul 1998 09:53:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA13975 for ; Sun, 5 Jul 1998 09:53:08 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA14927; Sun, 5 Jul 1998 12:56:09 -0400 From: Bill Paul Message-Id: <199807051656.MAA14927@skynet.ctr.columbia.edu> Subject: Re: inetd problems To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Sun, 5 Jul 1998 12:56:08 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Kris Kennaway" at Jul 6, 98 00:09:27 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Kris Kennaway had to walk into mine and say: > I'm getting the following on my smtp port when I connect to it: > > [morden|kkenn] 0:05 ~ telnet localhost smtp > Trying 127.0.0.1... > Connected to localhost.rebel.net.au. > Escape character is '^]'. > inetd in realloc(): warning: junk pointer, too low to make sense. > 220 morden.net.au ESMTP > > I recall noticing this some time ago as well, but didnt look into it any > further - but I'm currently having intermittent problems delivering messages > via smtp, and this is possibly related. > > [morden|kkenn] 0:08 ~ ls -l /usr/sbin/inetd > -r-xr-xr-x 1 bin bin 24576 Jun 21 22:18 /usr/sbin/inetd* > > (A diff between this and a copy compiled from current sources shows no > differences) > > Any ideas? Hm. You know, I've been watching messages like this go by (people getting noise from inetd about malloc()/realloc()/free() problems) and I can't help but wonder why nobody has really sat down and tried to debug things thoroughly. I encounter messages like this occasionally with my own code (mostly NIS+ stuff) and without exception, the cause has always been some kind of bug on my part (double free(), free()ing static buffers by mistake, corrupting the heap by wandering past the end of a malloc()ed buffer, etc...). All the theories I've heard so far point to some kind of VM problem; nobody as yet has been willing to admit that the problem is a bug in inetd. I've found that the best thing for nailing these kinds of bugs is Electric Fence and gdb. Recompile inetd with -g, link it with Electric Fence, and run it, then see if you can get it to explode. Once it dumps core, gdb will tell you exactly where the real problem is (alternatively, you can attach to the running instance of inetd with gdb and catch the crash immediately). I should point out however that I'm uncertain that the particular problem you're seeing is actually being caused by inetd. It seems unusual that inetd would give you such a message for a simple thing like spawing an smtp process for you, so I'm wondering if maybe the error message about realloc() isn't coming from the smtp server instead, and it only _says_ inetd because inetd was the parent process that launched smtpd. (It shouldn't do that of course, but anything's possible.) More details would help here: under what conditions does this problem occur? Do you see the 'realloc' error all the time, or just when the system is heavily loaded? Exactly what smtp server is this? How many users does the server handle mail for? Can you debug this by recompiling inetd with the Electric Fence library and analyzing the crash dump? If not, can you at least provide a recipe for duplicating the bug so that someone else can try debugging it? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 09:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02270 for freebsd-current-outgoing; Sun, 5 Jul 1998 09:58:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01139 for ; Sun, 5 Jul 1998 09:58:52 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA05506; Sun, 5 Jul 1998 09:59:12 -0700 (PDT) Message-Id: <199807051659.JAA05506@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: inetd problems In-reply-to: Your message of "Mon, 06 Jul 1998 00:09:27 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 09:59:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm getting the following on my smtp port when I connect to it: > > [morden|kkenn] 0:05 ~ telnet localhost smtp > Trying 127.0.0.1... > Connected to localhost.rebel.net.au. > Escape character is '^]'. > inetd in realloc(): warning: junk pointer, too low to make sense. > 220 morden.net.au ESMTP It's due to a bug in inetd that nobody has chased down yet; it often shows up after you run the system out of virtual memory. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 10:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05457 for freebsd-current-outgoing; Sun, 5 Jul 1998 10:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01988 for ; Sun, 5 Jul 1998 10:10:54 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA05231; Sun, 5 Jul 1998 09:30:31 -0700 (PDT) Message-Id: <199807051630.JAA05231@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: small locking patch for discussion In-reply-to: Your message of "Sat, 04 Jul 1998 14:58:11 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 09:30:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have this litle patch sitting around. > > > I don't know if it does anything but could someone who > knows about the locking comment? > > It was a "BTW" from terry and I'd like to either > commit it or throw it away, rather than have it > sitting there looking at me.. If you commit it, make sure you add a comment in VFSOP_RELOAD referring to it to make the comment reflexive. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 10:11:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17209 for freebsd-current-outgoing; Sun, 5 Jul 1998 10:11:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14616 for ; Sun, 5 Jul 1998 10:11:24 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA05583; Sun, 5 Jul 1998 10:11:36 -0700 (PDT) Message-Id: <199807051711.KAA05583@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, netchild@wurzelausix.cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: Kernel panic, solved! + question In-reply-to: Your message of "Mon, 06 Jul 1998 02:46:00 +1000." <199807051646.CAA06364@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Jul 1998 10:11:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I've solved my problem, I had > >> config kernel swap on generic > >> in my kernel, after changing it to > >> config kernel root on sd0s2 > >> the new kernel bootet without a panic. > >> > >> Q: Why did my old kernel boot, and the new one didn't? > > > >'on generic' is Evil. > > I always use it. It works fine, but has no effect unless you boot > with -a or the kernel can't find a root device in the normal way > (when it would panic outside of setconf()). Are you using any > other nonstandard options? That's not entirely correct, at least not as I read/experience it. If you don't boot with -a, it looks for the first disk on its list (wd, sd, etc.) and decides that root must be on that disk. This looses for lots of configurations. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 10:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29839 for freebsd-current-outgoing; Sun, 5 Jul 1998 10:19:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27768 for ; Sun, 5 Jul 1998 10:19:28 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA07540; Mon, 6 Jul 1998 03:19:29 +1000 Date: Mon, 6 Jul 1998 03:19:29 +1000 From: Bruce Evans Message-Id: <199807051719.DAA07540@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: Kernel panic, solved! + question Cc: current@FreeBSD.ORG, netchild@wurzelausix.cs.uni-sb.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >'on generic' is Evil. >> >> I always use it. It works fine, but has no effect unless you boot >> with -a or the kernel can't find a root device in the normal way >> (when it would panic outside of setconf()). Are you using any >> other nonstandard options? > >That's not entirely correct, at least not as I read/experience it. > >If you don't boot with -a, it looks for the first disk on its list (wd, >sd, etc.) and decides that root must be on that disk. This looses for >lots of configurations. Read closer. It only searches when rootdev != NODEV. If rootdev == NODEV, then mountroot would fail if `on generic' were not configured, so `on generic' should at worst help avoid failed mountroots (it only helps much when booting with -a, since the disks in its list are less likely to work than the one booted from). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24150 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:33:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24109 for ; Sun, 5 Jul 1998 13:33:18 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id TAA08756; Sun, 5 Jul 1998 19:45:49 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id TAA02169; Sun, 5 Jul 1998 19:43:11 +0200 (CEST) Date: Sun, 5 Jul 1998 19:43:10 +0200 (CEST) From: Blaz Zupan To: Bill Paul cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems In-Reply-To: <199807051656.MAA14927@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > More details would help here: under what conditions does this > problem occur? Do you see the 'realloc' error all the time, or just > when the system is heavily loaded? Exactly what smtp server is this? > How many users does the server handle mail for? Can you debug this > by recompiling inetd with the Electric Fence library and analyzing > the crash dump? If not, can you at least provide a recipe for > duplicating the bug so that someone else can try debugging it? I had a stupid router box running 2.2.5 with 4MB RAM (yeah, it's possible) which has been recently upgraded to 8MB (amazing, isn't it? :) and after telneting about 5-6 times into the box, the next try I try to telnet in I get the same message. So I guess the best way to reproduce this bug is just to run out of memory. Or install a box with little or no ram and little or no swap and start a couple of bigger processes and then telnet in a couple of times. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00347 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:40:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00300 for ; Sun, 5 Jul 1998 13:40:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA22619; Sun, 5 Jul 1998 13:30:16 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd022614; Sun Jul 5 20:30:08 1998 Date: Sun, 5 Jul 1998 13:30:04 -0700 (PDT) From: Julian Elischer To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: small locking patch for discussion In-Reply-To: <199807051959.PAA20741@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was not aware that it did it that way.. I'm just using pine.. I though it had done it 'plain text' here's the patch Index: ufs/ufs/ufs_quota.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_quota.c,v retrieving revision 1.23 diff -c -r1.23 ufs_quota.c *** ufs_quota.c 1998/06/21 14:53:40 1.23 --- ufs_quota.c 1998/07/04 20:39:16 *************** *** 465,478 **** /* * Search vnodes associated with this mount point, * deleting any references to quota file being closed. */ again: for (vp = mp->mnt_vnodelist.lh_first; vp != NULL; vp = nextvp) { nextvp = vp->v_mntvnodes.le_next; if (vp->v_type == VNON) continue; ! if (vget(vp, LK_EXCLUSIVE, p)) goto again; ip = VTOI(vp); dq = ip->i_dquot[type]; ip->i_dquot[type] = NODQUOT; --- 465,489 ---- /* * Search vnodes associated with this mount point, * deleting any references to quota file being closed. + * + * This is nearly identical to code in VFSOP_RELOAD, and + * *must* be maintained in parallel! */ again: + simple_lock(&mntvnode_slock); for (vp = mp->mnt_vnodelist.lh_first; vp != NULL; vp = nextvp) { + if (vp->v_mount != mp) { + simple_unlock(&mntvnode_slock); + goto again; + } nextvp = vp->v_mntvnodes.le_next; if (vp->v_type == VNON) continue; ! simple_lock(&vp->v_interlock); ! simple_unlock(&mntvnode_slock); ! if (vget(vp, LK_EXCLUSIVE | LK_INTERLOCK, p)) { goto again; + } ip = VTOI(vp); dq = ip->i_dquot[type]; ip->i_dquot[type] = NODQUOT; *************** *** 480,485 **** --- 491,497 ---- vput(vp); if (vp->v_mntvnodes.le_next != nextvp || vp->v_mount != mp) goto again; + simple_lock(&mntvnode_slock); } dqflush(qvp); qvp->v_flag &= ~VSYSTEM; #########------- On Sun, 5 Jul 1998, Garrett Wollman wrote: > < said: > > > --0-1966150496-899589491=:10069 > > Content-Type: TEXT/PLAIN; charset=US-ASCII; name=quotadiff > > Content-Transfer-Encoding: BASE64 > > Content-ID: > > Content-Description: > > Please explain to the authors of your MUA that base64-encoded US-ASCII > is an unspeakable evil. I would probably have read this patch were it > actually readable. > > > SW5kZXg6IHVmcy91ZnMvdWZzX3F1b3RhLmMNCj09PT09PT09PT09PT09PT09 > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02805 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:51:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.net (root@engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02702 for ; Sun, 5 Jul 1998 13:51:38 -0700 (PDT) (envelope-from brandon@engulf.net) Received: from localhost (brandon@localhost) by engulf.net (8.8.8/8.8.8) with SMTP id OAA17292 for ; Sun, 5 Jul 1998 14:48:15 -0400 (EDT) Date: Sun, 5 Jul 1998 14:47:38 -0400 (EDT) From: Brandon Lockhart To: current@FreeBSD.ORG Subject: QuickCAM question. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just downloaded the software "cqcam-0.45a" to use on my FreeBSD 3.0-CURRENT machine. Now, I know the software will most likely not work without a reboot, but here is a big issue, will I have to add anything into my kernel? If so, I can just patch it in and reboot, if not I will just wait until necessary. So, can someone help me with this? ,-----------------------------------------------------------------. | //// "Anything I say represents only my opinion." | | (o o) / | | ,---ooO--(_)--Ooo---------------------------------------------, | | | BRANDON LOCKHART | | | `-------------------------------------------------------------' | | brandon.lockhart@usinternetworking.com brandon@engulf.net | | Work: (410) 897-4551 Pager: (888) xxx-xxxx | `-----------------------------------------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02985 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:52:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gwinnett.com (root@mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02957 for ; Sun, 5 Jul 1998 13:52:10 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from gwinnett.com ([204.89.227.91]) by mail.gwinnett.com (8.8.7/8.8.5) with ESMTP id OAA16596 for ; Sun, 5 Jul 1998 14:00:17 -0400 Message-ID: <359FBF1C.18B9A00F@gwinnett.com> Date: Sun, 05 Jul 1998 13:59:56 -0400 From: Lee Reese X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980620-SNAP i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: .jpg Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can display *.gif images with xv. However, when I try to display *.jpg image, I get "Couldn't load the file '/tmp/leah564.jpg'. Wrong JPEG library version: library is 62, caller expect 61. Could someone on this list help me with this problem? Thanks. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:52:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03102 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:52:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (root@ts01-44.waterford.indigo.ie [194.125.139.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03005 for ; Sun, 5 Jul 1998 13:52:25 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id VAA04596; Sun, 5 Jul 1998 21:32:24 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807052032.VAA04596@indigo.ie> Date: Sun, 5 Jul 1998 21:32:21 +0000 In-Reply-To: Bill Paul "Re: inetd problems" (Jul 5, 12:56pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Bill Paul , kkennawa@physics.adelaide.edu.au (Kris Kennaway) Subject: Re: inetd problems Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 5, 12:56pm, Bill Paul wrote: } Subject: Re: inetd problems > > I encounter messages like this occasionally with my own code (mostly > NIS+ stuff) and without exception, the cause has always been some > kind of bug on my part (double free(), free()ing static buffers by > mistake, corrupting the heap by wandering past the end of a malloc()ed > buffer, etc...). All the theories I've heard so far point to some > kind of VM problem; nobody as yet has been willing to admit that > the problem is a bug in inetd. Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 you'll see why, it doesn't look like it's inetd's fault since other services fail at the same time. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 13:55:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04067 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:55:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04030 for ; Sun, 5 Jul 1998 13:55:35 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id PAA20741; Sun, 5 Jul 1998 15:59:53 -0400 (EDT) (envelope-from wollman) Date: Sun, 5 Jul 1998 15:59:53 -0400 (EDT) From: Garrett Wollman Message-Id: <199807051959.PAA20741@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: small locking patch for discussion In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > --0-1966150496-899589491=:10069 > Content-Type: TEXT/PLAIN; charset=US-ASCII; name=quotadiff > Content-Transfer-Encoding: BASE64 > Content-ID: > Content-Description: Please explain to the authors of your MUA that base64-encoded US-ASCII is an unspeakable evil. I would probably have read this patch were it actually readable. > SW5kZXg6IHVmcy91ZnMvdWZzX3F1b3RhLmMNCj09PT09PT09PT09PT09PT09 -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 14:00:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05917 for freebsd-current-outgoing; Sun, 5 Jul 1998 14:00:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05875 for ; Sun, 5 Jul 1998 14:00:34 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA16342; Mon, 6 Jul 1998 07:13:07 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807052113.HAA16342@cimlogic.com.au> Subject: Re: Ports breakage. In-Reply-To: <199807051634.JAA19919@hub.freebsd.org> from "owner-freebsd-current@FreeBSD.ORG" at "Jul 5, 98 09:34:26 am" To: alexandr@louie.udel.edu Date: Mon, 6 Jul 1998 07:13:06 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG owner-freebsd-current@FreeBSD.ORG wrote: > So what's the best way to clean up /usr/lib if it's got the old versions > in there? Is there some option that can be used during a "make world"? Make world can't really clean things out of /usr/lib because it has no simple way to determine what is used and what is not. On my -current system, /usr/lib has just aout and compat sub-directories. I haven't built ELF since upgrading from a clean 2.2.6-RELEASE installation. I built selected ports on this system after the upgrade and subsequent cleanup, so I didn't suffer any ports breakage doing this. YMMV unless you cleanup all installed ports and build them again. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 14:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13050 for freebsd-current-outgoing; Sun, 5 Jul 1998 14:40:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (fullermd@shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13010 for ; Sun, 5 Jul 1998 14:40:28 -0700 (PDT) (envelope-from fullermd@shell.futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id QAA06953; Sun, 5 Jul 1998 16:39:36 -0500 (CDT) Message-ID: <19980705163936.43005@futuresouth.com> Date: Sun, 5 Jul 1998 16:39:36 -0500 From: "Matthew D. Fuller" To: Blaz Zupan Cc: Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems References: <199807051656.MAA14927@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Blaz Zupan on Sun, Jul 05, 1998 at 07:43:10PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 05, 1998 at 07:43:10PM +0200, Blaz Zupan woke me up to tell me: > > More details would help here: under what conditions does this > > problem occur? Do you see the 'realloc' error all the time, or just > > when the system is heavily loaded? Exactly what smtp server is this? > > How many users does the server handle mail for? Can you debug this > > by recompiling inetd with the Electric Fence library and analyzing > > the crash dump? If not, can you at least provide a recipe for > > duplicating the bug so that someone else can try debugging it? > > I had a stupid router box running 2.2.5 with 4MB RAM (yeah, it's possible) > which has been recently upgraded to 8MB (amazing, isn't it? :) and after > telneting about 5-6 times into the box, the next try I try to telnet in I > get the same message. So I guess the best way to reproduce this bug is > just to run out of memory. Or install a box with little or no ram and > little or no swap and start a couple of bigger processes and then telnet > in a couple of times. Or open up Netscape, load a page with a couple of animated GIF's, and go home for the night. It'll just keep allocating more memory for the gif until it eats everything. No, of course I haven't done this! ;) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 15:03:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24150 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:33:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24109 for ; Sun, 5 Jul 1998 13:33:18 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id TAA08756; Sun, 5 Jul 1998 19:45:49 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id TAA02169; Sun, 5 Jul 1998 19:43:11 +0200 (CEST) Date: Sun, 5 Jul 1998 19:43:10 +0200 (CEST) From: Blaz Zupan To: Bill Paul cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems In-Reply-To: <199807051656.MAA14927@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > More details would help here: under what conditions does this > problem occur? Do you see the 'realloc' error all the time, or just > when the system is heavily loaded? Exactly what smtp server is this? > How many users does the server handle mail for? Can you debug this > by recompiling inetd with the Electric Fence library and analyzing > the crash dump? If not, can you at least provide a recipe for > duplicating the bug so that someone else can try debugging it? I had a stupid router box running 2.2.5 with 4MB RAM (yeah, it's possible) which has been recently upgraded to 8MB (amazing, isn't it? :) and after telneting about 5-6 times into the box, the next try I try to telnet in I get the same message. So I guess the best way to reproduce this bug is just to run out of memory. Or install a box with little or no ram and little or no swap and start a couple of bigger processes and then telnet in a couple of times. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 15:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19455 for freebsd-current-outgoing; Sun, 5 Jul 1998 15:15:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19367 for ; Sun, 5 Jul 1998 15:14:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id AAA10405; Mon, 6 Jul 1998 00:11:19 +0200 (CEST) To: rotel@indigo.ie cc: Bill Paul , kkennawa@physics.adelaide.edu.au (Kris Kennaway), current@FreeBSD.ORG Subject: Re: inetd problems In-reply-to: Your message of "Sun, 05 Jul 1998 21:32:21 -0000." <199807052032.VAA04596@indigo.ie> Date: Mon, 06 Jul 1998 00:11:18 +0200 Message-ID: <10403.899676678@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807052032.VAA04596@indigo.ie>, Niall Smart writes: >On Jul 5, 12:56pm, Bill Paul wrote: >} Subject: Re: inetd problems >> >> I encounter messages like this occasionally with my own code (mostly >> NIS+ stuff) and without exception, the cause has always been some >> kind of bug on my part (double free(), free()ing static buffers by >> mistake, corrupting the heap by wandering past the end of a malloc()ed >> buffer, etc...). All the theories I've heard so far point to some >> kind of VM problem; nobody as yet has been willing to admit that >> the problem is a bug in inetd. > >Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 >you'll see why, it doesn't look like it's inetd's fault since other >services fail at the same time. There are two problems here, at least as far as my diagnosis goes: 1: kernel/VM problem means that you run out of memory and eventually malloc(3) may fail. 2: inetd probelm inetd doesn't correctly handle some exception conditions, maybe related to malloc(3) failing for the above or other reasons. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 15:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25676 for freebsd-current-outgoing; Sun, 5 Jul 1998 15:49:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-155.acadiau.ca [131.162.2.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25620; Sun, 5 Jul 1998 15:49:09 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id TAA15393; Sun, 5 Jul 1998 19:49:11 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 5 Jul 1998 19:49:11 -0300 (ADT) From: The Hermit Hacker To: current@FreeBSD.ORG cc: multimedia@FreeBSD.ORG Subject: xf86OpenConsole: KDENABIO failed (Operation not permitted) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone tell me what this means? I'm running a CURRENT system as of yesterday + 3.3.2 compiled on Friday from ports, and I get the same error if I run KDE or olvwm or any other window manager...and whether I try to do a startx from root or from my personal userid... Fatal server error: xf86OpenConsole: KDENABIO failed (Operation not permitted) Thanks.. Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 17:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22125 for freebsd-current-outgoing; Sun, 5 Jul 1998 17:08:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22102; Sun, 5 Jul 1998 17:08:31 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id EAA02126; Mon, 6 Jul 1998 04:08:21 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Mon, 6 Jul 1998 04:08:21 +0400 (MSD) From: Hostas Red To: The Hermit Hacker cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Sun, 5 Jul 1998, The Hermit Hacker wrote: > Can someone tell me what this means? I'm running a CURRENT system as of > yesterday + 3.3.2 compiled on Friday from ports, and I get the same error > if I run KDE or olvwm or any other window manager...and whether I try to > do a startx from root or from my personal userid... > > Fatal server error: > xf86OpenConsole: KDENABIO failed (Operation not permitted) Turn off kernel security in your rc.conf. Get options from /usr/src/etc/rc.conf. Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 17:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22546 for freebsd-current-outgoing; Sun, 5 Jul 1998 17:11:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22532 for ; Sun, 5 Jul 1998 17:10:56 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id UAA24026; Sun, 5 Jul 1998 20:10:45 -0400 (EDT) Date: Sun, 5 Jul 1998 20:10:43 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: .jpg Question In-Reply-To: <359FBF1C.18B9A00F@gwinnett.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try uninstalling and recompiling/reinstalling xv. On Sun, 5 Jul 1998, Lee Reese wrote: > I can display *.gif images with xv. However, when I try to display > *.jpg image, I get "Couldn't load the file '/tmp/leah564.jpg'. Wrong > JPEG library version: library is 62, caller expect 61. Could someone on > this list help me with this problem? Thanks. > > Lee Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 17:15:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23211 for freebsd-current-outgoing; Sun, 5 Jul 1998 17:15:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-17.ix.netcom.com [207.93.136.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23189 for ; Sun, 5 Jul 1998 17:14:49 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id RAA02799; Sun, 5 Jul 1998 17:14:20 -0700 (PDT) (envelope-from tomdean) Date: Sun, 5 Jul 1998 17:14:20 -0700 (PDT) Message-Id: <199807060014.RAA02799@ix.netcom.com> From: Thomas Dean To: lee@gwinnett.com CC: current@FreeBSD.ORG In-reply-to: <359FBF1C.18B9A00F@gwinnett.com> (message from Lee Reese on Sun, 05 Jul 1998 13:59:56 -0400) Subject: Re: .jpg Question Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The lib expected by xv is older than expected. Reinstall xv from /usr/ports/graphics. This should pick up the proper lib. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 18:00:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29896 for freebsd-current-outgoing; Sun, 5 Jul 1998 18:00:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-10.acadiau.ca [131.162.2.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29870; Sun, 5 Jul 1998 18:00:47 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id WAA00367; Sun, 5 Jul 1998 22:00:22 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 5 Jul 1998 22:00:17 -0300 (ADT) From: The Hermit Hacker To: Hostas Red cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perfect, thanks...that did it... On Mon, 6 Jul 1998, Hostas Red wrote: > Hi! > > On Sun, 5 Jul 1998, The Hermit Hacker wrote: > > > Can someone tell me what this means? I'm running a CURRENT system as of > > yesterday + 3.3.2 compiled on Friday from ports, and I get the same error > > if I run KDE or olvwm or any other window manager...and whether I try to > > do a startx from root or from my personal userid... > > > > Fatal server error: > > xf86OpenConsole: KDENABIO failed (Operation not permitted) > > Turn off kernel security in your rc.conf. Get options from > /usr/src/etc/rc.conf. > > Adios, > /KONG > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 18:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06939 for freebsd-current-outgoing; Sun, 5 Jul 1998 18:42:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06889 for ; Sun, 5 Jul 1998 18:42:27 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA00552; Mon, 6 Jul 1998 11:42:19 +1000 Date: Mon, 6 Jul 1998 11:42:19 +1000 From: Bruce Evans Message-Id: <199807060142.LAA00552@godzilla.zeta.org.au> To: julian@whistle.com, wollman@khavrinen.lcs.mit.edu Subject: Re: small locking patch for discussion Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >here's the patch >Index: ufs/ufs/ufs_quota.c This seems to be more or less correct, but incomplete. >=================================================================== >RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_quota.c,v >retrieving revision 1.23 >diff -c -r1.23 ufs_quota.c >*** ufs_quota.c 1998/06/21 14:53:40 1.23 >--- ufs_quota.c 1998/07/04 20:39:16 >*************** >*** 465,478 **** > /* > * Search vnodes associated with this mount point, > * deleting any references to quota file being closed. > */ > again: > for (vp = mp->mnt_vnodelist.lh_first; vp != NULL; vp = nextvp) { > nextvp = vp->v_mntvnodes.le_next; > if (vp->v_type == VNON) > continue; >! if (vget(vp, LK_EXCLUSIVE, p)) > goto again; > ip = VTOI(vp); > dq = ip->i_dquot[type]; > ip->i_dquot[type] = NODQUOT; >--- 465,489 ---- > /* > * Search vnodes associated with this mount point, > * deleting any references to quota file being closed. >+ * >+ * This is nearly identical to code in VFSOP_RELOAD, and >+ * *must* be maintained in parallel! > */ This comment is an obfuscation. All mnt_vnodelist traversals should look much like this. Apart from the traversal, the code doesn't look much like ffs_reload(). VFSOP_RELOAD doesn't exist. Every traversal shouldn't be commented on. > again: >+ simple_lock(&mntvnode_slock); > for (vp = mp->mnt_vnodelist.lh_first; vp != NULL; vp = nextvp) { >+ if (vp->v_mount != mp) { >+ simple_unlock(&mntvnode_slock); >+ goto again; >+ } > nextvp = vp->v_mntvnodes.le_next; > if (vp->v_type == VNON) > continue; >! simple_lock(&vp->v_interlock); >! simple_unlock(&mntvnode_slock); >! if (vget(vp, LK_EXCLUSIVE | LK_INTERLOCK, p)) { > goto again; >+ } Style bugs: excess braces. > ip = VTOI(vp); > dq = ip->i_dquot[type]; > ip->i_dquot[type] = NODQUOT; >*************** >*** 480,485 **** >--- 491,497 ---- > vput(vp); > if (vp->v_mntvnodes.le_next != nextvp || vp->v_mount != mp) > goto again; >+ simple_lock(&mntvnode_slock); The check before locking is now bogus. It isn't valid to check (vp->v_mntvnodes.le_next != nextvp) before locking. This is harmless because the only effect of a wrong check is to "goto again" unnecessarily. The new consistency check on vp (= the newvp here) at the start of the loop handles all problems. Most other mnt_vnodelist traversals (but not the one in qsync()) don't bother checking vp here. > } > dqflush(qvp); qvp->v_flag &= ~VSYSTEM; >#########------- The above is for quotaoff(). quotaon() is also missing locking. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 18:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07247 for freebsd-current-outgoing; Sun, 5 Jul 1998 18:45:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07221 for ; Sun, 5 Jul 1998 18:44:42 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id LAA05754; Mon, 6 Jul 1998 11:13:02 +0930 (CST) Message-ID: <19980706111301.V18970@freebie.lemis.com> Date: Mon, 6 Jul 1998 11:13:01 +0930 From: Greg Lehey To: Poul-Henning Kamp , rotel@indigo.ie Cc: Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems References: <199807052032.VAA04596@indigo.ie> <10403.899676678@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <10403.899676678@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Jul 06, 1998 at 12:11:18AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 6 July 1998 at 0:11:18 +0200, Poul-Henning Kamp wrote: > In message <199807052032.VAA04596@indigo.ie>, Niall Smart writes: >> On Jul 5, 12:56pm, Bill Paul wrote: >>> Subject: Re: inetd problems >>> >>> I encounter messages like this occasionally with my own code (mostly >>> NIS+ stuff) and without exception, the cause has always been some >>> kind of bug on my part (double free(), free()ing static buffers by >>> mistake, corrupting the heap by wandering past the end of a malloc()ed >>> buffer, etc...). All the theories I've heard so far point to some >>> kind of VM problem; nobody as yet has been willing to admit that >>> the problem is a bug in inetd. >> >> Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 >> you'll see why, it doesn't look like it's inetd's fault since other >> services fail at the same time. > > There are two problems here, at least as far as my diagnosis goes: > > 1: kernel/VM problem > means that you run out of memory and eventually malloc(3) > may fail. Do you mean kernel/VM problem or resource problem? I don't see a kernel bug, just the probability that all memory gets used up. > 2: inetd probelm > inetd doesn't correctly handle some exception conditions, > maybe related to malloc(3) failing for the above or other > reasons. Agreed. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 20:21:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21922 for freebsd-current-outgoing; Sun, 5 Jul 1998 20:21:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from locnar.336.net (root@locnar.336.net [207.69.181.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21883 for ; Sun, 5 Jul 1998 20:21:37 -0700 (PDT) (envelope-from sevn@336.net) Received: from locnar.336.net (sevn@locnar.336.net [207.69.181.130]) by locnar.336.net (8.8.8/8.8.8) with SMTP id XAA14842 for ; Sun, 5 Jul 1998 23:22:01 -0400 (EDT) (envelope-from sevn@336.net) Date: Sun, 5 Jul 1998 23:22:01 -0400 (EDT) From: Scott To: freebsd-current@FreeBSD.ORG Subject: pr440fx and sound Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone ever gotten the sound on the pr440fx (onboard crystal cs4236) to work? I've been playing with this one for a few months. I was hoping there might be something documented somewhere. TIA Scott "I have made mistakes but I have never made the mistake of claiming that I have never made one." -- James Gordon Bennett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 21:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00782 for freebsd-current-outgoing; Sun, 5 Jul 1998 21:48:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rainier.cs.wustl.edu (root@cs.wustl.edu [128.252.165.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00700 for ; Sun, 5 Jul 1998 21:48:21 -0700 (PDT) (envelope-from nanbor@lambada.cs.wustl.edu) Received: from lambada.cs.wustl.edu (nanbor@lambada.cs.wustl.edu [128.252.165.142]) by rainier.cs.wustl.edu (8.8.5/CTS-JEK1.2) with ESMTP id XAA18911 for ; Sun, 5 Jul 1998 23:48:13 -0500 (CDT) Received: (from nanbor@localhost) by lambada.cs.wustl.edu (8.8.5/CTS-JEK1.2) id XAA02145; Sun, 5 Jul 1998 23:48:08 -0500 (CDT) To: freebsd-current@FreeBSD.ORG Subject: anoncvs difficulty From: Nanbor Wang Date: 05 Jul 1998 23:48:07 -0500 Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just tried to update the source tree on my machine but got this error: select: protocol failure in circuit setup cvs [checkout aborted]: end of file from server (consult above messages if any) Never seen this before. I was able to access our own cvs repository, so I assume cvs is working. Was there something I did wrong? Thanks, Nanbor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 22:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02354 for freebsd-current-outgoing; Sun, 5 Jul 1998 22:00:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02349 for ; Sun, 5 Jul 1998 22:00:26 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id OAA30205; Mon, 6 Jul 1998 14:26:05 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 3LFRGD1Q; Mon, 6 Jul 1998 14:30:12 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id OAA09111; Mon, 6 Jul 1998 14:30:13 +0930 (CST) Message-ID: <35A059DD.D99C0753@dsto.defence.gov.au> Date: Mon, 06 Jul 1998 14:30:13 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: The Hermit Hacker CC: freebsd-current@FreeBSD.ORG Subject: Re: X no longer works... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This could be related to the recent kernel security level changes. To check, run the following as root: # sysctl -a | grep secur kern.securelevel: -1 If your kernel is not running at level -1 you wont be able to start X. (at least I couldn't). To make sure it runs at level -1 make sure you have updated your /etc files after your lastest world build. In particular /etc/rc sets the security level based on the options in the latest /etc/rc.conf which has these 2 entries recently added: kern_securelevel_enable="NO" # kernel security level (see init(8)), kern_securelevel="-1" # range: -1..2 ; `-1' is the most insecure You do need to merge in the recent changes to rc.conf as the security level will be changed if kern_securelevel_enable is anything other than "NO". The Hermit Hacker wrote: > > Morning... > > I recently did an upgrade of my machine, running FreeBSD-CURRENT, > and now can't seem to run X anymore, with an error of: > > Fatal server error: > xf86OpenConsole: KDENABIO failed (Operation not permitted) > > My first thought was that it was KDE related, by the KEDNABIO > message, but disabling KDE and using some other window manager brings > up the same error message :( > > I've tried rebuilding XFree86 and KDE, but that hasn't appeared to > help any... > > Am going to upgrade my source tree and kernel today, but has > anyone else seen this? Did I just get a source snapshot between good > ones? > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 5 22:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07934 for freebsd-current-outgoing; Sun, 5 Jul 1998 22:56:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07927 for ; Sun, 5 Jul 1998 22:56:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id HAA11052; Mon, 6 Jul 1998 07:53:04 +0200 (CEST) To: Greg Lehey cc: rotel@indigo.ie, Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems In-reply-to: Your message of "Mon, 06 Jul 1998 11:13:01 +0930." <19980706111301.V18970@freebie.lemis.com> Date: Mon, 06 Jul 1998 07:53:01 +0200 Message-ID: <11050.899704381@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980706111301.V18970@freebie.lemis.com>, Greg Lehey writes: >> There are two problems here, at least as far as my diagnosis goes: >> >> 1: kernel/VM problem >> means that you run out of memory and eventually malloc(3) >> may fail. > >Do you mean kernel/VM problem or resource problem? I don't see a >kernel bug, just the probability that all memory gets used up. well, lets just say that under some bizarre circumstances this happens too fast, ok ? :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 00:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17462 for freebsd-current-outgoing; Mon, 6 Jul 1998 00:07:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17426 for ; Mon, 6 Jul 1998 00:07:30 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id AAA17905; Mon, 6 Jul 1998 00:07:27 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd017890; Mon Jul 6 00:07:23 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA22574; Mon, 6 Jul 1998 00:07:20 -0700 (MST) From: Terry Lambert Message-Id: <199807060707.AAA22574@usr02.primenet.com> Subject: Re: small locking patch for discussion To: bde@zeta.org.au (Bruce Evans) Date: Mon, 6 Jul 1998 07:07:20 +0000 (GMT) Cc: julian@whistle.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <199807060142.LAA00552@godzilla.zeta.org.au> from "Bruce Evans" at Jul 6, 98 11:42:19 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This seems to be more or less correct, but incomplete. Yes. It does not attempt to fix everything at once; I've heard that's one of my problems from some people... ;-) > > /* > > * Search vnodes associated with this mount point, > > * deleting any references to quota file being closed. > >+ * > >+ * This is nearly identical to code in VFSOP_RELOAD, and > >+ * *must* be maintained in parallel! > > */ > > This comment is an obfuscation. All mnt_vnodelist traversals should > look much like this. Apart from the traversal, the code doesn't look > much like ffs_reload(). VFSOP_RELOAD doesn't exist. Every traversal > shouldn't be commented on. Every traversal should be in common code; the reason the comment is there is that the traversal mechanism changed recently. > >! if (vget(vp, LK_EXCLUSIVE | LK_INTERLOCK, p)) { > > goto again; > >+ } > > Style bugs: excess braces. I think I can blame this one on Julian; he likes braces. Personally, I could care less, unless I have to go in and put a debug printf in there, in which case, I'd have to add them (probably in the first column, with the printf) at that time. It may be that this had a printf in it. > > vput(vp); > > if (vp->v_mntvnodes.le_next != nextvp || vp->v_mount != mp) > > goto again; > >+ simple_lock(&mntvnode_slock); > > The check before locking is now bogus. It isn't valid to check > (vp->v_mntvnodes.le_next != nextvp) before locking. This is harmless > because the only effect of a wrong check is to "goto again" unnecessarily. > The new consistency check on vp (= the newvp here) at the start of the > loop handles all problems. Most other mnt_vnodelist traversals (but > not the one in qsync()) don't bother checking vp here. The problem is if the user quota being updated is on the group quota file, or vice versa. This is to guard against that. The other use, to guard against the block dev on which you are mounted being in the list of vp's you are syncing to the block dev. This one is less of an issue if you run devfs. > > } > > dqflush(qvp); qvp->v_flag &= ~VSYSTEM; > >#########------- > > The above is for quotaoff(). quotaon() is also missing locking. Yes. But you can mount with quotas. This was specifically to deal with a shutdown unmount-all panic. I don't know if it should be committed. I vastly prefer that the quota code go into a stacking layer, allowing it to be shared among all FS types. However, I'm aware that that the layering changes needed for that code are unlikely to be commited soon, so it's OK with me if this is committed as a temporary workaround of the panic (since the panic is real, and the workaround is bound to stick around a long time). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 00:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17815 for freebsd-current-outgoing; Mon, 6 Jul 1998 00:09:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17750 for ; Mon, 6 Jul 1998 00:08:52 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA20403; Mon, 6 Jul 1998 00:08:47 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd020387; Mon Jul 6 00:08:37 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA22604; Mon, 6 Jul 1998 00:08:33 -0700 (MST) From: Terry Lambert Message-Id: <199807060708.AAA22604@usr02.primenet.com> Subject: Re: inetd problems To: rotel@indigo.ie Date: Mon, 6 Jul 1998 07:08:33 +0000 (GMT) Cc: wpaul@skynet.ctr.columbia.edu, kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG In-Reply-To: <199807052032.VAA04596@indigo.ie> from "Niall Smart" at Jul 5, 98 09:32:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 > you'll see why, it doesn't look like it's inetd's fault since other > services fail at the same time. Other services not routed through inetd, I assume here... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 00:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17987 for freebsd-current-outgoing; Mon, 6 Jul 1998 00:09:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17955 for ; Mon, 6 Jul 1998 00:09:40 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA20483; Mon, 6 Jul 1998 00:09:37 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd020460; Mon Jul 6 00:09:29 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA22656; Mon, 6 Jul 1998 00:09:25 -0700 (MST) From: Terry Lambert Message-Id: <199807060709.AAA22656@usr02.primenet.com> Subject: Re: inetd problems To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 6 Jul 1998 07:09:25 +0000 (GMT) Cc: rotel@indigo.ie, wpaul@skynet.ctr.columbia.edu, kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG In-Reply-To: <10403.899676678@critter.freebsd.dk> from "Poul-Henning Kamp" at Jul 6, 98 00:11:18 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2: inetd probelm > inetd doesn't correctly handle some exception conditions, > maybe related to malloc(3) failing for the above or other > reasons. It seems to not unwind state/check its return values very well. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 00:34:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22374 for freebsd-current-outgoing; Mon, 6 Jul 1998 00:34:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22347 for ; Mon, 6 Jul 1998 00:34:38 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id LAA11104 for ; Mon, 6 Jul 1998 11:34:33 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Mon, 6 Jul 1998 11:34:33 +0400 (MSD) From: Hostas Red To: current@FreeBSD.ORG Subject: kernel breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! --- ip_input.o --- ../../netinet/ip_input.c: In function `ip_input': ../../netinet/ip_input.c:380: `Use' undeclared (first use this function) ../../netinet/ip_input.c:380: (Each undeclared identifier is reported only once ../../netinet/ip_input.c:380: for each function it appears in.) ../../netinet/ip_input.c:380: parse error before `port' --- ip_input.o --- *** Error code 1 Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 00:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24194 for freebsd-current-outgoing; Mon, 6 Jul 1998 00:50:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24091 for ; Mon, 6 Jul 1998 00:49:58 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id JAA23664 for ; Mon, 6 Jul 1998 09:53:36 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 6 Jul 1998 09:53:36 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Memory usage map Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I remember someone (Terry Lambert?) was talking some time ago about his attempt to write a utility which would show which parts of physical memory are currently in use by which part of the system. Does something like this exist? Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 01:17:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28019 for freebsd-current-outgoing; Mon, 6 Jul 1998 01:17:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27939 for ; Mon, 6 Jul 1998 01:16:32 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id MAA24608 for ; Mon, 6 Jul 1998 12:16:24 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id MAA27917 for ; Mon, 6 Jul 1998 12:16:43 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199807060816.MAA27917@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message "Mon, 06 Jul 1998 04:08:21 +0400." Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 12:16:42 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hostas Red writes: >> Fatal server error: >> xf86OpenConsole: KDENABIO failed (Operation not permitted) > >Turn off kernel security in your rc.conf. Get options from >/usr/src/etc/rc.conf. Hmm... WHY X cannot be started with securelevel set? Is it a bug or a feature? Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 01:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00396 for freebsd-current-outgoing; Mon, 6 Jul 1998 01:27:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00361; Mon, 6 Jul 1998 01:27:35 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id MAA01456; Mon, 6 Jul 1998 12:27:23 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id MAA28573; Mon, 6 Jul 1998 12:27:45 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199807060827.MAA28573@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: ports@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: mySQL on CURRENT: lots of troubles X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Mon, 06 Jul 1998 12:27:45 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! mySQL (current version), compiled and run under 3.0 (late May SNAP) dumps core at every attempt to connect to it, and starting mysql daemon from /usr/local/etc/rc.d caused panic. Does anyone else have these troubles? Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 01:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01249 for freebsd-current-outgoing; Mon, 6 Jul 1998 01:31:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01230 for ; Mon, 6 Jul 1998 01:31:13 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA04174 for ; Mon, 6 Jul 1998 10:32:14 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 6 Jul 1998 10:32:14 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: FreeBSD in less than 4MB RAM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is slightly more general question than in the Subject. First issue is: what would it take to squeeze any useful combination of kernel, init plus two-three (small) user programs in 4MB? Which (dispensable) parts of the kernel require so much space? After removing all I could think of (leaving FFS, fd0, and ed0, though) the kernel size is still about 700kB big, and quite another question is how this translates into running size... The second issue is this: currently we're unable to boot (using BIOS) and mount as / other filesystems than FFS, NFS and CD9660. It would be great if we could use MSDOSFS as well (using special version of biosboot, with FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. What for? This could help get rid of fbsdboot.exe and related troubles - we could just directly start and run (and install!) on MSDOS partition. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 01:54:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04640 for freebsd-current-outgoing; Mon, 6 Jul 1998 01:54:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04634 for ; Mon, 6 Jul 1998 01:54:16 -0700 (PDT) (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 IAA22302; Mon, 6 Jul 1998 08:52:55 GMT Date: Mon, 6 Jul 1998 17:52:55 +0900 (JST) From: Michael Hancock To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Memory usage map In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You might be thinking of testset, which Terry wrote to test for namei() memory cn_path leaks, see ~terry. You will have to port it to current. I pieced together testvn to test vnode memory management using testset and vmstat/sysstat, see ~mch. This runs on current. Regards, Mike On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > Hi, > > I remember someone (Terry Lambert?) was talking some time ago about his > attempt to write a utility which would show which parts of physical memory > are currently in use by which part of the system. > > Does something like this exist? > > > Andrzej Bialecki > > --------------------+--------------------------------------------------------- > abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } > Research & Academic | "Be open-minded, but don't let your brains to fall out." > Network in Poland | All of the above (and more) is just my personal opinion. > --------------------+--------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 02:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07218 for freebsd-current-outgoing; Mon, 6 Jul 1998 02:18:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07210 for ; Mon, 6 Jul 1998 02:18:22 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id CAA07402; Mon, 6 Jul 1998 02:11:51 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd007399; Mon Jul 6 09:11:48 1998 Date: Mon, 6 Jul 1998 02:11:45 -0700 (PDT) From: Julian Elischer To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: kernel breakage In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gee you were quick.. it was only broken for minutes. see rev 1.95 On Mon, 6 Jul 1998, Hostas Red wrote: > Hi! > > --- ip_input.o --- > ../../netinet/ip_input.c: In function `ip_input': > ../../netinet/ip_input.c:380: `Use' undeclared (first use this function) > ../../netinet/ip_input.c:380: (Each undeclared identifier is reported only > once > ../../netinet/ip_input.c:380: for each function it appears in.) > ../../netinet/ip_input.c:380: parse error before `port' > --- ip_input.o --- > *** Error code 1 > > Adios, > /KONG > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 03:06:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13835 for freebsd-current-outgoing; Mon, 6 Jul 1998 03:06:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13829 for ; Mon, 6 Jul 1998 03:06:43 -0700 (PDT) (envelope-from smoergrd@geos01.oslo.geco-prakla.slb.com) Received: from sunw132.geco-prakla.slb.com (sunw132 [134.32.45.120]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA17914 ; Mon, 6 Jul 1998 12:06:08 +0200 (MET DST) Received: by sunw132.geco-prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA02273; Mon, 6 Jul 1998 12:06:07 +0200 To: tarkhil@asteroid.svib.ru Cc: current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) References: <199807060816.MAA27917@minas-tirith.pol.ru> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 06 Jul 1998 12:06:06 +0200 In-Reply-To: Alex Povolotsky's message of Mon, 06 Jul 1998 12:16:42 +0400 Message-ID: Lines: 19 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Povolotsky writes: > Hostas Red writes: > > > Fatal server error: > > > xf86OpenConsole: KDENABIO failed (Operation not permitted) > > Turn off kernel security in your rc.conf. Get options from > > /usr/src/etc/rc.conf. > Hmm... WHY X cannot be started with securelevel set? Is it a bug or a feature? I guess it's a feature. 'man 8 init'. Anyway, there are a lot more things you can't do at securelevel >= 1; installing a new kernel or world, for instance, since they involve overwriting immutable files. I guess you'd want to run your terminal server at securelevel 2, and use X terminals (or diskless workstations) instead of logging on directly on your server. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 03:18:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15614 for freebsd-current-outgoing; Mon, 6 Jul 1998 03:18:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15608 for ; Mon, 6 Jul 1998 03:18:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA08532; Mon, 6 Jul 1998 03:12:22 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008529; Mon Jul 6 10:12:21 1998 Date: Mon, 6 Jul 1998 03:12:18 -0700 (PDT) From: Julian Elischer To: Michael Hancock cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: Memory usage map In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi michael I was going to get you to review the VOP_STRATEGY changes I just did but couldn't remember your email address and eivind came along and I got him to do it.. :-) Never the less, could you look at the new VOP_STRATEGY definitios and see if I missed out anything.. (seems to run fine) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 04:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24230 for freebsd-current-outgoing; Mon, 6 Jul 1998 04:28:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sun-test.hightek.com (sun-test.hightek.com [194.74.141.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24210 for ; Mon, 6 Jul 1998 04:28:23 -0700 (PDT) (envelope-from andreas@klemm2.hightek.com) Received: from klemm2.hightek.com ([195.90.203.76]) by sun-test.hightek.com (Netscape Mail Server v1.1) with ESMTP id AAA16943; Mon, 6 Jul 1998 13:28:17 +0200 Received: (from andreas@localhost) by klemm2.hightek.com (8.8.8/8.8.8) id NAA00934; Mon, 6 Jul 1998 13:28:16 +0200 (CEST) (envelope-from andreas) Message-ID: <19980706132815.42445@hightek.com> Date: Mon, 6 Jul 1998 13:28:15 +0200 From: Andreas Klemm To: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Andrzej Bialecki on Mon, Jul 06, 1998 at 10:32:14AM +0200 X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 10:32:14AM +0200, Andrzej Bialecki wrote: > The second issue is this: currently we're unable to boot (using BIOS) and > mount as / other filesystems than FFS, NFS and CD9660. It would be great > if we could use MSDOSFS as well (using special version of biosboot, with > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. > > What for? This could help get rid of fbsdboot.exe and related troubles - > we could just directly start and run (and install!) on MSDOS partition. Like Solaris x86 ;-) The first two or three floppies are in MS-DOS format ;-)) -- B&K Gruppe - Wuppertal phone +49 202 7399 - 170 fax +49 202 7399 - 100 http://www.FreeBSD.ORG/~andreas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 05:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29210 for freebsd-current-outgoing; Mon, 6 Jul 1998 05:10:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29149 for ; Mon, 6 Jul 1998 05:10:06 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id QAA12873; Mon, 6 Jul 1998 16:09:32 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Mon, 6 Jul 1998 16:09:30 +0400 (MSD) From: Hostas Red To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: kernel breakage In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Mon, 6 Jul 1998, Julian Elischer wrote: > gee you were quick.. it was only broken for minutes. > see rev 1.95 I'm trying to be on touch. :) Thanx, now works fine. :) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 05:29:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00958 for freebsd-current-outgoing; Mon, 6 Jul 1998 05:29:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00949 for ; Mon, 6 Jul 1998 05:29:12 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id QAA12991; Mon, 6 Jul 1998 16:28:15 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Mon, 6 Jul 1998 16:28:15 +0400 (MSD) From: Hostas Red To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > The second issue is this: currently we're unable to boot (using BIOS) and > mount as / other filesystems than FFS, NFS and CD9660. It would be great > if we could use MSDOSFS as well (using special version of biosboot, with > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. > > What for? This could help get rid of fbsdboot.exe and related troubles - > we could just directly start and run (and install!) on MSDOS partition. I think, in that case we will need some system files with "extended attributes", like in OS/2-on-FAT, to keep longnames (FAT16), ownership and file modes. :) It's not so good solution, but without this we will have no security at all :( Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 05:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02882 for freebsd-current-outgoing; Mon, 6 Jul 1998 05:46:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02820 for ; Mon, 6 Jul 1998 05:46:04 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id OAA17421; Mon, 6 Jul 1998 14:48:31 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 6 Jul 1998 14:48:30 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Hostas Red cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998, Hostas Red wrote: > Hi! > > On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > > > The second issue is this: currently we're unable to boot (using BIOS) and > > mount as / other filesystems than FFS, NFS and CD9660. It would be great > > if we could use MSDOSFS as well (using special version of biosboot, with > > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. > > > > What for? This could help get rid of fbsdboot.exe and related troubles - > > we could just directly start and run (and install!) on MSDOS partition. > > I think, in that case we will need some system files with "extended > attributes", like in OS/2-on-FAT, to keep longnames (FAT16), ownership and > file modes. :) It's not so good solution, but without this we will have no > security at all :( Hmmm.. Perhaps I didn't make clear what was my intent: I'd like to be able to use MSDOS as root partition in cases where I don't need all semantics of FFS, like boot floppies and flash disk configurations. Or, in situation where users don't have any direct access to disk (like on a router running custom shell; yet another situation is when I want to boot from MSDOS partition and mount a file which resides there, as its e.g. /usr FFS). I don't want to use FFS there because it wastes a lot of space and is unnecessarily complicated. What I need there is something between rawboot (which treats medium as a chain of data blocks) and FFS. MSDOSFS is a good candidate, because we already have working support for it. And I wouldn't mind using long names on it either, though the short ones would suffice... So, security in these situations would be achieved by some other means. Anyway, once you have physical access to the medium on which the OS is installed, all other security issues are moot. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 08:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23483 for freebsd-current-outgoing; Mon, 6 Jul 1998 08:12:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from joshua.enteract.com (joshua.enteract.com [207.229.129.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA23472 for ; Mon, 6 Jul 1998 08:12:04 -0700 (PDT) (envelope-from djhoward@joshua.enteract.com) Received: (qmail 11599 invoked by uid 1032); 6 Jul 1998 15:12:02 -0000 Message-ID: <19980706101202.C9501@enteract.com> Date: Mon, 6 Jul 1998 10:12:02 -0500 From: dannyman To: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: mySQL on CURRENT: lots of troubles Mail-Followup-To: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG References: <199807060827.MAA28573@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807060827.MAA28573@minas-tirith.pol.ru>; from Alex Povolotsky on Mon, Jul 06, 1998 at 12:27:45PM +0400 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Reply-to: trimmed] On Mon, Jul 06, 1998 at 12:27:45PM +0400, Alex Povolotsky wrote: > at every attempt to connect to it, and starting mysql daemon from > /usr/local/etc/rc.d caused panic. there's a script that sets up default user permissions. Nuking the stuff in /var/db/mysql and then rerunning this script has helped, in my experience. -danny -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 08:33:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25691 for freebsd-current-outgoing; Mon, 6 Jul 1998 08:33:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dot.crosswinds.net (dot.crosswinds.net [209.47.139.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25670; Mon, 6 Jul 1998 08:33:20 -0700 (PDT) (envelope-from tony@crosswinds.net) Received: (from tony@localhost) by dot.crosswinds.net (8.8.7/8.8.8) id LAA27822; Mon, 6 Jul 1998 11:33:26 -0400 (EDT) (envelope-from tony) From: Tony Holmes Message-Id: <199807061533.LAA27822@dot.crosswinds.net> Subject: Load related wd problem To: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Date: Mon, 6 Jul 1998 11:33:25 -0400 (EDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I posted to -stable and -current since these seem to be the most appropriate places for this question - please correct me if this is wrong. I run a Network Service Provider and utilize FreeBSD exclusively on all my systems - I have come to trust and rely on FreeBSD's performance and stability. My systems range from 2.2.1 to 2.2.6 (with some stable patches thrown in) and provide a myriad of services, but I have only recently been able to verify the existence of a problem with heavy access to IDE disks. When the IDE disks are under heavy load, they will take down the system with no warning. This occurs across all versions - it find it easy to duplicate the problem - on a web server, while the http server is up, I will do some custom processing on the log files (cat, grepping, etc.) which hits the IDE disks hard. After a time (usually after 10-15 minutes) the system hangs and can only be rescued with a hard reset. I've seen the same effect on a system set up as a Squid proxy with 2 ide drives - loggings to one disk and caching on the other, where my peak wd interrupt rates reach 150-200/sec - this machine will hang after anywhere between 1.5 hours and 2 days of uptime. If it makes any difference, I use Seagate IDE disks on all my systems. Unfortunately, due to the nature of the crash and my limited resources, I cannot isolate the problem further, but am very curious as to whether or not anyone else has seen similar problems? Tony Holmes Senior Sysadmin Crosswinds Internet Communications Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 08:50:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28473 for freebsd-current-outgoing; Mon, 6 Jul 1998 08:50:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28458 for ; Mon, 6 Jul 1998 08:50:31 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03457; Mon, 6 Jul 1998 08:50:25 -0700 (PDT) Message-Id: <199807061550.IAA03457@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Mon, 06 Jul 1998 10:32:14 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 08:50:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > This is slightly more general question than in the Subject. > > First issue is: what would it take to squeeze any useful combination of > kernel, init plus two-three (small) user programs in 4MB? Which > (dispensable) parts of the kernel require so much space? After removing > all I could think of (leaving FFS, fd0, and ed0, though) the kernel size > is still about 700kB big, and quite another question is how this > translates into running size... try "du *.o | sort -n" in your compile directory. > The second issue is this: currently we're unable to boot (using BIOS) and > mount as / other filesystems than FFS, NFS and CD9660. It would be great > if we could use MSDOSFS as well (using special version of biosboot, with > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. All you have to do is add the mountroot stuff to MSDOSFS - nobody would complain if you did. > What for? This could help get rid of fbsdboot.exe and related troubles - > we could just directly start and run (and install!) on MSDOS partition. Permissions would suck. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 09:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07336 for freebsd-current-outgoing; Mon, 6 Jul 1998 09:47:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07327 for ; Mon, 6 Jul 1998 09:46:59 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-138.camalott.com [208.229.74.138]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA32031; Mon, 6 Jul 1998 11:46:55 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06285; Mon, 6 Jul 1998 11:46:33 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 11:46:33 -0500 (CDT) Message-Id: <199807061646.LAA06285@detlev.UUCP> To: smoergrd@oslo.geco-prakla.slb.com CC: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: (smoergrd@oslo.geco-prakla.slb.com) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807060816.MAA27917@minas-tirith.pol.ru> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Hmm... WHY X cannot be started with securelevel set? Is it a bug or >> a feature? > I guess it's a feature. 'man 8 init'. Anyway, there are a lot more > things you can't do at securelevel >= 1; installing a new kernel or > world, for instance, since they involve overwriting immutable files. Most things that are disallowed under securelevel 1 are things that aren't frequently done except during rc, a system install, or an attack. But running X is a normal operation. I'd classify it as a bug myself. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 09:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08257 for freebsd-current-outgoing; Mon, 6 Jul 1998 09:51:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08234 for ; Mon, 6 Jul 1998 09:51:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-138.camalott.com [208.229.74.138]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA32205; Mon, 6 Jul 1998 11:49:41 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06288; Mon, 6 Jul 1998 11:49:19 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 11:49:19 -0500 (CDT) Message-Id: <199807061649.LAA06288@detlev.UUCP> To: mike@smith.net.au CC: abial@nask.pl, freebsd-current@FreeBSD.ORG In-reply-to: <199807061550.IAA03457@antipodes.cdrom.com> (message from Mike Smith on Mon, 06 Jul 1998 08:50:24 -0700) Subject: Re: FreeBSD in less than 4MB RAM From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807061550.IAA03457@antipodes.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What for? This could help get rid of fbsdboot.exe and related troubles - >> we could just directly start and run (and install!) on MSDOS partition. > Permissions would suck. Not to mention performance, lack of links (sym or hard!), etc, etc. I'm not saying it's not doable, or even desirable under a few circumstances, but it still gives me the heebie-jeebies. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 10:35:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15120 for freebsd-current-outgoing; Mon, 6 Jul 1998 10:35:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15106 for ; Mon, 6 Jul 1998 10:35:16 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40753(1)>; Mon, 6 Jul 1998 10:34:42 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id KAA06821; Mon, 6 Jul 1998 10:34:33 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199807061734.KAA06821@mango.parc.xerox.com> To: Nanbor Wang cc: freebsd-current@FreeBSD.ORG Subject: Re: anoncvs difficulty In-reply-to: Your message of "Sun, 05 Jul 1998 21:48:07 PDT." Date: Mon, 6 Jul 1998 10:34:33 PDT From: Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message you write: > select: protocol failure in circuit setup > cvs [checkout aborted]: end of file from server (consult above messages if > any) > >Was there something I did wrong? No; the remote shell service on the anoncvs server is broken. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 12:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03702 for freebsd-current-outgoing; Mon, 6 Jul 1998 12:34:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03689 for ; Mon, 6 Jul 1998 12:34:07 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id PAA26076; Mon, 6 Jul 1998 15:34:01 -0400 (EDT) (envelope-from wollman) Date: Mon, 6 Jul 1998 15:34:01 -0400 (EDT) From: Garrett Wollman Message-Id: <199807061934.PAA26076@khavrinen.lcs.mit.edu> To: joelh@gnu.org Cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-Reply-To: <199807061646.LAA06285@detlev.UUCP> References: <199807060816.MAA27917@minas-tirith.pol.ru> <199807061646.LAA06285@detlev.UUCP> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > attack. But running X is a normal operation. I'd classify it as a > bug myself. You're welcome to do so. However, it is not a bug in FreeBSD -- it's a bug in the hardware design. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 13:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08504 for freebsd-current-outgoing; Mon, 6 Jul 1998 13:01:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fredriks-1.pr.mcs.net (fredriks-1.pr.mcs.net [205.164.50.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08479 for ; Mon, 6 Jul 1998 13:01:09 -0700 (PDT) (envelope-from lars@fredriks-1.pr.mcs.net) Received: (from lars@localhost) by hugin.odin-corporation.com (8.8.8/8.8.8) id LAA01419 for current@freebsd.org.; Mon, 6 Jul 1998 11:21:50 -0500 (CDT) (envelope-from lars) From: Lars Fredriksen Message-Id: <199807061621.LAA01419@hugin.odin-corporation.com> Subject: pppd not working anymore To: current@FreeBSD.ORG Date: Mon, 6 Jul 1998 11:21:50 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Something is broken with the new pppd. It gets the link up and running ok, but it doesn't seem to forward incoming packets at all. As an example ping sits there and doesn't get a single echo back. The route table looks the same regardless if the current pppd (as of July 1) or the old one (as of Feb 1998) is used. Netstat -s shows the icmp "host unreachable" count to be increasing. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@odin-corporation.com (home-work) www.odin-corporation.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 13:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16145 for freebsd-current-outgoing; Mon, 6 Jul 1998 13:47:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16129 for ; Mon, 6 Jul 1998 13:47:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA26019; Mon, 6 Jul 1998 13:46:14 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: joelh@gnu.org cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 11:46:33 CDT." <199807061646.LAA06285@detlev.UUCP> Date: Mon, 06 Jul 1998 13:46:13 -0700 Message-ID: <26015.899757973@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Most things that are disallowed under securelevel 1 are things that > aren't frequently done except during rc, a system install, or an > attack. But running X is a normal operation. I'd classify it as a > bug myself. Actually, running X is not a "normal" operation at all - it performs inb/outb instructions and does various privileged bits of syscons frobbing that could be potentially quite hazardous in the hands of the deliberately malicious. Running an X server should be a conscious compromise of certain types of security. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 14:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20229 for freebsd-current-outgoing; Mon, 6 Jul 1998 14:18:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts01-62.waterford.indigo.ie [194.125.139.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20179; Mon, 6 Jul 1998 14:18:17 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01507; Mon, 6 Jul 1998 22:13:34 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807062113.WAA01507@indigo.ie> Date: Mon, 6 Jul 1998 22:13:33 +0000 In-Reply-To: Tony Holmes "Load related wd problem" (Jul 6, 11:33am) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Tony Holmes , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Load related wd problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 6, 11:33am, Tony Holmes wrote: } Subject: Load related wd problem > > My systems range from 2.2.1 to 2.2.6 (with some stable patches thrown in) > and provide a myriad of services, but I have only recently been able to > verify the existence of a problem with heavy access to IDE disks. > > When the IDE disks are under heavy load, they will take down the system with > no warning. This occurs across all versions - it find it easy to duplicate > the problem - on a web server, while the http server is up, I will do some > custom processing on the log files (cat, grepping, etc.) which hits the IDE > disks hard. After a time (usually after 10-15 minutes) the system hangs > and can only be rescued with a hard reset. Hi Tony, I saw a PR go on a while back for a similar problem, it was some problem about using one variable for all disks instead of one each, I can't remember the details. Anyway, I'm not sure if it was even committed, but it might be worth searching freebsd.org to see if you can find it, sorry I can't be more help. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 14:24:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21504 for freebsd-current-outgoing; Mon, 6 Jul 1998 14:24:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21476 for ; Mon, 6 Jul 1998 14:24:30 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-82.camalott.com [208.229.74.82]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id QAA14486; Mon, 6 Jul 1998 16:24:17 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id QAA08328; Mon, 6 Jul 1998 16:23:55 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 16:23:55 -0500 (CDT) Message-Id: <199807062123.QAA08328@detlev.UUCP> To: wollman@khavrinen.lcs.mit.edu CC: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: <199807061934.PAA26076@khavrinen.lcs.mit.edu> (message from Garrett Wollman on Mon, 6 Jul 1998 15:34:01 -0400 (EDT)) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807060816.MAA27917@minas-tirith.pol.ru> <199807061646.LAA06285@detlev.UUCP> <199807061934.PAA26076@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> attack. But running X is a normal operation. I'd classify it as a >> bug myself. > You're welcome to do so. However, it is not a bug in FreeBSD -- it's > a bug in the hardware design. I will continue to do so-- that is, to classify it as a bug, for the reasons I stated already. However, since I don't use securelevel, and have n+1 other hacks on my plate, I'm still not in any hurry to fix it. I do agree that the PC hardware design is absurd, and this is probably lossage from that. (I say probably because I haven't looked at the issue myself.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 15:09:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28580 for freebsd-current-outgoing; Mon, 6 Jul 1998 15:09:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28573 for ; Mon, 6 Jul 1998 15:09:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA03901 for ; Mon, 6 Jul 1998 15:05:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003865; Mon Jul 6 22:05:02 1998 Message-ID: <35A14A02.15FB7483@whistle.com> Date: Mon, 06 Jul 1998 15:04:50 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: RECOMPILE IPFW Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When you compile a new kernel, if you use ipfw in -current you MUST RECOMPILE THE UTILITY or you won't be able to set firewall rules. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 15:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29417 for freebsd-current-outgoing; Mon, 6 Jul 1998 15:12:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29169 for ; Mon, 6 Jul 1998 15:12:01 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-124.camalott.com [208.229.74.124]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA17487; Mon, 6 Jul 1998 17:11:43 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA09001; Mon, 6 Jul 1998 17:11:22 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 17:11:22 -0500 (CDT) Message-Id: <199807062211.RAA09001@detlev.UUCP> To: jkh@time.cdrom.com CC: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: <26015.899757973@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <26015.899757973@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Most things that are disallowed under securelevel 1 are things that >> aren't frequently done except during rc, a system install, or an >> attack. But running X is a normal operation. I'd classify it as a >> bug myself. > Actually, running X is not a "normal" operation at all - it performs > inb/outb instructions and does various privileged bits of syscons > frobbing that could be potentially quite hazardous in the hands of the > deliberately malicious. Running an X server should be a conscious > compromise of certain types of security. While I will agree that it does not run in a normal manner, it is not an infrequent operation. I was about to continue that paragraph, when the question occurred: Are there no other userland programs (besides wine and doscmd) that do these ops? (Mind you, I'm not arguing that this should be fixed; we just don't have the people to fix every nit. I'm arguing that it's a Bad Thing.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 15:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04301 for freebsd-current-outgoing; Mon, 6 Jul 1998 15:38:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (root@ts01-62.waterford.indigo.ie [194.125.139.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04259; Mon, 6 Jul 1998 15:38:19 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id XAA01618; Mon, 6 Jul 1998 23:10:27 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807062210.XAA01618@indigo.ie> Date: Mon, 6 Jul 1998 23:10:25 +0000 In-Reply-To: rotel@indigo.ie "Re: Load related wd problem" (Jul 6, 10:13pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: rotel@indigo.ie, Tony Holmes , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Load related wd problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 6, 10:13pm, rotel@indigo.ie wrote: } Subject: Re: Load related wd problem > > > > When the IDE disks are under heavy load, they will take down the system with > > no warning. This occurs across all versions - it find it easy to duplicate > > the problem - on a web server, while the http server is up, I will do some > > custom processing on the log files (cat, grepping, etc.) which hits the IDE > > disks hard. After a time (usually after 10-15 minutes) the system hangs > > and can only be rescued with a hard reset. > > I saw a PR go on a while back for a similar problem, it was some > problem about using one variable for all disks instead of one each, > I can't remember the details. Anyway, I'm not sure if it was even > committed, but it might be worth searching freebsd.org to see if > you can find it, sorry I can't be more help. Damnit, I've searched GNATS, freebsd-bugs and freebsd-hackers and reviewed the changelog for wd.c and I can't find it. Does anyone else remember this? Sorry for the amount of cross-posting, but if the original patch was correct then its important. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 16:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14973 for freebsd-current-outgoing; Mon, 6 Jul 1998 16:59:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14968 for ; Mon, 6 Jul 1998 16:59:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01334; Mon, 6 Jul 1998 16:58:12 -0700 (PDT) Message-Id: <199807062358.QAA01334@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: joelh@gnu.org cc: jkh@time.cdrom.com, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 17:11:22 CDT." <199807062211.RAA09001@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 16:58:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Most things that are disallowed under securelevel 1 are things that > >> aren't frequently done except during rc, a system install, or an > >> attack. But running X is a normal operation. I'd classify it as a > >> bug myself. > > Actually, running X is not a "normal" operation at all - it performs > > inb/outb instructions and does various privileged bits of syscons > > frobbing that could be potentially quite hazardous in the hands of the > > deliberately malicious. Running an X server should be a conscious > > compromise of certain types of security. > > While I will agree that it does not run in a normal manner, it is not > an infrequent operation. > > I was about to continue that paragraph, when the question occurred: > Are there no other userland programs (besides wine and doscmd) that do > these ops? Lots of them; there's plenty of low-speed industrial control applications that dink the hardware directly courtesy of the IOPL bit. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 17:24:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17986 for freebsd-current-outgoing; Mon, 6 Jul 1998 17:24:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17932 for ; Mon, 6 Jul 1998 17:23:56 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id IAA02949; Tue, 7 Jul 1998 08:18:08 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199807070018.IAA02949@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: phk@critter.freebsd.dk (Poul-Henning Kamp), rotel@indigo.ie, wpaul@skynet.ctr.columbia.edu, kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG Subject: Re: inetd problems In-reply-to: Your message of "Mon, 06 Jul 1998 07:09:25 GMT." <199807060709.AAA22656@usr02.primenet.com> Date: Tue, 07 Jul 1998 08:18:07 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > 2: inetd probelm > > inetd doesn't correctly handle some exception conditions, > > maybe related to malloc(3) failing for the above or other > > reasons. > > It seems to not unwind state/check its return values very well. 8-(. I've looked at this before but never was able to catch it in the act with an inetd with enough symbols to make it worth tracing. I'm pretty sure it's not inetd itself, but some other libc routine that inetd calls. I wonder about the resolver getXXXbyYYY() stuff sometimes. I suspect that some state is being trashed somewhere and it's being accessed or freed in each child after the fork(). > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 17:39:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19323 for freebsd-current-outgoing; Mon, 6 Jul 1998 17:39:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19318 for ; Mon, 6 Jul 1998 17:39:26 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA15762; Tue, 7 Jul 1998 10:08:23 +0930 (CST) Message-Id: <199807070038.KAA15762@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: joelh@gnu.org, jkh@time.cdrom.com, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 16:58:12 MST." <199807062358.QAA01334@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 10:08:23 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I was about to continue that paragraph, when the question occurred: > > Are there no other userland programs (besides wine and doscmd) that do > > these ops? > Lots of them; there's plenty of low-speed industrial control > applications that dink the hardware directly courtesy of the IOPL bit. Hmm.. along with anything that uses a 3DFX =) (Well, until the 3dfx driver is ported) I'm just pointing out the important stuff here ;) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 19:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25871 for freebsd-current-outgoing; Mon, 6 Jul 1998 19:10:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (root@vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25841 for ; Mon, 6 Jul 1998 19:10:21 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id VAA22907; Mon, 6 Jul 1998 21:29:16 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Mon, 6 Jul 1998 21:29:16 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Lars Fredriksen cc: current@FreeBSD.ORG Subject: Re: pppd not working anymore In-Reply-To: <199807061621.LAA01419@hugin.odin-corporation.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe your isp is messed up. Look into this. Can you try the same dialup on another box? Maybe their portmasters are. See if its their route by pinging something within their lan, so the packets don't have to hit internet bandwidth at all. /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org * IRC Cabalnet +++ irc.sykotik.org */ On Mon, 6 Jul 1998, Lars Fredriksen wrote: > Hi, > Something is broken with the new pppd. It gets the link > up and running ok, but it doesn't seem to forward incoming > packets at all. As an example ping sits there > and doesn't get a single echo back. The route table looks the > same regardless if the current pppd (as of July 1) or the old > one (as of Feb 1998) is used. > > Netstat -s shows the icmp "host unreachable" count to be increasing. > > Lars > -- > ------------------------------------------------------------------- > Lars Fredriksen fredriks@mcs.com (home) > lars@odin-corporation.com (home-work) > www.odin-corporation.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 19:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28667 for freebsd-current-outgoing; Mon, 6 Jul 1998 19:31:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28617 for ; Mon, 6 Jul 1998 19:30:58 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-124.camalott.com [208.229.74.124]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id VAA00822; Mon, 6 Jul 1998 21:30:41 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id VAA10228; Mon, 6 Jul 1998 21:30:18 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 21:30:18 -0500 (CDT) Message-Id: <199807070230.VAA10228@detlev.UUCP> To: mike@smith.net.au CC: jkh@time.cdrom.com, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: <199807062358.QAA01334@dingo.cdrom.com> (message from Mike Smith on Mon, 06 Jul 1998 16:58:12 -0700) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807062358.QAA01334@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I was about to continue that paragraph, when the question occurred: >> Are there no other userland programs (besides wine and doscmd) that do >> these ops? > Lots of them; there's plenty of low-speed industrial control > applications that dink the hardware directly courtesy of the IOPL bit. Actually, I meant general-purpose apps, not application-specific apps like robotics. But I get the idea. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 19:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01383 for freebsd-current-outgoing; Mon, 6 Jul 1998 19:46:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (syko@vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01377 for ; Mon, 6 Jul 1998 19:46:35 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id WAA23352; Mon, 6 Jul 1998 22:45:46 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Mon, 6 Jul 1998 22:45:46 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I once successfully ran FreeBSD on a 486 33 with 8 megs of ram. (Box is still running in fact, no hdd space left, runs somewhat nicely. Its running 2.2.6-RELEASE now.) /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org * IRC Cabalnet +++ irc.sykotik.org */ On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > Hi, > > This is slightly more general question than in the Subject. > > First issue is: what would it take to squeeze any useful combination of > kernel, init plus two-three (small) user programs in 4MB? Which You don't want to run any inetd processes? As well as other such things which use memory. > (dispensable) parts of the kernel require so much space? After removing > all I could think of (leaving FFS, fd0, and ed0, though) the kernel size > is still about 700kB big, and quite another question is how this > translates into running size... The afforementioned box has been (although rarely) at 0.00 sysloads. :) Of course thats 8 megs. But hell, if you have a box sitting around with 4 megs of ram, either upgrade it, or if you can't, just try to run FreeBSD. If it doesn't work, what have you lost? If you wanna count on this as an internet server, well... good luck ;) ---[ SNIP ]--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 20:14:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05801 for freebsd-current-outgoing; Mon, 6 Jul 1998 20:14:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ms5.hinet.net (andyluo@ms5.hinet.net [168.95.4.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05715 for ; Mon, 6 Jul 1998 20:14:07 -0700 (PDT) (envelope-from andyluo@ms5.hinet.net) From: andyluo@ms5.hinet.net Received: (from andyluo@localhost) by ms5.hinet.net (8.8.8/8.8.8) id LAA25309; Tue, 7 Jul 1998 11:14:05 +0800 (CST) Date: Tue, 7 Jul 1998 11:14:05 +0800 (CST) Message-Id: <199807070314.LAA25309@ms5.hinet.net> To: current@FreeBSD.ORG, depend@ms5.hinet.net, failed@ms5.hinet.net Subject: make Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I use 3.0-980704-SNAP, but failed in make kernel with "device de0".. today, I up my kernel source to CTM #3444, but it failed too. error message from make depend: ../../pci/if_de.c:169: `#include' expects "FILENAME" or mkdep: compile failed *** Error code 1 Stop. -- Andy Luo keelung, TAIWAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 22:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24833 for freebsd-current-outgoing; Mon, 6 Jul 1998 22:13:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ConSys.COM (ConSys.COM [209.141.107.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24815 for ; Mon, 6 Jul 1998 22:13:38 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-216.prc.primenet.com [207.218.17.216]) by ConSys.COM (8.8.6/8.8.6) with ESMTP id WAA02133 for ; Mon, 6 Jul 1998 22:13:31 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.8.8/8.8.7) with ESMTP id WAA11141 for ; Mon, 6 Jul 1998 22:09:50 -0700 (MST) Message-Id: <199807070509.WAA11141@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: new list suggestion: makeworld Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Jul 1998 22:09:50 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not have a list for posting success/failure for making the world? Enough do it regularly, myself included, and we end up clogging current for usually banal reasons. The re:'s could take care of general user education over interface change issues as well. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 22:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25476 for freebsd-current-outgoing; Mon, 6 Jul 1998 22:18:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25471 for ; Mon, 6 Jul 1998 22:18:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA27604; Mon, 6 Jul 1998 22:17:46 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: joelh@gnu.org cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 17:11:22 CDT." <199807062211.RAA09001@detlev.UUCP> Date: Mon, 06 Jul 1998 22:17:46 -0700 Message-ID: <27600.899788666@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While I will agree that it does not run in a normal manner, it is not > an infrequent operation. Erm, fine. So come up with an access method for X that doesn't require this kind of security bypassing and I'm sure that everyone will be quite pleased with you. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 22:38:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28017 for freebsd-current-outgoing; Mon, 6 Jul 1998 22:38:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27908 for ; Mon, 6 Jul 1998 22:38:06 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA05836 for current@freebsd.org; Tue, 7 Jul 1998 15:37:58 +1000 Date: Tue, 7 Jul 1998 15:37:58 +1000 From: Bruce Evans Message-Id: <199807070537.PAA05836@godzilla.zeta.org.au> To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Modified files: > sys/pci pcisupport.c > Log: > Changed `#if defined(i386)' to `#ifdef __i386__'. > > `#if defined(ONE_THING)' is a style bug, and i386 instead of __i386__ > is a bug, since i386 is never defined when the kernel is compiled > by with the default flags (`gcc -ansi ...'). Here the bug disabled > the call to pmap_setvidram(), so ISA video memory was not mapped > WC on 686's. The bug may have been masked by bugs in the committer's > version of gcc - `gcc -ansi' incorrectly defines i386 for gcc = the > version of egcs on the 2.2.6 cdrom. Hopefully there is no hardware that depends on this bug. Write combining causes problems when it is used on device memory that doesn't look like frame buffer. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 22:41:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28552 for freebsd-current-outgoing; Mon, 6 Jul 1998 22:41:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28529 for ; Mon, 6 Jul 1998 22:41:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-124.camalott.com [208.229.74.124]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id AAA12420; Tue, 7 Jul 1998 00:41:11 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA10832; Tue, 7 Jul 1998 00:40:48 -0500 (CDT) (envelope-from joelh) Date: Tue, 7 Jul 1998 00:40:48 -0500 (CDT) Message-Id: <199807070540.AAA10832@detlev.UUCP> To: jkh@time.cdrom.com CC: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: <27600.899788666@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck References: <27600.899788666@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> While I will agree that it does not run in a normal manner, it is not >> an infrequent operation. > Erm, fine. So come up with an access method for X that doesn't > require this kind of security bypassing and I'm sure that everyone > will be quite pleased with you. :-) The implementation has been left as an exercise to the reader. Seriously, I didn't say it was something that should be fixed. In fact, I seem to recall saying that it's not worth fixing. I realize what is required to produce graphics on the PC, and that the security features of the architecture are laughable. I simply saw an email from somebody who was asking if this is a bug or a feature, and I gave my opinion. Now, will everybody please quit telling me why it exists, or why a fix is nontrivial? (If anybody thinks that not being able to run X when securelevel > 1 is the Right Thing, I would be happy to continue discussion.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 22:52:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00808 for freebsd-current-outgoing; Mon, 6 Jul 1998 22:52:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00798 for ; Mon, 6 Jul 1998 22:52:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA27827; Mon, 6 Jul 1998 22:51:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Joel Ray Holveck cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Tue, 07 Jul 1998 00:40:48 CDT." <199807070540.AAA10832@detlev.UUCP> Date: Mon, 06 Jul 1998 22:51:40 -0700 Message-ID: <27823.899790700@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now, will everybody please quit telling me why it exists, or why a fix > is nontrivial? (If anybody thinks that not being able to run X when > securelevel > 1 is the Right Thing, I would be happy to continue > discussion.) Erm, but what did you expect? Calling it a bug without attaching a fix is one of the most useless activities imaginable since the folks who are capable of "fixing" it already know why it's there and what the trade-offs are, so you're only going to get lots of the above from them ("this is why it exists, this is why a fix is non-trivial"). Those who aren't capable of fixing it aren't going to contribute much that's useful to the discussion either except for lots of "yeah! why does it work that way? Somebody should do something! I'm going to write my congressman!" :-) Truly, standing up on a soapbox and calling it a bug is Not Useful and has already been done before by a succession of previous soapbox orators (check out the OpenBSD mailing lists sometime for a whole book's worth of material on the topic). Suggesting some real, tangible approach to dealing with it would be a welcome switch from the usual. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 23:03:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02503 for freebsd-current-outgoing; Mon, 6 Jul 1998 23:03:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02485 for ; Mon, 6 Jul 1998 23:03:42 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id QAA07694; Tue, 7 Jul 1998 16:03:22 +1000 (EST) Message-ID: <19980707160322.48541@rf900.physics.usyd.edu.au> Date: Tue, 7 Jul 1998 16:03:22 +1000 From: David Dawes To: "Jordan K. Hubbard" Cc: joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) References: <199807062211.RAA09001@detlev.UUCP> <27600.899788666@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <27600.899788666@time.cdrom.com>; from Jordan K. Hubbard on Mon, Jul 06, 1998 at 10:17:46PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 10:17:46PM -0700, Jordan K. Hubbard wrote: >> While I will agree that it does not run in a normal manner, it is not >> an infrequent operation. > >Erm, fine. So come up with an access method for X that doesn't >require this kind of security bypassing and I'm sure that everyone >will be quite pleased with you. :-) Right. Running the X servers as they're currently implemented is totally inconsistent with the aims of running in secure mode. I don't understand why anyone is suggesting otherwise. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 23:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03970 for freebsd-current-outgoing; Mon, 6 Jul 1998 23:11:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03954 for ; Mon, 6 Jul 1998 23:11:36 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA21748; Tue, 7 Jul 1998 15:40:39 +0930 (CST) Message-Id: <199807070610.PAA21748@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 22:17:46 MST." <27600.899788666@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 15:40:39 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > While I will agree that it does not run in a normal manner, it is not > > an infrequent operation. > Erm, fine. So come up with an access method for X that doesn't > require this kind of security bypassing and I'm sure that everyone > will be quite pleased with you. :-) Hmm, well we could port GGI.. Kernel level graphics drivers :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 23:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05694 for freebsd-current-outgoing; Mon, 6 Jul 1998 23:24:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05683 for ; Mon, 6 Jul 1998 23:24:14 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id IAA26989; Tue, 7 Jul 1998 08:27:09 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 08:27:09 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Dusk Auriel Sykotik cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998, Dusk Auriel Sykotik wrote: > I once successfully ran FreeBSD on a 486 33 with 8 megs of ram. > (Box is still running in fact, no hdd space left, runs somewhat nicely. > Its running 2.2.6-RELEASE now.) I'm afraid you missed my point... :-) What you describe is not so unusual, especially if the box uses swap space. What I meant was to run in 4MB without swapping. > On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > > > Hi, > > > > This is slightly more general question than in the Subject. > > > > First issue is: what would it take to squeeze any useful combination of > > kernel, init plus two-three (small) user programs in 4MB? Which > > You don't want to run any inetd processes? As well as other such things > which use memory. No, I don't want. All I want to run is one or two daemons (routed + some remote login daemon). Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 6 23:45:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07955 for freebsd-current-outgoing; Mon, 6 Jul 1998 23:45:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07937 for ; Mon, 6 Jul 1998 23:45:27 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-42.camalott.com [208.229.74.42]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id BAA15059; Tue, 7 Jul 1998 01:45:35 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id BAA11011; Tue, 7 Jul 1998 01:43:45 -0500 (CDT) (envelope-from joelh) Date: Tue, 7 Jul 1998 01:43:45 -0500 (CDT) Message-Id: <199807070643.BAA11011@detlev.UUCP> To: jkh@time.cdrom.com CC: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: <27823.899790700@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck References: <27823.899790700@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Now, will everybody please quit telling me why it exists, or why a fix >> is nontrivial? (If anybody thinks that not being able to run X when >> securelevel > 1 is the Right Thing, I would be happy to continue >> discussion.) > Erm, but what did you expect? Calling it a bug without attaching a > fix is one of the most useless activities imaginable Woah, wait a sec. I was *answering a question*. If I need to either attach a fix or call it a feature, then we need to consider our terminology. I was *not* asking for it to be fixed. (I generally try not to ask for fixes; I send patches.) I was *not* saying that BSD / FreeBSD / XFree86 / securelevel or anything is evil because of this issue. What I was doing was *answering a question*. To be precise, from message ID <199807060816.MAA27917@minas-tirith.pol.ru>: > Hmm... WHY X cannot be started with securelevel set? Is it a bug or > a feature? I will answer questions. I consider answering questions useful. I see this, for a variety of reasons, as a bug. It's a bug dealing with the x86 architecture design, but I can't see how it could seriously be construed as a feature. I saw a question. I answered it. That is why I considered the activity useful. (I don't know why I find continuing this thread useful, and will probably cease to do so RSN.) > since the folks who are capable of "fixing" it already know why it's > there and what the trade-offs are, so you're only going to get lots > of the above from them ("this is why it exists, this is why a fix is > non-trivial"). Apologies for wasting said folks' time. I suppose I should have made my opinion known in private email, instead of on the lists. > Those who aren't capable of fixing it aren't going to contribute much > that's useful to the discussion either except for lots of "yeah! why > does it work that way? Somebody should do something! I'm going to > write my congressman!" :-) That's why I'm glad that 'd' is on the home row. > Truly, standing up on a soapbox and calling it a bug is Not Useful and > has already been done before by a succession of previous soapbox > orators (check out the OpenBSD mailing lists sometime for a whole > book's worth of material on the topic). Suggesting some real, > tangible approach to dealing with it would be a welcome switch from > the usual. I see more soapbox speeches than I can conveniently conceive of shaking a stick at. In everything I do, be that BSD or SCA. I have gotten into the habit of ignoring them and going on about life. I was not making a soapbox speech (or, if I was, I didn't realize it). I was not saying it should be fixed. In fact, if I didn't outright state it, I implied that it's not worth the time. And it's definately not worth the time for us to discuss the futility of bringing up problems without fixes. I know it, you know it, my ferrets are rapidly learning, I'm sure a few of your cats can recite a speech on it by now. Now, let's kindly let this die. I've got some hacking to do. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:03:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10902 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:03:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10892 for ; Tue, 7 Jul 1998 00:03:20 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA01156; Tue, 7 Jul 1998 00:02:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807070702.AAA01156@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 08:27:09 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 00:02:58 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > First issue is: what would it take to squeeze any useful combination of > > > kernel, init plus two-three (small) user programs in 4MB? Which > > > > You don't want to run any inetd processes? As well as other such things > > which use memory. > I would start by first knowing how much memory is needed to run a kernel, init plus two or three (small) user programs with the current system. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10933 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:03:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10924 for ; Tue, 7 Jul 1998 00:03:38 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA06515; Tue, 7 Jul 1998 00:03:33 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd006503; Tue Jul 7 00:03:31 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA03715; Tue, 7 Jul 1998 00:03:22 -0700 (MST) From: Terry Lambert Message-Id: <199807070703.AAA03715@usr06.primenet.com> Subject: Re: FreeBSD in less than 4MB RAM To: mike@smith.net.au (Mike Smith) Date: Tue, 7 Jul 1998 07:03:22 +0000 (GMT) Cc: abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <199807061550.IAA03457@antipodes.cdrom.com> from "Mike Smith" at Jul 6, 98 08:50:24 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The second issue is this: currently we're unable to boot (using BIOS) and > > mount as / other filesystems than FFS, NFS and CD9660. It would be great > > if we could use MSDOSFS as well (using special version of biosboot, with > > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. > > All you have to do is add the mountroot stuff to MSDOSFS - nobody would > complain if you did. I would. The "mountroot" and "mount" disctinctions are relatively stupid. There is duplicate code all over the place, only it's "almost duplicate" and causes lots of problems. The main tigers in the way of progress are NFS root mounts and CD9660, which is so conditionalized that it's nearly impossible to tread safely through the minefield. The way to fix this is to move the "root-ness" and "non-root-ness" to upper level (common!) code. The implementaiton of this is rather simple: 1) Change the per-FS VOP_MOUNT to mount the FS into the "mounted FS's" mount struct list *only*. 2) When doing a root mount, point to the appropriate list entry. 3) When doing a non-root ("map-into-hierarchy") mount, A) Point to the appropriate list entry using the "covered by" vnode pointer. B) Call the new VFSOP "SETMOUNT" to set the "last mounted on" field of the superblock. 4) Call back into the NFS export code from the upper level code. 5) return. I have implemented this three times (so far) in various versions of FreeBSD. This results in the following benefits: 1) All FS types may be mounted as root 2) All FS types may be exported via NFS 3) All commonly miswritten and/or "bit-rotted" code, like LFS's mount and NFS interaction code, is centrally maintained and automatically synchronized for all FS's. Therefore, all code is less succeptible to miswriting and/or "bit-rot". 4) New FS implementations become less work. 5) Kernel size is reduced. Perhaps you can get these changes in where I have failed. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11986 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:08:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11962 for ; Tue, 7 Jul 1998 00:08:51 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA21966; Tue, 7 Jul 1998 00:08:49 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd021954; Tue Jul 7 00:08:49 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA03942; Tue, 7 Jul 1998 00:08:43 -0700 (MST) From: Terry Lambert Message-Id: <199807070708.AAA03942@usr06.primenet.com> Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 7 Jul 1998 07:08:43 +0000 (GMT) Cc: joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-Reply-To: <26015.899757973@time.cdrom.com> from "Jordan K. Hubbard" at Jul 6, 98 01:46:13 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Most things that are disallowed under securelevel 1 are things that > > aren't frequently done except during rc, a system install, or an > > attack. But running X is a normal operation. I'd classify it as a > > bug myself. > > Actually, running X is not a "normal" operation at all - it performs > inb/outb instructions and does various privileged bits of syscons > frobbing that could be potentially quite hazardous in the hands of the > deliberately malicious. Running an X server should be a conscious > compromise of certain types of security. You wouldn't classify this as an architectural design bug in the granularity of FreeBSD's control over the I/O address space? Or in FreeBSD's console driver code leaving the X server no choice to obtain access to the display in bitmap mode? Admittedly, requiring user accessiblity to I/O space to get hardware to do something is wrong, but the requirement is because of FreeBSD not abstracting that access via a user<->kernel interface, not an inherent problem with the hardware. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12798 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:12:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12787 for ; Tue, 7 Jul 1998 00:12:49 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA21698; Tue, 7 Jul 1998 00:12:47 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd021684; Tue Jul 7 00:12:42 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA04296; Tue, 7 Jul 1998 00:12:40 -0700 (MST) From: Terry Lambert Message-Id: <199807070712.AAA04296@usr06.primenet.com> Subject: Re: new list suggestion: makeworld To: rcarter@pinyon.org (Russell L. Carter) Date: Tue, 7 Jul 1998 07:12:40 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199807070509.WAA11141@psf.Pinyon.ORG> from "Russell L. Carter" at Jul 6, 98 10:09:50 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why not have a list for posting success/failure > for making the world? Enough do it regularly, > myself included, and we end up clogging current > for usually banal reasons. No one who was causing the breakage would subscribe; I sure as heck wouldn't, especially if I were the type of person who broke the builds frequently. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:18:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13670 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:18:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13658 for ; Tue, 7 Jul 1998 00:18:13 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA24711; Tue, 7 Jul 1998 00:18:12 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd024668; Tue Jul 7 00:18:09 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA04728; Tue, 7 Jul 1998 00:18:05 -0700 (MST) From: Terry Lambert Message-Id: <199807070718.AAA04728@usr06.primenet.com> Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 7 Jul 1998 07:18:05 +0000 (GMT) Cc: joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-Reply-To: <27823.899790700@time.cdrom.com> from "Jordan K. Hubbard" at Jul 6, 98 10:51:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Truly, standing up on a soapbox and calling it a bug is Not Useful and > has already been done before by a succession of previous soapbox > orators (check out the OpenBSD mailing lists sometime for a whole > book's worth of material on the topic). Suggesting some real, > tangible approach to dealing with it would be a welcome switch from > the usual. I'm pretty sure patches to add Linux-like control to the I/O address space rather than using the /dev/io hack have gone by several times; from recollection, these patches have been rejected on the basis of performance degradation for context switching. But they *have* gone by on the list at least twice that I'm aware of (once in the context of X, and once in the context of the Linux emulator ABI support). This is on the order of the "f00f" fix: it degrades performance, but it fixes a problem. The difference is only in where the (arbitrary) cost/benefit axe comes down. PS: Linux has better context switch times than FreeBSD, if I recall correctly, so the argument about overhead being unacceptable has got to be pretty specious... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15438 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:40:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15433 for ; Tue, 7 Jul 1998 00:40:46 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA25954; Tue, 7 Jul 1998 00:40:46 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd025915; Tue Jul 7 00:40:39 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA05523; Tue, 7 Jul 1998 00:40:33 -0700 (MST) From: Terry Lambert Message-Id: <199807070740.AAA05523@usr06.primenet.com> Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Tue, 7 Jul 1998 07:40:32 +0000 (GMT) Cc: jkh@time.cdrom.com, joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-Reply-To: <199807070610.PAA21748@cain.gsoft.com.au> from "Daniel O'Connor" at Jul 7, 98 03:40:39 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, well we could port GGI.. > Kernel level graphics drivers :) Tragically, they have made this a closed standard by placing all components, including kernel components, under GPL. This means that the code is useless to anything but a GPL'ed OS, of which there is Linux. The code simple can not be mainstreamed, either by making a GGI using NT and windows 95/98 driver, or by adoption by any commercial or commercially exploitable or commercially embeddable OS. Currently, it serves a proprietary reference implemetnation, usable only by the authors porting platform, Linux. They might as well have implemented The Open Group's new version of X: available to be used, but not utilized, and therefore useless. 8-(. Basically, a totally seperate set of KGI code would be required. Their site claims the beginnings of an OpenBSD port, but hasn't (the US mirror, at least, which is what I can get to) hasn't been updated for over a month: http://www.lysator.liu.se/~mars/ggi/www-interface/ggit-extract-full-article.cgi?67/ If so, the KGI code must be a full rewrite, for the obvious reasons, above. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 00:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17312 for freebsd-current-outgoing; Tue, 7 Jul 1998 00:59:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17307 for ; Tue, 7 Jul 1998 00:59:21 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA22514; Tue, 7 Jul 1998 10:01:45 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 10:01:45 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807061550.IAA03457@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998, Mike Smith wrote: > > Hi, > > > > This is slightly more general question than in the Subject. > > > > First issue is: what would it take to squeeze any useful combination of > > kernel, init plus two-three (small) user programs in 4MB? Which > > (dispensable) parts of the kernel require so much space? After removing > > all I could think of (leaving FFS, fd0, and ed0, though) the kernel size > > is still about 700kB big, and quite another question is how this > > translates into running size... > > try "du *.o | sort -n" in your compile directory. I did (Soren can be proud - he wins with syscons.o :-), but this really doesn't tell anything about _running_ sizes of various data structures... Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 01:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17972 for freebsd-current-outgoing; Tue, 7 Jul 1998 01:03:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17960 for ; Tue, 7 Jul 1998 01:03:29 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA23425; Tue, 7 Jul 1998 10:06:11 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 10:06:10 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Terry Lambert cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807070703.AAA03715@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Terry Lambert wrote: > > All you have to do is add the mountroot stuff to MSDOSFS - nobody would > > complain if you did. > > I would. > > The "mountroot" and "mount" disctinctions are relatively stupid. > The implementaiton of this is rather simple: [...but way above my head... :-( ] > I have implemented this three times (so far) in various versions > of FreeBSD. Wow... So, what are the obstacles? As you present it, it has only advantages... Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 01:12:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19326 for freebsd-current-outgoing; Tue, 7 Jul 1998 01:12:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19317 for ; Tue, 7 Jul 1998 01:12:51 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA25848; Tue, 7 Jul 1998 10:15:14 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 10:15:14 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Amancio Hasty cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807070702.AAA01156@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Amancio Hasty wrote: > > > > > > > > > First issue is: what would it take to squeeze any useful combination of > > > > kernel, init plus two-three (small) user programs in 4MB? Which > > > > > > You don't want to run any inetd processes? As well as other such things > > > which use memory. > > > > I would start by first knowing how much memory is needed to run > a kernel, init plus two or three (small) user programs with the > current system. Not much - my experiments show it's somewhere around 6MB (if you start 2-3 different programs, so that they can't share their pages). Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 01:17:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19990 for freebsd-current-outgoing; Tue, 7 Jul 1998 01:17:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19956 for ; Tue, 7 Jul 1998 01:17:09 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA01682; Tue, 7 Jul 1998 01:16:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807070816.BAA01682@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 10:15:14 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 01:16:55 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now, where is all the memory being allocated: 1. kernel 2. small process 1 3. small process 2 4. xxxx any other daemons that you have running Also have you trimmed down the kernel? Cheers, Amancio > On Tue, 7 Jul 1998, Amancio Hasty wrote: > > > > > > > > > > > > > First issue is: what would it take to squeeze any useful combination of > > > > > kernel, init plus two-three (small) user programs in 4MB? Which > > > > > > > > You don't want to run any inetd processes? As well as other such things > > > > which use memory. > > > > > > > I would start by first knowing how much memory is needed to run > > a kernel, init plus two or three (small) user programs with the > > current system. > > Not much - my experiments show it's somewhere around 6MB (if you start 2-3 > different programs, so that they can't share their pages). > > Andrzej Bialecki > > --------------------+--------------------------------------------------------- > abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } > Research & Academic | "Be open-minded, but don't let your brains to fall out." > Network in Poland | All of the above (and more) is just my personal opinion. > --------------------+--------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 01:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22059 for freebsd-current-outgoing; Tue, 7 Jul 1998 01:33:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22052 for ; Tue, 7 Jul 1998 01:33:14 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA01484; Tue, 7 Jul 1998 10:36:09 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 10:36:08 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Amancio Hasty cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807070816.BAA01682@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Amancio Hasty wrote: > Now, where is all the memory being allocated: > > 1. kernel 1.1 init 1.2 fork() > 2. small process 1 2.1 fork() > 3. small process 2 > 4. xxxx any other daemons that you have running 4.x fork() ...and you start seeing "small_process (pid xxx): killed" and "out of swap space"... But that was also my question - to have a way to check what portion of memory is allocated to which structure... I'm afraid there is no generic answer to this. Also, "kernel" above doesn't equal `size kernel` - there are disk buffers, mbufs, stacks, and whatnot which are allocated on start; so its much bigger. > Also have you trimmed down the kernel? If you mean "stripping" - yes. What I forgot to add (sorry...) is that I'm primarily interested in situations where there is no swap. This usually means there is no disk and there is a MFS taking its sweet portion of RAM... Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 01:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23168 for freebsd-current-outgoing; Tue, 7 Jul 1998 01:45:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23162 for ; Tue, 7 Jul 1998 01:45:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA01867; Tue, 7 Jul 1998 01:45:04 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807070845.BAA01867@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 10:36:08 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 01:45:04 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you use something like vmstat to figure out how much memory is the kernel taking up? Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 02:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25401 for freebsd-current-outgoing; Tue, 7 Jul 1998 02:09:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25389 for ; Tue, 7 Jul 1998 02:09:46 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id LAA11125; Tue, 7 Jul 1998 11:12:00 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 7 Jul 1998 11:11:59 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Amancio Hasty cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807070845.BAA01867@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Jul 1998, Amancio Hasty wrote: > Can you use something like vmstat to figure out how much memory is > the kernel taking up? 8-O... Yes! I really should read manpages more thouroughly... vmstat -m gives quite a lot of info on internal structures' sizes - perhaps not all that I'd like to know, but it's something... Thanks! Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 02:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28185 for freebsd-current-outgoing; Tue, 7 Jul 1998 02:40:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28180 for ; Tue, 7 Jul 1998 02:40:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA13179; Tue, 7 Jul 1998 09:40:32 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA21094; Tue, 7 Jul 1998 11:40:31 +0200 (MET DST) Message-ID: <19980707114030.01585@follo.net> Date: Tue, 7 Jul 1998 11:40:30 +0200 From: Eivind Eklund To: "Russell L. Carter" , current@FreeBSD.ORG Subject: Re: new list suggestion: makeworld References: <199807070509.WAA11141@psf.Pinyon.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199807070509.WAA11141@psf.Pinyon.ORG>; from Russell L. Carter on Mon, Jul 06, 1998 at 10:09:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 10:09:50PM -0700, Russell L. Carter wrote: > > Why not have a list for posting success/failure > for making the world? Enough do it regularly, > myself included, and we end up clogging current > for usually banal reasons. > > The re:'s could take care of general user education > over interface change issues as well. IMO, this is quite relevant for -current. The problem is that there are lots of discussions in -current that really belong in -hackers, but that don't end up there because there is too much noise in -hackers. An option may be a moderated technical list, to have a more or less noise-less forum for technical discussions, freeing -current for the strict -current issues (as opposed to architectural discussions etc). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 03:36:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04789 for freebsd-current-outgoing; Tue, 7 Jul 1998 03:36:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04782 for ; Tue, 7 Jul 1998 03:36:42 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id DAA21110; Tue, 7 Jul 1998 03:36:42 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd021081; Tue Jul 7 03:36:32 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id DAA00212; Tue, 7 Jul 1998 03:36:22 -0700 (MST) From: Terry Lambert Message-Id: <199807071036.DAA00212@usr01.primenet.com> Subject: Re: FreeBSD in less than 4MB RAM To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 7 Jul 1998 10:36:22 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Jul 7, 98 10:06:10 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > All you have to do is add the mountroot stuff to MSDOSFS - nobody would > > > complain if you did. > > > > I would. > > > > The "mountroot" and "mount" disctinctions are relatively stupid. > > > > The implementaiton of this is rather simple: > > [...but way above my head... :-( ] BS. I could do an ASCII art of it, if I weren't about to hit the sack... it's very easy to visualize. The hardest part about explaining it is explaining the byzantine way it currently works so you can see what's changing and how it's better off changed. > > I have implemented this three times (so far) in various versions > > of FreeBSD. > > Wow... So, what are the obstacles? As you present it, it has > only advantages... The first time, it was USL. After USL? It touches a lot of code at once. Every FS. And everything that got touched would need to get tested. It also changes the VFS interface, damaging compatability with other 4.4-derived OS's; I don't think this is as big a problem as it was the last time, before the Lite2 release was integrated, though, since FreeBSD is diverging quite a bit now. Also, many times, when this testing happens, you see bugs that were there all along (NFS, especially), but were not revealed until the testing. And then, of course, the last change is the obvious culprit. 8-). Part of the changes made it in last time; the root/non-root mount unification was a step towards it, since it documents the code distinction much better. Moving the SETMOUNTON and the vn covering is pretty obvious, if you read the mount code for two or more FS's, side-by-side. Just avoid NFS and CD9660 as documentation, and move part of the FFS mount to common code, and another part of it to a seperate VFSOP, and FFS is pretty much done. I might do it this coming weekend, if I can get g++ 2.8.1 to behave correctly before then (the headers are either installed in the wrong place, or they are incorrectly referenced by the compiler, and you end up with the g++ 2.7.2 includes and a g++ 2.8.1 compiler, which is a bad mix -- the port is only partly happy). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 04:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08241 for freebsd-current-outgoing; Tue, 7 Jul 1998 04:01:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts01-53.waterford.indigo.ie [194.125.139.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08231 for ; Tue, 7 Jul 1998 04:01:34 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id LAA00722; Tue, 7 Jul 1998 11:56:22 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807071056.LAA00722@indigo.ie> Date: Tue, 7 Jul 1998 11:56:21 +0000 In-Reply-To: "Jordan K. Hubbard" "Re: xf86OpenConsole: KDENABIO failed (Operation not permitted)" (Jul 6, 10:17pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: "Jordan K. Hubbard" , joelh@gnu.org Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) Cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 6, 10:17pm, "Jordan K. Hubbard" wrote: } Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) > > While I will agree that it does not run in a normal manner, it is not > > an infrequent operation. > > Erm, fine. So come up with an access method for X that doesn't > require this kind of security bypassing and I'm sure that everyone > will be quite pleased with you. :-) It's not unreasonable to let X do its thing, on any secure system all of X will be gid consoleusers mode 750 anyway. Afaik you can let it do what it needs to do using iopl or a i/o port privilege map, the trick is authenticating X, perhaps a sysctl which is only settable in secure level < 0 which specifies which binaries get iopl permissions when running as root would do the trick, then again, perhaps someone has a better idea. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 05:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15017 for freebsd-current-outgoing; Tue, 7 Jul 1998 05:00:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.tue.le (pC19F83DB.dip.t-online.de [193.159.131.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14982 for ; Tue, 7 Jul 1998 05:00:26 -0700 (PDT) (envelope-from thz@Lennartz-Electronic.DE) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id NAA00381; Tue, 7 Jul 1998 13:58:47 +0200 (CEST) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.8.8/8.8.8) id NAA02688; Tue, 7 Jul 1998 13:58:47 +0200 (MET DST) (envelope-from thz) Message-ID: <19980707135847.61797@tue.le> Date: Tue, 7 Jul 1998 13:58:47 +0200 From: Thomas Zenker To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM Mail-Followup-To: Andrzej Bialecki , freebsd-current@freebsd.org References: <199807070702.AAA01156@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Andrzej Bialecki on Tue, Jul 07, 1998 at 10:15:14AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 07, 1998 at 10:15:14AM +0200, Andrzej Bialecki wrote: > On Tue, 7 Jul 1998, Amancio Hasty wrote: > >> > > > First issue is: what would it take to squeeze any useful combination of >> > > > kernel, init plus two-three (small) user programs in 4MB? Which >> > > >> > > You don't want to run any inetd processes? As well as other such things >> > > which use memory. >> > >> >> I would start by first knowing how much memory is needed to run >> a kernel, init plus two or three (small) user programs with the >> current system. > >Not much - my experiments show it's somewhere around 6MB (if you start 2-3 >different programs, so that they can't share their pages). A couple of years back it was easily possible to have kernel and a couple of user processes in 4 MB. I had such a thing running with BSD/386 0.9 - 1.1, then they got fat. Up to V1.1 it was possible to have a kernel size of about 360K with the same "needed" functionality as we got later with a 800K V 2.0 kernel. The same with FBSD, I can not get a kernel smaller than about 800K now. Probably it would be possible to get a better modularity, but that's very difficult. For those which say "put in more memory/disk": This doesn't help if you have to run out of batteries w/ solar-panels on very remote localities, only access by radio-telemetry. You need very low power equipment there. So the question is not $ but watts. -- Thomas Zenker at work thz@lennartz-electronic.de private thz@tuebingen.netsurf.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 09:56:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27104 for freebsd-current-outgoing; Tue, 7 Jul 1998 09:56:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27098 for ; Tue, 7 Jul 1998 09:56:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00592; Tue, 7 Jul 1998 09:54:34 -0700 (PDT) Message-Id: <199807071654.JAA00592@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 10:01:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 09:54:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 6 Jul 1998, Mike Smith wrote: > > > > Hi, > > > > > > This is slightly more general question than in the Subject. > > > > > > First issue is: what would it take to squeeze any useful combination of > > > kernel, init plus two-three (small) user programs in 4MB? Which > > > (dispensable) parts of the kernel require so much space? After removing > > > all I could think of (leaving FFS, fd0, and ed0, though) the kernel size > > > is still about 700kB big, and quite another question is how this > > > translates into running size... > > > > try "du *.o | sort -n" in your compile directory. > > I did (Soren can be proud - he wins with syscons.o :-), but this really > doesn't tell anything about _running_ sizes of various data structures... vmstat -m gives you allocation statistics while the kernel is running, and 'size' will tell you how big the bss is in total. If you want to work out how big the various symbols in the bss are, use something like # nm -t kernel | sort | where looks for lines with a type field of 'b' or 'B', and calculates the distance between the current symbol and the next one. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 10:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28581 for freebsd-current-outgoing; Tue, 7 Jul 1998 10:02:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28568 for ; Tue, 7 Jul 1998 10:02:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00644; Tue, 7 Jul 1998 10:00:04 -0700 (PDT) Message-Id: <199807071700.KAA00644@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: jkh@time.cdrom.com (Jordan K. Hubbard), joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Tue, 07 Jul 1998 07:18:05 -0000." <199807070718.AAA04728@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 10:00:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Truly, standing up on a soapbox and calling it a bug is Not Useful and > > has already been done before by a succession of previous soapbox > > orators (check out the OpenBSD mailing lists sometime for a whole > > book's worth of material on the topic). Suggesting some real, > > tangible approach to dealing with it would be a welcome switch from > > the usual. > > I'm pretty sure patches to add Linux-like control to the I/O address > space rather than using the /dev/io hack have gone by several times; They actually exist in -current, although Bruce is not fond of the implementation. He says: ... FreeBSD ioperm is not completely implemented. It is only available if the kernel was configured with `options "VM86"'. It is a subcall of sysarch(undocumented). You have to pass it a pointer to a poorly laid out struct giving the args, something like this: Linux: int ioperm(u_long from, u_long num, int turn_on); FreeBSD: struct i386_ioperm_args { u_short from, num; u_char turn_on; } foo; sysarch(I386_SET_IOPERM, /* XXX 1970's interface */ (char *)&foo); Here are some fixes for the bugs. They are untested. diff -c2 sys_machdep.c~ sys_machdep.c *** sys_machdep.c~ Fri Nov 28 14:37:35 1997 --- sys_machdep.c Fri Nov 28 17:28:16 1997 *************** *** 181,185 **** char *args; { ! int i, error = 0; struct i386_ioperm_args ua; char *iomap; --- 181,185 ---- char *args; { ! int i, error; struct i386_ioperm_args ua; char *iomap; *************** *** 188,194 **** return (error); - /* Only root can do this */ if (error = suser(p->p_ucred, &p->p_acflag)) return (error); /* * XXX --- 188,195 ---- return (error); if (error = suser(p->p_ucred, &p->p_acflag)) return (error); + if (securelevel > 0) + return (EPERM); /* * XXX *************** *** 203,207 **** iomap = (char *)p->p_addr->u_pcb.pcb_ext->ext_iomap; ! if ((int)(ua.start + ua.length) > 0xffff) return (EINVAL); --- 204,208 ---- iomap = (char *)p->p_addr->u_pcb.pcb_ext->ext_iomap; ! if (ua.start + ua.length > IOPAGES * PAGE_SIZE * NBBY) return (EINVAL); *************** *** 220,224 **** char *args; { ! int i, state, error = 0; struct i386_ioperm_args ua; char *iomap; --- 221,225 ---- char *args; { ! int i, state, error; struct i386_ioperm_args ua; char *iomap; *************** *** 226,229 **** --- 227,232 ---- if (error = copyin(args, &ua, sizeof(struct i386_ioperm_args))) return (error); + if (ua.start >= IOPAGES * PAGE_SIZE * NBBY) + return (EINVAL); if (p->p_addr->u_pcb.pcb_ext == 0) { *************** *** 234,237 **** --- 237,242 ---- iomap = (char *)p->p_addr->u_pcb.pcb_ext->ext_iomap; + i = ua.start; + state = (iomap[i >> 3] >> (i & 7)) & 1; ua.enable = !state; ua.length = 1; Bruce -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 10:26:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02086 for freebsd-current-outgoing; Tue, 7 Jul 1998 10:26:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02078 for ; Tue, 7 Jul 1998 10:26:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00785; Tue, 7 Jul 1998 10:25:50 -0700 (PDT) Message-Id: <199807071725.KAA00785@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Thomas Zenker cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 13:58:47 +0200." <19980707135847.61797@tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 10:25:50 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A couple of years back it was easily possible to have kernel and a couple of > user processes in 4 MB. I had such a thing running with BSD/386 0.9 - 1.1, > then they got fat. Up to V1.1 it was possible to have a kernel size of > about 360K with the same "needed" functionality as we got later with a > 800K V 2.0 kernel. The same with FBSD, I can not get a kernel smaller > than about 800K now. Probably it would be possible to get a better > modularity, but that's very difficult. > > For those which say "put in more memory/disk": This doesn't help if you > have to run out of batteries w/ solar-panels on very remote localities, > only access by radio-telemetry. You need very low power equipment there. > So the question is not $ but watts. In the same timeframe, memory power consumption has gone down by more than an order of maginitude, while cost has fallen even further. Sorry, but the argument still holds good. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 10:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05300 for freebsd-current-outgoing; Tue, 7 Jul 1998 10:50:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05241 for ; Tue, 7 Jul 1998 10:50:08 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA15882; Wed, 8 Jul 1998 03:49:32 +1000 Date: Wed, 8 Jul 1998 03:49:32 +1000 From: Bruce Evans Message-Id: <199807071749.DAA15882@godzilla.zeta.org.au> To: abial@nask.pl, mike@smith.net.au Subject: Re: FreeBSD in less than 4MB RAM Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >vmstat -m gives you allocation statistics while the kernel is running, vmstat -m doesn't actually show vm allocations. It only shows the allocations that go through malloc(), not the ones that go directly to the vm allocators. Lots of allocation is now done by the zone allocator and only shown by `sysctl vm.zone'. Lots of allocation is done by the mbuf allocator and only shown by `netstat -m' ... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 11:11:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08859 for freebsd-current-outgoing; Tue, 7 Jul 1998 11:11:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.tue.le (pC19F22CC.dip.t-online.de [193.159.34.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08851 for ; Tue, 7 Jul 1998 11:11:47 -0700 (PDT) (envelope-from thz@Lennartz-Electronic.DE) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id UAA00847; Tue, 7 Jul 1998 20:10:30 +0200 (CEST) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.8.8/8.8.8) id UAA10020; Tue, 7 Jul 1998 20:10:29 +0200 (MET DST) (envelope-from thz) Message-ID: <19980707201029.31948@tue.le> Date: Tue, 7 Jul 1998 20:10:29 +0200 From: Thomas Zenker To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM Mail-Followup-To: Mike Smith , freebsd-current@freebsd.org References: <19980707135847.61797@tue.le> <199807071725.KAA00785@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199807071725.KAA00785@dingo.cdrom.com>; from Mike Smith on Tue, Jul 07, 1998 at 10:25:50AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 07, 1998 at 10:25:50AM -0700, Mike Smith wrote: > > A couple of years back it was easily possible to have kernel and a couple of > > user processes in 4 MB. I had such a thing running with BSD/386 0.9 - 1.1, > > then they got fat. Up to V1.1 it was possible to have a kernel size of > > about 360K with the same "needed" functionality as we got later with a > > 800K V 2.0 kernel. The same with FBSD, I can not get a kernel smaller > > than about 800K now. Probably it would be possible to get a better > > modularity, but that's very difficult. > > > > For those which say "put in more memory/disk": This doesn't help if you > > have to run out of batteries w/ solar-panels on very remote localities, > > only access by radio-telemetry. You need very low power equipment there. > > So the question is not $ but watts. > > In the same timeframe, memory power consumption has gone down by more > than an order of maginitude, while cost has fallen even further. > > Sorry, but the argument still holds good. 8) Sorry, but to run with 3 watts from dynamic memory is not possible, do you know prices of SRAM? Also effordable harddisks are much lower now in consumption, but not that low. So booting from eprom or floppy is a must. -- Thomas Zenker at work thz@lennartz-electronic.de private thz@tuebingen.netsurf.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 11:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12184 for freebsd-current-outgoing; Tue, 7 Jul 1998 11:29:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12178 for ; Tue, 7 Jul 1998 11:29:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA01144; Tue, 7 Jul 1998 11:28:13 -0700 (PDT) Message-Id: <199807071828.LAA01144@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Thomas Zenker cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-reply-to: Your message of "Tue, 07 Jul 1998 20:10:29 +0200." <19980707201029.31948@tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jul 1998 11:28:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > For those which say "put in more memory/disk": This doesn't help if you > > > have to run out of batteries w/ solar-panels on very remote localities, > > > only access by radio-telemetry. You need very low power equipment there. > > > So the question is not $ but watts. > > > > In the same timeframe, memory power consumption has gone down by more > > than an order of maginitude, while cost has fallen even further. > > > > Sorry, but the argument still holds good. 8) > > Sorry, but to run with 3 watts from dynamic memory is not possible, > do you know prices of SRAM? Also effordable harddisks are > much lower now in consumption, but not that low. So booting from > eprom or floppy is a must. No insult intended, but your design obviously sucks. I am working right now with a PC104 board not specifically designed for low-power operation. It manages to put an NX586-based micro, all the standard PC peripherals, 8M of RAM, 8M of flash, etc. into a sub-3W power budget. Like I said, this is a design that's not even trying. Look at the power budget that eg. the Palm Pilot works with. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 16:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20631 for freebsd-current-outgoing; Tue, 7 Jul 1998 16:39:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20587 for ; Tue, 7 Jul 1998 16:39:09 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id BAA03213; Wed, 8 Jul 1998 01:39:02 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id AAA01215; Wed, 8 Jul 1998 00:50:57 +0200 (MET DST) (envelope-from wosch) Message-ID: <19980708005056.10385@panke.de> Date: Wed, 8 Jul 1998 00:50:56 +0200 From: Wolfram Schneider To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current wishlist References: <199807020322.WAA05412@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199807020322.WAA05412@home.dragondata.com>; from Kevin Day on Wed, Jul 01, 1998 at 10:22:08PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-01 22:22:08 -0500, Kevin Day wrote: > I don't know if there's a Santa Claus on -current right now, but I've got a > few suggestions/weak spots I see in -current now, and would be more than > willing to help anyone wanting to work on these. I'm not that deep into the > mysteries of the kernel to just do it myself, but I'm a willing test > subject. :) [...] > 8) Load average seems to have no bearing on how busy the system really is. > > last pid: 21803; load averages: 2.74, 2.82, 2.88 > 135 processes: 3 running, 131 sleeping, 1 zombie > CPU states: 1.7% user, 0.0% nice, 1.3% system, 1.7% interrupt, 95.2% idle > Mem: 75M Active, 12M Inact, 23M Wired, 6520K Cache, 8347K Buf, 8364K Free > Swap: 164M Total, 25M Used, 139M Free, 16% Inuse > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND > 21800 toasty 29 0 1664K 940K CPU0 1 0:00 2.15% 1.03% top > > If the load average is 2.74, how can the CPU be 95.2% idle? If it really is, > what's it waiting on so much? Or am I just misinterpreting this? The machine waits for i/o traffic. Processes which sleeps less than 1 second due net or disk i/o traffic counts as runnings processes. -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 7 18:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03162 for freebsd-current-outgoing; Tue, 7 Jul 1998 18:38:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (eppp6.sysnet.net [206.142.16.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03127 for ; Tue, 7 Jul 1998 18:38:10 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id VAA15385 for ; Tue, 7 Jul 1998 21:28:48 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Jul 1998 21:15:41 -0400 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: building world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry to have to drop this on the mailing list readership... I downloaded 2.2.6-release. acquired cvsup, and grabbed the whole source tree, or at least what corresponds to src-all. Tried a make "buildworld" and the top level make file blew up all over the place. Parse errors due to environment variables like MACHINE_ARCH or BINFORMAT not being defined. I figured it might be due to the 'old' make. Tried making just that bugger. No dice, couldn't link cause __error was missing. What library would that be from? So what is the proper series of steps one needs to follow to move from the release to -current? -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 02:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01126 for freebsd-current-outgoing; Wed, 8 Jul 1998 02:09:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01117 for ; Wed, 8 Jul 1998 02:09:12 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id WAA20954; Tue, 7 Jul 1998 22:04:34 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 7 Jul 1998 22:04:34 -0400 (EDT) From: "Alok K. Dhir" To: Sean Eric Fagan cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_sig.c In-Reply-To: <8A6103670C8BFCA28525663B00026B8B.0001A8048525663B@worldbank.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good stuff! Perhaps this should be added to rc.conf? On Tue, 7 Jul 1998, Sean Eric Fagan wrote: > > > In article <199807072341.QAA02595.kithrup.freebsd.cvs-all@dingo.cdrom.com> > you write: > >> I wish we had a sysctl variable for the coredump name. Eg. > >> > >> kern.coredump.name = > >> > >> 0 -> disable core dumps > >> 1 -> core dump filename 'core' > >> 2 -> core dump filename 'program.core' > >> 3 -> core dump filename 'core.program' > > > >I think you should buy Sean a beer. > > Indeed. I'd just sent Mike some diffs (Jordan's seen 'em too) to do this: > > He suggested changes, not all of which I've done yet. But this gives you > teh > basic idea. Note that it allows three format specifiers: %N == process > name, > %P == process ID, %U == user ID. > > Examples of ones I've tested: > > sysctl -w kern.corefilename="core" > sysctl -w kern.corefilename="%N.core" > sysctl -w kern.corefilename="core.%N" > sysctl -w kern.corefilename="/tmp/%N-%P.core" > sysctl -w kern.corefilename="/dev/null" > > Index: kern/kern_sig.c > =================================================================== > RCS file: /usr/cvs/src/sys/kern/kern_sig.c,v > retrieving revision 1.26.2.1 > diff -u -r1.26.2.1 kern_sig.c > --- kern_sig.c 1996/12/21 18:57:24 1.26.2.1 > +++ kern_sig.c 1998/07/04 18:25:22 > @@ -61,6 +61,8 @@ > #include > #include > #include > +#include > +#include > > #include > > @@ -75,6 +77,7 @@ > static int coredump __P((struct proc *p)); > static int killpg1 __P((struct proc *cp, int signum, int pgid, int > all)); > static void stop __P((struct proc *)); > +static char *expand_name __P((const char*, int, int)); > > /* > * Can process p, with pcred pc, send the signal signum to process q? > @@ -1219,6 +1222,75 @@ > /* NOTREACHED */ > } > > +static char corefilename[MAXPATHLEN+1] = {"%N.core"}; > +SYSCTL_STRING(_kern, KERN_COREFILENAME, corefilename, CTLFLAG_RW, > + corefilename, sizeof(corefilename), ""); > + > +static char * > +expand_name(name, uid, pid) > +const char *name; int uid; int pid; { > + char *temp; > + char buf[11]; /* Buffer for pid/uid -- max 4B */ > + int i, n; > + char *format = corefilename; > + > + temp = malloc(MAXPATHLEN + 3, M_TEMP, M_NOWAIT); > + bzero(temp, MAXPATHLEN+3); > + for (i = 0, n = 0; i < MAXPATHLEN && format[i]; i++) { > + int l; > + switch (format[i]) { > + case '%': /* Format character */ > + i++; > + switch (format[i]) { > + case '%': > + temp[n++] = '%'; > + break; > + case 'N': /* process name */ > + l = strlen(name); > + if ((n + l) > MAXPATHLEN) { > + log(LOG_ERR, "pid %d (%s), uid > (%d): Path `%s%s' is too long\n", > + pid, name, uid, temp, name); > + free(temp, M_TEMP); > + return NULL; > + } > + memcpy(temp+n, name, l); > + n += l; > + break; > + case 'P': /* process id */ > + sprintf(buf, "%u", pid); > + l = strlen(buf); > + if ((n + l) > MAXPATHLEN) { > + log(LOG_ERR, "pid %d (%s), uid > (%d): Path `%s%s' is too long\n", > + pid, name, uid, temp, name); > + free(temp, M_TEMP); > + return NULL; > + } > + memcpy(temp+n, buf, l); > + n += l; > + break; > + case 'U': /* user id */ > + sprintf(buf, "%u", uid); > + l = strlen(buf); > + if ((n + l) > MAXPATHLEN) { > + log(LOG_ERR, "pid %d (%s), uid > (%d): Path `%s%s' is too long\n", > + pid, name, uid, temp, name); > + free(temp, M_TEMP); > + return NULL; > + } > + memcpy(temp+n, buf, l); > + n += l; > + break; > + default: > + log(LOG_ERR, "Unknown format character %c > in `%s'\n", format[i], format); > + } > + break; > + default: > + temp[n++] = format[i]; > + } > + } > + return temp; > +} > + > /* > * Dump core, into a file named "progname.core", unless the process was > * setuid/setgid. > @@ -1233,17 +1305,21 @@ > struct nameidata nd; > struct vattr vattr; > int error, error1; > - char name[MAXCOMLEN+6]; /* progname.core */ > + char *name; > > if (p->p_flag & P_SUGID) > return (EFAULT); > if (ctob(UPAGES + vm->vm_dsize + vm->vm_ssize) >= > p->p_rlimit[RLIMIT_CORE].rlim_cur) > return (EFAULT); > - sprintf(name, "%s.core", p->p_comm); > + > + name = expand_name(p->p_comm, p->p_ucred->cr_uid, p->p_pid); > + if (name == NULL) > + return(EFAULT); > NDINIT(&nd, LOOKUP, FOLLOW, UIO_SYSSPACE, name, p); > - if ((error = vn_open(&nd, > - O_CREAT | FWRITE, S_IRUSR | S_IWUSR))) > + error = vn_open(&nd, O_CREAT | FWRITE, S_IRUSR | S_IWUSR); > + free(name, M_TEMP); > + if (error) > return (error); > vp = nd.ni_vp; > > Index: sys/sysctl.h > =================================================================== > RCS file: /usr/cvs/src/sys/sys/sysctl.h,v > retrieving revision 1.48.2.2 > diff -u -r1.48.2.2 sysctl.h > --- sysctl.h 1997/08/30 14:08:56 1.48.2.2 > +++ sysctl.h 1998/07/03 19:30:28 > @@ -230,7 +230,8 @@ > #define KERN_MAXSOCKBUF 31 /* int: max size of a > socket buffer */ > #define KERN_PS_STRINGS 32 /* int: address of > PS_STRINGS */ > #define KERN_USRSTACK 33 /* int: address of USRSTACK > */ > -#define KERN_MAXID 34 /* number of valid kern ids */ > +#define KERN_COREFILENAME 34 /* string: name of core > file */ > +#define KERN_MAXID 35 /* number of valid kern ids */ > > #define CTL_KERN_NAMES { \ > { 0, 0 }, \ > @@ -267,6 +268,7 @@ > { "maxsockbuf", CTLTYPE_INT }, \ > { "ps_strings", CTLTYPE_INT }, \ > { "usrstack", CTLTYPE_INT }, \ > + { "corefile", CTLTYPE_STRING }, \ > } > > /* > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe cvs-all" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 02:12:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02128 for freebsd-current-outgoing; Wed, 8 Jul 1998 02:12:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@dyn1-tnt13-191.detroit.mi.ameritech.net [199.179.188.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02092 for ; Wed, 8 Jul 1998 02:12:32 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id BAA20444 for ; Wed, 8 Jul 1998 01:26:06 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35A302EC.3F208FD4@ameritech.net> Date: Wed, 08 Jul 1998 01:26:04 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: X crashing on sig 6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I updated to a recent world and kernel and twice today X has all of a sudden exited (the second time im sure it said sig 6, the 1st I dont recall why). Wondering if anyone else has seen this? Or if anyone has any suggestions. (if it happens again I can start by recompiling Xfree...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 02:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10384 for freebsd-current-outgoing; Wed, 8 Jul 1998 02:33:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10248 for ; Wed, 8 Jul 1998 02:33:02 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id AAA29308 for ; Wed, 8 Jul 1998 00:46:20 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA12786 for freebsd-current@freefall.cdrom.com; Wed, 8 Jul 1998 09:46:25 +0200 (MEST) (envelope-from kuku) Date: Wed, 8 Jul 1998 09:46:25 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807080746.JAA12786@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: 'Frozen' Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I built a -current world+kernel of yesterday. AmdK5/133, 32MB, NCR SCSI and IDE disks, de0 network card, dmesg + kernel config appended. There was no panic of anything to be seen. This machine ran rock solid with a May-3.0-current for weeks and before that it ran 2.2.5 rock solid - never saw this 'freeze'. Yesterday, after building perl500404 and doing some build in /usr/ports/databases/mysql I logged out. A couple of hours later the machine didn't respond and when I went to the campus this morning I only saw the login: prompt, no kernel message on the screen, just frozen. I noticed though in the past that the sometimes the de0 interface has difficulties to come up (autoselect or whatever). (BTW, can anyone tell what the sendmail error messages in the messages file mean?) -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- DATA follow: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Tue Jul 7 09:44:53 MEST 1998 kuku@blues.physik.rwth-aachen.de:/a/src/sys/compile/NEWBLUES Timecounter "i8254" frequency 1193182 Hz cost 2677 ns Timecounter "TSC" frequency 100227877 Hz cost 284 ns CPU: AMD-K5(tm) Processor (100.23-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x511 Stepping=1 Features=0x21bf real memory = 33554432 (32768K bytes) avail memory = 30572544 (29856K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 de0: rev 0x11 int a irq 11 on pci0.8.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:06:e2:d2 ncr0: rev 0x02 int a irq 10 on pci0.9.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 2014MB (4124736 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: MDA/hercules <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 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-32 wd0: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa wdc1: unit 0 (wd1): , 32-bit, multi-block-32 wd1: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers changing root device to wd0s1a WARNING: / was not properly dismounted. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.46.2.6 1995/10/25 17:29:51 jkh Exp $ # machine "i386" cpu "I586_CPU" ident NEWBLUES maxusers 64 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options MROUTING options USER_LDT options USERCONFIG options KTRACE #options DEVFS #options DEVFS_ROOT options SYSVSHM options SYSVSEM options SYSVMSG ##obsolete options "GUSMAX" options ATAPI_STATIC options ATAPI config kernel root on sd0 controller isa0 controller pci0 controller ncr0 controller ncr1 controller scbus0 at ncr0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x000080ff vector wdintr disk wd0 at wdc0 drive 0 device wcd0 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x000080ff vector wdintr disk wd1 at wdc1 drive 0 device wcd0 disk sd0 device st0 device cd0 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device de0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd0000 vector edintr pseudo-device ccd 4 pseudo-device loop pseudo-device vn pseudo-device ether #pseudo-device pcaudio #pseudo-device log pseudo-device bpfilter 16 pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's /var/log/messages: (shows two situations: the 1st boot is right after the freeze and in consequence of the non-working de0 the names for /etc/exports cannot be respolved). Also fsck was necessary. The second boot then was OK. Jul 8 09:23:55 blues /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 8 09:23:55 blues /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 8 09:23:55 blues /kernel: The Regents of the University of California. All rights reserved. Jul 8 09:23:55 blues /kernel: FreeBSD 3.0-CURRENT #1: Tue Jul 7 09:44:53 MEST 1998 Jul 8 09:23:55 blues /kernel: kuku@blues.physik.rwth-aachen.de:/a/src/sys/compile/NEWBLUES Jul 8 09:23:55 blues /kernel: Timecounter "i8254" frequency 1193182 Hz cost 2677 ns Jul 8 09:23:55 blues /kernel: Timecounter "TSC" frequency 100227877 Hz cost 284 ns Jul 8 09:23:55 blues /kernel: CPU: AMD-K5(tm) Processor (100.23-MHz 586-class CPU) Jul 8 09:23:56 blues /kernel: Origin = "AuthenticAMD" Id = 0x511 Stepping=1 Jul 8 09:23:56 blues /kernel: Features=0x21bf Jul 8 09:23:56 blues /kernel: real memory = 33554432 (32768K bytes) Jul 8 09:23:56 blues /kernel: avail memory = 30572544 (29856K bytes) Jul 8 09:23:56 blues /kernel: Probing for devices on PCI bus 0: Jul 8 09:23:56 blues /kernel: chip0: rev 0x02 on pci0.0.0 Jul 8 09:23:56 blues /kernel: chip1: rev 0x01 on pci0.7.0 Jul 8 09:23:56 blues /kernel: ide_pci0: rev 0x00 on pci0.7.1 Jul 8 09:23:56 blues /kernel: de0: rev 0x11 int a irq 11 on pci0.8.0 Jul 8 09:23:56 blues /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 Jul 8 09:23:56 blues /kernel: de0: address 00:00:c0:08:d0:c4 Jul 8 09:23:56 blues /kernel: ncr0: rev 0x02 int Jul 8 09:23:56 blues /kernel: a irq 10 on pci0.9.0 Jul 8 09:23:56 blues /kernel: ncr0: waiting for scsi devices to settle Jul 8 09:23:56 blues /kernel: scbus0 at ncr0 bus 0 Jul 8 09:23:56 blues /kernel: sd0 at scbus0 target 0 lun 0 Jul 8 09:23:56 blues /kernel: sd0: type 0 fixed SCSI 2 Jul 8 09:23:56 blues /kernel: sd0: Direct-Access Jul 8 09:23:56 blues /kernel: sd0: 10.0 MB/s (100 ns, offset 8) Jul 8 09:23:56 blues /kernel: 2014MB (4124736 512 byte sectors) Jul 8 09:23:56 blues /kernel: Probing for devices on the ISA bus: Jul 8 09:23:56 blues /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 8 09:23:56 blues /kernel: sc0: MDA/hercules <16 virtual consoles, flags=0x0> Jul 8 09:23:56 blues /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 8 09:23:56 blues /kernel: sio0: type 16550A Jul 8 09:23:56 blues /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 8 09:23:56 blues /kernel: sio1: type 16550A Jul 8 09:23:56 blues /kernel: lpt0 at 0x3bc-0x3c3 irq 7 on isa Jul 8 09:23:56 blues /kernel: lpt0: Interrupt-driven port Jul 8 09:23:56 blues /kernel: lp0: TCP/IP capable interface Jul 8 09:23:56 blues /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 8 09:23:56 blues /kernel: fd0: 1.44MB 3.5in Jul 8 09:23:56 blues /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa Jul 8 09:23:56 blues /kernel: wdc0: unit 0 (wd0): , 32-bit, multi-block-32 Jul 8 09:23:56 blues /kernel: wd0: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S Jul 8 09:23:56 blues /kernel: wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa Jul 8 09:23:56 blues /kernel: wdc1: unit 0 (wd1): , 32-bit, multi-block-32 Jul 8 09:23:57 blues /kernel: wd1: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S Jul 8 09:23:57 blues /kernel: npx0 on motherboard Jul 8 09:23:57 blues /kernel: npx0: INT 16 Jul 8 09:23:57 blues /kernel: interface Jul 8 09:23:57 blues /kernel: ccd0-3: Concatenated disk drivers Jul 8 09:23:57 blues /kernel: changing root device to wd0s1a Jul 8 09:23:57 blues /kernel: WARNING: / was not properly dismounted. Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for bach Jul 8 09:23:57 blues mountd[90]: Bad host bach, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for mozart Jul 8 09:23:57 blues mountd[90]: Bad host mozart, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for vivaldi Jul 8 09:23:57 blues mountd[90]: Bad host vivaldi, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for toots Jul 8 09:23:57 blues mountd[90]: Bad host toots, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for aclpc0 Jul 8 09:23:57 blues mountd[90]: Bad host aclpc0, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for bach Jul 8 09:23:57 blues mountd[90]: Bad host bach, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for mozart Jul 8 09:23:57 blues mountd[90]: Bad host mozart, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for vivaldi Jul 8 09:23:57 blues mountd[90]: Bad host vivaldi, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for toots Jul 8 09:23:57 blues mountd[90]: Bad host toots, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for aclpc0 Jul 8 09:23:57 blues mountd[90]: Bad host aclpc0, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for agate Jul 8 09:23:57 blues mountd[90]: Bad host agate, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for bach Jul 8 09:23:57 blues mountd[90]: Bad host bach, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for mozart Jul 8 09:23:57 blues mountd[90]: Bad host mozart, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for vivaldi Jul 8 09:23:57 blues mountd[90]: Bad host vivaldi, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for toots Jul 8 09:23:57 blues mountd[90]: Bad host toots, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for aclpc0 Jul 8 09:23:57 blues mountd[90]: Bad host aclpc0, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for agate Jul 8 09:23:57 blues mountd[90]: Bad host agate, skipping Jul 8 09:23:57 blues mountd[90]: Gethostbyname failed for aclpc0 Jul 8 09:23:57 blues mountd[90]: Bad host aclpc0, skipping Jul 8 09:23:58 blues mrouted[136]: mrouted version 3.8a Jul 8 09:23:58 blues mrouted[136]: can't forward: only one enabled vif Jul 8 09:23:59 blues lpd[154]: restarted Jul 8 09:24:02 blues sshd[206]: log: Server listening on port 22. Jul 8 09:24:02 blues sshd[206]: log: Generating 768 bit RSA key. Jul 8 09:24:06 blues sshd[206]: log: RSA key generation complete. Jul 8 09:24:07 blues sendmail[236]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on output channel sending "451 fill_fd: before readcf: fd 1 not open: Bad file descriptor": Input/output error Jul 8 09:24:07 blues sendmail[236]: NOQUEUE: SYSERR(root): fill_fd: before readcf: fd 1 not open: Bad file descriptor Jul 8 09:24:07 blues sendmail[236]: NOQUEUE: SYSERR(root): fill_fd: before readcf: fd 2 not open: Bad file descriptor Jul 8 09:24:36 blues login: login on ttyv0 as kuku Jul 8 09:26:52 blues su: kuku to root on /dev/ttyv0 Jul 8 09:28:48 blues reboot: rebooted by kuku Jul 8 09:28:48 blues syslogd: exiting on signal 15 Jul 8 09:30:54 blues /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 8 09:30:55 blues /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 8 09:30:55 blues /kernel: The Regents of the University of California. All rights reserved. Jul 8 09:30:55 blues /kernel: FreeBSD 3.0-CURRENT #1: Tue Jul 7 09:44:53 MEST 1998 Jul 8 09:30:55 blues /kernel: kuku@blues.physik.rwth-aachen.de:/a/src/sys/compile/NEWBLUES Jul 8 09:30:55 blues /kernel: Timecounter "i8254" frequency 1193182 Hz cost 2677 ns Jul 8 09:30:55 blues /kernel: Timecounter "TSC" frequency 100227748 Hz cost 284 ns Jul 8 09:30:55 blues /kernel: CPU: AMD-K5(tm) Processor (100.23-MHz 586-class CPU) Jul 8 09:30:55 blues /kernel: Origin = "AuthenticAMD" Id = 0x511 Stepping=1 Jul 8 09:30:55 blues /kernel: Features=0x21bf Jul 8 09:30:55 blues /kernel: real memory = 33554432 (32768K bytes) Jul 8 09:30:55 blues /kernel: avail memory = 30572544 (29856K bytes) Jul 8 09:30:55 blues /kernel: Probing for devices on PCI bus 0: Jul 8 09:30:55 blues /kernel: chip0: rev 0x02 on pci0.0.0 Jul 8 09:30:55 blues /kernel: chip1: rev 0x01 on pci0.7.0 Jul 8 09:30:55 blues /kernel: ide_pci0: rev 0x00 on pci0.7.1 Jul 8 09:30:55 blues /kernel: de0: rev 0x11 int a irq 11 on pci0.8.0 Jul 8 09:30:55 blues /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 Jul 8 09:30:55 blues /kernel: de0: address 00:00:c0:08:d0:c4 Jul 8 09:30:55 blues /kernel: ncr0: rev 0x02 int Jul 8 09:30:55 blues /kernel: a irq 10 on pci0.9.0 Jul 8 09:30:55 blues /kernel: ncr0: waiting for scsi devices to settle Jul 8 09:30:55 blues /kernel: scbus0 at ncr0 bus 0 Jul 8 09:30:55 blues /kernel: sd0 at scbus0 target 0 lun 0 Jul 8 09:30:55 blues /kernel: sd0: type 0 fixed SCSI 2 Jul 8 09:30:55 blues /kernel: sd0: Direct-Access Jul 8 09:30:55 blues /kernel: sd0: 10.0 MB/s (100 ns, offset 8) Jul 8 09:30:55 blues /kernel: 2014MB (4124736 512 byte sectors) Jul 8 09:30:55 blues /kernel: Probing for devices on the ISA bus: Jul 8 09:30:55 blues /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 8 09:30:55 blues /kernel: sc0: MDA/hercules <16 virtual consoles, flags=0x0> Jul 8 09:30:56 blues /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 8 09:30:56 blues /kernel: sio0: type 16550A Jul 8 09:30:56 blues /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 8 09:30:56 blues /kernel: sio1: type 16550A Jul 8 09:30:56 blues /kernel: lpt0 at 0x3bc-0x3c3 irq 7 on isa Jul 8 09:30:56 blues /kernel: lpt0: Interrupt-driven port Jul 8 09:30:56 blues /kernel: lp0: TCP/IP capable interface Jul 8 09:30:56 blues /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 8 09:30:56 blues /kernel: fd0: 1.44MB 3.5in Jul 8 09:30:56 blues /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa Jul 8 09:30:56 blues /kernel: wdc0: unit 0 (wd0): , 32-bit, multi-block-32 Jul 8 09:30:56 blues /kernel: wd0: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S Jul 8 09:30:56 blues /kernel: wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa Jul 8 09:30:56 blues /kernel: wdc1: unit 0 (wd1): , 32-bit, multi-block-32 Jul 8 09:30:56 blues /kernel: wd1: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S Jul 8 09:30:56 blues /kernel: npx0 on motherboard Jul 8 09:30:56 blues /kernel: npx0: INT 16 Jul 8 09:30:56 blues /kernel: interface Jul 8 09:30:56 blues /kernel: ccd0-3: Concatenated disk drivers Jul 8 09:30:56 blues /kernel: changing root device to wd0s1a Jul 8 09:30:56 blues /kernel: de0: enabling BNC port Jul 8 09:32:38 blues mrouted[136]: mrouted version 3.8a Jul 8 09:32:38 blues mrouted[136]: can't forward: only one enabled vif Jul 8 09:32:39 blues lpd[154]: restarted Jul 8 09:32:42 blues sshd[206]: log: Server listening on port 22. Jul 8 09:32:42 blues sshd[206]: log: Generating 768 bit RSA key. Jul 8 09:32:46 blues sshd[206]: log: RSA key generation complete. Jul 8 09:32:46 blues sendmail[236]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on output channel sending "451 fill_fd: before main() initmaps: fd 1 not open: Bad file descriptor": Input/output error Jul 8 09:32:46 blues sendmail[236]: NOQUEUE: SYSERR(root): fill_fd: before main() initmaps: fd 1 not open: Bad file descriptor Jul 8 09:32:46 blues sendmail[236]: NOQUEUE: SYSERR(root): fill_fd: before main() initmaps: fd 2 not open: Bad file descriptor -- END OF DATA -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 03:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23413 for freebsd-current-outgoing; Wed, 8 Jul 1998 03:22:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA23388 for ; Wed, 8 Jul 1998 03:22:51 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 22967 invoked by uid 1001); 8 Jul 1998 08:33:28 +0000 (GMT) To: freebsd-current@FreeBSD.ORG Subject: Rate limit for system calls to prevent denial of service attacks? X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 08 Jul 1998 10:33:28 +0200 Message-ID: <22965.899886808@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following small program: main(){while(1) fork();} is a very effective denial of service attack against FreeBSD-2.2.6, despite reasonable defaults in login.conf. The problem is *not* the number of processes, but the system call rate. It's actually kind of amazing to follow this with vmstat, and see that the box is suddenly doing 395000 system calls per second :-) (this is a P-166). Yes, it's still responding to input, but very slowly. On a general login box, I think this would be a big problem. Limiting CPU time per process or user is probably not sufficient, unless you set it to absurdly small limits. It looks to me like we need some sort of *rate limiting* for system calls. Anybody looked at this? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 03:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24625 for freebsd-current-outgoing; Wed, 8 Jul 1998 03:27:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24605 for ; Wed, 8 Jul 1998 03:27:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA04653; Wed, 8 Jul 1998 03:27:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Matthew Patton cc: freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Mon, 06 Jul 1998 21:15:41 EDT." Date: Wed, 08 Jul 1998 03:27:03 -0700 Message-ID: <4648.899893623@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sorry to have to drop this on the mailing list readership... > > I downloaded 2.2.6-release. acquired cvsup, and grabbed the whole source > tree, or at least what corresponds to src-all. Tried a make "buildworld" > and the top level make file blew up all over the place. Parse errors due to > environment variables like MACHINE_ARCH or BINFORMAT not being defined. I Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src is a fairly difficult proposition unless you're expert qualified with berkeley make and the FreeBSD source tree in general. My recommendation, and the way I did this just a short time ago on another box as a sort of demo, is to extract the bindist from a 3.0-snap on top of your existing 2.2.x system and then make the world, a new kernel, reboot. Worked for me. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 04:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02440 for freebsd-current-outgoing; Wed, 8 Jul 1998 04:06:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02433 for ; Wed, 8 Jul 1998 04:06:37 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id GAA07173; Wed, 8 Jul 1998 06:06:30 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Jul 1998 06:04:50 -0500 To: current@FreeBSD.ORG From: Richard Wackerbarth Subject: TCP changes break CVSUP Cc: jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last week, everything was fine. However, last night, I built a new kernel, libs, etc. with today's (7/7/98) tree. That's July 7, not 7 July :-) I then tried to run cvsup to update the source tree again. After "whirring" the disks for a while, it hung until it finally timed out. Looking at the network status, I found that the tcp buffers used to communicate with the server were full and not getting processed. Other processes like ftp seem to work. I suspect the modula-3 libraries. Has anyone else encountered a similar reaction? Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 04:09:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02972 for freebsd-current-outgoing; Wed, 8 Jul 1998 04:09:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02937 for ; Wed, 8 Jul 1998 04:09:12 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id MAA01997; Wed, 8 Jul 1998 12:09:08 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id MAA03734; Wed, 8 Jul 1998 12:08:46 +0100 (BST) Message-ID: <19980708120844.61222@iii.co.uk> Date: Wed, 8 Jul 1998 12:08:44 +0100 To: Matthew Patton Cc: freebsd-current@FreeBSD.ORG Subject: Re: building world References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from Matthew Patton on Mon, Jul 06, 1998 at 09:15:41PM -0400 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 06, 1998 at 09:15:41PM -0400, Matthew Patton wrote: > So what is the proper series of steps one needs to follow to move from the > release to -current? I *believe* (from conversations on this list) that # cd /usr/src # make -m /usr/src/sys/mk buildworld # make -m /usr/src/sys/mk installworld is sufficient (although you could obviously combine the 'buildworld' and 'installworld' steps with the 'world' target). If the 'make new kernel, frob /etc' doesn't make sense, take a look at If you can confirm that adding the '-m' flag works for you, I'll add it to the tutorial. N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 04:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04241 for freebsd-current-outgoing; Wed, 8 Jul 1998 04:12:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04217 for ; Wed, 8 Jul 1998 04:12:28 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id VAA23031; Wed, 8 Jul 1998 21:24:16 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807081124.VAA23031@cimlogic.com.au> Subject: Re: building world In-Reply-To: <4648.899893623@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 8, 98 03:27:03 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 8 Jul 1998 21:24:16 +1000 (EST) Cc: patton@sysnet.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > I'm sorry to have to drop this on the mailing list readership... > > > > I downloaded 2.2.6-release. acquired cvsup, and grabbed the whole source > > tree, or at least what corresponds to src-all. Tried a make "buildworld" > > and the top level make file blew up all over the place. Parse errors due to > > environment variables like MACHINE_ARCH or BINFORMAT not being defined. I > > Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src > is a fairly difficult proposition unless you're expert qualified with > berkeley make and the FreeBSD source tree in general. Er, this is "mis-information" IMHO. > > My recommendation, and the way I did this just a short time ago on > another box as a sort of demo, is to extract the bindist from a > 3.0-snap on top of your existing 2.2.x system and then make the world, > a new kernel, reboot. Worked for me. This is not necessary. As I've said before: on a stock 2.2.6-RELEASE installation with 3-0-CURRENT sources mounted as /usr/src, all you need to do is: cd /usr/src make -m /usr/src/share/mk world Obviously sending this information to this list _every_ time someone compains about make world or buildworld not working on 2.2.6 doesn't get the message across. I'm seriously considering getting a religion... -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 04:37:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10874 for freebsd-current-outgoing; Wed, 8 Jul 1998 04:37:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10863 for ; Wed, 8 Jul 1998 04:37:35 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id LAA20705; Wed, 8 Jul 1998 11:37:32 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA04786; Wed, 8 Jul 1998 13:37:27 +0200 (MET DST) Message-ID: <19980708133726.17075@follo.net> Date: Wed, 8 Jul 1998 13:37:26 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , Matthew Patton Cc: freebsd-current@FreeBSD.ORG Subject: Re: building world References: <4648.899893623@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <4648.899893623@time.cdrom.com>; from Jordan K. Hubbard on Wed, Jul 08, 1998 at 03:27:03AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 03:27:03AM -0700, Jordan K. Hubbard wrote: > > I'm sorry to have to drop this on the mailing list readership... > > > > I downloaded 2.2.6-release. acquired cvsup, and grabbed the whole source > > tree, or at least what corresponds to src-all. Tried a make "buildworld" > > and the top level make file blew up all over the place. Parse errors due to > > environment variables like MACHINE_ARCH or BINFORMAT not being defined. I > > Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src > is a fairly difficult proposition unless you're expert qualified with > berkeley make and the FreeBSD source tree in general. > > My recommendation, and the way I did this just a short time ago on > another box as a sort of demo, is to extract the bindist from a > 3.0-snap on top of your existing 2.2.x system and then make the world, > a new kernel, reboot. Worked for me. In case you want to be more certain that that gun isn't pointing at your foot: Do the extraction in a chroot()ed tree, and run 'make buildworld' et al inside that, then do a full install. Still not perfect, but it at least allow you to verify that the world builds before you start your upgrade. Be aware that the 3.0 mount is not compatible with the 2.2.6 kernel, so you might want to update your kernel first (but remember to config the kernel with your new config...) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 05:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15250 for freebsd-current-outgoing; Wed, 8 Jul 1998 05:04:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15237 for ; Wed, 8 Jul 1998 05:04:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA05037; Wed, 8 Jul 1998 05:03:34 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Wed, 08 Jul 1998 21:24:16 +1000." <199807081124.VAA23031@cimlogic.com.au> Date: Wed, 08 Jul 1998 05:03:34 -0700 Message-ID: <5033.899899414@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src > > is a fairly difficult proposition unless you're expert qualified with > > berkeley make and the FreeBSD source tree in general. > > Er, this is "mis-information" IMHO. Well, if you say you've gotten all the way from 2.2.6-RELEASE to 3.0-current with absolutely nothing more than a ``make -m /usr/src/share/mk world'' and an updated kernel then I stand most certainly corrected. P.S. Rather than starting a religion, why not simply add an `upgrade' target to /usr/src/Makefile which does the appropriate submake? If nothing else, it would be a convenient hook for times when upgrading requires even more custom hackery than that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 05:15:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17139 for freebsd-current-outgoing; Wed, 8 Jul 1998 05:15:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17111 for ; Wed, 8 Jul 1998 05:15:15 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id WAA23208; Wed, 8 Jul 1998 22:28:33 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807081228.WAA23208@cimlogic.com.au> Subject: Re: building world In-Reply-To: <5033.899899414@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 8, 98 05:03:34 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 8 Jul 1998 22:28:33 +1000 (EST) Cc: jb@cimlogic.com.au, patton@sysnet.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > Well, if you say you've gotten all the way from 2.2.6-RELEASE to > 3.0-current with absolutely nothing more than a > ``make -m /usr/src/share/mk world'' and an updated kernel then > I stand most certainly corrected. > > P.S. Rather than starting a religion, why not simply add an `upgrade' > target to /usr/src/Makefile which does the appropriate submake? > If nothing else, it would be a convenient hook for times when > upgrading requires even more custom hackery than that. I was actually planning on using someone else's religion rather than starting my own. I don't need/want to go on TV. 8-) I think it is time to split /usr/src/Makefile so that the bits that depend on the included mk files are in a makefile that is only accessed by a make with -m and -f args. This probably will offend Bruce though. I might have to use _his_ religion. I wonder if he has one? 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 07:52:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09690 for freebsd-current-outgoing; Wed, 8 Jul 1998 07:52:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09653 for ; Wed, 8 Jul 1998 07:52:31 -0700 (PDT) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([209.12.57.17]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA260; Wed, 8 Jul 1998 10:46:27 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.8) id KAA00764; Wed, 8 Jul 1998 10:52:59 GMT (envelope-from root) Message-ID: <19980708105259.A744@scsn.net> Date: Wed, 8 Jul 1998 10:52:59 +0000 From: dmaddox@scsn.net (Donald J. Maddox) To: mcdougall@ameritech.net, current@FreeBSD.ORG Subject: Re: X crashing on sig 6 Reply-To: dmaddox@scsn.net Mail-Followup-To: mcdougall@ameritech.net, current@FreeBSD.ORG References: <35A302EC.3F208FD4@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35A302EC.3F208FD4@ameritech.net>; from Adam McDougall on Wed, Jul 08, 1998 at 01:26:04AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 01:26:04AM -0400, Adam McDougall wrote: > Yesterday I updated to a recent world and kernel and twice today X has > all of a sudden exited (the second time im sure it said sig 6, the 1st I > dont recall why). Wondering if anyone else has seen this? Or if anyone > has any suggestions. (if it happens again I can start by recompiling > Xfree...) I've been seeing X programs exiting on sig10s and other strange behaviour since a 'make world' yesterday... I rebuilt X and it didn't help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 08:41:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15891 for freebsd-current-outgoing; Wed, 8 Jul 1998 08:41:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from krabi.mbp.ee (krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15848 for ; Wed, 8 Jul 1998 08:41:00 -0700 (PDT) (envelope-from mauri@krabi.mbp.ee) Received: from localhost (mauri@localhost) by krabi.mbp.ee (8.8.8/8.8.8) with SMTP id SAA02767 for ; Wed, 8 Jul 1998 18:40:52 +0300 (EEST) (envelope-from mauri@krabi.mbp.ee) Date: Wed, 8 Jul 1998 18:40:52 +0300 (EEST) From: Lauri Laupmaa To: current@FreeBSD.ORG Subject: crt0.o Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there are some ports which cry for /usr/lib/crt0.o... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 08:49:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17181 for freebsd-current-outgoing; Wed, 8 Jul 1998 08:49:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17176 for ; Wed, 8 Jul 1998 08:49:10 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from sunix (eculp@sunix.mexcom.net [206.103.64.3]) by dns.webwizard.net.mx (8.8.8/8.8.7) with SMTP id KAA13992; Wed, 8 Jul 1998 10:48:23 -0500 (CDT) Message-ID: <35A38810.49560B34@webwizard.org.mx> Date: Wed, 08 Jul 1998 09:54:08 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Richard Wackerbarth CC: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: TCP changes break CVSUP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth wrote: > > Last week, everything was fine. > However, last night, I built a new kernel, libs, etc. > with today's (7/7/98) tree. > That's July 7, not 7 July :-) > > I then tried to run cvsup to update the source tree > again. > > After "whirring" the disks for a while, it hung > until it finally timed out. Looking at the network > status, I found that the tcp buffers used to > communicate with the server were full and not > getting processed. > > Other processes like ftp seem to work. I suspect > the modula-3 libraries. > > Has anyone else encountered a similar reaction? > > Richard Wackerbarth > I cvsuped last night about 23:30, made world between 00:10 and 02:00 today, built a new kernel and rebooted at 08:30 and just tried cvsup and worked fine found about four changes. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 08:59:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18723 for freebsd-current-outgoing; Wed, 8 Jul 1998 08:59:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18718 for ; Wed, 8 Jul 1998 08:59:20 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA10131 for ; Wed, 8 Jul 1998 08:59:07 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id RAA15036; Wed, 8 Jul 1998 17:58:29 +0200 (MEST) (envelope-from kuku) Message-ID: <19980708175829.38431@gil.physik.rwth-aachen.de> Date: Wed, 8 Jul 1998 17:58:29 +0200 From: Christoph Kukulies To: Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com Subject: Re: 'Frozen' References: <199807080746.JAA12786@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199807080746.JAA12786@gilberto.physik.RWTH-Aachen.DE>; from Christoph Kukulies on Wed, Jul 08, 1998 at 09:46:25AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 09:46:25AM +0200, Christoph Kukulies wrote: > > I built a -current world+kernel of yesterday. > AmdK5/133, 32MB, NCR SCSI and IDE disks, de0 network card, It crashed a again a couple of minutes ago. Jul 8 17:40:33 blues /kernel: de0: abnormal interrupt: transmit process stopped, transmit jabber timeout kernel instruction pointer was: 0xf0118edf That's somewhere near: f0118ec4 _tsleep f011911c _endtsleep > > dmesg + kernel config appended. (in prev message) -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 11:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10724 for freebsd-current-outgoing; Wed, 8 Jul 1998 11:49:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts01-54.waterford.indigo.ie [194.125.139.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10719 for ; Wed, 8 Jul 1998 11:49:13 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id TAA00943; Wed, 8 Jul 1998 19:44:27 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807081844.TAA00943@indigo.ie> Date: Wed, 8 Jul 1998 19:44:26 +0000 In-Reply-To: "Alok K. Dhir" "Re: cvs commit: src/sys/kern kern_sig.c" (Jul 7, 10:04pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: "Alok K. Dhir" , Sean Eric Fagan Subject: Re: cvs commit: src/sys/kern kern_sig.c Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 7, 10:04pm, "Alok K. Dhir" wrote: } Subject: Re: cvs commit: src/sys/kern kern_sig.c Hi, looks good, but the log messages are wrong for the %P and %U modifiers. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 11:50:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10960 for freebsd-current-outgoing; Wed, 8 Jul 1998 11:50:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.methow.com (qmailr@ns.methow.com [206.107.156.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10942 for ; Wed, 8 Jul 1998 11:50:08 -0700 (PDT) (envelope-from tcole@ns.methow.com) Received: (qmail 31482 invoked by uid 500); 8 Jul 1998 18:48:33 -0000 Message-ID: <19980708114832.B31417@nihilist.org> Date: Wed, 8 Jul 1998 11:48:32 -0700 From: Travis Cole To: John Birrell , "Jordan K. Hubbard" Cc: patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world References: <4648.899893623@time.cdrom.com> <199807081124.VAA23031@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199807081124.VAA23031@cimlogic.com.au>; from John Birrell on Wed, Jul 08, 1998 at 09:24:16PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 09:24:16PM +1000, John Birrell wrote: > Jordan K. Hubbard wrote: > > > > Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src > > is a fairly difficult proposition unless you're expert qualified with > > berkeley make and the FreeBSD source tree in general. > > Er, this is "mis-information" IMHO. > > > > > My recommendation, and the way I did this just a short time ago on > > another box as a sort of demo, is to extract the bindist from a > > 3.0-snap on top of your existing 2.2.x system and then make the world, > > a new kernel, reboot. Worked for me. > > This is not necessary. As I've said before: on a stock 2.2.6-RELEASE > installation with 3-0-CURRENT sources mounted as /usr/src, all you need > to do is: > > cd /usr/src > make -m /usr/src/share/mk world I am no expert at this (I have only been using FreeBSD for about 3 months) but I do know what works and the above does not. Just yesterday I cvsuped the 3.0-current source onto my 2.2.6-stable box. cd /usr/src make -m /usr/src/share/mk world (or buildworld) did *not* work. However cd /usr/src make -m buildworld MACHINE_ARCH="i386" BINFORMAT=aout *did* work and compiled the box I am sitting at right now. FreeBSD queequeg.dyn.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Tue Jul 7 > Obviously sending this information to this list _every_ time someone > compains about make world or buildworld not working on 2.2.6 doesn't > get the message across. I'm seriously considering getting a religion... Why doesn't some one add it to the FAQ or handbook? That was the first place I looked when *I* wanted to upgrade. Only after failing to find my answer there, did I start searching through the list archives -- --Travis tcole@nihilist.org -- http://nihilist.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 13:45:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26240 for freebsd-current-outgoing; Wed, 8 Jul 1998 13:45:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26223 for ; Wed, 8 Jul 1998 13:45:44 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA12071; Thu, 9 Jul 1998 06:45:38 +1000 Date: Thu, 9 Jul 1998 06:45:38 +1000 From: Bruce Evans Message-Id: <199807082045.GAA12071@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, sthaug@nethelp.no Subject: Re: Rate limit for system calls to prevent denial of service attacks? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The following small program: > > main(){while(1) fork();} > >is a very effective denial of service attack against FreeBSD-2.2.6, >despite reasonable defaults in login.conf. The problem is *not* the >number of processes, but the system call rate. It's actually kind of >amazing to follow this with vmstat, and see that the box is suddenly >doing 395000 system calls per second :-) (this is a P-166). The problem is actually the number of hog processes. If there are 100 of them then each will run for about 100ms every 10 seconds and competing processes won't be able to get more than 1/101 of the CPU although they may be able to run more often if they don't use much CPU. Nicing the hogs works OK, but the process priorities apparently don't decay fast enough to have much effect for a large number of nasty hogs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 14:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00657 for freebsd-current-outgoing; Wed, 8 Jul 1998 14:25:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00645 for ; Wed, 8 Jul 1998 14:25:49 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id OAA00621; Wed, 8 Jul 1998 14:24:04 -0700 (PDT) (envelope-from jdp) Message-Id: <199807082124.OAA00621@austin.polstra.com> To: thyerm@camtech.net.au Subject: Re: Problem with restore under current. In-Reply-To: <359A194D.8223143B@camtech.net.au> References: <359A194D.8223143B@camtech.net.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 08 Jul 1998 14:24:04 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <359A194D.8223143B@camtech.net.au>, Matthew Thyer wrote: > Unfortunately restore sets schg flags before it trys to create > links (at least that's how it appeared to me) so I got errors > which had to be fixed by hand on trying to restore: > > All of these were hard links by the way and this was a restore > of the /usr filesystem. > > ./bin/ypchsh could not be linked to ./bin/chpass > ./bin/ypchfn " ./bin/chpass > ./bin/ypchpass " ./bin/chpass > ./bin/chsh " ./bin/chpass > ./bin/chfn " ./bin/chpass > ./bin/yppasswd " ./bin/passwd Confirmed. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 15:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05076 for freebsd-current-outgoing; Wed, 8 Jul 1998 15:01:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA05064 for ; Wed, 8 Jul 1998 15:01:37 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yu2H1-0001DC-00; Wed, 8 Jul 1998 16:01:11 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id QAA09155; Wed, 8 Jul 1998 16:02:57 -0600 (MDT) Message-Id: <199807082202.QAA09155@harmony.village.org> To: Travis Cole Subject: Re: building world Cc: John Birrell , "Jordan K. Hubbard" , patton@sysnet.net, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Jul 1998 11:48:32 PDT." <19980708114832.B31417@nihilist.org> References: <19980708114832.B31417@nihilist.org> <4648.899893623@time.cdrom.com> <199807081124.VAA23031@cimlogic.com.au> Date: Wed, 08 Jul 1998 16:02:57 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980708114832.B31417@nihilist.org> Travis Cole writes: : cd /usr/src : make -m /usr/src/share/mk buildworld MACHINE_ARCH="i386" BINFORMAT=aout make updateworld seems in order :-) Or just putting MACHINE_ARCH?=i386 and BINFORMAT?=aout in /usr/src/Makefile Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 15:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06893 for freebsd-current-outgoing; Wed, 8 Jul 1998 15:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06888 for ; Wed, 8 Jul 1998 15:11:00 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA10365 for ; Wed, 8 Jul 1998 17:10:57 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Jul 1998 17:12:01 -0500 To: current@FreeBSD.ORG From: Richard Wackerbarth Subject: More on CVSUP and today's current -- looks like "de" driver related Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Further isolation of the hanging problem. "de" interface, today's kernel, AND CVsup: hangs with full buffers. However, if you change ANY ONE of the above, {"ed" interface OR Jun18 kernel.GENERIC OR ftp} and the other two as above: works. kernel rebuilt within the past hour. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 16:22:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14871 for freebsd-current-outgoing; Wed, 8 Jul 1998 16:22:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14854 for ; Wed, 8 Jul 1998 16:22:26 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA24403; Thu, 9 Jul 1998 09:36:07 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807082336.JAA24403@cimlogic.com.au> Subject: Re: building world In-Reply-To: <19980708114832.B31417@nihilist.org> from Travis Cole at "Jul 8, 98 11:48:32 am" To: tcole@nihilist.org (Travis Cole) Date: Thu, 9 Jul 1998 09:36:07 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Travis Cole wrote: > > cd /usr/src > > make -m /usr/src/share/mk world > > I am no expert at this (I have only been using FreeBSD for about 3 months) > but I do know what works and the above does not. > > Just yesterday I cvsuped the 3.0-current source onto my 2.2.6-stable box. > > cd /usr/src > make -m /usr/src/share/mk world (or buildworld) > > did *not* work. What was the error you got? Posting such messages without error output is not very helpful. Did you type the command exactly? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 16:32:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16075 for freebsd-current-outgoing; Wed, 8 Jul 1998 16:32:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16057 for ; Wed, 8 Jul 1998 16:32:11 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA27431; Wed, 8 Jul 1998 16:32:07 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd027403; Wed Jul 8 16:32:03 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA28398; Wed, 8 Jul 1998 16:31:59 -0700 (MST) From: Terry Lambert Message-Id: <199807082331.QAA28398@usr02.primenet.com> Subject: Re: building world To: jb@cimlogic.com.au (John Birrell) Date: Wed, 8 Jul 1998 23:31:58 +0000 (GMT) Cc: jkh@time.cdrom.com, patton@sysnet.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199807081124.VAA23031@cimlogic.com.au> from "John Birrell" at Jul 8, 98 09:24:16 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is not necessary. As I've said before: on a stock 2.2.6-RELEASE > installation with 3-0-CURRENT sources mounted as /usr/src, all you need > to do is: > > cd /usr/src > make -m /usr/src/share/mk world > > Obviously sending this information to this list _every_ time someone > compains about make world or buildworld not working on 2.2.6 doesn't > get the message across. I'm seriously considering getting a religion... I did this. It fails in two places: 1) Compiling the 3.0 kernel on a 2.2.6 box fails because of the "de" driver's use of version #ifdef's, and the fact that the compiler gets this information from when it was compiled, rather than from what system it is targetting. 2) The fstab is out of date because of the insistence on the use of the slice identifier by mount, so the system will only boot to single user mode after "upgrade". There are other types of compilation that I can make fail, as well, which a normal user would expect to work, but which don't work quite as the user expects. Several "cookbook" approaches have been posted in the past which get around this, but still leave you with the first two problems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 16:35:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16741 for freebsd-current-outgoing; Wed, 8 Jul 1998 16:35:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (root@mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16709 for ; Wed, 8 Jul 1998 16:35:06 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id TAA20220 for ; Wed, 8 Jul 1998 19:34:57 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199807082045.GAA12071@godzilla.zeta.org.au> Date: Wed, 8 Jul 1998 19:38:54 -0400 To: freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Rate limit for system calls to prevent denial of service attacks? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>The following small program: >> >> main(){while(1) fork();} >> >> is a very effective denial of service attack against FreeBSD-2.2.6, >> despite reasonable defaults in login.conf. The problem is *not* the >> number of processes, but the system call rate. It's actually kind of >> amazing to follow this with vmstat, and see that the box is suddenly >> doing 395000 system calls per second :-) (this is a P-166). The subject of this thread asks about adding a rate-limit for system calls. I don't think that's a good idea, but I would like to see some kind of throttling of calls to fork() in particular. Every year we (RPI) have a systems-programming project which introduces students to the fork() subroutine, and every year someone gets their if-statements mixed up and unwittingly writes a "fork bomb" which will bring down our remote-access machines. Now those machines aren't freebsd (not yet, at least!), but the idea of some extra logic in fork seems like it could be worthwhile. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 16:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18155 for freebsd-current-outgoing; Wed, 8 Jul 1998 16:47:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.methow.com (qmailr@ns.methow.com [206.107.156.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA18138 for ; Wed, 8 Jul 1998 16:47:30 -0700 (PDT) (envelope-from tcole@ns.methow.com) Received: (qmail 858 invoked by uid 500); 8 Jul 1998 23:47:25 -0000 Message-ID: <19980708164724.A733@nihilist.org> Date: Wed, 8 Jul 1998 16:47:24 -0700 From: Travis Cole To: John Birrell Cc: current@FreeBSD.ORG Subject: Re: building world References: <19980708114832.B31417@nihilist.org> <199807082336.JAA24403@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199807082336.JAA24403@cimlogic.com.au>; from John Birrell on Thu, Jul 09, 1998 at 09:36:07AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 09, 1998 at 09:36:07AM +1000, John Birrell wrote: > > What was the error you got? Posting such messages without error output > is not very helpful. > > Did you type the command exactly? > I am very sorry about that. Unfortunately I can't repost the exact error because I didn't recored it and my only FreeBSD-2.2.6 box has since been upgraded to 3.0-current. I will however try to explain as best I can the error. First there were several errors concerning the if {MACHINE_ARCH} = "i386" conditional in the toplevel make file. in /usr/src running: make -m buildworld or make -m /usr/src/share/mk buildworld both gave identical results. Running: make -m buildworld MACHINE_ARCH="i386" would build for a very short time (about 5 lines of output, sorry I can't be more specific) until it hit a simaler error about BINFORMAT Running the below command from /usr/src succesfuly built the 3.0-current source tree from yesterday. make -m buildworld MACHINE_ARCH="i386" BINFORMAT=aout This was all done on 2.2.6-stable from Sunday. I am quite sure I typed the command exactly since I tried it about 30 times. But to be sure I would have to check my .bash_history and I'm not at home right now. If this is really important I can try to replicate it on another computer but I would have to cvsup the 2.2.6-stable source tree, make world then cvsup 3.0-current, and make world. All with a 28.8 on a 486 133MHz. If its important I will do it. I hope I am being of a little help. -- --Travis tcole@nihilist.org -- http://nihilist.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 17:30:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23368 for freebsd-current-outgoing; Wed, 8 Jul 1998 17:30:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23361 for ; Wed, 8 Jul 1998 17:30:38 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA07644; Wed, 8 Jul 1998 17:29:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Warner Losh cc: Travis Cole , John Birrell , patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Wed, 08 Jul 1998 16:02:57 MDT." <199807082202.QAA09155@harmony.village.org> Date: Wed, 08 Jul 1998 17:29:56 -0700 Message-ID: <7641.899944196@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suggested a "make update" when this first came up, but nobody seems to want to go down that route. Too simple, I guess. :) - Jordan > In message <19980708114832.B31417@nihilist.org> Travis Cole writes: > : cd /usr/src > : make -m /usr/src/share/mk buildworld MACHINE_ARCH="i386" BINFORMAT=aout > > make updateworld seems in order :-) Or just putting > MACHINE_ARCH?=i386 and BINFORMAT?=aout in /usr/src/Makefile > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 17:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25122 for freebsd-current-outgoing; Wed, 8 Jul 1998 17:48:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.methow.com (qmailr@ns.methow.com [206.107.156.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA25093 for ; Wed, 8 Jul 1998 17:47:52 -0700 (PDT) (envelope-from tcole@ns.methow.com) Received: (qmail 1093 invoked by uid 500); 9 Jul 1998 00:47:48 -0000 Message-ID: <19980708174748.A1078@nihilist.org> Date: Wed, 8 Jul 1998 17:47:48 -0700 From: Travis Cole To: "Jordan K. Hubbard" , Warner Losh Cc: John Birrell , patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world References: <199807082202.QAA09155@harmony.village.org> <7641.899944196@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <7641.899944196@time.cdrom.com>; from Jordan K. Hubbard on Wed, Jul 08, 1998 at 05:29:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whats the difference between that and: cvsup standard-supfile Which is what I did about 8 times before I just run make buildworld MACHINE_ARCH="i386" BINFORMAT=aout -- --Travis tcole@nihilist.org -- http://nihilist.org On Wed, Jul 08, 1998 at 05:29:56PM -0700, Jordan K. Hubbard wrote: > I suggested a "make update" when this first came up, but nobody > seems to want to go down that route. Too simple, I guess. :) > > - Jordan > > In message <19980708114832.B31417@nihilist.org> Travis Cole writes: > > : cd /usr/src > > : make -m /usr/src/share/mk buildworld MACHINE_ARCH="i386" BINFORMAT=aout > > > > make updateworld seems in order :-) Or just putting > > MACHINE_ARCH?=i386 and BINFORMAT?=aout in /usr/src/Makefile > > > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 17:48:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25147 for freebsd-current-outgoing; Wed, 8 Jul 1998 17:48:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@libya-210.ppp.hooked.net [206.169.227.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25105 for ; Wed, 8 Jul 1998 17:47:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id RAA00375; Wed, 8 Jul 1998 17:48:54 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 8 Jul 1998 17:48:53 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: "Donald J. Maddox" cc: mcdougall@ameritech.net, current@FreeBSD.ORG Subject: Re: X crashing on sig 6 In-Reply-To: <19980708105259.A744@scsn.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Jul 1998, Donald J. Maddox wrote: > On Wed, Jul 08, 1998 at 01:26:04AM -0400, Adam McDougall wrote: > > Yesterday I updated to a recent world and kernel and twice today X has > > all of a sudden exited (the second time im sure it said sig 6, the 1st I > > dont recall why). Wondering if anyone else has seen this? Or if anyone > > has any suggestions. (if it happens again I can start by recompiling > > Xfree...) > > I've been seeing X programs exiting on sig10s and other strange behaviour > since a 'make world' yesterday... I rebuilt X and it didn't help. I've been seing weird X behavior after my softupdates kernel locked up (after 3 days!! yay!!) and I rebooted into a newer kernel. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 17:50:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25654 for freebsd-current-outgoing; Wed, 8 Jul 1998 17:50:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25649 for ; Wed, 8 Jul 1998 17:50:38 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id LAA24575; Thu, 9 Jul 1998 11:03:39 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807090103.LAA24575@cimlogic.com.au> Subject: Re: building world In-Reply-To: <7641.899944196@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 8, 98 05:29:56 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 9 Jul 1998 11:03:39 +1000 (EST) Cc: imp@village.org, tcole@nihilist.org, jb@cimlogic.com.au, patton@sysnet.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > I suggested a "make update" when this first came up, but nobody > seems to want to go down that route. Too simple, I guess. :) It's not simple at all! If make can't process the top level makefile because that assumes definitions in the included .mk files and the wrong ones of these get used, it just stops dead. People who have seen this will remember that make just spits errors "instantly". It To update, you need the correct .mk files, but if you had the correct .mk files, then you wouldn't need to update. Catch-22. 8-) For a "make update" to work, you'd need to peg the syntax in /usr/src/Makefile at something compatible with the year dot. Now since /usr/src/Makefile contains all the bells and whistles to get things updated in the correct order even for those who are already current, we've got a conflict there. I think that most of /usr/src/Makefile should be moved to /usr/src/Makefile.build (say) and put something really simple in /usr/src/Makefile that will DTRT (kick of make with the correct -m dir arguments etc). I wish we had some way of automatically capturing the end of a failed make so that failure reports would provide meaningful information. What about a program like "tee", but one which just keeps the last few hundred lines of output? If /usr/src/Makefile was split into /usr/src/Makefile.build, this error output capturing could be implemented as part of the execution of the sub-make. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:01:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26541 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:01:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26533 for ; Wed, 8 Jul 1998 18:01:04 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA20575; Thu, 9 Jul 1998 10:30:23 +0930 (CST) Message-Id: <199807090100.KAA20575@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG Subject: Re: Rate limit for system calls to prevent denial of service attacks? In-reply-to: Your message of "Wed, 08 Jul 1998 10:33:28 +0200." <22965.899886808@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 10:30:23 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Limiting CPU time per process or user is probably not sufficient, > unless you set it to absurdly small limits. It looks to me like we > need some sort of *rate limiting* for system calls. Anybody looked > at this? Hmm.. a neat idea :) I think this in conjunction with a decent sized process limit would be quite useful. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26963 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:05:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26958 for ; Wed, 8 Jul 1998 18:05:24 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA20643; Thu, 9 Jul 1998 10:34:35 +0930 (CST) Message-Id: <199807090104.KAA20643@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Matthew Patton , freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Wed, 08 Jul 1998 03:27:03 MST." <4648.899893623@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 10:34:35 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yep. Transitioning all the way from 2.2.6 to 3.0 using just /usr/src > is a fairly difficult proposition unless you're expert qualified with > berkeley make and the FreeBSD source tree in general. > > My recommendation, and the way I did this just a short time ago on > another box as a sort of demo, is to extract the bindist from a > 3.0-snap on top of your existing 2.2.x system and then make the world, > a new kernel, reboot. Worked for me. Hmm.. I did it a while ago from 2.2.5 to 3.0 but I think too many things have changed between -stable and -current now.. (ie source only no snap cd) Although I do have a box I could test going from 2.2.6 to 3.0 from :) Might be an interesting experiment =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:09:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27384 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:09:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27378 for ; Wed, 8 Jul 1998 18:09:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA07884; Wed, 8 Jul 1998 18:08:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: imp@village.org, tcole@nihilist.org, patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Thu, 09 Jul 1998 11:03:39 +1000." <199807090103.LAA24575@cimlogic.com.au> Date: Wed, 08 Jul 1998 18:08:47 -0700 Message-ID: <7880.899946527@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not simple at all! If make can't process the top level makefile > because that assumes definitions in the included .mk files and the > wrong ones of these get used, it just stops dead. People who have Oh. Right, "never mind." :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29477 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:23:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29471 for ; Wed, 8 Jul 1998 18:23:31 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id KAA13117; Thu, 9 Jul 1998 10:49:06 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 3QAQ405P; Thu, 9 Jul 1998 10:53:19 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id KAA04551; Thu, 9 Jul 1998 10:53:20 +0930 (CST) Message-ID: <35A41B87.66DA9A2C@dsto.defence.gov.au> Date: Thu, 09 Jul 1998 10:53:19 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: dmaddox@scsn.net CC: mcdougall@ameritech.net, current@FreeBSD.ORG Subject: Re: X crashing on sig 6 References: <35A302EC.3F208FD4@ameritech.net> <19980708105259.A744@scsn.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've recently had my X server just die. Most embarassing when you work in a huge cross platform environment with Linux heads and HP-UX worshippers looking for any opportunity to criticise FreeBSD. (I have told them I run the 'bleeding edge' and they are still very impressed by DEVFS and the ports collection so FreeBSD is holding its ground). Anyway, my X server death was on a P100 system built at CTM src-cur 3429. That delta arrived 1998-06-25 10:35 in my timezone (which is GMT + 9.5 hours). Donald J. Maddox wrote: > > On Wed, Jul 08, 1998 at 01:26:04AM -0400, Adam McDougall wrote: > > Yesterday I updated to a recent world and kernel and twice today X has > > all of a sudden exited (the second time im sure it said sig 6, the 1st I > > dont recall why). Wondering if anyone else has seen this? Or if anyone > > has any suggestions. (if it happens again I can start by recompiling > > Xfree...) > > I've been seeing X programs exiting on sig10s and other strange behaviour > since a 'make world' yesterday... I rebuilt X and it didn't help. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:31:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00458 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:31:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00449 for ; Wed, 8 Jul 1998 18:31:52 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA21078; Thu, 9 Jul 1998 11:00:40 +0930 (CST) Message-Id: <199807090130.LAA21078@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: jkh@time.cdrom.com (Jordan K. Hubbard), imp@village.org, tcole@nihilist.org, patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Thu, 09 Jul 1998 11:03:39 +1000." <199807090103.LAA24575@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 11:00:40 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > make so that failure reports would provide meaningful information. What > about a program like "tee", but one which just keeps the last few hundred > lines of output? If /usr/src/Makefile was split into /usr/src/Makefile.build, > this error output capturing could be implemented as part of the execution > of the sub-make. Hmm.. I suppose you want it automagic, but whenever I do a buildworld I always fo (for example) 'make -DNOPROFILE buildworld |& tee buildworld.log' Then if it blows up I can do 'tail -30 buildworld.log' --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:36:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01005 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:36:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mickey00.mickey.ai.kyutech.ac.jp (mickey.ai.kyutech.ac.jp [131.206.1.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00987; Wed, 8 Jul 1998 18:36:21 -0700 (PDT) (envelope-from ohashi@mickey.ai.kyutech.ac.jp) Received: from ateken2.mickey.ai.kyutech.ac.jp (ateken2.mickey.ai.kyutech.ac.jp [131.206.21.141]) by mickey00.mickey.ai.kyutech.ac.jp (8.8.8/3.6W-mickey) with ESMTP id KAA19717; Thu, 9 Jul 1998 10:36:15 +0900 (JST) Received: (from ohashi@localhost) by ateken2.mickey.ai.kyutech.ac.jp (8.8.8/3.5Wpl5) id KAA01795; Thu, 9 Jul 1998 10:36:21 +0900 (JST) Date: Thu, 9 Jul 1998 10:36:21 +0900 (JST) Message-Id: <199807090136.KAA01795@ateken2.mickey.ai.kyutech.ac.jp> To: mauri@krabi.mbp.ee Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: crt0.o In-Reply-To: Your message of "Wed, 8 Jul 1998 18:40:52 +0300 (EEST)". From: ohashi@mickey.ai.kyutech.ac.jp (Takeshi Ohashi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mauri>>Hi mauri>> mauri>>there are some ports which cry for /usr/lib/crt0.o... Some ports, mule-2.3 and emacs20, have same problem. # xemacs-mule seems no problem. AOUT binaries were moved from /usr/lib to /usr/lib/aout. I think ports should use ${LIBDIR}, but bsd.port.mk does not pass it to gmake. Then I made a small patch. --- /usr/share/mk/bsd.port.mk.orig Tue Jun 30 23:19:25 1998 +++ /usr/share/mk/bsd.port.mk Wed Jul 1 18:39:16 1998 @@ -407,7 +407,7 @@ MAKE_FLAGS?= -f MAKEFILE?= Makefile -MAKE_ENV+= PREFIX=${PREFIX} LOCALBASE=${LOCALBASE} X11BASE=${X11BASE} MOTIFLIB="${MOTIFLIB}" CFLAGS="${CFLAGS}" +MAKE_ENV+= PREFIX=${PREFIX} LOCALBASE=${LOCALBASE} X11BASE=${X11BASE} MOTIFLIB="${MOTIFLIB}" CFLAGS="${CFLAGS}" LIBDIR="${LIBDIR}" .if exists(/usr/bin/fetch) FETCH_CMD?= /usr/bin/fetch For mule-2.3 family, put the following patch for patch-am in mule-2.3-common/patches. --- ./src/s/freebsd.h.orig Wed Jul 1 11:53:10 1998 +++ ./src/s/freebsd.h Wed Jul 1 18:08:33 1998 @@ -34,7 +34,7 @@ #define LIBS_DEBUG -lcrypt #define LIBS_SYSTEM -lutil #define LIBS_TERMCAP -ltermcap -#define LIB_GCC /usr/lib/libgcc.a +#define LIB_GCC ${LIBDIR}/libgcc.a /* Reread the time zone on startup. */ #define LOCALTIME_CACHE @@ -47,7 +47,7 @@ #ifndef NO_SHARED_LIBS #define LD_SWITCH_SYSTEM -e start #define HAVE_TEXT_START /* No need to define `start_of_text'. */ -#define START_FILES pre-crt0.o /usr/lib/crt0.o +#define START_FILES pre-crt0.o ${LIBDIR}/crt0.o #define UNEXEC unexsunos4.o #define RUN_TIME_REMAP For emacs20, swap the following patch and patch-ae. --- src/s/freebsd.h.orig Fri Aug 1 16:17:24 1997 +++ src/s/freebsd.h Wed Jul 1 21:15:32 1998 @@ -45,8 +45,8 @@ #ifndef NO_SHARED_LIBS #define LD_SWITCH_SYSTEM -e start -dc -dp #define HAVE_TEXT_START /* No need to define `start_of_text'. */ -#define START_FILES pre-crt0.o /usr/lib/crt0.o -#define UNEXEC unexsunos4.o +#define START_FILES pre-crt0.o ${LIBDIR}/crt0.o +#define UNEXEC unexfreebsd.o #define RUN_TIME_REMAP #ifndef N_TRELOFF I have not yet done send-pr because the number of ports whitch have USE_GMAKE is 185. I could not check them. -- Takeshi OHASHI, Dept. of A.I., Kyushu Inst. of Tech., Iizuka 820, JAPAN ohashi@mickey.ai.kyutech.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 18:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02317 for freebsd-current-outgoing; Wed, 8 Jul 1998 18:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02302 for ; Wed, 8 Jul 1998 18:47:17 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA16245; Thu, 9 Jul 1998 09:46:13 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA15831; Thu, 9 Jul 1998 09:46:38 +0800 Message-Id: <199807090146.JAA15831@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: current@FreeBSD.ORG Subject: Re: Rate limit for system calls to prevent denial of service attacks? In-reply-to: Your message of "Thu, 09 Jul 1998 10:30:23 +0930." <199807090100.KAA20575@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 09:46:38 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Limiting CPU time per process or user is probably not sufficient, > > unless you set it to absurdly small limits. It looks to me like we > > need some sort of *rate limiting* for system calls. Anybody looked > > at this? > Hmm.. a neat idea :) > I think this in conjunction with a decent sized process limit would be quite > useful. Why does this whole discussion remind me of Softway's Fair SHare Scheduler, which was developed for a student environment? Basically, if the machine's under load, it allows you to limit the CPU used by a given group to X%. It was the subject of a couple of Usenix papers in the 80s as I recall. Sheesh, I'm sure BDE's heard of it, being a part of the Sydney Unix Mafia. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 19:40:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08484 for freebsd-current-outgoing; Wed, 8 Jul 1998 19:40:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08475 for ; Wed, 8 Jul 1998 19:40:17 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id VAA23209; Wed, 8 Jul 1998 21:40:39 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id VAA01464; Wed, 8 Jul 1998 21:39:56 -0500 (CDT) (envelope-from joelh) Date: Wed, 8 Jul 1998 21:39:56 -0500 (CDT) Message-Id: <199807090239.VAA01464@detlev.UUCP> To: ohashi@mickey.ai.kyutech.ac.jp CC: mauri@krabi.mbp.ee, current@FreeBSD.ORG In-reply-to: <199807090136.KAA01795@ateken2.mickey.ai.kyutech.ac.jp> (ohashi@mickey.ai.kyutech.ac.jp) Subject: Re: crt0.o From: Joel Ray Holveck References: <199807090136.KAA01795@ateken2.mickey.ai.kyutech.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removed from -ports] >>there are some ports which cry for /usr/lib/crt0.o... > Some ports, mule-2.3 and emacs20, have same problem. > I have not yet done send-pr because the number of ports whitch have > USE_GMAKE is 185. I could not check them. I'm doing some work on Emacs right now. If the /usr/lib/aout looks like it may be an extended situation (say, through the next Emacs release or two), I can make the necessary changes to the distribution. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 20:11:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11787 for freebsd-current-outgoing; Wed, 8 Jul 1998 20:11:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11782 for ; Wed, 8 Jul 1998 20:11:19 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA06773; Thu, 9 Jul 1998 13:11:15 +1000 Date: Thu, 9 Jul 1998 13:11:15 +1000 From: Bruce Evans Message-Id: <199807090311.NAA06773@godzilla.zeta.org.au> To: doconnor@gsoft.com.au, shocking@prth.pgs.com Subject: Re: Rate limit for system calls to prevent denial of service attacks? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Why does this whole discussion remind me of Softway's Fair SHare Scheduler, >which was developed for a student environment? Basically, if the machine's >under load, it allows you to limit the CPU used by a given group to X%. It was >the subject of a couple of Usenix papers in the 80s as I recall. Sheesh, I'm >sure BDE's heard of it, being a part of the Sydney Unix Mafia. I just live here :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 20:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17016 for freebsd-current-outgoing; Wed, 8 Jul 1998 20:43:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA17010 for ; Wed, 8 Jul 1998 20:43:26 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yu7c6-0001SH-00; Wed, 8 Jul 1998 21:43:18 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id VAA11270; Wed, 8 Jul 1998 21:45:09 -0600 (MDT) Message-Id: <199807090345.VAA11270@harmony.village.org> To: Stephen Hocking-Senior Programmer PGS Tensor Perth Subject: Re: Rate limit for system calls to prevent denial of service attacks? Cc: "Daniel O'Connor" , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Jul 1998 09:46:38 +0800." <199807090146.JAA15831@ariadne.tensor.pgs.com> References: <199807090146.JAA15831@ariadne.tensor.pgs.com> Date: Wed, 08 Jul 1998 21:45:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807090146.JAA15831@ariadne.tensor.pgs.com> Stephen Hocking-Senior Programmer PGS Tensor Perth writes: : Why does this whole discussion remind me of Softway's Fair SHare : Scheduler, which was developed for a student environment? Basically, : if the machine's under load, it allows you to limit the CPU used by : a given group to X%. It was the subject of a couple of Usenix papers : in the 80s as I recall. Sheesh, I'm sure BDE's heard of it, being a : part of the Sydney Unix Mafia. Related to this is the Lottery Scheduler that some folks have running on a K6-200 box running FreeBSD. Here's the URL that a friend sent me: >>http://www.research.digital.com/SRC/personal/caw/papers.html >> >>Carl A. Waldspurger and William E. Weihl. Lottery Scheduling: Flexible >>Proportional-Share Resource Mangement, Proceedings of the First >>Symposium on Operating Systems Design and Implementation (OSDI '94), >>pages 1-11, Monterey, California, November 1994. Received award for >>best paper. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 20:59:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19578 for freebsd-current-outgoing; Wed, 8 Jul 1998 20:59:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19572 for ; Wed, 8 Jul 1998 20:58:58 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA02268; Wed, 8 Jul 1998 20:58:51 -0700 (PDT) (envelope-from jdp) Message-Id: <199807090358.UAA02268@austin.polstra.com> To: thyerm@camtech.net.au Subject: Re: Problem with restore under current. In-Reply-To: <359A194D.8223143B@camtech.net.au> References: <359A194D.8223143B@camtech.net.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 08 Jul 1998 20:58:50 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <359A194D.8223143B@camtech.net.au>, Matthew Thyer wrote: > ./bin/ypchsh could not be linked to ./bin/chpass > ./bin/ypchfn " ./bin/chpass > ./bin/ypchpass " ./bin/chpass > ./bin/chsh " ./bin/chpass > ./bin/chfn " ./bin/chpass > ./bin/yppasswd " ./bin/passwd I committed a fix for this bug in -current a few minutes ago. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 8 22:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02329 for freebsd-current-outgoing; Wed, 8 Jul 1998 22:57:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xxx.syix.com (xxx.syix.com [209.155.24.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02318 for ; Wed, 8 Jul 1998 22:57:09 -0700 (PDT) (envelope-from dave@xxx.syix.com) Received: (from root@localhost) by xxx.syix.com (8.8.8/8.8.8) id WAA03999; Wed, 8 Jul 1998 22:56:56 -0700 (PDT) (envelope-from dave) Date: Wed, 8 Jul 1998 22:56:56 -0700 (PDT) Message-Id: <199807090556.WAA03999@xxx.syix.com> To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: file://localhost/usr/share/doc/handbook/handbook259.html X-Mailer: Lynx, Version 2.8rel.2 X-Personal_name: Dave Overton From: dave@syix.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 00:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09411 for freebsd-current-outgoing; Thu, 9 Jul 1998 00:03:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09386 for ; Thu, 9 Jul 1998 00:03:53 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA18215; Thu, 9 Jul 1998 09:03:26 +0200 (MEST) (envelope-from kuku) Message-ID: <19980709090325.05785@gil.physik.rwth-aachen.de> Date: Thu, 9 Jul 1998 09:03:25 +0200 From: Christoph Kukulies To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: More on CVSUP and today's current -- looks like "de" driver related References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Richard Wackerbarth on Wed, Jul 08, 1998 at 05:12:01PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 08, 1998 at 05:12:01PM -0500, Richard Wackerbarth wrote: > Further isolation of the hanging problem. > > "de" interface, today's kernel, AND CVsup: hangs with full buffers. I can confirm (see my post Subject: 'Frozen' ), that there are severe kernel problems with the de0 driver. (abnormal interrupt...) panic in tsleep. > However, if you change ANY ONE of the above, > {"ed" interface OR Jun18 kernel.GENERIC OR ftp} and the other two as above: > works. > > kernel rebuilt within the past hour. > > Richard Wackerbarth > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 03:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27083 for freebsd-current-outgoing; Thu, 9 Jul 1998 03:40:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27072 for ; Thu, 9 Jul 1998 03:40:54 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA14215 ; Thu, 9 Jul 1998 12:36:35 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA10648; Thu, 9 Jul 1998 12:36:34 +0200 To: Andrzej Bialecki Cc: Amancio Hasty , Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 12:36:34 +0200 In-Reply-To: Andrzej Bialecki's message of Tue, 7 Jul 1998 10:36:08 +0200 (CEST) Message-ID: Lines: 20 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > Also, "kernel" above doesn't equal `size kernel` - there are disk buffers, > mbufs, stacks, and whatnot which are allocated on start; so its much > bigger. I think a significant portion of that can be eliminated by reducing MAXUSERS, but it's quite possible I'm speaking out of my arse. If you blow away most of /etc and set up a completely customized environment, you might very well never need more than a handful of processes (ever tried MASUERS=2?) but it may have a detrimental effect on network performance since it also reduces the number of mbufs and mbuf clusters, which is Not Good (tm) if you're trying to set up a router or gateway or whatever. Just my (insert insignificant amount of your favorite currency here). DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 03:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27709 for freebsd-current-outgoing; Thu, 9 Jul 1998 03:46:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27703 for ; Thu, 9 Jul 1998 03:46:40 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA14581 ; Thu, 9 Jul 1998 12:44:48 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA10751; Thu, 9 Jul 1998 12:44:47 +0200 To: John Birrell Cc: jkh@time.cdrom.com (Jordan K. Hubbard), patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world References: <199807081124.VAA23031@cimlogic.com.au> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 12:44:46 +0200 In-Reply-To: John Birrell's message of Wed, 8 Jul 1998 21:24:16 +1000 (EST) Message-ID: Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell writes: > Obviously sending this information to this list _every_ time someone > compains about make world or buildworld not working on 2.2.6 doesn't > get the message across. I'm seriously considering getting a religion... Nah, religion is greatly overrated. One of my favorite quotes from Melanie Rawn's _The Ruins of Ambrai_: "I still say it doesn't make much sense." "My very precious and relentlessly literal child, it's religion. It doesn't have to make sense." DES (fervent admirer of Gorynel Desse) -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 04:58:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04554 for freebsd-current-outgoing; Thu, 9 Jul 1998 04:58:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04548 for ; Thu, 9 Jul 1998 04:58:39 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id NAA22712; Thu, 9 Jul 1998 13:58:43 +0200 (MEST) (envelope-from kuku) Message-ID: <19980709135843.B22696@gil.physik.rwth-aachen.de> Date: Thu, 9 Jul 1998 13:58:43 +0200 From: Christoph Kukulies To: Christoph Kukulies , Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: More on CVSUP and today's current -- looks like "de" driver related References: <19980709090325.05785@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: <19980709090325.05785@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Thu, Jul 09, 1998 at 09:03:25AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 09, 1998 at 09:03:25AM +0200, Christoph Kukulies wrote: > On Wed, Jul 08, 1998 at 05:12:01PM -0500, Richard Wackerbarth wrote: > > Further isolation of the hanging problem. > > > > "de" interface, today's kernel, AND CVsup: hangs with full buffers. > > I can confirm (see my post Subject: 'Frozen' ), that there are > severe kernel problems with the de0 driver. (abnormal interrupt...) > panic in tsleep. I found that backing out the last change Peter Wemm was talking about (#if 0 ) leads to some memory leak in the driver: No buffer space available after some hours of uptime. > > > > However, if you change ANY ONE of the above, > > {"ed" interface OR Jun18 kernel.GENERIC OR ftp} and the other two as above: > > works. > > > > kernel rebuilt within the past hour. > > > > Richard Wackerbarth > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 05:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05192 for freebsd-current-outgoing; Thu, 9 Jul 1998 05:07:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prcom.rcom.spb.su (prcom.rcom.spb.su [193.124.80.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05185 for ; Thu, 9 Jul 1998 05:07:17 -0700 (PDT) (envelope-from dragonfa@prcom.rcom.spb.su) Received: (from dragonfa@localhost) by prcom.rcom.spb.su (8.8.8/8.8.8) id QAA05076; Thu, 9 Jul 1998 16:05:36 +0400 (MSD) (envelope-from dragonfa) From: Alexey Pialkin Message-Id: <199807091205.QAA05076@prcom.rcom.spb.su> Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: <199807071828.LAA01144@dingo.cdrom.com> from Mike Smith at "Jul 7, 98 11:28:12 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 9 Jul 1998 16:05:36 +0400 (MSD) Cc: thz@Lennartz-Electronic.DE, mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > For those which say "put in more memory/disk": This doesn't help if you > > > > have to run out of batteries w/ solar-panels on very remote localities, > > > > only access by radio-telemetry. You need very low power equipment there. > > > > So the question is not $ but watts. > > > > > > In the same timeframe, memory power consumption has gone down by more > > > than an order of maginitude, while cost has fallen even further. > > > > > > Sorry, but the argument still holds good. 8) > > > > Sorry, but to run with 3 watts from dynamic memory is not possible, > > do you know prices of SRAM? Also effordable harddisks are > > much lower now in consumption, but not that low. So booting from > > eprom or floppy is a must. > > No insult intended, but your design obviously sucks. I am working right > now with a PC104 board not specifically designed for low-power > operation. It manages to put an NX586-based micro, all the standard PC > peripherals, 8M of RAM, 8M of flash, etc. into a sub-3W power budget. > > Like I said, this is a design that's not even trying. Look at the > power budget that eg. the Palm Pilot works with. PalmPilot have 1/2 mb ram and to run linux on it you should got a 8mb ram/2 mb flash upgrade... So only a kernel this a size about 300kb would be a real threat for PalmOS ;) Alexey Pialkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 05:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08995 for freebsd-current-outgoing; Thu, 9 Jul 1998 05:45:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08977 for ; Thu, 9 Jul 1998 05:45:38 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with ESMTP id OAA25444; Thu, 9 Jul 1998 14:48:25 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 9 Jul 1998 14:48:25 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: =?ISO-8859-2?Q?Dag-Erling_Coidan_Sm=F8rgrav?= cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > Andrzej Bialecki writes: > > Also, "kernel" above doesn't equal `size kernel` - there are disk buffers, > > mbufs, stacks, and whatnot which are allocated on start; so its much > > bigger. > > I think a significant portion of that can be eliminated by reducing > MAXUSERS, but it's quite possible I'm speaking out of my arse. You mean proc tables etc... I'm not sure if it's significant (see below). > If you blow away most of /etc and set up a completely customized > environment, you might very well never need more than a handful of > processes (ever tried MASUERS=2?) but it may have a detrimental effect Yes. I even tried MAXUSERS=1 :-). > on network performance since it also reduces the number of mbufs and > mbuf clusters, which is Not Good (tm) if you're trying to set up a > router or gateway or whatever. This I can adjust with NMBCLUSTERS and MBUFS, or tweak the numbers manually. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 06:10:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11512 for freebsd-current-outgoing; Thu, 9 Jul 1998 06:10:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11501 for ; Thu, 9 Jul 1998 06:10:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id JAA27937; Thu, 9 Jul 1998 09:09:59 -0400 (EDT) Date: Thu, 9 Jul 1998 09:09:58 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: "Jordan K. Hubbard" cc: Warner Losh , Travis Cole , John Birrell , patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-Reply-To: <7641.899944196@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Jul 1998, Jordan K. Hubbard wrote: > I suggested a "make update" when this first came up, but nobody > seems to want to go down that route. Too simple, I guess. :) I don't think an "update" target should be added to the top-level Makefile, only because it's already there. narcissus# make update -------------------------------------------------------------- Running /usr/local/bin/cvsup -------------------------------------------------------------- Parsing supfile "/usr/src/standard-supfile" ... Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 07:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23290 for freebsd-current-outgoing; Thu, 9 Jul 1998 07:50:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23280 for ; Thu, 9 Jul 1998 07:50:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA09555; Thu, 9 Jul 1998 07:49:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: ben@rosengart.com cc: Warner Losh , Travis Cole , John Birrell , patton@sysnet.net, freebsd-current@FreeBSD.ORG Subject: Re: building world In-reply-to: Your message of "Thu, 09 Jul 1998 09:09:58 EDT." Date: Thu, 09 Jul 1998 07:49:31 -0700 Message-ID: <9551.899995771@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Typo - I meant to say "make upgrade" :) - Jordan > On Wed, 8 Jul 1998, Jordan K. Hubbard wrote: > > > I suggested a "make update" when this first came up, but nobody > > seems to want to go down that route. Too simple, I guess. :) > > I don't think an "update" target should be added to the top-level > Makefile, only because it's already there. > > narcissus# make update > -------------------------------------------------------------- > Running /usr/local/bin/cvsup > -------------------------------------------------------------- > Parsing supfile "/usr/src/standard-supfile" > ... > > > Ben > > "You have your mind on computers, it seems." > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 08:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27157 for freebsd-current-outgoing; Thu, 9 Jul 1998 08:16:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27130 for ; Thu, 9 Jul 1998 08:16:15 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id SAA03380 for ; Thu, 9 Jul 1998 18:15:50 +0300 (EET DST) Date: Thu, 9 Jul 1998 18:15:50 +0300 (EEST) From: Vallo Kallaste X-Sender: root@myhakas.matti.ee To: current@FreeBSD.ORG Subject: mkhybrid port doesn't compile under -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! I have seen such behavior for a while now... about 4 weeks or so. Mkhybrid port compiles without any modifications under 2.2.5-RELEASE, I don't know other branches, but under -current it's broken. Personally I'm using that nice program about an half year, compiled it under 2.2.5 and used under -current. Must I send a PR ? Maybe some other more knowledgeable people can do that? Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 11:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22554 for freebsd-current-outgoing; Thu, 9 Jul 1998 11:03:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22541 for ; Thu, 9 Jul 1998 11:03:50 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id SAA19653 for ; Thu, 9 Jul 1998 18:03:43 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id OAA19109 for current@freebsd.org; Thu, 9 Jul 1998 14:03:33 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807091803.OAA19109@rtfm.ziplink.net> Subject: clock runs away To: current@FreeBSD.ORG Date: Thu, 9 Jul 1998 14:03:33 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25569 for freebsd-current-outgoing; Thu, 9 Jul 1998 11:16:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25564 for ; Thu, 9 Jul 1998 11:16:18 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA14947; Thu, 9 Jul 1998 11:15:47 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma014942; Thu Jul 9 11:15:28 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA09514; Thu, 9 Jul 1998 11:15:28 -0700 (PDT) From: Archie Cobbs Message-Id: <199807091815.LAA09514@bubba.whistle.com> Subject: Re: Rate limit for system calls to prevent denial of service attacks? In-Reply-To: from Garance A Drosihn at "Jul 8, 98 07:38:54 pm" To: drosih@rpi.edu (Garance A Drosihn) Date: Thu, 9 Jul 1998 11:15:28 -0700 (PDT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > >>The following small program: > >> > >> main(){while(1) fork();} > >> > >> is a very effective denial of service attack against FreeBSD-2.2.6, > >> despite reasonable defaults in login.conf. The problem is *not* the > >> number of processes, but the system call rate. It's actually kind of > >> amazing to follow this with vmstat, and see that the box is suddenly > >> doing 395000 system calls per second :-) (this is a P-166). > > The subject of this thread asks about adding a rate-limit for > system calls. I don't think that's a good idea, but I would like > to see some kind of throttling of calls to fork() in particular. Why would 100 processes doing main(){while(1) getpid();} be accounted for any differently than 100 processes doing main(){while(1) /* infinite loop in user mode */;} ? Or am I misunderstanding something. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 12:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05106 for freebsd-current-outgoing; Thu, 9 Jul 1998 12:04:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05099 for ; Thu, 9 Jul 1998 12:04:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00420; Thu, 9 Jul 1998 21:01:53 +0200 (CEST) To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: clock runs away In-reply-to: Your message of "Thu, 09 Jul 1998 14:03:33 EDT." <199807091803.OAA19109@rtfm.ziplink.net> Date: Thu, 09 Jul 1998 21:01:53 +0200 Message-ID: <418.900010913@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807091803.OAA19109@rtfm.ziplink.net>, Mikhail Teterin writes: >Hello! >I installed the May-20 snapshot on a friend's P100 system. The >clock started to gain a few extra minutes per hour -- never did >that with a pre-2.2 snapshot it ran before. Uhm, are we talking 2.2-980520 or 3.0-980520-SNAP here ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 12:07:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05493 for freebsd-current-outgoing; Thu, 9 Jul 1998 12:07:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (root@www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05488 for ; Thu, 9 Jul 1998 12:07:19 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id PAA08629 for ; Thu, 9 Jul 1998 15:08:38 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id PAA02042 for current@freebsd.org; Thu, 9 Jul 1998 15:07:14 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199807091907.PAA02042@xxx.video-collage.com> Subject: Re: clock runs away In-Reply-To: <418.900010913@critter.freebsd.dk> from Poul-Henning Kamp at "Jul 9, 98 09:01:53 pm" To: current@FreeBSD.ORG Date: Thu, 9 Jul 1998 15:07:14 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli", Mikhail Teterin writes: =>Hello! = =>I installed the May-20 snapshot on a friend's P100 system. The =>clock started to gain a few extra minutes per hour -- never did =>that with a pre-2.2 snapshot it ran before. = =Uhm, are we talking 2.2-980520 or 3.0-980520-SNAP here ? 3.0, the one that went out on CD. Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 12:53:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15000 for freebsd-current-outgoing; Thu, 9 Jul 1998 12:53:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14995 for ; Thu, 9 Jul 1998 12:53:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00567; Thu, 9 Jul 1998 21:50:50 +0200 (CEST) To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: clock runs away In-reply-to: Your message of "Thu, 09 Jul 1998 15:07:14 EDT." <199807091907.PAA02042@xxx.video-collage.com> Date: Thu, 09 Jul 1998 21:50:49 +0200 Message-ID: <565.900013849@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807091907.PAA02042@xxx.video-collage.com>, Mikhail Teterin write s: >Poul-Henning Kamp once stated: > >=In message <199807091803.OAA19109@rtfm.ziplink.net>, Mikhail Teterin writes: >=>Hello! >= >=>I installed the May-20 snapshot on a friend's P100 system. The >=>clock started to gain a few extra minutes per hour -- never did >=>that with a pre-2.2 snapshot it ran before. >= >=Uhm, are we talking 2.2-980520 or 3.0-980520-SNAP here ? > >3.0, the one that went out on CD. Thanks! ok, do this: boot the kernel it's running now with -v and save the dmesg output compile a kernel with options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION boot the new kernel with -v and save the dmesg output send me the two dmesg outputs in an email... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 13:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23764 for freebsd-current-outgoing; Thu, 9 Jul 1998 13:59:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23759 for ; Thu, 9 Jul 1998 13:59:07 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA11000 for ; Thu, 9 Jul 1998 13:56:15 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010998; Thu Jul 9 20:56:14 1998 Message-ID: <35A52E6B.6201DD56@whistle.com> Date: Thu, 09 Jul 1998 13:56:11 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: TESTERS NEEDED: Softupdates looks Very good. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of this morning there are 2 known bugs in Softupdates, and one known 'gotcha' The bugs are: 1/ the following "rare" panic has not been traced yet as we have been unable to get a core file with it.. panic: newdirrem: inum 26368 should be 26367 2/ there is also a dependency order problem in some cases (very rare) Over all a crash with soft updates will already probably leave your disk in a much cleaner state than you're used to. The "gotcha" is really quite hillarious.. This note from Matt Dillon at Best Communications.. ------ Begin quote------ unlink() is so fast under softupdates that Diablo's news spool expiration removed 80% of the files in the test news spool before it realized that it had sufficient free space. Oops! ------ This is because the unlink happens asynchronourly, and the space may not show up for 30 seconds or so. Unlink() is now 2 orders of magnitude faster.. in 30 seconds you could delete several million files, (and it apparently did). Unlinking the entire X11R6 hierarchy takes well under 1 second. It's now possible to type #rm -rf / and REALLY screw yourself before you have time to hit ^C :-) We need more testers. specifically to try get a core dump of that panic. If you know how to compile a debug kernel config -g MYKERNEL cd ../../compile/MYKERNEL make depend; make cp kernel kernel.debug strip -d kernel make install and you know how to get a core dump dumpon /dev/rsd0b and you know how to run softupdates cd /sys/ufs/ffs cat *READ* then YOU are needed for testing! if you get a core-dump and you have a matching debug kernel, let us know asap. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 16:21:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13822 for freebsd-current-outgoing; Thu, 9 Jul 1998 16:21:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13813 for ; Thu, 9 Jul 1998 16:21:34 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id QAA05971; Thu, 9 Jul 1998 16:25:13 -0700 (PDT) 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: <35A52E6B.6201DD56@whistle.com> Date: Thu, 09 Jul 1998 16:23:49 -0700 (PDT) Organization: Applied Physics Laboratory From: Steve Kargl To: Julian Elischer Subject: RE: TESTERS NEEDED: Softupdates looks Very good. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Jul-98 Julian Elischer wrote: >As of this morning there are 2 known bugs in Softupdates, >and one known 'gotcha' > >The bugs are: > >1/ >the following "rare" panic has not been traced yet as we have been >unable to get a core file with it.. > > panic: newdirrem: inum 26368 should be 26367 > [deleted gotcha] > >We need more testers. specifically to try get a core dump of that panic. > Any particular system configuration wrt to the above panic? Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 16:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18287 for freebsd-current-outgoing; Thu, 9 Jul 1998 16:54:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18278 for ; Thu, 9 Jul 1998 16:54:55 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id HAA15624 for ; Fri, 10 Jul 1998 07:53:59 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id HAA19771; Fri, 10 Jul 1998 07:54:22 +0800 Message-Id: <199807092354.HAA19771@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: CTM cvs-cur gone walkies from ftp.freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Jul 1998 07:54:22 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sigh - Hasn't been updated since cvs-cur.4450.gz. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 16:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18794 for freebsd-current-outgoing; Thu, 9 Jul 1998 16:59:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (appp11.sysnet.net [206.142.16.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18785 for ; Thu, 9 Jul 1998 16:59:24 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id TAA25912; Thu, 9 Jul 1998 19:49:41 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: In-Reply-To: <19980708114832.B31417@nihilist.org> References: <199807081124.VAA23031@cimlogic.com.au>; from John Birrell on Wed, Jul 08, 1998 at 09:24:16PM +1000 <4648.899893623@time.cdrom.com> <199807081124.VAA23031@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Jul 1998 20:02:49 -0400 To: Travis Cole From: Matthew Patton Subject: SOLUTION! 2.2.6-Release to -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I started this most recent round of posts on this infernal question, I am most happy to report that I have a working solution (others may exist). I wish somebody would try my solution again from a completely clean box so we can confirm it wasn't a fluke. Unless contrary evidence crops up, FAQ maintainers and buildworld webpage authors feel free to post the solution. somebody said: >cd /usr/src >make -m /usr/src/share/mk world (or buildworld) You'd think this would work but as others can attest to, it doesn't. I can't believe we've all fatfingered the command. If you are using 2.2.6-STABLE or some previous incarnation of -current, this may work just fine. BTW, what's up with the following logic? >.if (!make(world)) && (!make(buildworld)) && (!make(installworld)) >.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} >.endif if we're doing any of the *world, don't we WANT to be using the mk files in /usr/src/share/mk? >cd /usr/src >make -m buildworld MACHINE_ARCH="i386" BINFORMAT=aout is close but does *NOT* work from -RELEASE. You will get messages about the linker not finding "___error which was referenced from the text segment." The problem is that a library is old. I don't know which one. Anyone know? Rebuilding the libs solves it. So, (drumroll) this is how you build -current from 2.2.6-RELEASE. I make no promises about any earlier version. FWIW, I adopted the build procedure we use in OpenBSD to get things rolling. 1. cvsup src-all (8pm EST 9 July) 2. cd /usr/src/share/mk # not much point NOT to do this, also obviates the need for the "-m /usr/src/share/mk" directive 3. make MACHINE_ARCH="i386" BINFORMAT=aout install 4. cd /usr/src/include # old sources can be dangerous 5. make MACHINE_ARCH="i386" BINFORMAT=aout install 6. cd /usr/src/lib # nukes the ___error problem 7. make MACHINE_ARCH="i386" BINFORMAT=aout 8. make MACHINE_ARCH="i386" BINFORMAT=aout install *caution* a couple of make files are broken, see notes 9. cd /usr/src 10. make MACHINE_ARCH="i386" BINFORMAT=aout buildworld 11. wait an eternity (even on a PPro233 with 128mb of RAM), watch a movie 12. make MACHINE_ARCH="i386" BINFORMAT=aout installworld 13. quick, compile a new kernel Notes: /usr/src/lib/libtcl/Makefile is broken in the beforeinstall: target. The 'for' loop with argument 'e' that's supposed to install the *.tcl files from the library directory, constructs a command line for install that it barfs on. Make quits with error 64. Do it by hand or simply comment out the section. It's not crucial. I put in a sendbug. Hopefully it went thru. /usr/src/lib/libc/gen/Makefile tries to install a file lockf.3.gz in the man(3) section. I deleted the entry from the list though lockf.3 does exist. Will have to look at this again. To think I went through all this pain just to get a SMP kernel so I can crack rc5des faster. My word of advice: if you want SMP, save yourself the hassle and start with a -current snapshot. *whew* -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 17:28:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21712 for freebsd-current-outgoing; Thu, 9 Jul 1998 17:28:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21707 for ; Thu, 9 Jul 1998 17:28:45 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA19465; Thu, 9 Jul 1998 17:22:57 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd019461; Fri Jul 10 00:22:49 1998 Date: Thu, 9 Jul 1998 17:22:45 -0700 (PDT) From: Julian Elischer To: Steve Kargl cc: current@FreeBSD.ORG Subject: RE: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Jul 1998, Steve Kargl wrote: > > On 09-Jul-98 Julian Elischer wrote: > >As of this morning there are 2 known bugs in Softupdates, > >and one known 'gotcha' > > > >The bugs are: > > > >1/ > >the following "rare" panic has not been traced yet as we have been > >unable to get a core file with it.. > > > > panic: newdirrem: inum 26368 should be 26367 > > > > [deleted gotcha] > > > > >We need more testers. specifically to try get a core dump of that panic. > > > > Any particular system configuration wrt to the above panic? > Not that I've been able to see.. maybe those who have seen it could say more.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 17:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25128 for freebsd-current-outgoing; Thu, 9 Jul 1998 17:41:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25123 for ; Thu, 9 Jul 1998 17:41:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA16042; Fri, 10 Jul 1998 10:41:19 +1000 Date: Fri, 10 Jul 1998 10:41:19 +1000 From: Bruce Evans Message-Id: <199807100041.KAA16042@godzilla.zeta.org.au> To: current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: CTM cvs-cur gone walkies from ftp.freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Sigh - Hasn't been updated since cvs-cur.4450.gz. It seemed to miss a few deliveries, but is now up to 4454. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 18:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27991 for freebsd-current-outgoing; Thu, 9 Jul 1998 18:09:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27983 for ; Thu, 9 Jul 1998 18:09:04 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.48.34]) by mailman.cs.ucla.edu (8.8.8/UCLACS-4.0) with ESMTP id SAA26518; Thu, 9 Jul 1998 18:09:03 -0700 (PDT) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.8.8/8.8.8) with ESMTP id SAA01971; Thu, 9 Jul 1998 18:09:02 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199807100109.SAA01971@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Patton cc: Travis Cole , freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current In-reply-to: Your message of "Wed, 08 Jul 1998 20:02:49 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 18:09:01 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > somebody said: > >cd /usr/src > >make -m /usr/src/share/mk world (or buildworld) This is correct. It doesn't work, per se. > >cd /usr/src > >make -m buildworld MACHINE_ARCH="i386" BINFORMAT=aout And yes, this also appears to be true. However, last night, I upgraded my 2.2.2 system as follows: setenv BINFORMAT aout setenv MACHINE_ARCH i386 make -m /usr/src/share/mk buildworld It went through to completion... No extra make frobbing, incremental installing of headers, rebuilding of libs, gnashing of teeth, and removal of hair. -scooter -- Scott Michel | No research ideal ever survives UCLA Computer Science | contact with implementation. PhD Graduate Student | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 18:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28095 for freebsd-current-outgoing; Thu, 9 Jul 1998 18:09:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28056 for ; Thu, 9 Jul 1998 18:09:27 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA03033; Thu, 9 Jul 1998 20:07:56 -0400 (EDT) Date: Thu, 9 Jul 1998 20:07:56 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Bruce Evans cc: current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: CTM cvs-cur gone walkies from ftp.freebsd.org In-Reply-To: <199807100041.KAA16042@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Jul 1998, Bruce Evans wrote: > >Sigh - Hasn't been updated since cvs-cur.4450.gz. > > It seemed to miss a few deliveries, but is now up to 4454. I guess not to every one, because I have an unbroken string, now up to 4454 (like you said). I see some are missing, tho, from wcarchive, so if you want some, I could email them to you. Tell me which ones you've missed, ok? > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 18:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29548 for freebsd-current-outgoing; Thu, 9 Jul 1998 18:24:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29543 for ; Thu, 9 Jul 1998 18:24:10 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA19511; Fri, 10 Jul 1998 11:24:01 +1000 Date: Fri, 10 Jul 1998 11:24:01 +1000 From: Bruce Evans Message-Id: <199807100124.LAA19511@godzilla.zeta.org.au> To: patton@sysnet.net, tcole@nihilist.org Subject: Re: SOLUTION! 2.2.6-Release to -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >somebody said: > >cd /usr/src > >make -m /usr/src/share/mk world (or buildworld) > >You'd think this would work but as others can attest to, it doesn't. I >can't believe we've all fatfingered the command. If you are using >2.2.6-STABLE or some previous incarnation of -current, this may work just >fine. It seems to work as advertised. Except /usr/src is wrong if the current sources are not in /usr/src. Somebody should have said: cd /wherever/the/current/sources/are make -m `pwd`/share/mk world >BTW, what's up with the following logic? > >.if (!make(world)) && (!make(buildworld)) && (!make(installworld)) > >.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} > >.endif Nothing. -m doesn't work in FreeBSD-2.1.any, so it can't be used unconditionally. Somebody should have said that the above only works in FreeBSD-2.2.any (and in certain versions of -current). >if we're doing any of the *world, don't we WANT to be using the mk files in >/usr/src/share/mk? No, we want to use the mk files in ${.CURDIR}/share/mk :-). > >cd /usr/src > >make -m buildworld MACHINE_ARCH="i386" BINFORMAT=aout > >is close but does *NOT* work from -RELEASE. You will get messages about the It is nonsense. It says to search for the mk files in the "buildworld" subdirectory of the current directory and make the default target (all). It has nothing to do with the world targets. Setting MACHINE_ARCH helps avoid syntax errors in src/Makefile and setting BINFORMAT helps avoid syntax errors in bsd.own.mk but otherwise have very little effect for the `all' target. >linker not finding "___error which was referenced from the text segment." >The problem is that a library is old. I don't know which one. Anyone know? >Rebuilding the libs solves it. libc. Libraries are rebuilt by `make world', by LIBDIR is set wrong by the old mk files, so the linker can't find the new libraries. The settings of LIBDIR, MACHINE_ARCH and BINFORMAT seem to be the only things that are really broken. >So, (drumroll) this is how you build -current from 2.2.6-RELEASE. I make no >promises about any earlier version. FWIW, I adopted the build procedure we >use in OpenBSD to get things rolling. > >1. cvsup src-all (8pm EST 9 July) >2. cd /usr/src/share/mk # not much point NOT to do this, also >obviates the need for the "-m /usr/src/share/mk" directive >3. make MACHINE_ARCH="i386" BINFORMAT=aout install >4. cd /usr/src/include # old sources can be dangerous >5. make MACHINE_ARCH="i386" BINFORMAT=aout install >6. cd /usr/src/lib # nukes the ___error problem >7. make MACHINE_ARCH="i386" BINFORMAT=aout >8. make MACHINE_ARCH="i386" BINFORMAT=aout install > *caution* a couple of make files are broken, see notes >9. cd /usr/src >10. make MACHINE_ARCH="i386" BINFORMAT=aout buildworld >11. wait an eternity (even on a PPro233 with 128mb of RAM), watch a movie >12. make MACHINE_ARCH="i386" BINFORMAT=aout installworld >13. quick, compile a new kernel About 11 steps too many for FreeBSD :-). Steps 2-8 break things in certain configurations that `make world' is supposed to handle. Steps 4-5 tend to _cause_ the ___error problem. Of course you can work around the breakage by doing fixup steps if you understand the makefiles. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 18:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02320 for freebsd-current-outgoing; Thu, 9 Jul 1998 18:56:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02312 for ; Thu, 9 Jul 1998 18:56:06 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id UAA01739; Thu, 9 Jul 1998 20:56:02 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 9 Jul 1998 20:56:01 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Julian Elischer cc: Steve Kargl , current@FreeBSD.ORG Subject: RE: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Jul 1998, Julian Elischer wrote: > > > On Thu, 9 Jul 1998, Steve Kargl wrote: > > > > > On 09-Jul-98 Julian Elischer wrote: > > >As of this morning there are 2 known bugs in Softupdates, > > >and one known 'gotcha' > > > > > >The bugs are: > > > > > >1/ > > >the following "rare" panic has not been traced yet as we have been > > >unable to get a core file with it.. > > > > > > panic: newdirrem: inum 26368 should be 26367 > > > > > > > [deleted gotcha] > > > > > > > >We need more testers. specifically to try get a core dump of that panic. > > > > > > > Any particular system configuration wrt to the above panic? > > > > Not that I've been able to see.. > maybe those who have seen it could say more.. > > julian I believe that was the one I experienced a while back. I still have that debugging kernel ready to catch it, but it hasn't happened again. Maybe I'll get around to torturing the filesystem one of these days. I don't think there's anything really special about my setup, though. I have two 4.3GB IBM DCAS-34330W's on a NCR 53C875 based controller. Bunch of data to help you see what I have follows... Keep in mind this system is never on for more than a day or two, or else I wouldn't be able to sleep. :-) It has also only been on 4 hours now, almost entirely idle, so the 'writes:' numbers are low. /dev/sd0s1a on / (local, writes: sync 5 async 1061) /dev/sd1s1f on /devel (local, soft-updates, writes: sync 2 async 0) /dev/sd1s1g on /extra (local, writes: sync 2 async 0) /dev/sd0s1e on /tmp (local, soft-updates, writes: sync 2 async 347) /dev/ccd0a on /usr (local, soft-updates, writes: sync 6 async 2125) /dev/sd0s1h on /release (local, soft-updates, writes: sync 2 async 0) /dev/sd1s1e on /usr/obj (local, soft-updates, writes: sync 2 async 0) /dev/sd0s1g on /usr/src (local, soft-updates, writes: sync 2 async 0) /dev/sd0s1f on /var (local, writes: sync 191 async 719) procfs on /proc (local) Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Wed Jul 1 12:13:53 CDT 1998 root@cheetah.privatenet:/usr/src/sys/compile/CHEETAH Timecounter "i8254" frequency 1193182 Hz cost 2301 ns Timecounter "TSC" frequency 198948158 Hz cost 117 ns CPU: Pentium/P55C (198.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 83886080 (81920K bytes) avail memory = 79097856 (77244K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x02 on pci0.7.1 vga0: rev 0x01 int a irq 10 on pci0.10.0 ncr0: rev 0x03 int a irq 15 on pci0.12.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 scbus0 target 0 lun 0: WIDE SCSI (16 bit) enabledscbus0 target 0 lun 0: 10.0 MB/s (200 ns, offset 15) sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: WIDE SCSI (16 bit) enabled sd0: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) scbus0 target 1 lun 0: WIDE SCSI (16 bit) enabledscbus0 target 1 lun 0: 10.0 MB/s (200 ns, offset 15) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: WIDE SCSI (16 bit) enabled sd1: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) cd0 at scbus0 target 2 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: 10.0 MB/s (100 ns, offset 15) can't get the size st0 at scbus0 target 5 lun 0 st0: type 1 removable SCSI 1 st0: Sequential-Access density code 0x0, drive empty Probing for PnP devices: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 9 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model MouseMan+, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S aic0 at 0x340-0x35f irq 11 on isa aic0: waiting for scsi devices to settle scbus1 at aic0 bus 0 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround ccd0-1: Concatenated disk drivers IP packet filtering initialized, divert disabled, logging limited to 100 packets/entry changing root device to sd0s1a ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated I also noticed something kinda funny up there in the dmesg. See where it reports scbus0 target 0 lun0 as 10.0MB/sec, then says the same device (sd0) is 40.0MB/sec a few lines later? Same with sd1. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 19:23:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05288 for freebsd-current-outgoing; Thu, 9 Jul 1998 19:23:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05279 for ; Thu, 9 Jul 1998 19:23:06 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA28421; Thu, 9 Jul 1998 19:23:04 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd028392; Thu Jul 9 19:23:00 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id TAA10893; Thu, 9 Jul 1998 19:22:56 -0700 (MST) From: Terry Lambert Message-Id: <199807100222.TAA10893@usr09.primenet.com> Subject: Re: Rate limit for system calls to prevent denial of service attacks? To: archie@whistle.com (Archie Cobbs) Date: Fri, 10 Jul 1998 02:22:56 +0000 (GMT) Cc: drosih@rpi.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199807091815.LAA09514@bubba.whistle.com> from "Archie Cobbs" at Jul 9, 98 11:15:28 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why would 100 processes doing > > main(){while(1) getpid();} > > be accounted for any differently than 100 processes doing > > main(){while(1) /* infinite loop in user mode */;} > > ? Or am I misunderstanding something. 1) Accounting is by process. 2) The issue is competition for quantum, and the current scheduler algorithm fails to decrease virtual priorities sufficiently fast if there is a large number of quanta between when you were last scheduled and when you are next scheduled. For the large number of processes that result from "for(;;) { fork(); }", this is a degenerate case for teh scheduling algorithm. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 21:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19948 for freebsd-current-outgoing; Thu, 9 Jul 1998 21:55:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19937 for ; Thu, 9 Jul 1998 21:55:11 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA19584 for ; Thu, 9 Jul 1998 21:55:07 -0700 (PDT) (envelope-from jdp) Message-Id: <199807100455.VAA19584@austin.polstra.com> To: current@FreeBSD.ORG Subject: Does "make -j4 buildworld" actually help anybody? Date: Thu, 09 Jul 1998 21:55:07 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently got what I thought would be a perfect box to take advantage of "make -j4": a PII/400 with 128 MB of RAM. But "-j4" slows things down considerably. Under identical conditions, the timings were: Without -j4: real 47m14.643s user 36m7.531s sys 12m20.942s With -j4: real 55m59.989s user 34m50.985s sys 12m54.567s This is a "make -DNOCLEAN buildworld" with an empty, async-mounted /usr/obj on a different spindle than /usr/src. Have any of you actually measured an improvement from using "-j4"? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 22:45:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23514 for freebsd-current-outgoing; Thu, 9 Jul 1998 22:45:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23509 for ; Thu, 9 Jul 1998 22:45:44 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA26794; Thu, 9 Jul 1998 22:45:43 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807100545.WAA26794@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-reply-to: Your message of "Thu, 09 Jul 1998 13:56:11 PDT." <35A52E6B.6201DD56@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 22:45:42 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sure I am willing to test soft updates however I think -current at the moment is broken: n file included from /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:40, from /usr/src/lib/libc/../libc/gmon/gmon.c:41: /usr/obj/usr/src/tmp/usr/include/machine/profile.h:136: parse error before `from pc' In file included from /usr/src/lib/libc/../libc/gmon/gm Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 23:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27550 for freebsd-current-outgoing; Thu, 9 Jul 1998 23:24:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles356.castles.com [208.214.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27537 for ; Thu, 9 Jul 1998 23:24:05 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA05713; Thu, 9 Jul 1998 22:24:37 -0700 (PDT) Message-Id: <199807100524.WAA05713@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG Subject: Re: Rate limit for system calls to prevent denial of service attacks? In-reply-to: Your message of "Wed, 08 Jul 1998 10:33:28 +0200." <22965.899886808@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Jul 1998 22:24:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following small program: > > main(){while(1) fork();} > > is a very effective denial of service attack against FreeBSD-2.2.6, > despite reasonable defaults in login.conf. The problem is *not* the > number of processes, but the system call rate. It's actually kind of > amazing to follow this with vmstat, and see that the box is suddenly > doing 395000 system calls per second :-) (this is a P-166). 8) > Limiting CPU time per process or user is probably not sufficient, > unless you set it to absurdly small limits. It looks to me like we > need some sort of *rate limiting* for system calls. Anybody looked > at this? There was an interesting paper presented at Usenix this year on system QoS (as opposed to network QoS). You should try chasing the proceedings, as I'm certain that one of the platforms it was developed on was FreeBSD. Needless to say, a module like this would be *very* desirable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 9 23:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28761 for freebsd-current-outgoing; Thu, 9 Jul 1998 23:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28756 for ; Thu, 9 Jul 1998 23:34:17 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA09859; Fri, 10 Jul 1998 16:34:13 +1000 Date: Fri, 10 Jul 1998 16:34:13 +1000 From: Bruce Evans Message-Id: <199807100634.QAA09859@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: Does "make -j4 buildworld" actually help anybody? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I recently got what I thought would be a perfect box to take advantage >of "make -j4": a PII/400 with 128 MB of RAM. But "-j4" slows things >down considerably. Under identical conditions, the timings were: I think it only helps with multiple CPUs and enough disk parallelism to prevent too many extra seeks. >Without -j4: > real 47m14.643s > user 36m7.531s > sys 12m20.942s It is hard to improve on a negative amount of time waiting for the disks :-). I still haven't committed a fix for fork time getting counted twice. Here is a cryptic version: diff -c2 kern_resource.c~ kern_resource.c *** kern_resource.c~ Fri May 29 13:02:39 1998 --- kern_resource.c Fri Jul 10 16:26:57 1998 *************** *** 523,526 **** --- 523,527 ---- */ microuptime(&tv); + switchtime = tv; /* XXX */ totusec += (tv.tv_usec - p->p_switchtime.tv_usec) + (tv.tv_sec - p->p_switchtime.tv_sec) * (int64_t)1000000; Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 00:54:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05126 for freebsd-current-outgoing; Fri, 10 Jul 1998 00:54:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05121 for ; Fri, 10 Jul 1998 00:54:49 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA15228; Fri, 10 Jul 1998 17:54:45 +1000 Date: Fri, 10 Jul 1998 17:54:45 +1000 From: Bruce Evans Message-Id: <199807100754.RAA15228@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, julian@whistle.com Subject: Re: TESTERS NEEDED: Softupdates looks Very good. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Sure I am willing to test soft updates however I think -current >at the moment is broken: > >n file included from /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:40, > from /usr/src/lib/libc/../libc/gmon/gmon.c:41: >/usr/obj/usr/src/tmp/usr/include/machine/profile.h:136: parse error before >`from >pc' >In file included from /usr/src/lib/libc/../libc/gmon/gm I broke it about 4 hours 41 minutes ago, and since freefall has been down for about 4 hours 40 minutes I haven't been able to fix it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 01:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08532 for freebsd-current-outgoing; Fri, 10 Jul 1998 01:29:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08525 for ; Fri, 10 Jul 1998 01:29:53 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA27370; Fri, 10 Jul 1998 18:43:49 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807100843.SAA27370@cimlogic.com.au> Subject: Re: SOLUTION! 2.2.6-Release to -current In-Reply-To: from Matthew Patton at "Jul 8, 98 08:02:49 pm" To: patton@sysnet.net (Matthew Patton) Date: Fri, 10 Jul 1998 18:43:49 +1000 (EST) Cc: tcole@nihilist.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Patton wrote: > To think I went through all this pain just to get a SMP kernel so I can > crack rc5des faster. My word of advice: if you want SMP, save yourself the > hassle and start with a -current snapshot. *whew* *Grumble*. Today I went though the exercise of installing 2.2.6-RELEASE from the CD that WC ships. I booted from the install CD, used the visual thingy to deselect all the hardware I don't have (leaving just ide/fd controllers, par/ser ports, ed0) and did a novice install. I gave it the whole disk (wd0), let it use the default partitions, and selected just the user binaries. I created one group and one user, set the timezone and root password, rebooted, logged in as root, NFS mounted /usr/src from another machine. Then I did exactly as I have been advising people to do: cd /usr/src make -m /usr/src/share/mk world I sat and watched it do the complete build without error. No need to set BINFORMAT or MACHINE_ARCH. No editing /etc/make.conf. No specially installing mk files. No rebuilding just libc. No secret handshake. No rocket science. Just a simple make. Next I built the kernel: cd /usr/src/sys/i386/conf /usr/sbin/config GENERIC cd ../../compile/GENERIC make depend && make all && make install This barfed on vnode_if. The solution to that is to simply repeat the command: make depend && make all && make install The kernel built and installed just like it does on current. I edited /etc/rc to change /usr/lib to /usr/lib/aout, sync; sync; sync'd the disk because all the binaries are now incompatible with the booted kernel (so shutdown etc don't work) and power cycled the machine. It booted, fsck'd the disk and let me log in as root. And now the machine is running 3.0-CURRENT. I'm prepared to concede that people _are_ having problems doing this, but I ask you to consider the possibility that the build process _does_ work as advertised on a clean installation. If you're having difficulty, then it makes more sense to address the issue of what is different between _your_ machine and a clean installation before you go to all lengths to hack a build, only getting into more trouble in the process, and then sending misleading messages to this list yelling that you have the solution. If anyone has a 2.2.6-RELEASE installation (unhacked) that can't build current in this manner, please send me private mail containing the error output you are getting. As I've said before, posting messages stating that "it doesn't work" is not helpful. Let's try to find out what breaks the build in some cases. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 03:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17733 for freebsd-current-outgoing; Fri, 10 Jul 1998 03:14:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17728 for ; Fri, 10 Jul 1998 03:14:21 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id DAA22643; Fri, 10 Jul 1998 03:13:59 -0700 (PDT) Message-Id: <199807101013.DAA22643@mailgate.cadence.com> Received: from unknown(194.32.96.130) by mailgate.cadence.com via smap (mjr-v1.2) id xma900065637.022635; Fri, 10 Jul 98 03:13:57 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: patton@sysnet.net (Matthew Patton), John Birrell Date: Fri, 10 Jul 1998 11:13:36 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: SOLUTION! 2.2.6-Release to -current Reply-to: dmlb@ragnet.demon.co.uk CC: tcole@nihilist.org, freebsd-current@FreeBSD.ORG In-reply-to: <199807100843.SAA27370@cimlogic.com.au> References: from Matthew Patton at "Jul 8, 98 08:02:49 pm" X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthew Patton wrote: > > To think I went through all this pain just to get a SMP kernel so I can > > crack rc5des faster. My word of advice: if you want SMP, save yourself the > > hassle and start with a -current snapshot. *whew* > > *Grumble*. Today I went though the exercise of installing 2.2.6-RELEASE > from the CD that WC ships. I booted from the install CD, used the > visual thingy to deselect all the hardware I don't have (leaving > just ide/fd controllers, par/ser ports, ed0) and did a novice > install. I gave it the whole disk (wd0), let it use the default > partitions, and selected just the user binaries. I created one group > and one user, set the timezone and root password, rebooted, logged > in as root, NFS mounted /usr/src from another machine. Then I did > exactly as I have been advising people to do: > > cd /usr/src > make -m /usr/src/share/mk world > > I sat and watched it do the complete build without error. No need to > set BINFORMAT or MACHINE_ARCH. No editing /etc/make.conf. No > specially installing mk files. No rebuilding just libc. No secret > handshake. No rocket science. Just a simple make. > To echo and reinforce that this works I did the following a couple of weeks ago whilst setting -current up on a spare MB. vanilla 2.2.6 relase from the CDs checked out -current source from CD2 into /bigdisk/current cvsup'd the tree cd /bigdisk/current/src make -m `pwd`/share/mk buildworld make DESTDIR=/smalldisk -m `pwd`/share/mk installworld mkdir -p /smalldisk/usr/src/sys pax'd sys into /smalldisk/usr/sys chroot'd to /smalldisk cd /sys/i386/conf configure GENERIC cd ../../compile/GENERIC make depend make all make install (this is from memory, but the buildworld certainly was done as advertised). I then took out smalldisk from my big machine and put it onto an old 486 MB, and turned it and booted -current. Since then I've done NFS re-installs via PLIP (I have three network cards, at least two are dead :-(). Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 04:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24874 for freebsd-current-outgoing; Fri, 10 Jul 1998 04:11:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24868 for ; Fri, 10 Jul 1998 04:11:18 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id NAA00658 for freebsd-current@freebsd.org; Fri, 10 Jul 1998 13:11:15 +0200 (CEST) From: Holm Tiffe Message-Id: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de> Subject: Arrgh ! resubscribing again again again.... To: freebsd-current@FreeBSD.ORG Date: Fri, 10 Jul 1998 13:11:15 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Could someone please take a look at the long standing problem, with the dying daemons on -current ? This number 6 or 7 of subscribing our lists, because my computer with 32 Mbytes of memory tracks -current and sendmail's childs are getting killed on segfaults when I start netscape or so. Than the mail bounces back, I have to resubscribe our own lists. THX, Holm PS: sorry for my poor english. -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 04:39:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27770 for freebsd-current-outgoing; Fri, 10 Jul 1998 04:39:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27765 for ; Fri, 10 Jul 1998 04:39:17 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id NAA03093 ; Fri, 10 Jul 1998 13:38:40 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id NAA29866; Fri, 10 Jul 1998 13:38:39 +0200 To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <35A52E6B.6201DD56@whistle.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 10 Jul 1998 13:38:38 +0200 In-Reply-To: Julian Elischer's message of Thu, 09 Jul 1998 13:56:11 -0700 Message-ID: Lines: 14 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > We need more testers. specifically to try get a core dump of that panic. OK, I'm setting up a scratch box tonight. If you want something specific tested, or have suggestions on how to reproduce the panic, just say the word... Am I right to assume that failing a news server, 'make world' is the best file system stress test? I might install a repository copy and do a complete 'make release NOPORTS=YES NODOCS=YES' while I'm at it... DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 09:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05822 for freebsd-current-outgoing; Fri, 10 Jul 1998 09:55:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05802 for ; Fri, 10 Jul 1998 09:55:51 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA29491; Fri, 10 Jul 1998 09:55:37 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807101655.JAA29491@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Does "make -j4 buildworld" actually help anybody? In-reply-to: Your message of "Thu, 09 Jul 1998 21:55:07 PDT." <199807100455.VAA19584@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Jul 1998 09:55:37 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What sort of disks do you have ? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 10:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08083 for freebsd-current-outgoing; Fri, 10 Jul 1998 10:11:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08043 for ; Fri, 10 Jul 1998 10:11:20 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id KAA29210; Fri, 10 Jul 1998 10:11:15 -0700 (PDT) (envelope-from jdp) Message-Id: <199807101711.KAA29210@austin.polstra.com> To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Does "make -j4 buildworld" actually help anybody? In-reply-to: Your message of "Fri, 10 Jul 1998 09:55:37 PDT." <199807101655.JAA29491@rah.star-gate.com> Date: Fri, 10 Jul 1998 10:11:15 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What sort of disks do you have ? IBM DDRS-34560W. These are the 4.5 GB version of the so-called Ultrastar 9ES SCSI disks. Justin recommended them to me, and they seem quite fast and nice so far. Though I have a feeling that the shipper dropped the box off of a loading dock somewhere along the line. Of three disks (shipped installed in the system), one was perfect, one had about 20 new defects, and I gave up and sent back the third after correcting more than 60 new defects with no end in sight. The vendor says he tested the system before shipping it, and I choose to believe him. One strange thing is that reformatting the disk from the controller BIOS (AIC-7895) did _not_ remap or avoid the defects. They were still there, and the only way I could get rid of them was one by one using the controller's SCSI verify. The SCSI spec says it's optional to test the media during a reformat, but this is the first disk I've seen that didn't do it. I think I could have crafted a scsi(8) command that would have forced it, but with so many defects I preferred to exchange the disk. Anyway, despite all that, I think they are good disks. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 10:43:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12826 for freebsd-current-outgoing; Fri, 10 Jul 1998 10:43:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12811 for ; Fri, 10 Jul 1998 10:43:04 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id TAA23669; Fri, 10 Jul 1998 19:30:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id TAA04883; Fri, 10 Jul 1998 19:14:59 +0200 (CEST) (envelope-from andreas) Message-ID: <19980710191459.A4449@klemm.gtn.com> Date: Fri, 10 Jul 1998 19:14:59 +0200 From: Andreas Klemm To: Julian Elischer , current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <35A52E6B.6201DD56@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35A52E6B.6201DD56@whistle.com>; from Julian Elischer on Thu, Jul 09, 1998 at 01:56:11PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 09, 1998 at 01:56:11PM -0700, Julian Elischer wrote: [...] > We need more testers. specifically to try get a core dump of that panic. I'm running the latest -current with Softupdates and i4b (isdn) on a SMP board. Never had a crash. But I'll run the debugging kernel in case one happens ... Just wanted to let you know. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 10:52:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14186 for freebsd-current-outgoing; Fri, 10 Jul 1998 10:52:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14181 for ; Fri, 10 Jul 1998 10:52:21 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA12313; Fri, 10 Jul 1998 10:48:29 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd012287; Fri Jul 10 17:48:18 1998 Date: Fri, 10 Jul 1998 10:48:04 -0700 (PDT) From: Julian Elischer To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <19980710191459.A4449@klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. A commit yestaerday fixed one of the known problems. that leases us with only the 'hard to reproduce panic'. I'd say that if people have been hanging back from using soft updates for safety reasons, then it's possibly reached the stage where it's more risk to your filesystem to NOT use soft updates... :-) julian On Fri, 10 Jul 1998, Andreas Klemm wrote: > On Thu, Jul 09, 1998 at 01:56:11PM -0700, Julian Elischer wrote: > [...] > > We need more testers. specifically to try get a core dump of that panic. > > I'm running the latest -current with Softupdates and i4b (isdn) > on a SMP board. Never had a crash. But I'll run the debugging > kernel in case one happens ... > > Just wanted to let you know. > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 13:34:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06880 for freebsd-current-outgoing; Fri, 10 Jul 1998 13:34:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06864 for ; Fri, 10 Jul 1998 13:34:44 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA03087; Fri, 10 Jul 1998 22:30:23 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA21657; Fri, 10 Jul 1998 22:21:25 +0200 (CEST) (envelope-from andreas) Message-ID: <19980710222125.B20745@klemm.gtn.com> Date: Fri, 10 Jul 1998 22:21:25 +0200 From: Andreas Klemm To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <19980710191459.A4449@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Fri, Jul 10, 1998 at 10:48:04AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 10:48:04AM -0700, Julian Elischer wrote: > Thanks. A commit yestaerday fixed one of the known problems. > that leases us with only the 'hard to reproduce panic'. Ah, fine ! > I'd say that if people have been hanging back from using soft updates for > safety reasons, then it's possibly reached the stage where it's more risk > to your filesystem to NOT use soft updates... :-) Well argued ;-) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 13:40:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08036 for freebsd-current-outgoing; Fri, 10 Jul 1998 13:40:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07988 for ; Fri, 10 Jul 1998 13:40:07 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA08992 for ; Fri, 10 Jul 1998 13:21:25 -0400 (EDT) Date: Fri, 10 Jul 1998 13:21:25 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: xmix now bombs out, any ideas? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a make world and kernel rebuild the other day, I can no longer run xmix: supported = 0x31ff X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 3 (X_GetWindowAttributes) Serial number of failed request: 1319 Current serial number in output stream: 1690 Can some X guru tell me what this means, please? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 13:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08080 for freebsd-current-outgoing; Fri, 10 Jul 1998 13:40:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08006 for ; Fri, 10 Jul 1998 13:40:12 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA13821; Fri, 10 Jul 1998 13:39:44 -0400 (EDT) Date: Fri, 10 Jul 1998 13:39:44 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: John Birrell cc: Matthew Patton , tcole@nihilist.org, freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current In-Reply-To: <199807100843.SAA27370@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Jul 1998, John Birrell wrote: > If you're having difficulty, then it makes more sense to address the > issue of what is different between _your_ machine and a clean > installation before you go to all lengths to hack a build, only > getting into more trouble in the process, and then sending misleading > messages to this list yelling that you have the solution. I have a 2.2.6-stable system as of last week or so. I cvsup'd 3.0 source and ran the make with the arguments you gave, but the build died in libc: In file included from /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:40, from /usr/src/lib/libc/../libc/gmon/gmon.c:41: /usr/obj/usr/src/tmp/usr/include/machine/profile.h:136: parse error before `frompc' In file included from /usr/src/lib/libc/../libc/gmon/gmon.c:41: /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: parse error before `fptrint_t' /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: warning: no semicolon at end of struct or union This was followed by several screens' worth of similar error output, and then the build stopped. Any ideas what I should do to remedy this? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 13:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09020 for freebsd-current-outgoing; Fri, 10 Jul 1998 13:43:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08932 for ; Fri, 10 Jul 1998 13:42:51 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id EAA26997; Fri, 10 Jul 1998 04:45:49 -0400 (EDT) (envelope-from mark) Message-ID: <19980710044549.A26780@vmunix.com> Date: Fri, 10 Jul 1998 04:45:49 -0400 From: Mark Mayo To: Archie Cobbs , Garance A Drosihn Cc: freebsd-current@FreeBSD.ORG Subject: Re: Rate limit for system calls to prevent denial of service attacks? References: <199807091815.LAA09514@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807091815.LAA09514@bubba.whistle.com>; from Archie Cobbs on Thu, Jul 09, 1998 at 11:15:28AM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 09, 1998 at 11:15:28AM -0700, Archie Cobbs wrote: > Garance A Drosihn writes: > > >>The following small program: > > >> > > >> main(){while(1) fork();} > > >> > > >> is a very effective denial of service attack against FreeBSD-2.2.6, > > >> despite reasonable defaults in login.conf. The problem is *not* the > > >> number of processes, but the system call rate. It's actually kind of > > >> amazing to follow this with vmstat, and see that the box is suddenly > > >> doing 395000 system calls per second :-) (this is a P-166). > > > > The subject of this thread asks about adding a rate-limit for > > system calls. I don't think that's a good idea, but I would like > > to see some kind of throttling of calls to fork() in particular. > > Why would 100 processes doing > > main(){while(1) getpid();} > > be accounted for any differently than 100 processes doing > > main(){while(1) /* infinite loop in user mode */;} Well, in my short test, while doing while(1) fork(); my mpg123 player basically stopped - a few short cracks and squawks here and there. Login.conf was limiting me to 64 processes, and although I could still type, that's about it. :-) Syscall rate approached 700,000/sec for a short time, then fell back to about 340,000/sec. while(1) getpid(); basically had no effect on my mp3 player, and I was able to run netscape, etc. Still about 380,000 syscalls per second, but context switches per second were about 300, as opposed to 40/sec during the fork() loop. So forking definately seems to be worse in terms of denial of service type attacks.. I'm not qualified to comment on why.. :-) I would assume scheduling that rapidly would be a source of problems. System was 3.0-CURRENT/June-10 on a PPro 200. -Mark > > ? Or am I misunderstanding something. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 14:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15785 for freebsd-current-outgoing; Fri, 10 Jul 1998 14:05:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15774 for ; Fri, 10 Jul 1998 14:05:09 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA03164; Sat, 11 Jul 1998 07:19:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807102119.HAA03164@cimlogic.com.au> Subject: Re: SOLUTION! 2.2.6-Release to -current In-Reply-To: from Snob Art Genre at "Jul 10, 98 01:39:44 pm" To: ben@rosengart.com Date: Sat, 11 Jul 1998 07:19:30 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > I have a 2.2.6-stable system as of last week or so. I cvsup'd 3.0 > source and ran the make with the arguments you gave, but the build died > in libc: > > In file included from /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:40, > from /usr/src/lib/libc/../libc/gmon/gmon.c:41: > /usr/obj/usr/src/tmp/usr/include/machine/profile.h:136: parse error > before `frompc' > In file included from /usr/src/lib/libc/../libc/gmon/gmon.c:41: > /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: parse error before > `fptrint_t' > /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: warning: no semicolon > at end of struct or union > > This was followed by several screens' worth of similar error output, and > then the build stopped. Any ideas what I should do to remedy this? I think you got caught in the middle of Bruce's changes. Another CVSup. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 15:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28896 for freebsd-current-outgoing; Fri, 10 Jul 1998 15:16:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28873 for ; Fri, 10 Jul 1998 15:16:16 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id AAA19624 for current@FreeBSD.ORG; Sat, 11 Jul 1998 00:16:04 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id XAA06708 for current@FreeBSD.ORG; Fri, 10 Jul 1998 23:55:29 +0200 (CEST) (envelope-from roberto) Message-ID: <19980710235529.A6695@keltia.freenix.fr> Date: Fri, 10 Jul 1998 23:55:29 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. Mail-Followup-To: current@FreeBSD.ORG References: <35A52E6B.6201DD56@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.92.14i In-Reply-To: =?iso-8859-1?Q?=3Crx4lnq2x7ep=2Efsf=40oslo=2Egeco-prakla=2Eslb=2Ecom=3E?= =?iso-8859-1?Q?=3B_from_Dag-Erling_Coidan_Sm=F8rgrav_on_Fri=2C_Jul_10=2C?= =?iso-8859-1?Q?_1998_at_01:38:38PM_+0200?= X-Operating-System: FreeBSD 3.0-CURRENT ctm#4419 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dag-Erling Coidan Smørgrav: > Am I right to assume that failing a news server, 'make world' is the > best file system stress test? I might install a repository copy and do > a complete 'make release NOPORTS=YES NODOCS=YES' while I'm at it... "make buildworld" should succeed without problem. Now, "make installworld" is another matter and what was failing up to now. I'll test the new version soon. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #11: Sat Jun 27 00:41:06 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 15:26:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00647 for freebsd-current-outgoing; Fri, 10 Jul 1998 15:26:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00632 for ; Fri, 10 Jul 1998 15:26:53 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id SAA10620; Fri, 10 Jul 1998 18:19:47 -0400 (EDT) Date: Fri, 10 Jul 1998 18:26:41 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: ben@rosengart.com cc: John Birrell , freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Jul 1998, Snob Art Genre wrote: > I have a 2.2.6-stable system as of last week or so. I cvsup'd 3.0 > source and ran the make with the arguments you gave, but the build died > in libc: > > In file included from /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:40, > from /usr/src/lib/libc/../libc/gmon/gmon.c:41: > /usr/obj/usr/src/tmp/usr/include/machine/profile.h:136: parse error > before `frompc' > In file included from /usr/src/lib/libc/../libc/gmon/gmon.c:41: > /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: parse error before > `fptrint_t' > /usr/obj/usr/src/tmp/usr/include/sys/gmon.h:168: warning: no semicolon > at end of struct or union No need for john to reply, bruce broke this like 41 hours ago and freefall went down 40 hours ago before he could get a fix in. It should be commited now and be ready for you to grab with cvsup. And everything should build fine again. Or words to that effect. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 15:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05974 for freebsd-current-outgoing; Fri, 10 Jul 1998 15:53:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05894 for ; Fri, 10 Jul 1998 15:52:43 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id AAA11283; Sat, 11 Jul 1998 00:45:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id AAA22846; Sat, 11 Jul 1998 00:09:57 +0200 (CEST) (envelope-from andreas) Message-ID: <19980711000956.A21101@klemm.gtn.com> Date: Sat, 11 Jul 1998 00:09:56 +0200 From: Andreas Klemm To: Holm Tiffe , freebsd-current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... References: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Fri, Jul 10, 1998 at 01:11:15PM +0200 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 01:11:15PM +0200, Holm Tiffe wrote: > Hi, > Could someone please take a look at the long standing > problem, with the dying daemons on -current ? No daemons dying here. Which version (date) of -current do you use ? Might that be a hardware related thing ? What hardware are you using ? What kernel config file ? > This number 6 or 7 of subscribing our lists, because > my computer with 32 Mbytes of memory tracks -current > and sendmail's childs are getting killed on segfaults > when I start netscape or so. ??? > Than the mail bounces back, I have to resubscribe our > own lists. What does a dying daemon have to do with subscribing to a list (aliases file, majordomo ???). > sorry for my poor english. Don't understand your problem, sorry. Please explain more verbose. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 16:12:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09381 for freebsd-current-outgoing; Fri, 10 Jul 1998 16:12:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09300; Fri, 10 Jul 1998 16:11:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA25371; Fri, 10 Jul 1998 16:03:05 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd025366; Fri Jul 10 23:02:55 1998 Date: Fri, 10 Jul 1998 16:02:51 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: -current buildworld broken by libc/gmon.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/gmon/gmon.c -o gmon.o In file included from /usr/include/sys/gmon.h:40, from /usr/src/lib/libc/../libc/gmon/gmon.c:41: /usr/include/machine/profile.h:136: parse error before `frompc' In file included from /usr/src/lib/libc/../libc/gmon/gmon.c:41: /usr/include/sys/gmon.h:168: parse error before `fptrint_t' /usr/include/sys/gmon.h:168: warning: no semicolon at end of struct or union /usr/include/sys/gmon.h:169: warning: data definition has no type or storage class /usr/include/sys/gmon.h:183: parse error before `}' /usr/src/lib/libc/../libc/gmon/gmon.c:54: variable `_gmonparam' has initializer but incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:54: warning: excess elements in struct initializer after `_gmonparam' /usr/src/lib/libc/../libc/gmon/gmon.c: In function `monstartup': /usr/src/lib/libc/../libc/gmon/gmon.c:78: dereferencing pointer to incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:79: dereferencing pointer to incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:80: dereferencing pointer to incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:80: dereferencing pointer to incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:80: dereferencing pointer to incomplete type /usr/src/lib/libc/../libc/gmon/gmon.c:81: dereferencing pointer to incomplete type ---etc---- fptrint_t is now dependent on the definition KERNEL being true. I just removed the Ifdef KERNEL in i386/include/types.h is there a better answer? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 16:51:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16363 for freebsd-current-outgoing; Fri, 10 Jul 1998 16:51:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA16337 for ; Fri, 10 Jul 1998 16:50:59 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA23827 for current@freebsd.org; Fri, 10 Jul 1998 19:54:09 -0400 From: Bill Paul Message-Id: <199807102354.TAA23827@skynet.ctr.columbia.edu> Subject: Device driver weirdness To: current@FreeBSD.ORG Date: Fri, 10 Jul 1998 19:54:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question for other driver developers writing/maintaining things for -current. I've been trying to track down a problem I've been having with the ThunderLAN driver and today I finally found it, but I'm not sure how to fix it. The problem seems to manifest itself mostly when running at 10Mb/s mode. Here's how I reproduce it: - system is a Compaq Deskpro 4000 or Proliant server with embedded ThunderLAN chip, 64MB RAM, Pentium Pro 300Mhz CPU with 512K cache - connect system to 10Mb/s network or otherwise force the chip to work at 10Mb/s, half-duplex - run ping -f some.machine.on.local.net - While the first ping -f is running, start another ping -f to the same host (on another virtual console) The first ping -f, if left alone, goes on about its way without any problems, until you start the second ping -f. After a few seconds, the chip generates an adapter check interrupt with a status code indicating that either EOF interrupts are being underserviced or a TX-GO command was issued before an outstanting TXEOC interrupt was acknowledged. Once an adapter check interrupt hits, you have to reset the chip. Basically, the chip is complaining that EOF or EOC interrupts aren't being acknowledged. It turns out that the reason this happens is that I wrote the driver to use memory mapped I/O. PCI devices can be accessed using either programmed I/O or memory mapped I/O. In PIO mode, you have to use inb/outb and friends and go through the I/O ports returned by the PCI autoconfig. With MMIO, the chip's registers are mapped into the system's memory and you access them simply by reading or writing to the right memory addresses. The problem, I think, is the cache. Interrupts are acknowledged by writing an ACK command (and some other info) to the ThunderLAN's host command register, which is 32 bits wide. In order for this to work, the 32-bit word has to be written out to main memory rather than getting written to the cache and then flushed out to memory later, otherwise it might happen that the interrupt acknowledge command is delayed long enough for the driver to do something else that it isn't supposed to do until after the ack has been sent. For the moment, I've fixed this by changing code like this: csr->tl_host_cmd = TL_CMD_ACK; to this: CMD_PUT(csr, TL_CMD_ACK); where CMD_PUT() is a macro that looks like this: #define CMD_PUT(c, x) { \ u_int32_t f; \ c->tl_host_cmd = (u_int32_t)x;\ f = c->tl_host_cmd; \ } The macro basically reads back the command register after it's been written. This seems to defeat the cache and forces the interrupt acknowledgement to be written out. What I don't understand is why I have to do this. I have declared the csr structure like this: struct tl_csr { volatile u_int32_t tl_host_cmd; volatile u_int32_t tl_ch_parm; volatile u_int16_t tl_dio_addr; volatile u_int16_t tl_host_int; union { volatile u_int32_t tl_dio_data; volatile struct tl_regwords tl_dio_words; volatile struct tl_regbytes tl_dio_bytes; } u; }; I was under the impression that the volatile keyword was supposed to help avoid this problem, but even with 'volatile' in there I still need to use the macros to force the cache flush in order for commands to be written to the chip on time. I had the same problem with the code that read the EEPROM and used the same macro workaround, but I stupidly forgot the lesson I'd learned and didn't think I might have the same problem with the other registers. The two other ThunderLAN drivers I've seen (one from Linux and one from NetBSD) both use programmed I/O. Consequently, they don't have these problems. I thought I'd be clever by using memory mapped I/O, and naturally Murphy just had to zonk me for it. Can anybody tell me the 'politically correct' way to work around this problem? I'm prepared to update the code to use the macro hack, but I want to see if there's a better way first. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 16:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16568 for freebsd-current-outgoing; Fri, 10 Jul 1998 16:52:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16453; Fri, 10 Jul 1998 16:51:51 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA28777; Sat, 11 Jul 1998 09:51:47 +1000 Date: Sat, 11 Jul 1998 09:51:47 +1000 From: Bruce Evans Message-Id: <199807102351.JAA28777@godzilla.zeta.org.au> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: -current buildworld broken by libc/gmon.. Cc: bde@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >/usr/src/lib/libc/../libc/gmon/gmon.c:81: dereferencing pointer to >incomplete type > >---etc---- > >fptrint_t is now dependent on the definition KERNEL being true. > >I just removed the Ifdef KERNEL >in i386/include/types.h > >is there a better answer? Fetch a new version. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 17:41:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28698 for freebsd-current-outgoing; Fri, 10 Jul 1998 17:41:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28651 for ; Fri, 10 Jul 1998 17:41:35 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id UAA27049; Fri, 10 Jul 1998 20:41:14 -0400 (EDT) Date: Fri, 10 Jul 1998 20:41:13 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Open Systems Networking cc: ben@rosengart.com, John Birrell , freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Jul 1998, Open Systems Networking wrote: > No need for john to reply, bruce broke this like 41 hours ago and freefall > went down 40 hours ago before he could get a fix in. It should be commited > now and be ready for you to grab with cvsup. And everything should build > fine again. Or words to that effect. Yep, and please accept my apologies. I saw the damn message from Bruce about freefall going down, but I didn't make the connection. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 19:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14244 for freebsd-current-outgoing; Fri, 10 Jul 1998 19:48:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bleep.ishiboo.com (user7365@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA14238 for ; Fri, 10 Jul 1998 19:48:34 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 19132 invoked by uid 1000); 11 Jul 1998 02:48:31 -0000 Message-ID: <19980710224831.60505@bleep.ishiboo.com> Date: Fri, 10 Jul 1998 22:48:31 -0400 From: Danny Dulai To: Julian Elischer Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <19980710191459.A4449@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Julian Elischer on Fri, Jul 10, 1998 at 10:48:04AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Julian Elischer (julian@whistle.com): > Thanks. A commit yestaerday fixed one of the known problems. > that leases us with only the 'hard to reproduce panic'. > > I'd say that if people have been hanging back from using soft updates for > safety reasons, then it's possibly reached the stage where it's more risk > to your filesystem to NOT use soft updates... :-) SMP included? -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 19:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15276 for freebsd-current-outgoing; Fri, 10 Jul 1998 19:56:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from weevil.nac.net (elite.weevil.net [207.99.6.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15270 for ; Fri, 10 Jul 1998 19:56:48 -0700 (PDT) (envelope-from afn@weevil.net) Received: from localhost (afn@localhost) by weevil.nac.net (8.8.8/8.8.8) with SMTP id WAA03612 for ; Fri, 10 Jul 1998 22:57:27 -0400 (EDT) (envelope-from afn@weevil.net) Date: Fri, 10 Jul 1998 22:57:27 -0400 (EDT) From: Antal Novak X-Sender: afn@weevil.nac.net To: freebsd-current@FreeBSD.ORG Subject: Bug in Netatalk! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops... typo in src/sys/netatalk/ddp_output.h in the current CVS version: Line 188: elh->el_dnode = gate->sat_addr.s_node; Should be: elh->el_dnode = gate.sat_addr.s_node; (gate is defined at line 108 as:) struct sockaddr_at gate; PS I'm not on the freebsd-current list (I'm on too many mailing lists as it is, being a KDE and SANE developer among other things!) so please send any relevant replies to me, as well as to the list. Antal Novak Weevil Systems Programming Enterprises afn@weevil.net http://www.weevil.net "It took only 6 days for God to make world; Why is it taking me twice as long in FreeBSD?" from #FreeBSD I searched for my Soul, but found it nowhere... I searched for God, but found him nowhere... I searched for my Brother, and found all Three. Ancient Chinese Proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 20:18:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17254 for freebsd-current-outgoing; Fri, 10 Jul 1998 20:18:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17249 for ; Fri, 10 Jul 1998 20:18:19 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA03126; Fri, 10 Jul 1998 20:13:57 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003124; Sat Jul 11 03:13:49 1998 Date: Fri, 10 Jul 1998 20:13:46 -0700 (PDT) From: Julian Elischer To: Danny Dulai cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <19980710224831.60505@bleep.ishiboo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would appear so. julian On Fri, 10 Jul 1998, Danny Dulai wrote: > Quoting Julian Elischer (julian@whistle.com): > > Thanks. A commit yestaerday fixed one of the known problems. > > that leases us with only the 'hard to reproduce panic'. > > > > I'd say that if people have been hanging back from using soft updates for > > safety reasons, then it's possibly reached the stage where it's more risk > > to your filesystem to NOT use soft updates... :-) > > SMP included? > > -- > ___________________________________________________________________________ > Danny Dulai Feet. Pumice. Lotion. > http://www.ishiboo.com/~nirva/ nirva@ishiboo.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 21:36:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24293 for freebsd-current-outgoing; Fri, 10 Jul 1998 21:36:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24282 for ; Fri, 10 Jul 1998 21:36:15 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id MAA08117 for ; Sat, 11 Jul 1998 12:35:13 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id MAA25621; Sat, 11 Jul 1998 12:35:39 +0800 Message-Id: <199807110435.MAA25621@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Other sites to ftp cvs-cur.????.gz from? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Jul 1998 12:35:39 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ftp.freebsd.org's /pub/FreeBSD/CTM/cvs-cur area hasn't been updated for quite some time. Does anyone know the location of a site which is archiving this, or (the preferred option) can someone please fix the problem of ftp.freebsd.org? Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 10 22:56:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00418 for freebsd-current-outgoing; Fri, 10 Jul 1998 22:56:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@spain-26.ppp.hooked.net [206.169.228.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00413 for ; Fri, 10 Jul 1998 22:56:15 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id WAA00758; Fri, 10 Jul 1998 22:57:18 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 10 Jul 1998 22:57:18 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Julian Elischer cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Jul 1998, Julian Elischer wrote: > Thanks. A commit yestaerday fixed one of the known problems. > that leases us with only the 'hard to reproduce panic'. > > I'd say that if people have been hanging back from using soft updates for > safety reasons, then it's possibly reached the stage where it's more risk > to your filesystem to NOT use soft updates... :-) What about on root filesystems? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 00:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06075 for freebsd-current-outgoing; Sat, 11 Jul 1998 00:11:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06068 for ; Sat, 11 Jul 1998 00:11:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA16672; Sat, 11 Jul 1998 17:11:09 +1000 Date: Sat, 11 Jul 1998 17:11:09 +1000 From: Bruce Evans Message-Id: <199807110711.RAA16672@godzilla.zeta.org.au> To: current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: Other sites to ftp cvs-cur.????.gz from? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >ftp.freebsd.org's /pub/FreeBSD/CTM/cvs-cur area hasn't been updated for quite >some time. Does anyone know the location of a site which is archiving this, or >(the preferred option) can someone please fix the problem of ftp.freebsd.org? ftp.uni-trier.de has always seemed to have a much more reliable cvs-cur collection than ftp.freebsd.org. Brue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 01:21:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10909 for freebsd-current-outgoing; Sat, 11 Jul 1998 01:21:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10904 for ; Sat, 11 Jul 1998 01:20:57 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id KAA04937 for freebsd-current@freebsd.org; Sat, 11 Jul 1998 10:20:56 +0200 (CEST) From: Holm Tiffe Message-Id: <199807110820.KAA04937@magnet.geophysik.tu-freiberg.de> Subject: Re: Arrgh ! resubscribing again again again.... (fwd) To: freebsd-current@FreeBSD.ORG Date: Sat, 11 Jul 1998 10:20:55 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Forwarded message from freebsd ----- >From freebsd Sat Jul 11 10:18:01 1998 Subject: Re: Arrgh ! resubscribing again again again.... In-Reply-To: <19980711000956.A21101@klemm.gtn.com> from Andreas Klemm at "Jul 11, 98 00:09:56 am" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sat, 11 Jul 1998 10:18:01 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] Content-Length: 10208 > On Fri, Jul 10, 1998 at 01:11:15PM +0200, Holm Tiffe wrote: > > Hi, > > Could someone please take a look at the long standing > > problem, with the dying daemons on -current ? > > No daemons dying here. Which version (date) of -current do > you use ? Might that be a hardware related thing ? > > What hardware are you using ? > What kernel config file ? This problem in the VM Subsystem persists since around mid of January 1998 and ther was already a thread on this lists about "dying daemons". Here an example what happens: (a little old now, but unchanged behavior on a current -current) Jun 3 13:41:28 magnet /kernel: npx0: INT 16 interface Jun 3 13:41:28 magnet named[74]: starting. named 8.1.2-T3B Tue Jun 2 11:30:43 CEST 1998 root@red-bul l.geophysik.tu-freiberg.de:/usr/obj/usr/src/usr.sbin/named Jun 3 13:41:31 magnet named[75]: Ready to answer queries. Jun 3 13:41:34 magnet amd[112]: NIS domain name is not set. NIS ignored. Jun 3 13:41:38 magnet lpd[135]: restarted Jun 3 14:13:33 magnet su: holm to root on /dev/ttyp3 Jun 3 14:13:58 magnet su: holm to root on /dev/ttyp3 Jun 3 14:15:28 magnet su: holm to root on /dev/ttyp1 Jun 3 16:10:20 magnet /kernel: swap_pager: suggest more swap space: 61 MB ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This comes from starting netscape 4.05 and now: Jun 3 16:12:17 magnet su: holm to root on /dev/ttyp3 Jun 3 16:15:10 magnet su: holm to freebsd on /dev/ttyp2 Jun 3 16:31:43 magnet /kernel: pid 3385 (sendmail), uid 0: exited on signal 11 This is what I mean ! Because I know that problem for long, the next action is killing sendmail and restarting it per hand: Jun 3 16:36:20 magnet su: holm to root on /dev/ttyp2 Jun 3 16:38:11 magnet sendmail[4980]: NOQUEUE: SYSERR(root): opendaemonsocket: cannot bind: Address already in use Jun 3 16:38:11 magnet sendmail[4980]: problem creating SMTP socket Jun 3 16:38:16 magnet sendmail[4980]: NOQUEUE: SYSERR(root): opendaemonsocket: cannot bind: Address already ... but this is normal. Like this problem I have problems with inetd too, telnetd is claiming about junk pointer to low etc. All this after starting navigator4.05. This machine waits for an upgrade next time. It is a 486DX2/80 with 32Mbyte RAM, and tracks -current since 2.0.0. ###################################################### dmesg output here: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #6: Fri Jul 10 14:13:28 CEST 1998 root@red-bull.geophysik.tu-freiberg.de:/usr/src/sys/compile/MAGNET Timecounter "i8254" frequency 1193182 Hz cost 6501 ns CPU: i486DX (486-class CPU) real memory = 33554432 (32768K bytes) avail memory = 30785536 (30064K bytes) eisa0: Probing for devices on the EISA bus ahc0: at 0x3c00-0x3cff irq 11 on eisa0 slot 3 ahc0: aic7770 <= Rev C, Twin Channel, A SCSI Id=7, B SCSI Id=7, 4 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 995MB (2039283 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 2151MB (4406960 512 byte sectors) cd0 at scbus0 target 4 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [303846 x 2048 byte records] st1 at scbus0 target 5 lun 0 st1: type 1 removable SCSI 2 st1: Sequential-Access density code 0x13, variable blocks, write-enabled ahc0: waiting for scsi devices to settle scbus1 at ahc0 bus 1 st0 at scbus1 target 3 lun 0 st0: type 1 removable SCSI 1 st0: Sequential-Access density code 0x10, drive empty 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 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:90:69:63, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio4 at 0x2a0-0x2a7 flags 0x781 on isa sio4: type 16550A (multiport) sio5 at 0x2a8-0x2af flags 0x781 on isa sio5: type 16550A (multiport) sio6 at 0x2b0-0x2b7 flags 0x781 on isa sio6: type 16550A (multiport) sio7 at 0x2b8-0x2bf irq 5 flags 0x781 on isa sio7: type 16550A (multiport master) 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 fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface changing root device to sd0s1a ###################################################### $ swapinfo Device 1024-blocks Used Avail Capacity Type /dev/sd0s1b 65536 29392 36016 45% Interleaved $ ###################################################### Kernel config: # # MAGNET # # # machine "i386" cpu "I486_CPU" ident MAGNET maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options KTRACE options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAX=16777216" options "SHMSEG=32" options "SHMMNI=128" options "SHMALL=4096" options COM_MULTIPORT config kernel root on sd0 controller isa0 controller eisa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # A single entry for any of these controllers (ncr, ahb, ahc) is sufficient # for any number of installed devices. controller ahc0 controller scbus0 at ahc0 bus 0 controller scbus1 at ahc0 bus 1 device sd0 at scbus0 target 0 #device sd1 at scbus0 target 2 #device sd2 at scbus1 target 2 device st0 at scbus1 target 3 device st1 at scbus0 target 5 #device cd0 at scbus0 target 4 device od0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? port "IO_COM3" tty irq 9 vector siointr #device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr # AST-4 Port device sio4 at isa? port 0x2a0 tty flags 0x781 device sio5 at isa? port 0x2a8 tty flags 0x781 device sio6 at isa? port 0x2b0 tty flags 0x781 device sio7 at isa? port 0x2b8 tty flags 0x781 irq5 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device lpt2 at isa? port? tty # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 # keep this if you want to be able to continue to use /stand/sysinstall pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 #Berkeley packet-filter pseudo-device vn 2 ################################################################ > > > This number 6 or 7 of subscribing our lists, because > > my computer with 32 Mbytes of memory tracks -current > > and sendmail's childs are getting killed on segfaults > > when I start netscape or so. > > ??? > > > Than the mail bounces back, I have to resubscribe our > > own lists. > > What does a dying daemon have to do with subscribing to > a list (aliases file, majordomo ???). The problem occours on weekends and holydays, when I'm away from that host for several days and forgot to restart sendmail. > > > sorry for my poor english. > this belives actual! Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* ----- End of forwarded message from freebsd ----- -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 01:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13266 for freebsd-current-outgoing; Sat, 11 Jul 1998 01:51:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13261 for ; Sat, 11 Jul 1998 01:51:39 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA01739; Sat, 11 Jul 1998 01:51:27 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807110851.BAA01739@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Holm Tiffe cc: freebsd-current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... (fwd) In-reply-to: Your message of "Sat, 11 Jul 1998 10:20:55 +0200." <199807110820.KAA04937@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Jul 1998 01:51:27 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are not the only experiencing this problem something seems to triggger the dying daemon problem over here. I just updated my systems today and will be happy to report if the problem still with us. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 02:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14319 for freebsd-current-outgoing; Sat, 11 Jul 1998 02:05:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14302 for ; Sat, 11 Jul 1998 02:05:30 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA29853; Sat, 11 Jul 1998 02:05:29 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd029842; Sat Jul 11 02:05:27 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id CAA16491; Sat, 11 Jul 1998 02:05:26 -0700 (MST) From: Terry Lambert Message-Id: <199807110905.CAA16491@usr08.primenet.com> Subject: Re: Device driver weirdness To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sat, 11 Jul 1998 09:05:26 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199807102354.TAA23827@skynet.ctr.columbia.edu> from "Bill Paul" at Jul 10, 98 07:54:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The macro basically reads back the command register after it's been > written. This seems to defeat the cache and forces the interrupt > acknowledgement to be written out. > > What I don't understand is why I have to do this. I have declared > the csr structure like this: [ ... major use of "volatile" keyword ... ] > I was under the impression that the volatile keyword was supposed to > help avoid this problem, but even with 'volatile' in there I still need > to use the macros to force the cache flush in order for commands to > be written to the chip on time. I had the same problem with the code > that read the EEPROM and used the same macro workaround, but I stupidly > forgot the lesson I'd learned and didn't think I might have the same > problem with the other registers. The "volatile" keyword indicates something that might have changed since the last time it was accessed, and thus should not be optimied into a cached reference (ie: in a register) instead of a memory reference. In general, it refers to disabling the class of optimizations permitted by ANSI C when assuming that there is a single program counter context executing in a region of code, and that there will not be an async escape to a seperate context, with a subsequent return to the original. This is very different from affecting cached values that are cached inn an L1 or L2 cache, not auto variables cached in a register. To resolve this issue, you will need to mark the memory region non-cacheable, and if you are running an older IBM or Cyrix processor (pre the "Blue Lightning" chipmask), you will either need to disable the CPU cache or explicitly call BINVD on the memory address range in question after notification that the I/O has completed (since these processors do not honor the "noncacheable" bit). For your use, you will need to mark the memory in the ack region as non-cacheable. You can either mark all the memory non-cacheable, which may impact performance if you reference it directly, multiple times, from the driver, or you can butt a page up against the area and mark the page prior as non-cacheable. Most liely, you should explicitly call BINVD on the region in question, or use the hack you are currently using to force the cache invalidation. Since your current hack relies a bit on chip architecture (much like BSD's DELAY() macro does), you should probably use BINVD to force the flush of the cache contents (since the cache is write-through), or disable the cache for the relevent page(s) -- or both, if you want it to work with older processors. There are write cache effects in the I/O address space as well, but they can be defeated with read-after-write (see the Linux DELAY() macro, and compare and contrast it to the FreeBSD version of the macro; this is why some keyboards still lock up with FreeBSD console drivers when LED changes are occurring). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 02:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15874 for freebsd-current-outgoing; Sat, 11 Jul 1998 02:25:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15869 for ; Sat, 11 Jul 1998 02:25:20 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA02320 for ; Sat, 11 Jul 1998 02:25:19 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd002309; Sat Jul 11 02:25:11 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id CAA16987 for current@freebsd.org; Sat, 11 Jul 1998 02:25:11 -0700 (MST) From: Terry Lambert Message-Id: <199807110925.CAA16987@usr08.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: current@FreeBSD.ORG Date: Sat, 11 Jul 1998 09:25:11 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This problem in the VM Subsystem persists since around mid of January > 1998 and ther was already a thread on this lists about "dying daemons". [ ... ] > Jun 3 16:10:20 magnet /kernel: swap_pager: suggest more swap space: 61 MB > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This comes from starting netscape 4.05 > > and now: > > Jun 3 16:12:17 magnet su: holm to root on /dev/ttyp3 > Jun 3 16:15:10 magnet su: holm to freebsd on /dev/ttyp2 > Jun 3 16:31:43 magnet /kernel: pid 3385 (sendmail), uid 0: exited on signal 11 > > This is what I mean ! This is normal. FreeBSD VM uses a memory overcommit architecture. This means data pages are marked "copy on write" and pulled from the swap store (in this case, the vnode) until such time as a write occurs. When a write to the page occurs, it becomes "dirty", and the page is copied as a result of a write fault. When no backing pages exist (becaues you've used them all up and are out of swap space), the process requesting the page as a result of the copy on write fault can not have its request satisfied. The result of an unsatified fault request is a SIGSEGV, or signal 11; this is because the page you are writing does not exist (since the system was unable to allocate it on your behalf; like dereferencing a NULL pointer, it means "the page you tried to write/read can not be written/read"). This is a normal result of not reserving all possible memory a program needs when the program is invoked (which, if it failed, would give an "out of resources error" to the fork(2) call or execve(2) call, instead). The problem is complicated by the fact that programs which use malloc(3) call sbrk(2) to increase their heap, and stack depth increases can result in similar needs for pages, even if the data pages were committed up front. This means that to totally solve the problem, you would have to commit real pages in swap or system memory not only for the data pages that may be written that you know about, but that the programmer would also need to estimate the number of additional pages that the program will ever need for dynamically allocated data space and/or stack, and get backing store (in real or virtual memeory) for those, as well. Not only is this impractical (because of the way the FreeBSD libraries are programmed), most programmers who were taught on or after about 1982 simply don't know how to make this calculation; they were never taught the concept that it was possible for there to be a system where memory wasn't "free". The general fix for this problem is to provide more than sufficient swap space for the system as a whole, and then use "limit" (or login.conf) to limit the portion of that space which can be consumed by a single process. Done correctly, this will result in your Netscape process or X11 server failing from hitting the soft limit before the system starts failing from hitting the hard limit. Of course, many times, the soft limit is set higher than the hard limit by people annoyed by login.conf, and who simply do not understand the consequences of their actions. Per the memory leak in Netscape: when you start your X11 server, if you disable the shared memory extensions, or you run your Netscape from a machine other than the one you are running the X server on (which will prevent it from using the shared memory extensions, which can only be used by local X11 programs), then you should see the memory leak go away. This is the only documented (ie: "proven") workaround for this problem at this time, short of setting soft limits that will cause Netscape and/or X11 to fail spectacularly. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 02:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16687 for freebsd-current-outgoing; Sat, 11 Jul 1998 02:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16680 for ; Sat, 11 Jul 1998 02:34:14 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id MAA12578 for ; Sat, 11 Jul 1998 12:34:08 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id MAA25949 for current@freebsd.org; Sat, 11 Jul 1998 12:32:07 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id MAA12629; Sat, 11 Jul 1998 12:21:09 +0300 (EEST) (envelope-from archer) Date: Sat, 11 Jul 1998 12:21:09 +0300 (EEST) From: Alexander Litvin Message-Id: <199807110921.MAA12629@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. X-Newsgroups: grape.freebsd.current In-Reply-To: <35A52E6B.6201DD56@whistle.com> <19980710235529.A6695@keltia.freenix.fr> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980710235529.A6695@keltia.freenix.fr> you wrote: OR> According to Dag-Erling Coidan Smørgrav: >> Am I right to assume that failing a news server, 'make world' is the >> best file system stress test? I might install a repository copy and do >> a complete 'make release NOPORTS=YES NODOCS=YES' while I'm at it... OR> "make buildworld" should succeed without problem. Now, "make installworld" OR> is another matter and what was failing up to now. I'll test the new version OR> soon. I have softupdates enabled on all slices for about two mounths. Newer had any crash with buildorld/installworld (unfortunately have no space to make release). All my tests to stress the system with '-j' either passed or failed because of VM starvation (the problem with daemons failing to fork/exec after swap was once exhausted remains :( ). I forgot when I had last panic due to softupdates. Though the system does not have any 'quirks' (e.g. unionfs, devfs, ccd) enabled. OR> -- OR> Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr OR> FreeBSD keltia.freenix.fr 3.0-CURRENT #11: Sat Jun 27 00:41:06 CEST 1998 OR> To Unsubscribe: send mail to majordomo@FreeBSD.org OR> with "unsubscribe freebsd-current" in the body of the message Alexader Litvin --- Most of your faults are not your fault. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 02:37:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17085 for freebsd-current-outgoing; Sat, 11 Jul 1998 02:37:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17066; Sat, 11 Jul 1998 02:37:07 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id LAA20656; Sat, 11 Jul 1998 11:37:02 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id KAA02162; Sat, 11 Jul 1998 10:56:44 +0200 (CEST) X-Face: " Date: Sat, 11 Jul 1998 10:56:43 +0200 From: Stefan Esser To: Chris Dillon , Julian Elischer Cc: Steve Kargl , current@FreeBSD.ORG, Stefan Esser Subject: Re: TESTERS NEEDED: Softupdates looks Very good. Mail-Followup-To: Chris Dillon , Julian Elischer , Steve Kargl , current@FreeBSD.ORG, Stefan Esser References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Chris Dillon on Thu, Jul 09, 1998 at 08:56:01PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-09 20:56 -0500, Chris Dillon wrote: > ncr0: rev 0x03 int a irq 15 on pci0.12.0 > scbus0 at ncr0 bus 0 > scbus0 target 0 lun 0: WIDE SCSI (16 bit) enabled > scbus0 target 0 lun 0: 10.0 MB/s (200 ns, offset 15) > sd0 at scbus0 target 0 lun 0 > sd0: type 0 fixed SCSI 2 > sd0: Direct-Access > sd0: WIDE SCSI (16 bit) enabled > sd0: 40.0 MB/s (50 ns, offset 15) > 4134MB (8467200 512 byte sectors) [ slightly reformatted ... ] > I also noticed something kinda funny up there in the dmesg. See where > it reports scbus0 target 0 lun0 as 10.0MB/sec, then says the same > device (sd0) is 40.0MB/sec a few lines later? Same with sd1. Don't worry, that's just a precaution taken by the driver code. There have been SCSI devices that are willing to accept any data rate offered during negotiation, but actually can't handle more than 5MHz. These are pre-SCSI-2 drives, which just knew they are *that* fast, they can handle *any* data rate offered by the host adapter (which was at most 5MHz at that time ;-) The driver won't negotiate data rates beyond 5MHz until the drive has been identified as a SCSI-2 device, and that's when another negotiation is started by the driver ... Negotiations may be started by both the drive or host adapter at any time. But except for IBM, most vendors leave it up to the host system to send the first message (which the driver does after receiving the result of an INQUIRY command). Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 03:12:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18878 for freebsd-current-outgoing; Sat, 11 Jul 1998 03:12:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csns02.comp.polyu.edu.hk (csns02.COMP.POLYU.EDU.HK [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18865 for ; Sat, 11 Jul 1998 03:12:25 -0700 (PDT) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar85.COMP.HKP.HK (cssolar85 [158.132.8.174]) by csns02.comp.polyu.edu.hk (8.8.8/8.8.8) with SMTP id SAA05652 for ; Sat, 11 Jul 1998 18:11:27 +0800 (HKT) Received: (from c5666305@localhost) by cssolar85.COMP.HKP.HK (SMI-8.6/) id SAA14624 for freebsd-current@freebsd.org; Sat, 11 Jul 1998 18:11:26 +0800 Message-Id: <199807111011.SAA14624@cssolar85.COMP.HKP.HK> Subject: non 512 bytes device support (MO 640M) To: freebsd-current@FreeBSD.ORG Date: Sat, 11 Jul 1998 18:11:26 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to know if the MO 640M support by FreeBSD 2.2.x or 3.0-snap or not. Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 03:19:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19227 for freebsd-current-outgoing; Sat, 11 Jul 1998 03:19:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19220 for ; Sat, 11 Jul 1998 03:19:23 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id NAA14890 for ; Sat, 11 Jul 1998 13:19:07 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id NAA29499 for current@freebsd.org; Sat, 11 Jul 1998 13:17:10 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id MAA13140; Sat, 11 Jul 1998 12:57:23 +0300 (EEST) (envelope-from archer) Date: Sat, 11 Jul 1998 12:57:23 +0300 (EEST) From: Alexander Litvin Message-Id: <199807110957.MAA13140@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... X-Newsgroups: grape.freebsd.current In-Reply-To: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de> <19980711000956.A21101@klemm.gtn.com> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980711000956.A21101@klemm.gtn.com> you wrote: AK> On Fri, Jul 10, 1998 at 01:11:15PM +0200, Holm Tiffe wrote: >> Hi, >> Could someone please take a look at the long standing >> problem, with the dying daemons on -current ? AK> No daemons dying here. Which version (date) of -current do AK> you use ? Might that be a hardware related thing ? AK> What hardware are you using ? AK> What kernel config file ? I can reproduce the problem very easily -- just start 'make -j64 buildworld'. With 32M RAM and 128M swap it will 'suggest more swap' in half an hour, and then I sometimes have the situation when cron/sendmail/etc fail to work. They just fork and childs die, despite the fact that memory shortage has already gone and makeworld has finished some 10 hours ago! It happened last time about a week ago (with CURRENT that time old). As no changes seem to be made to VM since then, I assume that today's CURRENT is not better. :(( Quite ordinary hardware, working perfect in all situations (except mentioned memory shortage). >> This number 6 or 7 of subscribing our lists, because >> my computer with 32 Mbytes of memory tracks -current >> and sendmail's childs are getting killed on segfaults >> when I start netscape or so. AK> ??? >> Than the mail bounces back, I have to resubscribe our >> own lists. AK> What does a dying daemon have to do with subscribing to AK> a list (aliases file, majordomo ???). I assume that majordomo@freebsd.org is unsubscribing a man when the sendmail on his box fails in described above way, and majordomo gets too many bounces (?) >> sorry for my poor english. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AK> Don't understand your problem, sorry. Please explain more AK> verbose. AK> -- AK> Andreas Klemm http://www.FreeBSD.ORG/~andreas AK> What gives you 90% more speed, for example, in kernel compilation ? AK> http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html AK> "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' --- Did you know ... That no-one ever reads these things? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 04:10:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25508 for freebsd-current-outgoing; Sat, 11 Jul 1998 04:10:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25502 for ; Sat, 11 Jul 1998 04:10:20 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA15688; Sat, 11 Jul 1998 04:10:56 -0700 (PDT) Message-Id: <199807111110.EAA15688@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... In-reply-to: Your message of "Sat, 11 Jul 1998 09:25:11 -0000." <199807110925.CAA16987@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 11 Jul 1998 04:10:56 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When no backing pages exist (becaues you've used them all up and are >out of swap space), the process requesting the page as a result of >the copy on write fault can not have its request satisfied. > >The result of an unsatified fault request is a SIGSEGV, or signal 11; Wrong. The result of running out of swap space is a SIGKILL, or signal 9. The bug that people are refering to seems to have been introduced around the time that John was messing with the VM map code, but might predate that to when he was messing with some of the swap pager algorithms. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 07:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08354 for freebsd-current-outgoing; Sat, 11 Jul 1998 07:58:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de ([139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08344 for ; Sat, 11 Jul 1998 07:58:51 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id QAA05465; Sat, 11 Jul 1998 16:57:50 +0200 (CEST) From: Holm Tiffe Message-Id: <199807111457.QAA05465@magnet.geophysik.tu-freiberg.de> Subject: Re: Arrgh ! resubscribing again again again.... In-Reply-To: <199807110925.CAA16987@usr08.primenet.com> from Terry Lambert at "Jul 11, 98 09:25:11 am" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 11 Jul 1998 16:57:50 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This problem in the VM Subsystem persists since around mid of January > > 1998 and ther was already a thread on this lists about "dying daemons". > > [ ... ] > > > Jun 3 16:10:20 magnet /kernel: swap_pager: suggest more swap space: 61 MB > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This comes from starting netscape 4.05 > > > > and now: > > > > Jun 3 16:12:17 magnet su: holm to root on /dev/ttyp3 > > Jun 3 16:15:10 magnet su: holm to freebsd on /dev/ttyp2 > > Jun 3 16:31:43 magnet /kernel: pid 3385 (sendmail), uid 0: exited on signal 11 > > > > This is what I mean ! > > This is normal. Terry, I think I don't understand fully what you have written later, but one thing I know: It is ok, that sendmail dies when it forks when netscape is running, but it is all but not ok, when sendmails childs are dying when no netscape is running anymore ! When this case is ok, then the swap/VM algorithms are bad and faulty! Any time, when the system was under high load, I have to kill the daemons per hand and to restart (or reboot). This can't be ok. This is a way to crash a FreeBSD with a userland program. I don't have seen this behavior before Jan/98, when the above behavior is correct, then please give us the old VM - System back. Better to have a slow VM then a faulty one. [..] Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 11:42:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00617 for freebsd-current-outgoing; Sat, 11 Jul 1998 11:42:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00602 for ; Sat, 11 Jul 1998 11:42:05 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id OAA27314; Sat, 11 Jul 1998 14:41:59 -0400 (EDT) (envelope-from wollman) Date: Sat, 11 Jul 1998 14:41:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199807111841.OAA27314@khavrinen.lcs.mit.edu> To: dg@root.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... In-Reply-To: <19980711000956.A21101@klemm.gtn.com> References: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de> <19980711000956.A21101@klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > No daemons dying here. Which version (date) of -current do > you use ? Might that be a hardware related thing ? An interesting note I might make: When I was running diablo, I would see `daemons dying' quite regularly. Right now, I'm running a beta of Cyclone, which has a serious memory leak. It eats up all available memory within two hours. I don't see `daemons dying' fairly often. My suspicion is that the problem in question is specific to the situation where the program requesting the memory is NOT the one which gets killed. When I'm running cyclone, it is by far the biggest hog, and it's a single process; the system kills it off, and the next top-hour a cron job runs which restarts it without incident. When I ran diablo, however, I don't recall anything ever getting explicitly killed by the system. Diablo consists of about 100 separate, small processes all running simultaneously, half of which are driven by a cron job. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 12:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00482 for freebsd-current-outgoing; Sat, 11 Jul 1998 12:48:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00477 for ; Sat, 11 Jul 1998 12:48:16 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA20110; Sat, 11 Jul 1998 12:43:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020108; Sat Jul 11 19:43:18 1998 Date: Sat, 11 Jul 1998 12:43:14 -0700 (PDT) From: Julian Elischer To: Alex cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG some fixes were committed for that, but I don't know if they cover all aspects.. On Fri, 10 Jul 1998, Alex wrote: > > On Fri, 10 Jul 1998, Julian Elischer wrote: > > > Thanks. A commit yestaerday fixed one of the known problems. > > that leases us with only the 'hard to reproduce panic'. > > > > I'd say that if people have been hanging back from using soft updates for > > safety reasons, then it's possibly reached the stage where it's more risk > > to your filesystem to NOT use soft updates... :-) > > What about on root filesystems? > > - alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00628 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:07:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (root@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00576 for ; Sat, 11 Jul 1998 19:07:06 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA10910; Sat, 11 Jul 1998 17:53:05 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd010889; Sat Jul 11 17:52:58 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA15975; Sat, 11 Jul 1998 17:52:51 -0700 (MST) From: Terry Lambert Message-Id: <199807120052.RAA15975@usr08.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: dg@root.com Date: Sun, 12 Jul 1998 00:52:51 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199807111110.EAA15688@implode.root.com> from "David Greenman" at Jul 11, 98 04:10:56 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >When no backing pages exist (becaues you've used them all up and are > >out of swap space), the process requesting the page as a result of > >the copy on write fault can not have its request satisfied. > > > >The result of an unsatified fault request is a SIGSEGV, or signal 11; > > Wrong. The result of running out of swap space is a SIGKILL, or signal 9. > The bug that people are refering to seems to have been introduced around the > time that John was messing with the VM map code, but might predate that to > when he was messing with some of the swap pager algorithms. Hmmm. I was able to cause the problem (with SIGSEGV) by mapping a large shared memory segment, and then traversing the pages to dirty them (one byte per page). I see in the VM code where a SIGKILL could result, but it seems to me that the page table entry exists, it just doesn't have pages to back it, and when the page to back the entry fails allocation, you get SIGSEGV, since it isn't mapped when you do the reference. Am I reading this code wrong? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00694 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:07:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00689 for ; Sat, 11 Jul 1998 19:07:32 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id BAA09163; Sun, 12 Jul 1998 01:45:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id BAA00951; Sun, 12 Jul 1998 01:38:07 +0200 (CEST) (envelope-from andreas) Message-ID: <19980712013807.A522@klemm.gtn.com> Date: Sun, 12 Jul 1998 01:38:07 +0200 From: Andreas Klemm To: Alex Cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <19980711233051.A15797@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alex on Sat, Jul 11, 1998 at 03:00:42PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 11, 1998 at 03:00:42PM -0700, Alex wrote: > > On Sat, 11 Jul 1998, Andreas Klemm wrote: > > > On Fri, Jul 10, 1998 at 10:57:18PM -0700, Alex wrote: > > > What about on root filesystems? > > > > /dev/sd0s2a on / (local, writes: sync 377 async 8611) ^^^ ^^^^ > > So that's a no? That's a yes, you see the softupdates statistics for root fs as well ?! -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00724 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:07:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00713 for ; Sat, 11 Jul 1998 19:07:39 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id XAA03611; Sat, 11 Jul 1998 23:45:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id XAA15810; Sat, 11 Jul 1998 23:30:51 +0200 (CEST) (envelope-from andreas) Message-ID: <19980711233051.A15797@klemm.gtn.com> Date: Sat, 11 Jul 1998 23:30:51 +0200 From: Andreas Klemm To: Alex Cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alex on Fri, Jul 10, 1998 at 10:57:18PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 10:57:18PM -0700, Alex wrote: > What about on root filesystems? /dev/sd0s2a on / (local, writes: sync 377 async 8611) /dev/sd0s2f on /usr (NFS exported, local, soft-updates, writes: sync 7 async 10028) /dev/sd0s2e on /var (local, soft-updates, writes: sync 43 async 7443) /dev/ccd0c on /obj (asynchronous, local, noatime, writes: sync 2 async 0) /dev/ccd1c on /news (NFS exported, local, noatime, soft-updates, writes: sync 2 async 1988) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 719) /dev/ccd3c on /home (NFS exported, local, soft-updates, writes: sync 45 async 12121) mfs:17065 on /tmp (asynchronous, local, writes: sync 34 async 1106) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:11:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01587 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:11:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01575 for ; Sat, 11 Jul 1998 19:11:46 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA01054; Sat, 11 Jul 1998 19:11:45 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd001028; Sat Jul 11 19:11:39 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA29647; Sat, 11 Jul 1998 19:11:36 -0700 (MST) From: Terry Lambert Message-Id: <199807120211.TAA29647@usr08.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: dg@root.com Date: Sun, 12 Jul 1998 02:11:36 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199807120115.SAA28466@implode.root.com> from "David Greenman" at Jul 11, 98 06:15:45 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I see in the VM code where a SIGKILL could result, but it seems to me that > >the page table entry exists, it just doesn't have pages to back it, and > >when the page to back the entry fails allocation, you get SIGSEGV, since > >it isn't mapped when you do the reference. > > > >Am I reading this code wrong? > > Yes, you are reading the code wrong. A SIGSEGV will only occur when there > is no mapping. If this happend for you, then either there was no mapping (a > programatic error), or there is a bug in the kernel. > In fact, one of the VM system test programs that John and I used frequently > is called "testswap", which does something similar to that suggested above; it > never exited with SIGSEGV in the past. Source attached. [ ... code elided ... ] This code doesn't use a shared memory segment, it uses heap memory. I believe the falure is specific to shared memory and/or mmap. By using dbm, which mmap's its files, I can read the clean pages out of the dabase file backing the object. Then I swap the system heavily, causing the page to be LRU'ed out from the vnode that is backing the object -- but *not* dissociated from the process address space. I keep the database open a very long time. This is typical behaviour for some types of password file using programs that don't explicitly call endpwent. Then the page gets marked dirty by another process. Then I write the page (modify the database), and the page gets written to the wrong file. I am able to get it to fairly consistently corrupt crontab by running cron and having it do something (newsyslog, in my test case) once a minute. It is generally always part of the password dbm contents that are written to the crontab. This example is just to show that there are bugs in the mmap code. Unfortunately, this is not a set of test programs, it's a production system that behaves this way, fairly reliably. Now with a second test case, I can map a very large file, and then rotor through all the pages except one, constantly. I run something else, which grabs and sbrk's back memory, sleeping 20 seconds between iterations, one page more each time, touching the memory that it sbrk's in before giving it back. Once every 20 rotors in the first program, I touch the page I skipped, causing it to be dirty, and be written. I *only* write the page, and I *only* write the page with a page worth of data on a page boundry, so there is no read-before write. Eventually, the program doing the sbrk's SIGSEGV's (signal 11, logged to the console). It's not logical, given the code, but it happens. I suspect that ther page is marked as being in core, but isn't, because it has been improperly reused out from under it (ie: there get to be two mappings, and the page is written out as a result of a write, and having been written is discarded, leaving the other page mapping hanging). I first noticed this problem in 2.2.6-stable. I'm at work right now; the code is pretty obvious, but I can send it to you when I get home, if you want. You will need enough disk to hold the large mapped file, which the shell script creates via dd of /dev/zero. I generally run this on a 16M system with 48M of swap, making the file approximately 100M; if you have more than this, you will need a bigger file; the point is to cause thrashing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:16:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03341 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:16:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03298 for ; Sat, 11 Jul 1998 19:16:28 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA25532; Sat, 11 Jul 1998 19:16:26 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd025523; Sat Jul 11 19:16:24 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA01815; Sat, 11 Jul 1998 19:16:21 -0700 (MST) From: Terry Lambert Message-Id: <199807120216.TAA01815@usr08.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: tlambert@primenet.com (Terry Lambert) Date: Sun, 12 Jul 1998 02:16:21 +0000 (GMT) Cc: dg@root.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199807120211.TAA29647@usr08.primenet.com> from "Terry Lambert" at Jul 12, 98 02:11:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm at work right now; the code is pretty obvious, but I can send it > to you when I get home, if you want. You will need enough disk to hold > the large mapped file, which the shell script creates via dd of /dev/zero. PS: If you do run this code, do it on a quiescent system, and be prepared to have any open file's contents trashed; it's not so reliable a flaw that it trashes only the target file... expect to potentially have to reinstall. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04931 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:20:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04884 for ; Sat, 11 Jul 1998 19:20:44 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA28466; Sat, 11 Jul 1998 18:15:45 -0700 (PDT) Message-Id: <199807120115.SAA28466@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... In-reply-to: Your message of "Sun, 12 Jul 1998 00:52:51 -0000." <199807120052.RAA15975@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 11 Jul 1998 18:15:45 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >When no backing pages exist (becaues you've used them all up and are >> >out of swap space), the process requesting the page as a result of >> >the copy on write fault can not have its request satisfied. >> > >> >The result of an unsatified fault request is a SIGSEGV, or signal 11; >> >> Wrong. The result of running out of swap space is a SIGKILL, or signal 9. >> The bug that people are refering to seems to have been introduced around the >> time that John was messing with the VM map code, but might predate that to >> when he was messing with some of the swap pager algorithms. > >Hmmm. I was able to cause the problem (with SIGSEGV) by mapping a large >shared memory segment, and then traversing the pages to dirty them (one >byte per page). > >I see in the VM code where a SIGKILL could result, but it seems to me that >the page table entry exists, it just doesn't have pages to back it, and >when the page to back the entry fails allocation, you get SIGSEGV, since >it isn't mapped when you do the reference. > >Am I reading this code wrong? Yes, you are reading the code wrong. A SIGSEGV will only occur when there is no mapping. If this happend for you, then either there was no mapping (a programatic error), or there is a bug in the kernel. In fact, one of the VM system test programs that John and I used frequently is called "testswap", which does something similar to that suggested above; it never exited with SIGSEGV in the past. Source attached. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project #include main() { int i; char *s; for(i=0;i<16000;i++) { s = malloc(0x1000); if( (i % 100) == 0) { printf("%d ",i*0x1000); fflush(stdout); } if( !s) { printf("no mem: %d\n", i*0x1000); exit(1); } /* memset(s,0,0x1000); */ *s = 0; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:21:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05212 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:21:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soccer.ksg.com (ftw-tsa5-60.cyberramp.net [207.158.119.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05128 for ; Sat, 11 Jul 1998 19:21:28 -0700 (PDT) (envelope-from kgor@soccer.ksg.com) Received: (from kgor@localhost) by soccer.ksg.com (8.8.8/8.8.8) id TAA09949; Sat, 11 Jul 1998 19:18:15 -0500 (CDT) (envelope-from kgor) Date: Sat, 11 Jul 1998 19:18:15 -0500 (CDT) Message-Id: <199807120018.TAA09949@soccer.ksg.com> From: "Kent S. Gordon" To: freebsd-current@FreeBSD.ORG Subject: Elf 3.0 Snap available? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is a 3.0 snap available that uses elf? It would make upgrading to elf a lot easier in many cases. -- Kent S. Gordon KSG -- Unix, Network, Database Consulting Postal: 76 Corral Drive North, Keller, Texas 76248 e-mail: kgor@ksg.com Phone:(817)431-8775 Resume: http://www.ksg.com/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:26:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06484 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:26:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06432 for ; Sat, 11 Jul 1998 19:26:17 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id SAA07063; Sat, 11 Jul 1998 18:26:30 -0400 (EDT) Message-ID: <19980711182630.64575@supersex.com> Date: Sat, 11 Jul 1998 18:26:30 -0400 From: Leo Papandreou To: current@FreeBSD.ORG Subject: Re: Does "make -j4 buildworld" actually help anybody? References: <199807101655.JAA29491@rah.star-gate.com> <199807101711.KAA29210@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199807101711.KAA29210@austin.polstra.com>; from John Polstra on Fri, Jul 10, 1998 at 10:11:15AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 10:11:15AM -0700, John Polstra wrote: > > What sort of disks do you have ? > > IBM DDRS-34560W. These are the 4.5 GB version of the so-called > Ultrastar 9ES SCSI disks. Justin recommended them to me, and they > seem quite fast and nice so far. I have the 9 GB version (DDRS-39130W) and its probably twice as slow as the quantum II's and III's on the same machine. It is cheap, tho, the 9GB model is half again as slim as the Quantums, its never given me any problems (unlike the quantums which have suffered 3 failures - including a replacement unit which failed to work out of the box) and runs very cool. *Much* cheaper than the quantums. [...] > > Anyway, despite all that, I think they are good disks. They are perfect if you need to fill a tower with a lot of drives and put it on the web but they are not speed demons. > > John > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:38:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09931 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:38:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (root@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09818 for ; Sat, 11 Jul 1998 19:37:18 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA18710; Sat, 11 Jul 1998 18:49:59 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd018692; Sat Jul 11 18:49:56 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA18536; Sat, 11 Jul 1998 18:49:52 -0700 (MST) From: Terry Lambert Message-Id: <199807120149.SAA18536@usr08.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: freebsd@magnet.geophysik.tu-freiberg.de (Holm Tiffe) Date: Sun, 12 Jul 1998 01:49:50 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199807111457.QAA05465@magnet.geophysik.tu-freiberg.de> from "Holm Tiffe" at Jul 11, 98 04:57:50 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is normal. > > Terry, I think I don't understand fully what you have written later, but one > thing I know: > > It is ok, that sendmail dies when it forks when netscape is running, but > it is all but not ok, when sendmails childs are dying when no netscape > is running anymore ! Then force NetScape to uncache the objects that it has places int the X server's shared memroy segment. The problem is that objects in the shared memory segment are not reference counted, and Netscape does nto explicitly free them. You could argue that this is an X server bug (ie: the server should reference count the objects, and decrement the reference count when Netscape's connection goes away, removing the object when the reference goes to zero), and you could argue that this is a Netscape bug. Either way, you can "fix" the galloping memory problem by disabling the shared memory extensions so that Netscape can't use them, and then no matter who is really at fault, the memory leak will go away. > When this case is ok, then the swap/VM algorithms are bad and faulty! There is still a process context claiming ownership of the memory, and it is therefore not being released back to the system. The faulty behaviour lies in pilot error, of one kind or another. > Any time, when the system was under high load, I have to kill the > daemons per hand and to restart (or reboot). This can't be ok. You don't *have* to do that. You *could* shutdown your X server and restart it. You simply choose to have your demons die, instead of doing this and/or limiting the amount of VM available to the X server and Netscape, or disabling the X shm extensions. > This is a way to crash a FreeBSD with a userland program. Not a correctly configured FreeBSD, which will have memoryuse, datasize, and stacksize limits that will prevent this problem. > I don't have seen this behavior before Jan/98, when the above behavior > is correct, then please give us the old VM - System back. > Better to have a slow VM then a faulty one. There are a number of known VM bugs; I can, for example, randomly corrupt open files by using mmap() in particular ways (having to do with the page becoming disassociated from the vnode backing it, but not from the address space of the process doing the mapping, and therefore subject to erroneous reuse). I don't believe this (and the other known probls) are what you are seeing, however. You should try reproducing the problem with the shm extensions disabled. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:38:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10027 for freebsd-current-outgoing; Sat, 11 Jul 1998 19:38:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09920 for ; Sat, 11 Jul 1998 19:37:44 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA29759; Sat, 11 Jul 1998 19:38:03 -0700 (PDT) Message-Id: <199807120238.TAA29759@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... In-reply-to: Your message of "Sun, 12 Jul 1998 02:11:36 -0000." <199807120211.TAA29647@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 11 Jul 1998 19:38:03 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I run something else, which grabs and sbrk's back memory, sleeping 20 ... >It's not logical, given the code, but it happens. ... >I first noticed this problem in 2.2.6-stable. I think it is likely that you are seeing the effects of a bug in the program - perhaps with the usage of sbrk (specifically, "giving back" memory), since non-careful use of brk/sbrk will interact badly with malloc which also does this (and malloc() can be called from libc, inside innocuous functions like printf()). If that isn't the cause, then it might be caused by a kernel bug in not properly sensing that a page has been modified, discarding the contents without writing to swap. When this occurs with stack or data/bss pages, pointers can end up being wrong - often 0 since the kernel will fabricate a demand zero page if there is no backing in swap, and lead to a NULL pointer dereference. I thought we had fixed all of these type bugs in the 2.2 branch (actually earlier in 2.1) long ago, but perhaps there is still one lurking somewhere. I certainly have never seen this on any of the machines that I have access to, and I have done extensive regression testing with the 2.2 branch. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 19:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00482 for freebsd-current-outgoing; Sat, 11 Jul 1998 12:48:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00477 for ; Sat, 11 Jul 1998 12:48:16 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA20110; Sat, 11 Jul 1998 12:43:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020108; Sat Jul 11 19:43:18 1998 Date: Sat, 11 Jul 1998 12:43:14 -0700 (PDT) From: Julian Elischer To: Alex cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG some fixes were committed for that, but I don't know if they cover all aspects.. On Fri, 10 Jul 1998, Alex wrote: > > On Fri, 10 Jul 1998, Julian Elischer wrote: > > > Thanks. A commit yestaerday fixed one of the known problems. > > that leases us with only the 'hard to reproduce panic'. > > > > I'd say that if people have been hanging back from using soft updates for > > safety reasons, then it's possibly reached the stage where it's more risk > > to your filesystem to NOT use soft updates... :-) > > What about on root filesystems? > > - alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 20:22:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19440 for freebsd-current-outgoing; Sat, 11 Jul 1998 20:22:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19432 for ; Sat, 11 Jul 1998 20:22:12 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA00562; Sat, 11 Jul 1998 20:22:31 -0700 (PDT) Message-Id: <199807120322.UAA00562@implode.root.com> To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: current@FreeBSD.ORG Subject: Re: Other sites to ftp cvs-cur.????.gz from? In-reply-to: Your message of "Sat, 11 Jul 1998 12:35:39 +0800." <199807110435.MAA25621@ariadne.tensor.pgs.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 11 Jul 1998 20:22:31 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >ftp.freebsd.org's /pub/FreeBSD/CTM/cvs-cur area hasn't been updated for quite >some time. Does anyone know the location of a site which is archiving this, or >(the preferred option) can someone please fix the problem of ftp.freebsd.org? If someone would let me know where the most reliable source of this is located (available via anonymous FTP), then I will change the wcarchive mirror to point to that. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 20:54:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25127 for freebsd-current-outgoing; Sat, 11 Jul 1998 20:54:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25115 for ; Sat, 11 Jul 1998 20:54:32 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id WAA07850; Sat, 11 Jul 1998 22:54:19 -0500 (CDT) (envelope-from dan) Message-ID: <19980711225419.A7755@emsphone.com> Date: Sat, 11 Jul 1998 22:54:19 -0500 From: Dan Nelson To: Andreas Klemm , Alex Cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <19980711233051.A15797@klemm.gtn.com> <19980712013807.A522@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19980712013807.A522@klemm.gtn.com>; from "Andreas Klemm" on Sun Jul 12 01:38:07 GMT 1998 X-OS: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 12), Andreas Klemm said: > On Sat, Jul 11, 1998 at 03:00:42PM -0700, Alex wrote: > > > > On Sat, 11 Jul 1998, Andreas Klemm wrote: > > > > > On Fri, Jul 10, 1998 at 10:57:18PM -0700, Alex wrote: > > > > What about on root filesystems? > > > > > > /dev/sd0s2a on / (local, writes: sync 377 async 8611) > > ^^^ ^^^^ > > > > So that's a no? > > That's a yes, you see the softupdates statistics for root fs as well ?! No; you see a count of sync and async writes. An async-mounted root looks like this: /dev/sd0s2a on / (local, soft-updates, writes: sync 18 async 6138) And works just fine. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 22:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06481 for freebsd-current-outgoing; Sat, 11 Jul 1998 22:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (root@haiti-89.ppp.hooked.net [206.169.228.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06468 for ; Sat, 11 Jul 1998 22:08:16 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id RAA10827; Sat, 11 Jul 1998 17:01:45 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 11 Jul 1998 17:01:45 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Andreas Klemm cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <19980712013807.A522@klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Jul 1998, Andreas Klemm wrote: > On Sat, Jul 11, 1998 at 03:00:42PM -0700, Alex wrote: > > > > On Sat, 11 Jul 1998, Andreas Klemm wrote: > > > > > On Fri, Jul 10, 1998 at 10:57:18PM -0700, Alex wrote: > > > > What about on root filesystems? > > > > > > /dev/sd0s2a on / (local, writes: sync 377 async 8611) > ^^^ ^^^^ > > > > So that's a no? > > That's a yes, you see the softupdates statistics for root fs as well ?! No, I don't. zippy:~/kde/ksmiletris-0.3#mount /dev/sd0s1a on / (local, writes: sync 17610 async 66257) /dev/sd1s1e on /mnt/usr2 (local, writes: sync 1409 async 2942) procfs on /proc (local) kernfs on /kern (local) Both drives are mounted sync, without softupdates included in the kernel. Note the lack of the words soft and update. That pretty much means a filesystem isn't running without soft updates :^) zippy:~/kde/ksmiletris-0.3#strings `sysctl -n kern.bootfile` |grep -i soft|grep options zippy:~/kde/ksmiletris-0.3#strings `sysctl -n kern.bootfile` |grep -i include_config|grep options ___options INCLUDE_CONFIG_FILE # Include this file in kernel zippy:~/kde/ksmiletris-0.3# As opposed to this which you posted earlier: /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 719) ^^^^^^^^^^^^ - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 22:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06499 for freebsd-current-outgoing; Sat, 11 Jul 1998 22:08:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (root@haiti-89.ppp.hooked.net [206.169.228.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06477 for ; Sat, 11 Jul 1998 22:08:21 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id PAA08467; Sat, 11 Jul 1998 15:00:42 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 11 Jul 1998 15:00:42 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Andreas Klemm cc: current Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <19980711233051.A15797@klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Jul 1998, Andreas Klemm wrote: > On Fri, Jul 10, 1998 at 10:57:18PM -0700, Alex wrote: > > What about on root filesystems? > > /dev/sd0s2a on / (local, writes: sync 377 async 8611) So that's a no? > /dev/sd0s2f on /usr (NFS exported, local, soft-updates, writes: sync 7 async 10028) > /dev/sd0s2e on /var (local, soft-updates, writes: sync 43 async 7443) > /dev/ccd0c on /obj (asynchronous, local, noatime, writes: sync 2 async 0) > /dev/ccd1c on /news (NFS exported, local, noatime, soft-updates, writes: sync 2 async 1988) > /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 719) > /dev/ccd3c on /home (NFS exported, local, soft-updates, writes: sync 45 async 12121) > mfs:17065 on /tmp (asynchronous, local, writes: sync 34 async 1106) - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 22:48:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10658 for freebsd-current-outgoing; Sat, 11 Jul 1998 22:48:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10648 for ; Sat, 11 Jul 1998 22:48:26 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id IAA02517 for ; Sun, 12 Jul 1998 08:48:18 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id IAA01509 for current@freebsd.org; Sun, 12 Jul 1998 08:46:13 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id IAA07205; Sun, 12 Jul 1998 08:36:31 +0300 (EEST) (envelope-from archer) Date: Sun, 12 Jul 1998 08:36:31 +0300 (EEST) From: Alexander Litvin Message-Id: <199807120536.IAA07205@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... X-Newsgroups: grape.freebsd.current In-Reply-To: <199807120149.SAA18536@usr08.primenet.com> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807120149.SAA18536@usr08.primenet.com> you wrote: >> > This is normal. >> >> Terry, I think I don't understand fully what you have written later, but one >> thing I know: >> >> It is ok, that sendmail dies when it forks when netscape is running, but >> it is all but not ok, when sendmails childs are dying when no netscape >> is running anymore ! TL> Then force NetScape to uncache the objects that it has places int the TL> X server's shared memroy segment. TL> The problem is that objects in the shared memory segment are not reference TL> counted, and Netscape does nto explicitly free them. TL> You could argue that this is an X server bug (ie: the server should TL> reference count the objects, and decrement the reference count when TL> Netscape's connection goes away, removing the object when the reference TL> goes to zero), and you could argue that this is a Netscape bug. TL> Either way, you can "fix" the galloping memory problem by disabling the TL> shared memory extensions so that Netscape can't use them, and then no TL> matter who is really at fault, the memory leak will go away. >> When this case is ok, then the swap/VM algorithms are bad and faulty! TL> There is still a process context claiming ownership of the memory, and TL> it is therefore not being released back to the system. TL> The faulty behaviour lies in pilot error, of one kind or another. >> Any time, when the system was under high load, I have to kill the >> daemons per hand and to restart (or reboot). This can't be ok. TL> You don't *have* to do that. You *could* shutdown your X server and TL> restart it. You simply choose to have your demons die, instead of TL> doing this and/or limiting the amount of VM available to the X server TL> and Netscape, or disabling the X shm extensions. Terry, your explanation is ok. But what X-server should I shutdown? For I don't have any X's. And yesterday I repeated 'make -j64 buildworld', and as always: sendmail childs die with SIGSEGV, cron seems to be in memory, but no cron jobs run. And all that after makeworld has finished, system is _absolutely_ idle. TL> Terry Lambert TL> terry@lambert.org TL> --- TL> Any opinions in this posting are my own and not those of my present TL> or previous employers. TL> To Unsubscribe: send mail to majordomo@FreeBSD.org TL> with "unsubscribe freebsd-current" in the body of the message --- If you have to ask how much it is, you can't afford it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 11 23:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14766 for freebsd-current-outgoing; Sat, 11 Jul 1998 23:22:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14758 for ; Sat, 11 Jul 1998 23:22:03 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA06041; Sat, 11 Jul 1998 23:21:59 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd006020; Sat Jul 11 23:21:55 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id XAA29796; Sat, 11 Jul 1998 23:21:52 -0700 (MST) From: Terry Lambert Message-Id: <199807120621.XAA29796@usr07.primenet.com> Subject: Re: Arrgh ! resubscribing again again again.... To: archer@lucky.net (Alexander Litvin) Date: Sun, 12 Jul 1998 06:21:52 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199807120536.IAA07205@grape.carrier.kiev.ua> from "Alexander Litvin" at Jul 12, 98 08:36:31 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > TL> You don't *have* to do that. You *could* shutdown your X server and > TL> restart it. You simply choose to have your demons die, instead of > TL> doing this and/or limiting the amount of VM available to the X server > TL> and Netscape, or disabling the X shm extensions. > > Terry, your explanation is ok. But what X-server should I shutdown? > For I don't have any X's. And yesterday I repeated 'make -j64 buildworld', > and as always: sendmail childs die with SIGSEGV, cron seems to be in > memory, but no cron jobs run. And all that after makeworld has finished, > system is _absolutely_ idle. Interesting. Clearly, you're not the person running Netscape to cause a similar problem. 8-). Do you have any zombie processes? Have you looked at the vmstat output? If you kill -HUP cron, what happens? If you kill -HUP sendmail, what happens? Did you get any errors in the buildworld, or did it complete without damaging itself (only damaging sendmail and cron)? Are you overclocking your CPU? How much memory do you have -- is it enough that if you missed a refresh cycle or two (say, because you did something silly, like a buildworld with -j64 and you have an Adaptec controller with a high bus-on time, or you are using a PIO IDE controller, etc...), that the upper memory contents might degrade and cause these problems? Does -j32 have the same problem? -j16? etc.? It would be nice to know if this problem was the result of running out of VM, or if you can cause it by load without actually exhasting the VM... Makeworld takes a while; have you tried putting a crontab entry that spits the time out to the console once a minute, and bracketing the buildworld with "date"? Maybe it's a particular section of the tree, and not the load, that's getting you? Perhaps that region of the disk is corrupt? Obviously, I don't expect you to answer all of these to the list, or even to me, if the answer to the questions is "no impact". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message