From owner-freebsd-current Sun Aug 9 00:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23834 for freebsd-current-outgoing; Sun, 9 Aug 1998 00:59:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hybrid.soho (cs1p07.txg.ttn.net.tw [210.17.80.104] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23829 for ; Sun, 9 Aug 1998 00:59:39 -0700 (PDT) (envelope-from jonahkuo@mail.ttn.com.tw) Received: from mail.ttn.com.tw (amd133.soho [192.168.82.31]) by hybrid.soho (8.9.1/8.8.7) with ESMTP id PAA00384 for ; Sun, 9 Aug 1998 15:45:56 +0800 (CST) (envelope-from jonahkuo@mail.ttn.com.tw) Message-ID: <35CD56E6.890CC83B@mail.ttn.com.tw> Date: Sun, 09 Aug 1998 15:59:35 +0800 From: Jonah Kuo Reply-To: jonahkuo@mail.ttn.com.tw X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ' /usr/lib' can not be used. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, I makeworld several times these days, then I found /usr/lib wasn't updated correctly, so the boot message tells: ldconfig: WARNING! ' /usr/lib' can not be used. Doesn't 'make world' update the whole freebsd system? The system (3.0-current) runs everything fine so far, should I worry about anything? Jonah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 01:21:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24886 for freebsd-current-outgoing; Sun, 9 Aug 1998 01:21:28 -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 BAA24881 for ; Sun, 9 Aug 1998 01:21:24 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA15661; Sun, 9 Aug 1998 18:27:14 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808090827.SAA15661@cimlogic.com.au> Subject: Re: ' /usr/lib' can not be used. In-Reply-To: <35CD56E6.890CC83B@mail.ttn.com.tw> from Jonah Kuo at "Aug 9, 98 03:59:35 pm" To: jonahkuo@mail.ttn.com.tw Date: Sun, 9 Aug 1998 18:27:14 +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 Jonah Kuo wrote: > Hello there, > > I makeworld several times these days, then I found /usr/lib > wasn't updated correctly, so the boot message tells: > > ldconfig: WARNING! ' /usr/lib' can not be used. > > Doesn't 'make world' update the whole freebsd system? > > The system (3.0-current) runs everything fine so far, > should I worry about anything? Edit /etc/rc and change /usr/lib to /usr/lib/aout -- 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 Aug 9 01:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25295 for freebsd-current-outgoing; Sun, 9 Aug 1998 01:25:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25284 for ; Sun, 9 Aug 1998 01:24:57 -0700 (PDT) (envelope-from chat.ru!osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id MAA10061; Sun, 9 Aug 1998 12:24:36 +0400 (MSD) Received: by sunny.aha.ru id MAA28903; (8.8.8/vak/1.9) Sun, 9 Aug 1998 12:24:13 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma028878; Sun Aug 9 12:23:50 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id MAA10050; (8.9.1/vak/1.9) Sun, 9 Aug 1998 12:26:48 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.0/8.9.0) with ESMTP id MAA03083; Sun, 9 Aug 1998 12:28:59 +0400 (MSD) Date: Sun, 9 Aug 1998 12:28:58 +0400 (MSD) From: oZZ!!! X-Sender: osa@localhost To: Jonah Kuo cc: current@FreeBSD.ORG Subject: Re: ' /usr/lib' can not be used. In-Reply-To: <35CD56E6.890CC83B@mail.ttn.com.tw> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R X-MIME-Autoconverted: from 8bit to quoted-printable by serv.etrust.ru id MAA10050 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA25287 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Aug 1998, Jonah Kuo wrote: > Hello there, > I makeworld several times these days, then I found /usr/lib > wasn't updated correctly, so the boot message tells: > ldconfig: WARNING! ' /usr/lib' can not be used. change /usr/lib to /usr/lib/aout in your /etc/rc.conf > Doesn't 'make world' update the whole freebsd system? > The system (3.0-current) runs everything fine so far, > should I worry about anything? If you update your system, why you can't update /etc from /usr/src ? > Jonah > Rgdz, Осокин Сергей aka oZZ, osa@chat.ru FreeBSD - Да пребудет с нами сила! http://www.chat.ru/~osa/main.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 06:57:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20047 for freebsd-current-outgoing; Sun, 9 Aug 1998 06:57:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20039 for ; Sun, 9 Aug 1998 06:57:04 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id JAA23904; Sun, 9 Aug 1998 09:56:19 -0400 (EDT) Date: Sun, 9 Aug 1998 09:56:19 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG cc: julian@whistle.com Subject: New softupdates code panics 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 Well, I had patched my ffs_softdep.c and my ufs_vnops.c according to Luoqi and Kirk's patches and soon after rebooting, I got a panic (I don't think I was removing anything at the time, but oh well there are other processes than the ones I watch). I've still got the full debugging kernel and a core dump, so if anyone wants more just ask. #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf0119157 in panic ( fmt=0xf01b386c "handle_workitem_remove: bad dir delta") at ../../kern/kern_shutdown.c:427 #2 0xf01b3942 in handle_workitem_remove (dirrem=0xf0be1c60) at ../../ufs/ffs/ffs_softdep.c:2560 #3 0xf01b0db9 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:534 #4 0xf013b866 in sched_sync () at ../../kern/vfs_subr.c:977 #5 0xf010c29e in kproc_start (udata=0xf0223724) at ../../kern/init_main.c:245 #6 0xf01d70c0 in fork_trampoline () Cannot access memory at address 0x2000. Cheers, Brian Feldman green@unixhelp.com P.S. This is the first softupdates panic I've had in a _long_ time, so good job you guys! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 08:58:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27898 for freebsd-current-outgoing; Sun, 9 Aug 1998 08:58:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (gw03.mpoweredpc.net [142.177.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27893 for ; Sun, 9 Aug 1998 08:58:51 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.8) with SMTP id MAA00174; Sun, 9 Aug 1998 12:57:10 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 9 Aug 1998 12:57:10 -0300 (ADT) From: The Hermit Hacker To: John Birrell cc: jonahkuo@mail.ttn.com.tw, current@FreeBSD.ORG Subject: Re: ' /usr/lib' can not be used. In-Reply-To: <199808090827.SAA15661@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 Sun, 9 Aug 1998, John Birrell wrote: > Jonah Kuo wrote: > > Hello there, > > > > I makeworld several times these days, then I found /usr/lib > > wasn't updated correctly, so the boot message tells: > > > > ldconfig: WARNING! ' /usr/lib' can not be used. > > > > Doesn't 'make world' update the whole freebsd system? > > > > The system (3.0-current) runs everything fine so far, > > should I worry about anything? > > Edit /etc/rc and change /usr/lib to /usr/lib/aout Better yet, spend a little time checking changes between /usr/src/etc and /etc, so that *all* changes are reflected. /etc/rc.conf has changed dramatically also, over the past while, with more optoins added like the security stuff... 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 Aug 9 10:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02404 for freebsd-current-outgoing; Sun, 9 Aug 1998 10:12:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02399 for ; Sun, 9 Aug 1998 10:12:45 -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 NAA20300; Sun, 9 Aug 1998 13:12:17 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <35CD56E6.890CC83B@mail.ttn.com.tw> Date: Sun, 9 Aug 1998 13:16:15 -0400 To: jonahkuo@mail.ttn.com.tw, current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: ' /usr/lib' can not be used. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:59 PM +0800 8/9/98, Jonah Kuo wrote: > Hello there, > > I makeworld several times these days, then I found /usr/lib > wasn't updated correctly, so the boot message tells: > > ldconfig: WARNING! ' /usr/lib' can not be used. > > Doesn't 'make world' update the whole freebsd system? It does not automatically update configuration files in /etc, because there's probably no good safe way to automate that. (there's no way for an automated process to know why you have decided to configure your system the way you have it configured, so it can't know what changes are safe). So, if you look under the "Tutorials" section at http://www.freebsd.org/docs.html, you'll see one for "Upgrading FreeBSD from source (using _make_world_)". That tutorial lists all the steps you have to do, including the process of checking thru any changes to /etc by hand. In this case it's a probably change to /etc/rc that you are missing. --- 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 Sun Aug 9 12:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14519 for freebsd-current-outgoing; Sun, 9 Aug 1998 12:33:50 -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 MAA14513 for ; Sun, 9 Aug 1998 12:33:49 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: (from hasty@localhost) by rah.star-gate.com (8.8.8/8.8.8) id MAA07114 for current@freebsd.org; Sun, 9 Aug 1998 12:33:27 -0700 (PDT) (envelope-from hasty) Date: Sun, 9 Aug 1998 12:33:27 -0700 (PDT) From: Amancio Hasty Message-Id: <199808091933.MAA07114@rah.star-gate.com> To: current@FreeBSD.ORG Subject: Reminder : can't fork Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Occassionally, my system refuses to fork and pending on what I was doing daemons such as sendmail die -- usually this is after I tried to compile a big program such as mozilla however I have seen the bug surfaced when I think I have not exhausted my swap space unfortunately most of the times this happens I am at work and it is really hard to diagnose the problem. This problem has been around for about 6 months now. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 13:21:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19707 for freebsd-current-outgoing; Sun, 9 Aug 1998 13:21:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles167.castles.com [208.214.165.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19685 for ; Sun, 9 Aug 1998 13:21:38 -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 NAA07708; Sun, 9 Aug 1998 13:20:11 -0700 (PDT) Message-Id: <199808092020.NAA07708@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 12:33:27 PDT." <199808091933.MAA07114@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 13:20:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Occassionally, my system refuses to fork and pending on what I was doing > daemons such as sendmail die -- usually this is after I tried to compile > a big program such as mozilla however I have seen the bug surfaced when > I think I have not exhausted my swap space unfortunately most of the times > this happens I am at work and it is really hard to diagnose the problem. > > This problem has been around for about 6 months now. Pilot error. Your resource limits are too low. -- \\ 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 Aug 9 13:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22437 for freebsd-current-outgoing; Sun, 9 Aug 1998 13:48:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22428 for ; Sun, 9 Aug 1998 13:48:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-118.camalott.com [208.229.74.118]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA27315; Sun, 9 Aug 1998 15:49:06 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id PAA03447; Sun, 9 Aug 1998 15:46:37 -0500 (CDT) (envelope-from joelh) Date: Sun, 9 Aug 1998 15:46:37 -0500 (CDT) Message-Id: <199808092046.PAA03447@detlev.UUCP> To: mike@smith.net.au CC: ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG In-reply-to: <199808061544.IAA03196@antipodes.cdrom.com> (message from Mike Smith on Thu, 06 Aug 1998 08:44:07 -0700) Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808061544.IAA03196@antipodes.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> I would like to force my systems to always boot with '-v'.. Is there >>>> any way to do this without operator intervention? >>> Take a look at what boot(8) has to say about /boot.config. >> It says that -v doesn't make the cut for boot.config. The fix is >> trivial, but I haven't yet rolled a pr. >> This suggestion hasn't been carefully considered or tested, but if you >> want to fix it yourself, then in /sys/i386/boot/biosboot/boot.c, move >> the bit about "loadflags &= (RB_DUAL | RB_SERIAL);" to right around >> "readfile("boot.config", ...);" about 40 lines up. (The key is that >> it should be before "getbootdev(boot_config, &loadflags);".) This >> will effectively allow any boot flags in. > It will become either "-v" in /boot.config or "set bootverbose" in > the new bootstrap config, which I haven't named. > And this is a handy topic to raise it under; the new bootstrap will > (optionally) need access to quite a few files, and we may not really > want these cluttering up the root directory. How do people feel about > a /boot directory these days? If you're reworking the bootstrap, is it worth me submitting a pr with this patch? (I'm implementing it locally anyway.) 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 Sun Aug 9 14:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26912 for freebsd-current-outgoing; Sun, 9 Aug 1998 14:40:24 -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 OAA26905 for ; Sun, 9 Aug 1998 14:40:22 -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 OAA07390; Sun, 9 Aug 1998 14:39:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808092139.OAA07390@rah.star-gate.com> To: Mike Smith cc: Amancio Hasty , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 13:20:11 PDT." <199808092020.NAA07708@antipodes.cdrom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7387.902698790.1@rah.star-gate.com> Date: Sun, 09 Aug 1998 14:39:50 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pilot error is for sure a possibility however it does not explain why sendmail dies when I am compiling mozilla from my account. I think that this problem has been reported by other users. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 15:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00672 for freebsd-current-outgoing; Sun, 9 Aug 1998 15:25:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00667 for ; Sun, 9 Aug 1998 15:25:10 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA02005; Sun, 9 Aug 1998 15:24:50 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd001998; Sun Aug 9 15:24:43 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA21506; Sun, 9 Aug 1998 15:24:40 -0700 (MST) From: Terry Lambert Message-Id: <199808092224.PAA21506@usr04.primenet.com> Subject: Re: ' /usr/lib' can not be used. To: drosih@rpi.edu (Garance A Drosihn) Date: Sun, 9 Aug 1998 22:24:40 +0000 (GMT) Cc: jonahkuo@mail.ttn.com.tw, current@FreeBSD.ORG In-Reply-To: from "Garance A Drosihn" at Aug 9, 98 01:16:15 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 > It does not automatically update configuration files in /etc, > because there's probably no good safe way to automate that. Sure there is. Seperate the schema from the subschema and the parameter store. Retrieve data using the old schema. Restore data using the new schema. Dynamically extend the schema between releases using subschema changes. In general, unless something radically changes, it's not necessary to do the retrieve/restore, except for the first time you change over to a schema-based system. And this *can* be automated by providing a commandline tool to allow sourcing the config then writing the parameter store. A radical change would be "total conversion to USB devices" or something similar. 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 Sun Aug 9 15:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00980 for freebsd-current-outgoing; Sun, 9 Aug 1998 15:27:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00975 for ; Sun, 9 Aug 1998 15:27:54 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA22200; Sun, 9 Aug 1998 15:27:34 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd022192; Sun Aug 9 15:27:28 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA21586; Sun, 9 Aug 1998 15:27:23 -0700 (MST) From: Terry Lambert Message-Id: <199808092227.PAA21586@usr04.primenet.com> Subject: Re: Reminder : can't fork To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 9 Aug 1998 22:27:23 +0000 (GMT) Cc: mike@smith.net.au, hasty@rah.star-gate.com, current@FreeBSD.ORG In-Reply-To: <199808092139.OAA07390@rah.star-gate.com> from "Amancio Hasty" at Aug 9, 98 02:39: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 > Pilot error is for sure a possibility however it does not explain why > sendmail dies when I am compiling mozilla from my account. I think that > this problem has been reported by other users. If you control-alt-F1 over to the console, is it asking for more swap, or not? If so, it's pilot error. If not, it's a bug or it's bad RAM or overclocking. Given the recent high level of VM instability, it's very hard to discount the "bug theory". 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 Sun Aug 9 15:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03778 for freebsd-current-outgoing; Sun, 9 Aug 1998 15:54:34 -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 PAA03767 for ; Sun, 9 Aug 1998 15:54:31 -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 PAA07594; Sun, 9 Aug 1998 15:53:59 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808092253.PAA07594@rah.star-gate.com> To: Terry Lambert cc: hasty@rah.star-gate.com (Amancio Hasty), mike@smith.net.au, current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 22:27:23 -0000." <199808092227.PAA21586@usr04.primenet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7591.902703239.1@rah.star-gate.com> Date: Sun, 09 Aug 1998 15:53:59 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well okay, lets see if others report the same problem. I will play with my system tonite when I get home from work. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 19:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27680 for freebsd-current-outgoing; Sun, 9 Aug 1998 19:13:45 -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 TAA27675 for ; Sun, 9 Aug 1998 19:13:41 -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 LAA09090; Mon, 10 Aug 1998 11:41:50 +0930 (CST) Message-Id: <199808100211.LAA09090@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Dan Nelson , Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea In-reply-to: Your message of "Sat, 08 Aug 1998 17:40:45 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 11:41:49 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No offense, but instead of shutdown -r now, a bit of a better idea is to > try modload /lkm/linux_mod.o *grin. Or maybe just 'linux' which does that for you :) --------------------------------------------------------------------- |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 Sun Aug 9 22:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11563 for freebsd-current-outgoing; Sun, 9 Aug 1998 22:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles217.castles.com [208.214.165.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11537 for ; Sun, 9 Aug 1998 22:23:58 -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 WAA09698; Sun, 9 Aug 1998 22:22:06 -0700 (PDT) Message-Id: <199808100522.WAA09698@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 14:39:50 PDT." <199808092139.OAA07390@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 22:22:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Pilot error is for sure a possibility however it does not explain why > sendmail dies when I am compiling mozilla from my account. I think that > this problem has been reported by other users. "Cannot fork" is either "too many processess (for you or the system in toto)" or some other resource starvation. If you're not out of memory or file descriptors, then you've hit the limit on the maximum number of processes. Let's guess that this is a FAQ; what is the value of 'maxusers' in your kernel config? -- \\ 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 Aug 9 22:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12148 for freebsd-current-outgoing; Sun, 9 Aug 1998 22:31:28 -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 WAA12143 for ; Sun, 9 Aug 1998 22:31:27 -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 WAA09127; Sun, 9 Aug 1998 22:31:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100531.WAA09127@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 22:22:06 PDT." <199808100522.WAA09698@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 22:31:01 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In my kernel config file I have: maxusers 30 Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 22:48:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13502 for freebsd-current-outgoing; Sun, 9 Aug 1998 22:48:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13494 for ; Sun, 9 Aug 1998 22:48:52 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id BAA29411 for ; Mon, 10 Aug 1998 01:48:31 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA08376; Mon, 10 Aug 1998 01:48:30 -0400 From: "John W. DeBoskey" Message-Id: <199808100548.AA08376@mozart> Subject: chflags: <> Operation not permitted To: freebsd-current@FreeBSD.ORG Date: Mon, 10 Aug 1998 01:48:30 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been getting the following error for a little over a week now during my nightly build.. Does anyone have any ideas as to what's going on ? -------------------------------------------------------------- Cleaning up the temporary build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ chflags: /usr/obj/usr/src/tmp/usr/lib/aout/libdescrypt.so.2.0: Operation not permitted *** Error code 1 Stop. FreeBSD# uname -a FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Jul 21 09:24:24 EDT 1998 root@FreeBSD.pc.sas.com:/usr/src/sys/compile/FreeBSD i386 FreeBSD# cd /usr/obj/usr/src/tmp/usr/lib/aout/ FreeBSD# ls -lo libdescrypt.so.2.0 -r--r--r-- 1 bin bin schg 16718 Aug 8 02:53 libdescrypt.so.2.0 FreeBSD# rm -f libdescrypt.so.2.0 rm: libdescrypt.so.2.0: Operation not permitted FreeBSD# chflags noschg libdescrypt.so.2.0 chflags: libdescrypt.so.2.0: Operation not permitted The only way I've been able to remove this file is to newfs the filesystem... :-( Note: the above output is without the filesystem being newfs'd before the make. Comments? Critiques? Stupid user problem? Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 23:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15349 for freebsd-current-outgoing; Sun, 9 Aug 1998 23:13:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles217.castles.com [208.214.165.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15344 for ; Sun, 9 Aug 1998 23:13: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 XAA10034; Sun, 9 Aug 1998 23:11:45 -0700 (PDT) Message-Id: <199808100611.XAA10034@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 22:31:01 PDT." <199808100531.WAA09127@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 23:11:45 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > In my kernel config file I have: > > maxusers 30 Probably not enough; what's 'sysctl kern.maxproc' give you? How much stuff do you have running? Come on Amancio; you're hardly a newbie, and this is first-week admin stuff. -- \\ 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 Aug 9 23:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16259 for freebsd-current-outgoing; Sun, 9 Aug 1998 23:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16221 for ; Sun, 9 Aug 1998 23:25:59 -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 JAA14593 for ; Mon, 10 Aug 1998 09:25:24 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id JAA25358 for current@freebsd.org; Mon, 10 Aug 1998 09:23:21 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id JAA07064; Mon, 10 Aug 1998 09:11:24 +0300 (EEST) (envelope-from archer) Date: Mon, 10 Aug 1998 09:11:24 +0300 (EEST) From: Alexander Litvin Message-Id: <199808100611.JAA07064@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Reminder : can't fork X-Newsgroups: grape.freebsd.current In-Reply-To: <199808092253.PAA07594@rah.star-gate.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 <199808092253.PAA07594@rah.star-gate.com> you wrote: AH> Well okay, lets see if others report the same problem. Hmm, description of the problem was quite short, so I didn't understand whether that was notorious "daemons dying". If it is, who said it is gone? And it seemed to me, that agreement was achieved on that it cannot be explained just by memory overcommit. I don't mind if the system kill my processes when out of swap, but why should all forked sendmails get SIGSEGV 8 hours after the "out of swap" condition was gone? It is easy to reproduce. What looks strange to me is the following. I wrote a "dummy" daemon -- just simple prog which daemonised and then periodically forked to do some dummy work. I tought it whould be easier to debug the problem with simple prog. I have not been able to make it fail. Though sendmail and cron still die. What is different between them and my daemon? AH> I will play with my system tonite when I get home from work. AH> Cheers, AH> Amancio --- Unix is the worst operating system; except for all others. -- Berry Kercheval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 23:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17623 for freebsd-current-outgoing; Sun, 9 Aug 1998 23:40:21 -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 XAA17618 for ; Sun, 9 Aug 1998 23:40: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 XAA24146; Sun, 9 Aug 1998 23:39:46 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100639.XAA24146@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 23:11:45 PDT." <199808100611.XAA10034@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 23:39:44 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks Mike I will try to narrow down the bug . Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 9 23:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19098 for freebsd-current-outgoing; Sun, 9 Aug 1998 23:49:52 -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 XAA19092 for ; Sun, 9 Aug 1998 23:49:50 -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 GAA16935; Mon, 10 Aug 1998 06:49:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id IAA10710; Mon, 10 Aug 1998 08:49:22 +0200 (MET DST) Message-ID: <19980810084921.21729@follo.net> Date: Mon, 10 Aug 1998 08:49:21 +0200 From: Eivind Eklund To: Mike Smith , Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: Reminder : can't fork References: <199808091933.MAA07114@rah.star-gate.com> <199808092020.NAA07708@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808092020.NAA07708@antipodes.cdrom.com>; from Mike Smith on Sun, Aug 09, 1998 at 01:20:11PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 09, 1998 at 01:20:11PM -0700, Mike Smith wrote: > > > > Occassionally, my system refuses to fork and pending on what I was doing > > daemons such as sendmail die -- usually this is after I tried to compile > > a big program such as mozilla however I have seen the bug surfaced when > > I think I have not exhausted my swap space unfortunately most of the times > > this happens I am at work and it is really hard to diagnose the problem. > > > > This problem has been around for about 6 months now. > > Pilot error. Your resource limits are too low. Actually, it sound suspiciously like the old 'split page' bug where there would be problems with forking after you had had a swap space exhaustion. This was really easy to repoduce - after you ran out of swap, all daemons would die when they tried to fork. You had to restart them to get them to work again. If this still can happen in some cases, it is _extremely_ important that we get it fixed - IMO, we can't send out 3.0 with this kind of bug in it :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 00:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23453 for freebsd-current-outgoing; Mon, 10 Aug 1998 00:29:56 -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 AAA23448 for ; Mon, 10 Aug 1998 00:29:49 -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 AAA03741; Mon, 10 Aug 1998 00:29:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100729.AAA03741@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Mon, 10 Aug 1998 08:49:21 +0200." <19980810084921.21729@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 00:29:16 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Your bug description sounds very similar to what I am experiencing however I can't reproduce the problem so far. Wrote a short program which allocates memory then touches every page -- repeated the same procedure till I ran out of swap space and the system kills my process which is okay. Daemons seems to stay up so I am going to have to wait till I can reproduce the problem . Regards, Amancio > On Sun, Aug 09, 1998 at 01:20:11PM -0700, Mike Smith wrote: > > > > > > Occassionally, my system refuses to fork and pending on what I was doing > > > daemons such as sendmail die -- usually this is after I tried to compile > > > a big program such as mozilla however I have seen the bug surfaced when > > > I think I have not exhausted my swap space unfortunately most of the times > > > this happens I am at work and it is really hard to diagnose the problem. > > > > > > This problem has been around for about 6 months now. > > > > Pilot error. Your resource limits are too low. > > Actually, it sound suspiciously like the old 'split page' bug where there > would be problems with forking after you had had a swap space exhaustion. > This was really easy to repoduce - after you ran out of swap, all daemons > would die when they tried to fork. You had to restart them to get them to > work again. > > If this still can happen in some cases, it is _extremely_ important that we > get it fixed - IMO, we can't send out 3.0 with this kind of bug in it :-( > > Eivind. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 00:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26084 for freebsd-current-outgoing; Mon, 10 Aug 1998 00:49:59 -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 AAA26075 for ; Mon, 10 Aug 1998 00:49:55 -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 AAA03860; Mon, 10 Aug 1998 00:49:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100749.AAA03860@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Mon, 10 Aug 1998 08:49:21 +0200." <19980810084921.21729@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 00:49:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think the culprit over here is netscape. I just "tuned in" to http://www.abcnews.com/sections/tech/DailyNews/microsoft980806.html A nice java script 8) Since it started this is what vmstat reports: Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 68 188 47620 1280 0 32 278 9834 116316 640 4215 64 5032 1624 3797511 320 205 128 1285 14235 131860 160 12190 256 155 37 1823 80 0 512 4278 42 384183 40 318 1K 207 205 22908 20 861 2K 41 29 602 10 249 4K 15 1 3283 5 0 8K 9 10 343 5 175 16K 9 0 9 5 0 32K 1 0 2 5 0 128K 0 0 37 5 0 Memory usage type by bucket size Size Type(s) 16 shm, sysctl, soname, ether_multi, routetbl, pcb, proc, devbuf, DEVFS mount, temp 32 mkdir, freefile, dirrem, indirdep, freefrag, sysctl, diradd, bmsafemap, soname, in_multi, ether_multi, pgrp, subproc, routetbl, pcb, newblk, vnodes, ifaddr, devbuf, temp, kld 64 allocindir, shm, allocdirect, lockf, file, session, routetbl, pcb, pagedep, namecache, proc, ifaddr, devbuf, DEVFS name, temp 128 VM pgdata, freeblks, soname, zombie, file desc, routetbl, inodedep, namecache, vnodes, cred, ZONE, ttys, ifaddr, DEVFS node, temp 256 VM pgdata, Export Host, file desc, subproc, routetbl, newblk, NFS daemon, NFS srvsock, vnodes, proc, devbuf 512 VM pgdata, ioctlops, FFS node, UFS mount, BIO buffer, NFS daemon, devbuf, mount, temp 1K VM pgdata, BIO buffer, NQNFS Lease, devbuf, temp 2K VM pgdata, UFS mount, BIO buffer, pcb, ttys, devbuf, mbuf 4K VM pgdata, ioctlops, UFS mount, pagedep, devbuf, temp 8K indirdep, VM pgdata, MSDOSFS mount, devbuf, temp 16K UFS ihash, inodedep, NFS hash, ISOFS mount, devbuf 32K VM pgdata, namecache 128K VM pgdata Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mkdir 0 0K 9K 15768K 1748 0 0 32 freefile 0 0K 231K 15768K 10933 0 0 32 dirrem 0 0K 271K 15768K 11501 0 0 32 indirdep 1 1K 105K 15768K 577 0 0 32,8K allocindir 0 0K 28K 15768K 6943 0 0 64 freefrag 0 0K 9K 15768K 6761 0 0 32 shm 1 1K 1K 15768K 8 0 0 16,64 VM pgdata 590 146K 420K 15768K 1039 0 0 128,256,512,1K,2K,4K,8K,32K,128K sysctl 0 0K 1K 15768K 5010 0 0 16,32 allocdirect 0 0K 112K 15768K 26717 0 0 64 freeblks 0 0K 919K 15768K 11015 0 0 128 diradd 0 0K 71K 15768K 11628 0 0 32 bmsafemap 0 0K 2K 15768K 1810 0 0 32 lockf 2 1K 1K 15768K 11746 0 0 64 Export Host 2 1K 1K 15768K 2 0 0 256 soname 19 1K 1K 15768K 15962 0 0 16,32,128 in_multi 4 1K 1K 15768K 4 0 0 32 ether_multi 14 1K 1K 15768K 14 0 0 16,32 ioctlops 0 0K 4K 15768K 6 0 0 512,4K zombie 0 0K 1K 15768K 33608 0 0 128 file 205 13K 16K 15768K 2821029 0 0 64 session 25 2K 2K 15768K 986 0 0 64 pgrp 33 2K 2K 15768K 1882 0 0 32 file desc 61 8K 10K 15768K 33675 0 0 128,256 subproc 69 5K 7K 15768K 35097 0 0 32,256 FFS node 4231 2116K 2144K 15768K 383993 0 0 512 UFS mount 15 29K 29K 15768K 15 0 0 512,2K,4K BIO buffer 217 236K 419K 15768K 13738 0 0 512,1K,2K routetbl 78 11K 14K 15768K 363 0 0 16,32,64,128,256 pcb 36 5K 5K 15768K 2653 0 0 16,32,64,2K UFS ihash 1 16K 16K 15768K 1 0 0 16K newblk 1 1K 1K 15768K 33661 0 0 32,256 inodedep 1 16K 1192K 15768K 41006 0 0 128,16K pagedep 1 4K 52K 15768K 2708 0 0 64,4K NQNFS Lease 1 1K 1K 15768K 1 0 0 1K NFS daemon 5 3K 3K 15768K 5 0 0 256,512 NFS srvsock 2 1K 1K 15768K 2 0 0 256 NFS hash 1 16K 16K 15768K 1 0 0 16K MSDOSFS mount 1 8K 8K 15768K 1 0 0 8K ISOFS mount 1 16K 16K 15768K 1 0 0 16K namecache 4508 314K 414K 15768K 933316 0 0 64,128,32K vnodes 54 7K 24K 15768K 1269 0 0 32,128,256 cred 20 3K 5K 15768K 3810 0 0 128 ZONE 17 3K 3K 15768K 17 0 0 128 proc 7 1K 1K 15768K 8 0 0 16,64,256 ttys 442 59K 64K 15768K 1300 0 0 128,2K ifaddr 17 2K 2K 15768K 17 0 0 32,64,128 devbuf 101 166K 166K 15768K 161 0 0 16,32,64,256,512,1K,2K,4K,8K,16K DEVFS mount 1 1K 1K 15768K 1 0 0 16 mount 7 4K 4K 15768K 7 0 0 512 DEVFS name 265 17K 17K 15768K 305 0 0 64 DEVFS node 243 31K 31K 15768K 283 0 0 128 mbuf 1 2K 2K 15768K 1 0 0 2K temp 76 6K 15K 15768K 38151 0 0 16,32,64,128,512,1K,4K,8K kld 1 1K 1K 15768K 1 0 0 32 Memory Totals: In Use Free Requests 3260K 2569K 4506497 after a few minutes I get: Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 67 189 47701 1280 0 32 275 9837 116621 640 4268 64 5027 1629 3798419 320 205 128 1286 14234 132021 160 12236 256 151 41 1827 80 0 512 4274 46 384227 40 318 1K 207 205 22915 20 861 2K 41 29 602 10 249 4K 15 1 3285 5 0 8K 9 10 345 5 177 16K 9 0 9 5 0 32K 1 0 2 5 0 128K 0 0 37 5 0 Memory usage type by bucket size Size Type(s) 16 shm, sysctl, soname, ether_multi, routetbl, pcb, proc, devbuf, DEVFS mount, temp 32 mkdir, freefile, dirrem, indirdep, freefrag, sysctl, diradd, bmsafemap, soname, in_multi, ether_multi, pgrp, subproc, routetbl, pcb, newblk, vnodes, ifaddr, devbuf, temp, kld 64 allocindir, shm, allocdirect, lockf, file, session, routetbl, pcb, pagedep, namecache, proc, ifaddr, devbuf, DEVFS name, temp 128 VM pgdata, freeblks, soname, zombie, file desc, routetbl, inodedep, namecache, vnodes, cred, ZONE, ttys, ifaddr, DEVFS node, temp 256 VM pgdata, Export Host, file desc, subproc, routetbl, newblk, NFS daemon, NFS srvsock, vnodes, proc, devbuf 512 VM pgdata, ioctlops, FFS node, UFS mount, BIO buffer, NFS daemon, devbuf, mount, temp 1K VM pgdata, BIO buffer, NQNFS Lease, devbuf, temp 2K VM pgdata, UFS mount, BIO buffer, pcb, ttys, devbuf, mbuf 4K VM pgdata, ioctlops, UFS mount, pagedep, devbuf, temp 8K indirdep, VM pgdata, MSDOSFS mount, devbuf, temp 16K UFS ihash, inodedep, NFS hash, ISOFS mount, devbuf 32K VM pgdata, namecache 128K VM pgdata Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mkdir 0 0K 9K 15768K 1748 0 0 32 freefile 0 0K 231K 15768K 10939 0 0 32 dirrem 0 0K 271K 15768K 11513 0 0 32 indirdep 0 0K 105K 15768K 581 0 0 32,8K allocindir 0 0K 28K 15768K 7035 0 0 64 freefrag 0 0K 9K 15768K 6790 0 0 32 shm 1 1K 1K 15768K 8 0 0 16,64 VM pgdata 590 146K 420K 15768K 1039 0 0 128,256,512,1K,2K,4K,8K,32K,128K sysctl 0 0K 1K 15768K 5011 0 0 16,32 allocdirect 1 1K 112K 15768K 26789 0 0 64 freeblks 0 0K 919K 15768K 11029 0 0 128 diradd 0 0K 71K 15768K 11642 0 0 32 bmsafemap 0 0K 2K 15768K 1823 0 0 32 lockf 2 1K 1K 15768K 11788 0 0 64 Export Host 2 1K 1K 15768K 2 0 0 256 soname 19 1K 1K 15768K 16030 0 0 16,32,128 in_multi 4 1K 1K 15768K 4 0 0 32 ether_multi 14 1K 1K 15768K 14 0 0 16,32 ioctlops 0 0K 4K 15768K 6 0 0 512,4K zombie 0 0K 1K 15768K 33655 0 0 128 file 205 13K 16K 15768K 2821662 0 0 64 session 25 2K 2K 15768K 990 0 0 64 pgrp 33 2K 2K 15768K 1897 0 0 32 file desc 61 8K 10K 15768K 33722 0 0 128,256 subproc 69 5K 7K 15768K 35147 0 0 32,256 FFS node 4227 2114K 2144K 15768K 384037 0 0 512 UFS mount 15 29K 29K 15768K 15 0 0 512,2K,4K BIO buffer 217 236K 419K 15768K 13738 0 0 512,1K,2K routetbl 70 10K 14K 15768K 365 0 0 16,32,64,128,256 pcb 35 5K 5K 15768K 2665 0 0 16,32,64,2K UFS ihash 1 16K 16K 15768K 1 0 0 16K newblk 1 1K 1K 15768K 33825 0 0 32,256 inodedep 2 17K 1192K 15768K 41032 0 0 128,16K pagedep 1 4K 52K 15768K 2716 0 0 64,4K NQNFS Lease 1 1K 1K 15768K 1 0 0 1K NFS daemon 5 3K 3K 15768K 5 0 0 256,512 NFS srvsock 2 1K 1K 15768K 2 0 0 256 NFS hash 1 16K 16K 15768K 1 0 0 16K MSDOSFS mount 1 8K 8K 15768K 1 0 0 8K ISOFS mount 1 16K 16K 15768K 1 0 0 16K namecache 4502 314K 414K 15768K 933373 0 0 64,128,32K vnodes 54 7K 24K 15768K 1269 0 0 32,128,256 cred 20 3K 5K 15768K 3837 0 0 128 ZONE 17 3K 3K 15768K 17 0 0 128 proc 7 1K 1K 15768K 8 0 0 16,64,256 ttys 442 59K 64K 15768K 1300 0 0 128,2K ifaddr 17 2K 2K 15768K 17 0 0 32,64,128 devbuf 101 166K 166K 15768K 161 0 0 16,32,64,256,512,1K,2K,4K,8K,16K DEVFS mount 1 1K 1K 15768K 1 0 0 16 mount 7 4K 4K 15768K 7 0 0 512 DEVFS name 265 17K 17K 15768K 305 0 0 64 DEVFS node 243 31K 31K 15768K 283 0 0 128 mbuf 1 2K 2K 15768K 1 0 0 2K temp 78 6K 15K 15768K 38162 0 0 16,32,64,128,512,1K,4K,8K kld 1 1K 1K 15768K 1 0 0 32 Memory Totals: In Use Free Requests 3257K 2572K 4508011 Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 01:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01242 for freebsd-current-outgoing; Mon, 10 Aug 1998 01:36:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01237 for ; Mon, 10 Aug 1998 01:36:36 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id KAA19797; Mon, 10 Aug 1998 10:36:11 +0200 (MET DST) Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Mon, 10 Aug 1998 10:36:11 +0200 (MET DST) Mime-Version: 1.0 To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: chflags: <> Operation not permitted References: <199808100548.AA08376@mozart> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Aug 1998 10:36:10 +0200 In-Reply-To: "John W. DeBoskey"'s message of "Mon, 10 Aug 1998 01:48:30 -0400 (EDT)" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA01238 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" writes: > -------------------------------------------------------------- > Cleaning up the temporary build tree > -------------------------------------------------------------- > mkdir -p /usr/obj/usr/src/tmp > chflags -R noschg /usr/obj/usr/src/tmp/ > chflags: /usr/obj/usr/src/tmp/usr/lib/aout/libdescrypt.so.2.0: Operation not permitted > *** Error code 1 > > Stop. > What does 'ls -loF /usr/obj/usr/src/tmp/usr/lib/aout/libdes*' say? Which user does make world run as? DES -- Dag-Erling SmЬrgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 01:59:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04922 for freebsd-current-outgoing; Mon, 10 Aug 1998 01:59:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from meta.sub.org (lance.pond.sub.org [192.129.33.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04897 for ; Mon, 10 Aug 1998 01:59:24 -0700 (PDT) (envelope-from armin@meta.sub.org) Received: (from armin@localhost) by meta.sub.org (8.8.8/8.8.8) id KAA00409; Mon, 10 Aug 1998 10:59:02 +0200 (CEST) (envelope-from armin) Date: Mon, 10 Aug 1998 10:59:02 +0200 (CEST) From: Armin Arh Message-Id: <199808100859.KAA00409@meta.sub.org> To: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: chflags: <> Operation not permitted Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD# uname -a > FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Jul 21 09:24:24 EDT 1998 root@FreeBSD.pc.sas.com:/usr/src/sys/compile/FreeBSD i386 > FreeBSD# cd /usr/obj/usr/src/tmp/usr/lib/aout/ > FreeBSD# ls -lo libdescrypt.so.2.0 > -r--r--r-- 1 bin bin schg 16718 Aug 8 02:53 libdescrypt.so.2.0 > FreeBSD# rm -f libdescrypt.so.2.0 > rm: libdescrypt.so.2.0: Operation not permitted > FreeBSD# chflags noschg libdescrypt.so.2.0 > chflags: libdescrypt.so.2.0: Operation not permitted This is normal, if your securelevel is higher then 0. Check this out by typing: # sysctl kern.securelevel While booting, the securelevel is raised, depending on your configuration (/etc/rc.conf?). Once raised, there is no chance to lower it, or to remove the schg- flag. Armin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 02:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11144 for freebsd-current-outgoing; Mon, 10 Aug 1998 02:40:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11116 for ; Mon, 10 Aug 1998 02:40:08 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id JAA16002; Mon, 10 Aug 1998 09:52:02 +0100 (BST) Message-ID: <35CEB4B2.A12C18CD@tdx.co.uk> Date: Mon, 10 Aug 1998 09:52:02 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "John W. DeBoskey" CC: freebsd-current@FreeBSD.ORG Subject: Re: chflags: <> Operation not permitted References: <199808100548.AA08376@mozart> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote: > > Hi, > > I've been getting the following error for a little over a week > now during my nightly build.. Does anyone have any ideas as to > what's going on ? The latest -CURRENT automatically raises the kernel security level after booting, this means you can only do some operations (e.g. types of chflags) when in single user mode (when the secure level is -1 ;_) Have a look at /etc/rc " if [ "X${kern_securelevel_enable}" != X"NO" -a "${kern_securelevel}" -ge 0 ]; then echo 'Raising kernel security level' sysctl -w kern.securelevel=${kern_securelevel} fi " Putting: kern_securelevel_enable="NO" Into your /etc/rc.conf should do the trick... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 03:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18785 for freebsd-current-outgoing; Mon, 10 Aug 1998 03:33:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18778 for ; Mon, 10 Aug 1998 03:33:10 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from gladsheim.ifi.uio.no (2602@gladsheim.ifi.uio.no [129.240.64.132]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA00514; Mon, 10 Aug 1998 12:32:45 +0200 (MET DST) Received: (from dag-erli@localhost) by gladsheim.ifi.uio.no ; Mon, 10 Aug 1998 12:32:44 +0200 (MET DST) Mime-Version: 1.0 To: Armin Arh Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: chflags: <> Operation not permitted References: <199808100859.KAA00409@meta.sub.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Aug 1998 12:32:43 +0200 In-Reply-To: Armin Arh's message of "Mon, 10 Aug 1998 10:59:02 +0200 (CEST)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA18779 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Armin Arh writes: > While booting, the securelevel is raised, depending on your It normally isn't (it defaults to -1, which means "always run at securelevel 0") DES -- Dag-Erling SmЬrgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 03:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20899 for freebsd-current-outgoing; Mon, 10 Aug 1998 03:50:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20828 for ; Mon, 10 Aug 1998 03:49:59 -0700 (PDT) (envelope-from archer@lucky.net) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) id NAA09982 for current@freebsd.org; Mon, 10 Aug 1998 13:49:35 +0300 (EEST) Message-ID: <19980810134934.A6840@burka.carrier.kiev.ua> Date: Mon, 10 Aug 1998 13:49:35 +0300 From: Alexander Litvin To: current@FreeBSD.ORG Subject: Re: New softupdates code panics References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: ; from Brian Feldman on Sun, Aug 09, 1998 at 09:56:19AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Brian Feldman! In message about "New softupdates code panics" on Sun, Aug 09, 1998, at 09:56:19 AM you wrote: > Well, I had patched my ffs_softdep.c and my ufs_vnops.c according to > Luoqi and Kirk's patches and soon after rebooting, I got a panic (I don't > think I was removing anything at the time, but oh well there are other > processes than the ones I watch). I've still got the full debugging kernel > and a core dump, so if anyone wants more just ask. The same here. My system paniced two times for some 4 hours after I've booted kernel with Kirk's patches. The system was not very busy, just ordinary mail/news reception (it is home computer). Here's my backtrace: (kgdb) exec-file /var/crash/kernel.1 (kgdb) symbol-file /var/crash/kernel.debug.0 Reading symbols from /var/crash/kernel.debug.0...done. (kgdb) core-file /var/crash/vmcore.0 IdlePTD 2236416 initial pcb at 1d2304 panicstr: handle_workitem_remove: bad dir delta panic messages: --- panic: handle_workitem_remove: bad dir delta syncing disks... 32 31 28 23 13 2 done dumping to dev 20001, offset 196608 dump 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 286 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf01149e7 in panic ( fmt=0xf017a1dc "handle_workitem_remove: bad dir delta") at ../../kern/kern_shutdown.c:427 #2 0xf017a2b2 in handle_workitem_remove (dirrem=0xf04daa80) at ../../ufs/ffs/ffs_softdep.c:2560 #3 0xf0177729 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:534 #4 0xf0133b46 in sched_sync () at ../../kern/vfs_subr.c:977 #5 0xf010846e in kproc_start (udata=0xf01c8264) at ../../kern/init_main.c:245 #6 0xf019c4d0 in fork_trampoline () #7 0x66da89f0 in ?? () Cannot access memory at address 0x19c410bb. > Cheers, > Brian Feldman > green@unixhelp.com > P.S. This is the first softupdates panic I've had in a _long_ time, so > good job you guys! --- Fairy Tale, n.: A horror story to prepare children for the newspapers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 04:50:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27625 for freebsd-current-outgoing; Mon, 10 Aug 1998 04:50:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ishtar (dialup09.wr.com.au [203.27.69.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA27611 for ; Mon, 10 Aug 1998 04:50:24 -0700 (PDT) (envelope-from davidh@wr.com.au) Received: (qmail 3276 invoked by uid 1411); 10 Aug 1998 11:52:00 -0000 Message-ID: <19980810215200.33285@wr.com.au> Date: Mon, 10 Aug 1998 21:52:00 +1000 From: David Hobley To: Amancio Hasty , Eivind Eklund Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork References: <19980810084921.21729@follo.net> <199808100749.AAA03860@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808100749.AAA03860@rah.star-gate.com>; from Amancio Hasty on Mon, Aug 10, 1998 at 12:49:21AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 10, 1998 at 12:49:21AM -0700, Amancio Hasty wrote: > Hi, > > I think the culprit over here is netscape. I just "tuned in" to > http://www.abcnews.com/sections/tech/DailyNews/microsoft980806.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message FWIW, I have noticed on 3.0 -current: [8 ishtar: /home/davidh] % uname -a FreeBSD ishtar 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Wed Aug 5 08:53:19 EST 1998 davidh@ishtar:/usr/src/sys/compile/ISHTAR i386 with a kern.maxproc of 180 that if I leave Netscape 4.5 up for any length of time I get a situation where all new (non cache?) processes segmentation fault. (ie. su, csh etc) If I don't run Netscape I get uptime of more than a few days. This is under X, but I can't seem to get Ctrl-Alt-F1 to get back to the console to see if there are any further diagnostics. -- Cheers, david -- http://www.angelfire.com/wa/hobley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 06:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12730 for freebsd-current-outgoing; Mon, 10 Aug 1998 06:53:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12725 for ; Mon, 10 Aug 1998 06:53:20 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id JAA13045 for ; Mon, 10 Aug 1998 09:53:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 10 Aug 1998 09:53:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: questions about DEVFS 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 heh, the man page for devfs is quite terse but i tried it anyhow. options DEVFS options SLICE problems i had: my scsi disk is detected however no DEVFS entry is made. (my boot disk is an IDE drive) i don't think my sound device was found. questions: how can i make symlinks in it? ( i really didn't try yet, but i'd like to have /dev/mouse -> /dev/cuaa0 and whatnot ) is devfs considered stable? it doesn't seem that usable in it's current state, but i'm assuming it's operator error ;) thanks, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Mon Aug 10 07:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16175 for freebsd-current-outgoing; Mon, 10 Aug 1998 07:30:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16165 for ; Mon, 10 Aug 1998 07:30:09 -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 KAA31768; Mon, 10 Aug 1998 10:26:52 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Mon, 10 Aug 1998 10:26:52 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Mike Smith cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-Reply-To: <199808100522.WAA09698@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 Hmmm, do you have any idea what errno is being set to after the problem occurs? That could point to a reason. After fork() (and many other functions) fail, they set the variable errno to the error that they've hit. `man fork` for details. /* ** Matt Harris Syko ** BPSOFH, BIOFH, C, SQL, PERL http://www.sykotik.org/~syko/ ** FreeBSD SysAdmin sykotik.org ** IRC TechnoNet - dark.technonet.net Cabalnet - dark-temple.cabalnet.org ** "Those who are right in the mind are left in the dust." -- Me. */ On Sun, 9 Aug 1998, Mike Smith wrote: > > Pilot error is for sure a possibility however it does not explain why > > sendmail dies when I am compiling mozilla from my account. I think that > > this problem has been reported by other users. > > "Cannot fork" is either "too many processess (for you or the system in > toto)" or some other resource starvation. > > If you're not out of memory or file descriptors, then you've hit the > limit on the maximum number of processes. > > Let's guess that this is a FAQ; what is the value of 'maxusers' in your > kernel config? > > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 08:57:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23958 for freebsd-current-outgoing; Mon, 10 Aug 1998 08:57:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles176.castles.com [208.214.165.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23950 for ; Mon, 10 Aug 1998 08:57:56 -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 IAA12351; Mon, 10 Aug 1998 08:56:24 -0700 (PDT) Message-Id: <199808101556.IAA12351@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: questions about DEVFS In-reply-to: Your message of "Mon, 10 Aug 1998 09:53:51 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 08:56:24 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > heh, the man page for devfs is quite terse but i tried it anyhow. > > options DEVFS > options SLICE > > problems i had: > > my scsi disk is detected however no DEVFS entry is made. (my boot disk is > an IDE drive) You need to look at the noise that SLICE makes when you're booting to see why it didn't find anything. > i don't think my sound device was found. Hassle Luigi about that; I don't think he's playing the DEVFA game yet. > questions: > > how can i make symlinks in it? ( i really didn't try yet, but i'd like to > have /dev/mouse -> /dev/cuaa0 and whatnot ) 'ln -s' > is devfs considered stable? it doesn't seem that usable in it's current > state, but i'm assuming it's operator error ;) Works fine here, and for lots of other people. -- \\ 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 Aug 10 09:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27225 for freebsd-current-outgoing; Mon, 10 Aug 1998 09:24:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles176.castles.com [208.214.165.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27191 for ; Mon, 10 Aug 1998 09:24:48 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA12534; Mon, 10 Aug 1998 09:22:36 -0700 (PDT) Message-Id: <199808101622.JAA12534@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: joelh@gnu.org cc: mike@smith.net.au, ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-reply-to: Your message of "Sun, 09 Aug 1998 15:46:37 CDT." <199808092046.PAA03447@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 09:22:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> This suggestion hasn't been carefully considered or tested, but if you > >> want to fix it yourself, then in /sys/i386/boot/biosboot/boot.c, move > >> the bit about "loadflags &= (RB_DUAL | RB_SERIAL);" to right around > >> "readfile("boot.config", ...);" about 40 lines up. (The key is that > >> it should be before "getbootdev(boot_config, &loadflags);".) This > >> will effectively allow any boot flags in. > > It will become either "-v" in /boot.config or "set bootverbose" in > > the new bootstrap config, which I haven't named. > > And this is a handy topic to raise it under; the new bootstrap will > > (optionally) need access to quite a few files, and we may not really > > want these cluttering up the root directory. How do people feel about > > a /boot directory these days? > > If you're reworking the bootstrap, is it worth me submitting a pr with > this patch? (I'm implementing it locally anyway.) By all means. It's never a good idea to lose information, even if you're not going to use it straight away. -- \\ 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 Aug 10 10:36:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07483 for freebsd-current-outgoing; Mon, 10 Aug 1998 10:36:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA07469 for ; Mon, 10 Aug 1998 10:36:48 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 5720 invoked from network); 10 Aug 1998 17:36:07 -0000 Received: from userb125.uk.uudial.com (HELO k2c.co.uk) (193.149.71.108) by smtp.dial.pipex.com with SMTP; 10 Aug 1998 17:36:07 -0000 Message-ID: <35CF2ED0.F5DB8D93@k2c.co.uk> Date: Mon, 10 Aug 1998 18:33:04 +0100 From: "Pierre Y. Dampure" Organization: K2C Limited X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: Failing to build Modula-3 port under SMP-current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few months ago, I posted reports of problems encountered while building the Modula-3 port under SMP-current (the port built perfectly OK on a non-SMP kernel, but quake aborted while building the libarries). John Polstra and John Dyson both got involved and I ended up trying the various SMP patches John Dyson released at the time -- to no avail. The situation is still the same today (I just retried a build on an SMP-current CVSup'd yesterday). I'm more than willing to help, but will require a few directions as to what to look for. I didn't post a PR for this one, maybe it's time I did... Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 10:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08081 for freebsd-current-outgoing; Mon, 10 Aug 1998 10:40:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08074 for ; Mon, 10 Aug 1998 10:40: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 UAA16852 for ; Mon, 10 Aug 1998 20:24:37 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id UAA14758 for current@freebsd.org; Mon, 10 Aug 1998 20:21:10 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id UAA06899; Mon, 10 Aug 1998 20:15:52 +0300 (EEST) (envelope-from archer) Date: Mon, 10 Aug 1998 20:15:52 +0300 (EEST) From: Alexander Litvin Message-Id: <199808101715.UAA06899@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Reminder : can't fork X-Newsgroups: grape.freebsd.current In-Reply-To: <199808091933.MAA07114@rah.star-gate.com> <199808092020.NAA07708@antipodes.cdrom.com> <19980810084921.21729@follo.net> 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 <19980810084921.21729@follo.net> you wrote: EE> On Sun, Aug 09, 1998 at 01:20:11PM -0700, Mike Smith wrote: >> > >> > Occassionally, my system refuses to fork and pending on what I was doing >> > daemons such as sendmail die -- usually this is after I tried to compile >> > a big program such as mozilla however I have seen the bug surfaced when >> > I think I have not exhausted my swap space unfortunately most of the times >> > this happens I am at work and it is really hard to diagnose the problem. >> > >> > This problem has been around for about 6 months now. >> >> Pilot error. Your resource limits are too low. EE> Actually, it sound suspiciously like the old 'split page' bug where there EE> would be problems with forking after you had had a swap space exhaustion. EE> This was really easy to repoduce - after you ran out of swap, all daemons EE> would die when they tried to fork. You had to restart them to get them to EE> work again. I'm as sure as hell this bug is still in CURRENT. Everybody can see it himself. It ease easy to exhaust one's swap. If after that at list in 50% of cases forked sendmails don't die with SIGSEGV I'll eat my heat. EE> If this still can happen in some cases, it is _extremely_ important that we EE> get it fixed - IMO, we can't send out 3.0 with this kind of bug in it :-( EE> Eivind. --- Happiness, n.: An agreeable sensation arising from contemplating the misery of another. -- Ambrose Bierce, "The Devil's Dictionary" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 11:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13337 for freebsd-current-outgoing; Mon, 10 Aug 1998 11:24:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13318 for ; Mon, 10 Aug 1998 11:24:24 -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 VAA20963 for ; Mon, 10 Aug 1998 21:23:58 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id VAA26682 for current@freebsd.org; Mon, 10 Aug 1998 21:21:05 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id VAA07767; Mon, 10 Aug 1998 21:01:00 +0300 (EEST) (envelope-from archer) Date: Mon, 10 Aug 1998 21:01:00 +0300 (EEST) From: Alexander Litvin Message-Id: <199808101801.VAA07767@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Reminder : can't fork X-Newsgroups: grape.freebsd.current In-Reply-To: <199808100729.AAA03741@rah.star-gate.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 <199808100729.AAA03741@rah.star-gate.com> you wrote: AH> Hi, AH> Your bug description sounds very similar to what I am experiencing AH> however I can't reproduce the problem so far. Wrote a short program AH> which allocates memory then touches every page -- repeated the AH> same procedure till I ran out of swap space and the system kills AH> my process which is okay. Have a simple way to reproduce the problem. For me it is like that. I have 32M RAM + 128M swap. I have a simple prog which just allocs 32M of mem and "touches" it: ---------------------------------------------------------- #include #include #define MEMSIZE 33554432 int main() { int i; char* buf; buf=malloc(MEMSIZE); if(buf==NULL) { printf("Can't alloc mem\n"); exit(1); } else for(i=0;i Daemons seems to stay up so I am going to have to wait till AH> I can reproduce the problem . AH> Regards, AH> Amancio --- Misfortune, n.: The kind of fortune that never misses. -- Ambrose Bierce, "The Devil's Dictionary" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 11:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16243 for freebsd-current-outgoing; Mon, 10 Aug 1998 11:52:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--162.sirius.net [205.134.241.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16221 for ; Mon, 10 Aug 1998 11:52:16 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id LAA00615 for ; Mon, 10 Aug 1998 11:51:55 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808101851.LAA00615@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: A couple of low-level (non-CAM) SCSI subsystem problems X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 11:51:54 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just moved my UMAX 600S scanner from my Mac to FreeBSD 3.0-CURRENT without CAM. It works with the latest sane-0.74 code (which is not yet a port - 0.73 does not work properly for this scanner). Anyway, I started getting a lot (20-50) of these errors from the SCSI subsystem in the kernel whenever it scans an image: uk1: unknown error category from host adapter code After some debug-printfs, this is due to a select-timeout (XS_SELTIMEOUT) presumably because the scanner is busy moving its scan head back to the top or doing other house-keeping, and it isn't sending back a proper busy code. A quick-n-dirty patch to scsi/scsi_ioctl.c seems to eliminate this message without causing any other effects: =================================================================== RCS file: /src/freebsd/src/sys/scsi/scsi_ioctl.c,v retrieving revision 1.31 diff -c -r1.31 scsi_ioctl.c *** scsi_ioctl.c 1998/06/07 17:12:49 1.31 --- scsi_ioctl.c 1998/08/10 18:23:41 *************** *** 121,126 **** --- 121,127 ---- break; case XS_TIMEOUT: + case XS_SELTIMEOUT: SC_DEBUG(xs->sc_link,SDEV_DB3,("timeout\n")); screq->retsts = SCCMD_TIMEOUT; break; =================================================================== Is this OK, or is there a better fix (ie switch to CAM)? The second problem is during boot-up. If the scanner is powered on during boot, FreeBSD seems to think the scanner is at every SCSI address. However, if I leave it powered offduring boot, then do a "scsi -r" after the system is running, it probes the scanner properly (at SCSI ID 4) with no bogus extra LUNs. ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 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 4134MB (8467200 512 byte sectors) ahc0:A:1: refuses WIDE negotiation. Using 8bit transfers sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 3067MB (6281856 512 byte sectors) ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers ahc0:A:4: refuses synchronous negotiation. Using asynchronous transfers uk0 at scbus0 target 4 lun 0 uk0: type 6 fixed SCSI 2 uk0: Unknown uk1 at scbus0 target 4 lun 1 uk1: type 6 fixed SCSI 2 uk1: Unknown uk2 at scbus0 target 4 lun 2 uk2: type 6 fixed SCSI 2 uk2: Unknown uk3 at scbus0 target 4 lun 3 uk3: type 6 fixed SCSI 2 uk3: Unknown uk4 at scbus0 target 4 lun 4 uk4: type 6 fixed SCSI 2 uk4: Unknown uk5 at scbus0 target 4 lun 5 uk5: type 6 fixed SCSI 2 uk5: Unknown uk6 at scbus0 target 4 lun 6 uk6: type 6 fixed SCSI 2 uk6: Unknown uk7 at scbus0 target 4 lun 7 uk7: type 6 fixed SCSI 2 uk7: Unknown ahc0:A:6: refuses WIDE negotiation. Using 8bit transfers uk8 at scbus0 target 6 lun 0 uk8: type 4 removable SCSI 2 uk8: Unknown Perhaps the workaround is to simply switch to CAM? Since CAM isn't the default yet, I was wondering if I should send-pr these two problems or not. Thanks in advance! -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 12:31:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20762 for freebsd-current-outgoing; Mon, 10 Aug 1998 12:31:56 -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 MAA20753 for ; Mon, 10 Aug 1998 12:31:55 -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 MAA08223; Mon, 10 Aug 1998 12:31:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808101931.MAA08223@rah.star-gate.com> To: Alexander Litvin cc: current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Reminder : can't fork In-reply-to: Your message of "Mon, 10 Aug 1998 21:01:00 +0300." <199808101801.VAA07767@grape.carrier.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8220.902777480.1@rah.star-gate.com> Date: Mon, 10 Aug 1998 12:31:20 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good I am glad that someone else managed to reproduce the problem. Will try again tonite. Basically, I have a program very similar to yours however I ran it only once instead of trying to run multiple copies of the program in a loop. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 12:45:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22543 for freebsd-current-outgoing; Mon, 10 Aug 1998 12:45:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jump.azeri.com (jump.azeri.com [208.210.122.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22532 for ; Mon, 10 Aug 1998 12:45:39 -0700 (PDT) (envelope-from mirlok@twin.ab.az) Received: from twin.ab.az ([208.210.122.71]) by jump.azeri.com (8.7.3/8.7.3) with SMTP id AAA09488 for ; Tue, 11 Aug 1998 00:47:22 +0500 (BSD) Received: from [194.27.4.200] by twin.ab.az (5.x/SMI-SVR4) id AA15650; Tue, 11 Aug 1998 00:44:48 -0400 Message-Id: <35CF5BFC.80556FEF@twin.ab.az> Date: Tue, 11 Aug 1998 00:45:48 +0400 From: Mirlok X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: Secondary master & boot manager? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I want to install FreeBSD 2.2.7 on the secondary master. When I tried to do it i've got normal win95 start up from my primary master. The boot manager appears only when I make my FreeBSD drive a primary master. How can I install it on secondary so, that I could have a choise whether start my win95 from primary drive or msdos or FreeBSD from seconadary? Thank you very much! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 12:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24226 for freebsd-current-outgoing; Mon, 10 Aug 1998 12:58:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24216 for ; Mon, 10 Aug 1998 12:58:12 -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 PAA109492; Mon, 10 Aug 1998 15:57:58 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <35CF2ED0.F5DB8D93@k2c.co.uk> Date: Mon, 10 Aug 1998 16:01:56 -0400 To: "Pierre Y. Dampure" , FreeBSD-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Failing to build Modula-3 port under SMP-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:33 PM +0100 8/10/98, Pierre Y. Dampure wrote: > A few months ago, I posted reports of problems encountered while > building the Modula-3 port under SMP-current (the port built perfectly > OK on a non-SMP kernel, but quake aborted while building the libarries). > John Polstra and John Dyson both got involved and I ended up trying the > various SMP patches John Dyson released at the time -- to no avail. > > The situation is still the same today (I just retried a build on an > SMP-current CVSup'd yesterday). I'm more than willing to help, but will > require a few directions as to what to look for. > > I didn't post a PR for this one, maybe it's time I did... I noticed this too, with some snap I tried in July, and then again after I did a 'make world' to current as of August 1st or so. The first time I figured it was something I had hosed up (and besides, I didn't save the error message from modula-3), but when it happened again in August I did file a PR for it. I believe it's PR = ports/7468 Other than this one problem with building modula-3, the SMP kernel I have has worked fine for everything else I've done on the machine. As to modula-3, I just reboot into a single-CPU kernel to make it and cvsup, and the results also seem to work OK. --- 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 Mon Aug 10 14:35:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04250 for freebsd-current-outgoing; Mon, 10 Aug 1998 14:35:06 -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 OAA04238 for ; Mon, 10 Aug 1998 14:35:01 -0700 (PDT) (envelope-from <@eecis.udel.edu:alexandr@ren.eecis.udel.edu>) Received: from localhost by eecis.udel.edu id aa28145; 10 Aug 1998 17:34 EDT To: freebsd-current@FreeBSD.ORG Subject: ALTQ and DEVFS Organization: Mos Eisley Candy Store Reply-To: alexandr@louie.udel.edu Date: Mon, 10 Aug 1998 17:34:36 -0400 From: Jerry Alexandratos Message-ID: <199808101734.aa28145@eecis.udel.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do I create the devices for ALTQ when using DEVFS/SLICE? I thought that they would be automagically created by devfs. Thanks. --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 Mon Aug 10 14:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06797 for freebsd-current-outgoing; Mon, 10 Aug 1998 14:59:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06789 for ; Mon, 10 Aug 1998 14:59:42 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.8.8/8.8.8) with SMTP id RAA00872 for ; Mon, 10 Aug 1998 17:59:58 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 10 Aug 1998 17:59:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: KERNFS and MFS 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 2 ideas: add mfs to sysinstall options (visible so as to encourage use for /tmp) the reason is that it can provide a huge speed increase if used properly KERNFS urm... this works, why is not used/installed by default? Thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Mon Aug 10 15:02:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07202 for freebsd-current-outgoing; Mon, 10 Aug 1998 15:02:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07194 for ; Mon, 10 Aug 1998 15:02:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA23076; Mon, 10 Aug 1998 17:00:31 -0500 (EST) (envelope-from toor) Message-Id: <199808102200.RAA23076@dyson.iquest.net> Subject: Re: Reminder : can't fork In-Reply-To: <199808092227.PAA21586@usr04.primenet.com> from Terry Lambert at "Aug 9, 98 10:27:23 pm" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 10 Aug 1998 17:00:31 -0500 (EST) Cc: hasty@rah.star-gate.com, mike@smith.net.au, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 Terry Lambert said: > > Pilot error is for sure a possibility however it does not explain why > > sendmail dies when I am compiling mozilla from my account. I think that > > this problem has been reported by other users. > > If you control-alt-F1 over to the console, is it asking for more swap, > or not? > > If so, it's pilot error. If not, it's a bug or it's bad RAM or overclocking. > > > Given the recent high level of VM instability, it's very hard to > discount the "bug theory". 8-(. > If the problems persist, I'll try to look at them in the next few months. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 15:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11283 for freebsd-current-outgoing; Mon, 10 Aug 1998 15:40:36 -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 PAA11277 for ; Mon, 10 Aug 1998 15:40:34 -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 PAA08708; Mon, 10 Aug 1998 15:39:34 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808102239.PAA08708@rah.star-gate.com> To: dyson@iquest.net cc: tlambert@primenet.com (Terry Lambert), hasty@rah.star-gate.com, mike@smith.net.au, current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Reminder : can't fork In-reply-to: Your message of "Mon, 10 Aug 1998 17:00:31 CDT." <199808102200.RAA23076@dyson.iquest.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8705.902788774.1@rah.star-gate.com> Date: Mon, 10 Aug 1998 15:39:34 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, if you can download the latest release, exercise, and report back it will be of immense help. The same goes to the rest of the group . I just want to avoid the scenario in which 3.0 gets released and then bug reports starts flying by 8) In my case , it is not a big deal because usually I just keep updating even after an official release. Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 15:46:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12225 for freebsd-current-outgoing; Mon, 10 Aug 1998 15:46:14 -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 PAA12214 for ; Mon, 10 Aug 1998 15:46:13 -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 PAA00405; Mon, 10 Aug 1998 15:44:39 -0700 (PDT) Message-Id: <199808102244.PAA00405@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: alexandr@louie.udel.edu cc: freebsd-current@FreeBSD.ORG Subject: Re: ALTQ and DEVFS In-reply-to: Your message of "Mon, 10 Aug 1998 17:34:36 EDT." <199808101734.aa28145@eecis.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 15:44:39 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How do I create the devices for ALTQ when using DEVFS/SLICE? I thought > that they would be automagically created by devfs. Fix ALTQ so that it creates them. -- \\ 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 Aug 10 16:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16280 for freebsd-current-outgoing; Mon, 10 Aug 1998 16:16:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16275 for ; Mon, 10 Aug 1998 16:16:39 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA23222; Mon, 10 Aug 1998 18:15:22 -0500 (EST) (envelope-from toor) Message-Id: <199808102315.SAA23222@dyson.iquest.net> Subject: Re: Reminder : can't fork In-Reply-To: <199808102239.PAA08708@rah.star-gate.com> from Amancio Hasty at "Aug 10, 98 03:39:34 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Mon, 10 Aug 1998 18:15:22 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, hasty@rah.star-gate.com, mike@smith.net.au, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 Amancio Hasty said: > Actually, if you can download the latest release, exercise, and > report back it will be of immense help. > > The same goes to the rest of the group . I just want to avoid the > scenario in which 3.0 gets released and then bug reports starts > flying by 8) > I won't have time for a while. Will also look into merging in some necessary fixes (if they aren't in there, there is little reason to exhaustively excercise the code.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 17:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28590 for freebsd-current-outgoing; Mon, 10 Aug 1998 17:26:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (libya-228.ppp.hooked.net [206.169.227.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28573 for ; Mon, 10 Aug 1998 17:26:30 -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 RAA02398; Mon, 10 Aug 1998 17:26:05 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 10 Aug 1998 17:26:05 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: David Hobley cc: Amancio Hasty , Eivind Eklund , Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-Reply-To: <19980810215200.33285@wr.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 Mon, 10 Aug 1998, David Hobley wrote: [...] > This is under X, but I can't seem to get Ctrl-Alt-F1 to get back to > the console to see if there are any further diagnostics. Run xconsole before hand. It's quite helpful when you need to look at what might be displayed on /dev/console. - 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 Mon Aug 10 17:45:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01703 for freebsd-current-outgoing; Mon, 10 Aug 1998 17:45: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 RAA01669 for ; Mon, 10 Aug 1998 17:44:56 -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 UAA11183; Mon, 10 Aug 1998 20:44:23 -0400 (EDT) (envelope-from wollman) Date: Mon, 10 Aug 1998 20:44:23 -0400 (EDT) From: Garrett Wollman Message-Id: <199808110044.UAA11183@khavrinen.lcs.mit.edu> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: KERNFS and MFS In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > KERNFS urm... this works, why is not used/installed by default? Um, because it serves no useful function? It's mostly there as an example of what a simple but non-trivial filesystem needs to implement. -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 Aug 10 18:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06013 for freebsd-current-outgoing; Mon, 10 Aug 1998 18:12:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soccer.ksg.com (ftw-tsa7-27.cyberramp.net [207.158.119.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06004 for ; Mon, 10 Aug 1998 18:12:18 -0700 (PDT) (envelope-from kgor@soccer.ksg.com) Received: (from kgor@localhost) by soccer.ksg.com (8.8.8/8.8.8) id UAA03006; Mon, 10 Aug 1998 20:16:36 -0500 (CDT) (envelope-from kgor) Date: Mon, 10 Aug 1998 20:16:36 -0500 (CDT) Message-Id: <199808110116.UAA03006@soccer.ksg.com> From: "Kent S. Gordon" To: current@FreeBSD.ORG Subject: Is 3.0 going to be a.out? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the conversion from a.out to elf going to happen before or after the release of 3.0 (~ Oct. 15)? -- 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 Mon Aug 10 18:22:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07884 for freebsd-current-outgoing; Mon, 10 Aug 1998 18:22:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (spain-20.ppp.hooked.net [206.169.228.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07867 for ; Mon, 10 Aug 1998 18:22:35 -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 SAA03922; Mon, 10 Aug 1998 18:23:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 10 Aug 1998 18:23:22 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Garrett Wollman cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: KERNFS and MFS In-Reply-To: <199808110044.UAA11183@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 On Mon, 10 Aug 1998, Garrett Wollman wrote: > < said: > > > KERNFS urm... this works, why is not used/installed by default? > > Um, because it serves no useful function? > > It's mostly there as an example of what a simple but non-trivial > filesystem needs to implement. Yes, but it could be very useful. I for one would love to see kernfs as an extension of the sysctl interface. Suitable perhaps for sh scripts and the like. And actually it is kinda useful as-is. - 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 Mon Aug 10 20:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23020 for freebsd-current-outgoing; Mon, 10 Aug 1998 20:29:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22945 for ; Mon, 10 Aug 1998 20:29:40 -0700 (PDT) (envelope-from fluffy@vszbr.cz) Received: from localhost (pivrnec@localhost) by coredump.int.tele.dk (8.8.8/8.8.8) with SMTP id FAA01912 for ; Tue, 11 Aug 1998 05:29:11 +0200 (CEST) (envelope-from fluffy@vszbr.cz) X-Authentication-Warning: coredump.int.tele.dk: pivrnec owned process doing -bs Date: Tue, 11 Aug 1998 05:29:10 +0200 (CEST) From: Barry Bierbauch X-Sender: fluffy@coredump.int.tele.dk Reply-To: Barry Bouwsma To: freebsd-current@FreeBSD.ORG Subject: update frequency with recent current snaps? 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've recently upgraded my suffering news swerver from a -current snapshot of last November this past week to 3.0-19980802-SNAP. One problem I suffered was that sometimes, after rebuilding the kernel and rebooting, /etc/rc.conf would somehow have the line router_enable="YES" # Set to YES to enable a routing daemon. rewritten to "NO", so I had to fix this several times. This didn't always happen, only enough to unnerve me, and it also didn't happen at last reboot, so I can't say anything more about it other than I don't plan any remote kernel upgrades any more. Also, a minor nit, lines in /var/log/messages are sometimes split in the middle of the line: Aug 5 14:02:53 marley /kernel: lnc1 Aug 5 14:02:53 marley /kernel: : rev 0x16 int a irq 10 on pci0.11.0 [...] Aug 5 14:02:54 marley /kernel: changing root Aug 5 14:02:54 marley /kernel: device to wd1s1a [...] Aug 5 15:28:06 marley /kernel-updated-xl0: ccd0-3: Concatenated disk d Aug 5 15:28:06 marley /kernel-updated-xl0: rivers But the big question is about the kern.update sysctl variable, which used to allow one to tune how often one would sync data to disk from the default of 30 seconds: # We only sync once an hour ... we don't believe in crashes :-) sysctl -w kern.update=3600 I presume this has disappeared with the softupdates code. The point of doing something as risky as this, is that when running INN as news server, one has a history database text file which is updated by appending to the end for each incoming article, plus one or two files which are updated at unpredictable points throughout the file for each of some 15 articles/second. The thing is that when one is handling a full feed, the text file runs to around a gigabyte in size, and the index/hash/pag files can be several hundred megabytes in size when one keeps two weeks worth of entries. What happens when the periodic syncs happen is that the system practically freezes as the single-threaded innd gets stuck in ufslk2 state for several seconds up to several minutes under 2.2-RELENG, as the random points in the index/hash/pag files need to be updated for all of the half-thousand or more new entries that have arrived in those 30 seconds, which then happens again 30 seconds after this lengthy process completes, and so on. Barring a major rewrite of the dbz database code to only update a much smaller database (as one has with a much smaller history file), experimenting has shown that by delaying the updates to the disk, the additional data that needs to be written does not significantly increase the time spent blocked, as one is already updating most of the files anyway, so one gains a significant amount of time by postponing all the updates to a much less frequent time. As far as I can see now, the innd process periodically gets blocked in the `inode' state with the latest code on the server that handles far less than a full feed, so if this state could be postponed until `later', like a few minutes later, I'd gain more productive time per hour. At least, that's been my theory. There does seem to be a difference with the latest code, although I have not yet enabled softupdates for the history database, but my swerver hasn't been stable enough yet to know if it is still a significant problem with the database files ten times larger than on this micro-server. Actual file sizes in question (no significant filesystem tuning has been done w/r/t blocksize) for the recently-updated server -- the .pag file will probably stabilize around 2/3 of this size Real Soon Now: -rw-rw-r-- 1 news news 263050014 Aug 11 04:56 history -rw-rw-r-- 1 news news 127 Aug 11 04:56 history.dir -rw-rw-r-- 1 news news 32374604 Aug 11 04:55 history.pag The swerver where the files were significantly large enough to merit the hourly updates: -rw-rw-r-- 1 news news 845530318 Aug 11 04:56 history -rw-rw-r-- 1 news news 120 Aug 11 04:56 history.dir -rw-rw-r-- 1 news news 100214082 Aug 11 03:59 history.hash -rw-rw-r-- 1 news news 66809856 Aug 11 03:59 history.index Barry Bouwsma, Mendel University of Forestry and Agriculture, Brno, CZ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 21:02:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28504 for freebsd-current-outgoing; Mon, 10 Aug 1998 21:02:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28397 for ; Mon, 10 Aug 1998 21:01:58 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA24913; Tue, 11 Aug 1998 00:01:02 -0400 (EDT) (envelope-from luoqi) Date: Tue, 11 Aug 1998 00:01:02 -0400 (EDT) From: Luoqi Chen Message-Id: <199808110401.AAA24913@lor.watermarkgroup.com> To: archer@lucky.net, current@FreeBSD.ORG Subject: Re: New softupdates code panics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, Brian Feldman! > > In message about "New softupdates code panics" > on Sun, Aug 09, 1998, at 09:56:19 AM you wrote: > > > Well, I had patched my ffs_softdep.c and my ufs_vnops.c according to > > Luoqi and Kirk's patches and soon after rebooting, I got a panic (I don't > > think I was removing anything at the time, but oh well there are other > > processes than the ones I watch). I've still got the full debugging kernel > > and a core dump, so if anyone wants more just ask. > > The same here. My system paniced two times for some 4 hours after > I've booted kernel with Kirk's patches. The system was not very > busy, just ordinary mail/news reception (it is home computer). > Change the expression ``newparent ? newparent : doingdirectory'' in Kirk's patch to ``doingdirectory && newparent ? newparent : doingdirectory''. (for file ufs/ufs/ufs_vnops.c) -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 10 22:52:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12839 for freebsd-current-outgoing; Mon, 10 Aug 1998 22:52:36 -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 WAA12834 for ; Mon, 10 Aug 1998 22:52:31 -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 PAA03860; Tue, 11 Aug 1998 15:51:53 +1000 Date: Tue, 11 Aug 1998 15:51:53 +1000 From: Bruce Evans Message-Id: <199808110551.PAA03860@godzilla.zeta.org.au> To: archer@lucky.net, current@FreeBSD.ORG, luoqi@watermarkgroup.com Subject: Re: New softupdates code panics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The same here. My system paniced two times for some 4 hours after >> I've booted kernel with Kirk's patches. The system was not very >> busy, just ordinary mail/news reception (it is home computer). >> >Change the expression ``newparent ? newparent : doingdirectory'' in Kirk's >patch to ``doingdirectory && newparent ? newparent : doingdirectory''. >(for file ufs/ufs/ufs_vnops.c) Um, this expression is equivalent to ``doingdirectory'', which is the same as the unpatched expression. General fuzzy reasoning suggests that the expression should be ``doingdirectory && !newparent''. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 11 06:33:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00297 for freebsd-current-outgoing; Tue, 11 Aug 1998 06:33:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.fcc.net (shell.fcc.net [207.198.253.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00290 for ; Tue, 11 Aug 1998 06:33:54 -0700 (PDT) (envelope-from nathan@shell.fcc.net) Received: (from nathan@localhost) by shell.fcc.net (8.8.8/8.8.8) id JAA11955; Tue, 11 Aug 1998 09:33:33 -0400 (EDT) (envelope-from nathan) Message-ID: <19980811093333.A11944@fcc.net> Date: Tue, 11 Aug 1998 09:33:33 -0400 From: Nathan Dorfman To: freebsd-current@FreeBSD.ORG Subject: syslogd modification Mail-Followup-To: freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How about adding yet another -s option to syslogd? There is no reason for a luser to be able to do something like logger -p auth.notice -t su BAD SU bob to root on /dev/ttyp3 On a machine with many users (such as a shell server), would it make sense to keep all log sockets 0660 root/wheel? Something like: --- syslogd.c Tue Aug 11 08:59:19 1998 +++ syslogd.c.orig Tue Aug 11 08:51:45 1998 @@ -385,8 +385,7 @@ if (funix[i] < 0 || bind(funix[i], (struct sockaddr *)&sunx, SUN_LEN(&sunx)) < 0 || - chmod(funixn[i], SecureMode >= 2 ? 0660: 0666) < 0 || - chown(funixn[i], 0, 0) < 0) { + chmod(funixn[i], 0666) < 0) { (void) snprintf(line, sizeof line, "cannot create %s", funixn[i]); logerror(line); This approach, as opposed to simply chmodding the file in /etc/rc, may work better when you are using -l to create additional log sockets and want them with these permissions too. With this patch, just run syslogd -ssl /tmp/foolog -l /tmp/barlog If this is the Wrong Thing To Do (tm) can someone point out why? -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 11 06:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03182 for freebsd-current-outgoing; Tue, 11 Aug 1998 06:57:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03177 for ; Tue, 11 Aug 1998 06:57:12 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.8.8/8.8.8) with SMTP id JAA06881 for ; Tue, 11 Aug 1998 09:57:32 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 11 Aug 1998 09:57:30 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: status of softupdates? (directory bug fixed?) 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 noticed some traffic about bug fixes for softupdates, however then several people complained of panics immediatly following applying the patches. what's the deal? thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Tue Aug 11 07:25:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05974 for freebsd-current-outgoing; Tue, 11 Aug 1998 07:25:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05959 for ; Tue, 11 Aug 1998 07:25:15 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA27035; Tue, 11 Aug 1998 10:12:49 -0400 (EDT) (envelope-from luoqi) Date: Tue, 11 Aug 1998 10:12:49 -0400 (EDT) From: Luoqi Chen Message-Id: <199808111412.KAA27035@lor.watermarkgroup.com> To: archer@lucky.net, bde@zeta.org.au, current@FreeBSD.ORG, luoqi@watermarkgroup.com Subject: Re: New softupdates code panics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> The same here. My system paniced two times for some 4 hours after > >> I've booted kernel with Kirk's patches. The system was not very > >> busy, just ordinary mail/news reception (it is home computer). > >> > >Change the expression ``newparent ? newparent : doingdirectory'' in Kirk's > >patch to ``doingdirectory && newparent ? newparent : doingdirectory''. > >(for file ufs/ufs/ufs_vnops.c) > > Um, this expression is equivalent to ``doingdirectory'', which is the > same as the unpatched expression. General fuzzy reasoning suggests that > the expression should be ``doingdirectory && !newparent''. > > Bruce > newparent is not a boolean, and neither is the expression, they are integers. The expression used to be boolean, but now we want it to have three states: 0, 1, and >1, with the third state be doingdirectory && newparent. You could write the expression as ``doingdirectory && newparent ? 2 : doingdirectory''. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 11 10:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04624 for freebsd-current-outgoing; Tue, 11 Aug 1998 10:14:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.NET (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04618 for ; Tue, 11 Aug 1998 10:14:04 -0700 (PDT) (envelope-from green@zone.syracuse.NET) Received: from localhost (green@localhost) by zone.syracuse.NET (8.8.8/8.8.7) with SMTP id NAA01664; Tue, 11 Aug 1998 13:12:06 -0400 (EDT) Date: Tue, 11 Aug 1998 13:12:06 -0400 (EDT) From: Brian Feldman To: Luoqi Chen cc: archer@lucky.net, bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: New softupdates code panics In-Reply-To: <199808111412.KAA27035@lor.watermarkgroup.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 I think I understand here, you meant the association of the code would be (doingdirectory && newparent) ? newparent : doingdirectory rather that doingdirectory && (newparent ? newparent : doingdirectory) correct? And that would have been what led to the confusion. Cheers, Brian Feldman On Tue, 11 Aug 1998, Luoqi Chen wrote: > > >> The same here. My system paniced two times for some 4 hours after > > >> I've booted kernel with Kirk's patches. The system was not very > > >> busy, just ordinary mail/news reception (it is home computer). > > >> > > >Change the expression ``newparent ? newparent : doingdirectory'' in Kirk's > > >patch to ``doingdirectory && newparent ? newparent : doingdirectory''. > > >(for file ufs/ufs/ufs_vnops.c) > > > > Um, this expression is equivalent to ``doingdirectory'', which is the > > same as the unpatched expression. General fuzzy reasoning suggests that > > the expression should be ``doingdirectory && !newparent''. > > > > Bruce > > > newparent is not a boolean, and neither is the expression, they are integers. > The expression used to be boolean, but now we want it to have three states: > 0, 1, and >1, with the third state be doingdirectory && newparent. You could > write the expression as ``doingdirectory && newparent ? 2 : doingdirectory''. > > -lq > > 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 Tue Aug 11 10:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07520 for freebsd-current-outgoing; Tue, 11 Aug 1998 10:49:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07515 for ; Tue, 11 Aug 1998 10:49:58 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA29106; Tue, 11 Aug 1998 13:46:44 -0400 (EDT) (envelope-from luoqi) Date: Tue, 11 Aug 1998 13:46:44 -0400 (EDT) From: Luoqi Chen Message-Id: <199808111746.NAA29106@lor.watermarkgroup.com> To: green@zone.syracuse.NET, luoqi@watermarkgroup.com Subject: Re: New softupdates code panics Cc: archer@lucky.net, bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think I understand here, you meant the association of the code would be > (doingdirectory && newparent) ? newparent : doingdirectory > rather that > doingdirectory && (newparent ? newparent : doingdirectory) > correct? And that would have been what led to the confusion. > > Cheers, > Brian Feldman > Actually that's not the reason, && always has a higher associativity priority than ?: The real reason is if both doingdirectory and newparent are boolean, then the expression equals to doingdirectory: Let D = doingdirectory, N = newparent, the expression is (DN)N + !(DN)D = DN + (!DD + !ND) = DN + D!N = D This is no longer true if newparent and the expression are integer valued. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 11 15:55:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21855 for freebsd-current-outgoing; Tue, 11 Aug 1998 15:55:08 -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 PAA21835 for ; Tue, 11 Aug 1998 15:55:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA23391; Tue, 11 Aug 1998 15:51:37 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF23387; Tue Aug 11 22:51:33 1998 Date: Tue, 11 Aug 1998 15:51:29 -0700 (PDT) From: Julian Elischer To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: status of softupdates? (directory bug fixed?) 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 there is a patch to the patch.. after testing I will commit the complete fix.. the original wasn't too common..... julian On Tue, 11 Aug 1998, Alfred Perlstein wrote: > > i noticed some traffic about bug fixes for softupdates, however then > several people complained of panics immediatly following applying the > patches. > > what's the deal? > > thank you, > Alfred Perlstein > -- > > Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] > |-- There are operating systems, and then there's BSD. > \-- http://www.freebsd.org/ > > > 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 Tue Aug 11 18:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19377 for freebsd-current-outgoing; Tue, 11 Aug 1998 18:30:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (gw03.mpoweredpc.net [142.177.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19363; Tue, 11 Aug 1998 18:30:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.8) with SMTP id WAA00512; Tue, 11 Aug 1998 22:29:13 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 11 Aug 1998 22:29:13 -0300 (ADT) From: The Hermit Hacker To: Bruce Albrecht cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Odd problems with -current... In-Reply-To: <13766.34658.202254.310696@zuhause.zuhause.mn.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 On Mon, 3 Aug 1998, Bruce Albrecht wrote: > The Hermit Hacker writes: > > I'm trying to debug a problem that I'm having on my home machine > > that has me totally baffled, and am hoping someone here can "show me the > > way"... > > > > I just put in a 2gig Seagate SCSI drive on my system, to replace a > > 2gig IDE drive, and after running for awhile, it *seems* that the drive is > > powering down, cause when I try to access something on that drive after > > leaving for a period of time, you can hear it power back up again. > > Are you sure that it's not powering down because it's overheating? > I've got a couple of Hawk drives that shut down until I added extra fans. I'm not certain of anything right now, but I've got a larger email to send later tonight with, what I hope, is alot more detail... 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 Wed Aug 12 00:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03188 for freebsd-current-outgoing; Wed, 12 Aug 1998 00:02:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03163 for ; Wed, 12 Aug 1998 00:02:40 -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 KAA25265 for ; Wed, 12 Aug 1998 10:02:07 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id KAA05460 for current@freebsd.org; Wed, 12 Aug 1998 10:01:06 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id JAA26911; Wed, 12 Aug 1998 09:54:59 +0300 (EEST) (envelope-from archer) Date: Wed, 12 Aug 1998 09:54:59 +0300 (EEST) From: Alexander Litvin Message-Id: <199808120654.JAA26911@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: New softupdates code panics X-Newsgroups: grape.freebsd.current In-Reply-To: <199808110401.AAA24913@lor.watermarkgroup.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 <199808110401.AAA24913@lor.watermarkgroup.com> you wrote: >> > Well, I had patched my ffs_softdep.c and my ufs_vnops.c according to >> > Luoqi and Kirk's patches and soon after rebooting, I got a panic (I don't >> > think I was removing anything at the time, but oh well there are other >> > processes than the ones I watch). I've still got the full debugging kernel >> > and a core dump, so if anyone wants more just ask. >> >> The same here. My system paniced two times for some 4 hours after >> I've booted kernel with Kirk's patches. The system was not very >> busy, just ordinary mail/news reception (it is home computer). >> LC> Change the expression ``newparent ? newparent : doingdirectory'' in Kirk's LC> patch to ``doingdirectory && newparent ? newparent : doingdirectory''. LC> (for file ufs/ufs/ufs_vnops.c) With this patch it works much better. Up for 13 hours -- no panics. I've run 'make -j16 buildworld' -- it's ok. Thanx. LC> -lq LC> To Unsubscribe: send mail to majordomo@FreeBSD.org LC> with "unsubscribe freebsd-current" in the body of the message --- Beware of computerized fortune-tellers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 11:33:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15468 for freebsd-current-outgoing; Wed, 12 Aug 1998 11:33:53 -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 LAA15439 for ; Wed, 12 Aug 1998 11:33: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 LAA17111; Wed, 12 Aug 1998 11:32:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808121832.LAA17111@rah.star-gate.com> To: Alexander Litvin cc: current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: New softupdates code panics In-reply-to: Your message of "Wed, 12 Aug 1998 09:54:59 +0300." <199808120654.JAA26911@grape.carrier.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17108.902946769.1@rah.star-gate.com> Date: Wed, 12 Aug 1998 11:32:49 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same here . My test system seems to be okay with last soft update patch. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 12:33:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26379 for freebsd-current-outgoing; Wed, 12 Aug 1998 12:33:52 -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 MAA26369 for ; Wed, 12 Aug 1998 12:33:46 -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 PAA11851; Wed, 12 Aug 1998 15:32:01 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 12 Aug 1998 15:32:01 -0400 (EDT) From: "Alok K. Dhir" To: Amancio Hasty cc: Alexander Litvin , current@FreeBSD.ORG Subject: Re: New softupdates code panics In-Reply-To: <933086471D2265748525665E0066BEAA.0065B88D8525665E@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 Has said patch been committed already? On Wed, 12 Aug 1998, Amancio Hasty wrote: > > > Same here . My test system seems to be okay with last soft update > patch. > > Cheers, > Amancio > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" 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 Aug 12 12:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29785 for freebsd-current-outgoing; Wed, 12 Aug 1998 12:59:08 -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 MAA29773 for ; Wed, 12 Aug 1998 12:58:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: (from hasty@localhost) by rah.star-gate.com (8.8.8/8.8.8) id MAA17497; Wed, 12 Aug 1998 12:58:17 -0700 (PDT) (envelope-from hasty) Date: Wed, 12 Aug 1998 12:58:17 -0700 (PDT) From: Amancio Hasty Message-Id: <199808121958.MAA17497@rah.star-gate.com> To: adhir@worldbank.org, hasty@rah.star-gate.com Subject: Re: New softupdates code panics Cc: archer@lucky.net, current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that the softupdate team is still in the fix test stage hence I volunteer to test the patch. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 13:05:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01059 for freebsd-current-outgoing; Wed, 12 Aug 1998 13:05:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from egyptian.microxp.com (ns.microxp.com [209.207.52.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01041 for ; Wed, 12 Aug 1998 13:05:39 -0700 (PDT) (envelope-from randyd@ameritech.net) Received: from arabian (arabian.microxp.com [209.207.52.35]) by egyptian.microxp.com (8.8.8/8.8.8) with SMTP id OAA07727 for ; Wed, 12 Aug 1998 14:57:08 -0500 (CDT) (envelope-from randyd@ameritech.net) Received: by localhost with Microsoft MAPI; Wed, 12 Aug 1998 15:16:00 -0500 Message-ID: <01BDC604.1D2932D0.randyd@ameritech.net> From: "Randall D. DuCharme" Reply-To: "randyd@ameritech.net" To: "'current@freebsd.org'" Subject: Unexpected busfree??? Date: Wed, 12 Aug 1998 15:15:59 -0500 Organization: Computer Specialists X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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, This message just popped up on one of my 3.0-SNAP machines.... Unexpected busfree. LASTPHASE == 0x0 SEQADDR = 0x121 Things seem ok... I'm just wondering what this means. Thanks much -- Randall D DuCharme Systems Engineer Novell, Microsoft, and UNIX Networking Support Computer Specialists Free Your Machine.... FreeBSD 414-253-9998 414-253-9919 (fax) The Power To Serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 13:56:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09586 for freebsd-current-outgoing; Wed, 12 Aug 1998 13:56:27 -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 NAA09580 for ; Wed, 12 Aug 1998 13:56:24 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA28603; Wed, 12 Aug 1998 13:51:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdB28595; Wed Aug 12 20:51:13 1998 Message-ID: <35D20038.41C67EA6@whistle.com> Date: Wed, 12 Aug 1998 13:51:05 -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: Amancio Hasty CC: adhir@worldbank.org, archer@lucky.net, current@FreeBSD.ORG Subject: Re: New softupdates code panics References: <199808121958.MAA17497@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > I think that the softupdate team is still in the fix test stage hence > I volunteer to test the patch. > > Cheers, > Amancio > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I just committed a tested version of the directory fix.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 15:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20870 for freebsd-current-outgoing; Wed, 12 Aug 1998 15:02:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from central.picker.com (central.picker.com [144.54.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20796; Wed, 12 Aug 1998 15:02:15 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com (ct.picker.com [144.54.37.11]) by central.picker.com (8.9.1/8.9.1) with SMTP id SAA20049; Wed, 12 Aug 1998 18:13:01 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA21120; Wed, 12 Aug 98 18:01:46 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id SAA25475; Wed, 12 Aug 1998 18:01:29 -0400 Message-Id: <19980812180129.D25281@ct.picker.com> Date: Wed, 12 Aug 1998 18:01:29 -0400 From: Randall Hopper To: Roger Hardiman , current@FreeBSD.ORG, multimedia@FreeBSD.ORG Cc: Sren Schmidt Subject: Re: brooktree848 driver for 2.2.8 and -stable Mail-Followup-To: Roger Hardiman , current@FreeBSD.ORG, multimedia@FreeBSD.ORG, Sren Schmidt References: <35C9DF20.462DF047@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35C9DF20.462DF047@cs.strath.ac.uk>; from Roger Hardiman on Thu, Aug 06, 1998 at 05:51:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger Hardiman: |Recently a few users have complained about card detection of their |bt848 based TV cards which were solved by using the -current driver. |(Mainly Hauppauge users and Hauppauge 404 cards with 878 chips) | |As the -current driver has proved trustworthy, I think we should merge |it into the -stable tree for inclusion in 2.2.8. | |What do you think to this? It sounds like a good idea to me. This should greatly help user frustration in getting their card set up, particularly on -stable where they're not supposed to have to be hackers to get going. I'd sponser, but I don't have commit. Soren, would you sponser it? Randall Hopper rhh@ct.picker.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 21:05:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05274 for freebsd-current-outgoing; Wed, 12 Aug 1998 21:05:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05261 for ; Wed, 12 Aug 1998 21:05:15 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA01243; Wed, 12 Aug 1998 21:59:02 -0600 (MDT) Date: Wed, 12 Aug 1998 21:59:02 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808130359.VAA01243@narnia.plutotech.com> To: "randyd@ameritech.net" cc: current@FreeBSD.ORG Subject: Re: Unexpected busfree??? Newsgroups: pluto.freebsd.current In-Reply-To: <01BDC604.1D2932D0.randyd@ameritech.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <01BDC604.1D2932D0.randyd@ameritech.net> you wrote: > Greetings, > > This message just popped up on one of my 3.0-SNAP machines.... > > Unexpected busfree. LASTPHASE == 0x0 > SEQADDR = 0x121 It means that a target released the BSY signal on the bus unexpectedly. Bus free should only occur after a disconnect or command complete message, or in responds to an abort, abort tag, bus device reset, or BUS RESET request from the initior. If you system stayed up, the driver recovered properly from the target's protocol botch. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 12 23:16:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15415 for freebsd-current-outgoing; Wed, 12 Aug 1998 23:16:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15398; Wed, 12 Aug 1998 23:16:30 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id IAA00342; Thu, 13 Aug 1998 08:15:02 +0200 (CEST) (envelope-from sos) Message-Id: <199808130615.IAA00342@sos.freebsd.dk> Subject: Re: brooktree848 driver for 2.2.8 and -stable In-Reply-To: <19980812180129.D25281@ct.picker.com> from Randall Hopper at "Aug 12, 98 06:01:29 pm" To: rhh@ct.picker.com (Randall Hopper) Date: Thu, 13 Aug 1998 08:15:02 +0200 (CEST) Cc: roger@cs.strath.ac.uk, current@FreeBSD.ORG, multimedia@FreeBSD.ORG, sos@FreeBSD.ORG From: SЬren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Randall Hopper who wrote: > Roger Hardiman: > |Recently a few users have complained about card detection of their > |bt848 based TV cards which were solved by using the -current driver. > |(Mainly Hauppauge users and Hauppauge 404 cards with 878 chips) > | > |As the -current driver has proved trustworthy, I think we should merge > |it into the -stable tree for inclusion in 2.2.8. > | > |What do you think to this? > > It sounds like a good idea to me. This should greatly help user > frustration in getting their card set up, particularly on -stable where > they're not supposed to have to be hackers to get going. > > I'd sponser, but I don't have commit. Soren, would you sponser it? I've allready got a deal with Roger :), I'll get it in as soon as I get a few moments... I cannot promise anything about a 2.2.8 release though, but the snaps are daily generated at releng22.freebsd.org. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 04:26:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14163 for freebsd-current-outgoing; Thu, 13 Aug 1998 04:26:49 -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 EAA14155 for ; Thu, 13 Aug 1998 04:26:45 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id VAA29742 for current@freebsd.org; Thu, 13 Aug 1998 21:34:06 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808131134.VAA29742@cimlogic.com.au> Subject: NOOBJ in build To: current@FreeBSD.ORG Date: Thu, 13 Aug 1998 21:34:05 +1000 (EST) 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 Can anyone give me a *good* reason why we need to support NOOBJ in the make world/buildworld/installworld process? I'd like to be able to keep the different object formats apart during a build to help (1) the transition build from aout to elf; and (2) cross compilation. If I remove the .ifdefs for NOOBJ, I can set the obj directory path to include the object format so that it isn't necessary to clean the obj tree between building things in different formats. -- 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 Thu Aug 13 08:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10347 for freebsd-current-outgoing; Thu, 13 Aug 1998 08:16:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pasebo.nnettown.or.jp (pasebo.nnettown.or.jp [202.229.198.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10325; Thu, 13 Aug 1998 08:16:17 -0700 (PDT) (envelope-from sean@pasebo.nnet.ne.jp) Received: from J ([202.229.198.156]) by pasebo.nnettown.or.jp (8.9.1/3.5Wpl7-pasebo-97/08/31/18) with SMTP id AAA16504; Fri, 14 Aug 1998 00:13:39 +0900 (JST) Message-ID: <00b901bdc6ce$03be2ec0$9cc6e5ca@J.SeanBennett> From: "J. Sean Bennett" To: "The Hermit Hacker" , "Bruce Albrecht" Cc: , Subject: Re: Odd problems with -current... Date: Fri, 14 Aug 1998 00:13:43 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3115.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does it only happen when the drive has been inactive for awhile?? It could just be an energy saving mode of the drive, or your bios. Mine powers down if I leave the system on but inactive for awhile, and then spins up as I start working again. Sean sean@mail.nnet.ne.jp -----Original Message----- From: The Hermit Hacker To: Bruce Albrecht Cc: scsi@FreeBSD.ORG ; current@FreeBSD.ORG Date: August 12, 1998 11:02 AM Subject: Re: Odd problems with -current... >On Mon, 3 Aug 1998, Bruce Albrecht wrote: > >> The Hermit Hacker writes: >> > I'm trying to debug a problem that I'm having on my home machine >> > that has me totally baffled, and am hoping someone here can "show me the >> > way"... >> > >> > I just put in a 2gig Seagate SCSI drive on my system, to replace a >> > 2gig IDE drive, and after running for awhile, it *seems* that the drive is >> > powering down, cause when I try to access something on that drive after >> > leaving for a period of time, you can hear it power back up again. >> >> Are you sure that it's not powering down because it's overheating? >> I've got a couple of Hawk drives that shut down until I added extra fans. > >I'm not certain of anything right now, but I've got a larger email to send >later tonight with, what I hope, is alot more detail... > >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 08:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11747 for freebsd-current-outgoing; Thu, 13 Aug 1998 08:25:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shawn.holwegner.com (holwegner.com [205.158.165.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11742 for ; Thu, 13 Aug 1998 08:25:06 -0700 (PDT) (envelope-from shawn@shawn.holwegner.com) Received: (from shawn@localhost) by shawn.holwegner.com (8.9.1/8.8.8) id IAA02163; Thu, 13 Aug 1998 08:24:36 -0700 (PDT) (envelope-from shawn) Message-ID: <19980813082436.07107@holwegner.com> Date: Thu, 13 Aug 1998 08:24:36 -0700 From: Shawn Holwegner To: freebsd-current@FreeBSD.ORG Subject: Someone just did a booboo w/ sys/kern/subr_diskslice.c Reply-To: shawn@holwegner.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heya all. Just want to report the latest checkin of 3.0-C has a trivial break. /usr/src/sys/kern/subr_diskslice.c: Changed cmd from int to u_long, while leaving sys/sys/diskslice.h as int cmd. - Shawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 08:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16941 for freebsd-current-outgoing; Thu, 13 Aug 1998 08:59:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16927 for ; Thu, 13 Aug 1998 08:59:49 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with ESMTP id LAA22234 for ; Thu, 13 Aug 1998 11:59:14 -0400 (EDT) Date: Thu, 13 Aug 1998 11:59:14 -0400 (EDT) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: More PCI Slots... (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I couldn't think of anywhere else more appropriate...but, is this restricted to only Sun's, or has anyone looked at similar under an Intel/PCI environment? ---------- Forwarded message ---------- Date: Thu, 13 Aug 1998 08:32:03 -0700 From: MAGMA Subject: More PCI Slots... ****************************** MAGMA PCI Expansion Systems are available for Sun's PCI Based Workstations ****************************** Sun's Ultras are great computers, a great price and plenty of power. But, they may not have enough PCI slots for your application. True, you can buy an Ultra 450 with ten PCI slots but why, if you only need Ultra 5 performance, pay a premium. MAGMA's PCI Expansion Systems are the ideal solution for machines that require more slots to add PCI option boards. The Sun Ultra Workstation has three or four PCI slots for serial cards, video boards, sound cards, data collection boards, controllers or other devices. A PCI expansion system offers you the extra slots that you need to effectively use your Sun Microsystems Workstation. The PCI expansion systems are available in seven or thirteen slot configurations. The seven slot expansion system is available in a desktop or a rackmount enclosure. The thirteen slot expansion system is available in a rackmount enclosure only. If more than thirteen slots are needed, multiple PCI expansion systems can be connected to your computer or the expansion systems can be daisy-chained. All slots support full length PCI options cards with a maximum clock frequency of 33mhz. The PCI expansion systems are packaged in industry standard enclosures. The desktop chassis offers a 200 to 400 watt power supply and provides mounting bays for three 5.25" x 1.75" and two 3.5" x 1" peripherals. The rackmount chassis includes three quiet cooling fans, a 200 to 400 watt power supply and provides mounting bays for three 3.5" x 1" peripherals. No special software is required for full operation of the PCI expansion system. MAGMA's PCI Expansion Systems are certified by Sun and start at $1050.00 for a 7-slot desktop configuration. Visit our web site at www.magma.com and get a 15% discount on your first purchase from MAGMA. For additional information, contact MAGMA at Tel: (619) 457-0750, Fax: (619) 457-0798, Email: sales@magma.com or Web: www.magma.com -------------------------------------------------------- MAGMA═════════════════════Tel:══ (619) 457-0750 6725 Mesa Ridge Road════════════ (800) 285-8990 Suite 100═════════════════Fax:══ (619) 457-0798 San Diego, CA 92121═══════Web:══ http://www.magma.com ══ Email: sales@magma.com -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 10:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29067 for freebsd-current-outgoing; Thu, 13 Aug 1998 10:11:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA29061 for ; Thu, 13 Aug 1998 10:11:22 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z70tk-0004pp-00; Thu, 13 Aug 1998 10:10:48 -0700 Date: Thu, 13 Aug 1998 10:10:46 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: More PCI Slots... (fwd) 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, 13 Aug 1998, The Hermit Hacker wrote: > Sorry, I couldn't think of anywhere else more appropriate...but, is this > restricted to only Sun's, or has anyone looked at similar under an > Intel/PCI environment? PCI extender boxes have been available for a long time. Not long ago there was a mention of someone who hooked several of these up to a FreeBSD system. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 10:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02073 for freebsd-current-outgoing; Thu, 13 Aug 1998 10:27:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02056 for ; Thu, 13 Aug 1998 10:27:07 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id NAA12504; Thu, 13 Aug 1998 13:26:34 -0400 (EDT) Date: Thu, 13 Aug 1998 13:26:34 -0400 (EDT) From: The Hermit Hacker To: Tom cc: freebsd-current@FreeBSD.ORG Subject: Re: More PCI Slots... (fwd) 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, 13 Aug 1998, Tom wrote: > > On Thu, 13 Aug 1998, The Hermit Hacker wrote: > > > Sorry, I couldn't think of anywhere else more appropriate...but, is this > > restricted to only Sun's, or has anyone looked at similar under an > > Intel/PCI environment? > > PCI extender boxes have been available for a long time. Not long ago > there was a mention of someone who hooked several of these up to a FreeBSD > system. The OS doesn't need to do anything special to recognize them? Are there any limitations? At work, we are looking at a Sparc Enterprise 450, which has 10PCI slots spread over something like 3-4 PCI busses...do the extende do something like that, or is it all one big bus? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 10:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08953 for freebsd-current-outgoing; Thu, 13 Aug 1998 10:57:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08946 for ; Thu, 13 Aug 1998 10:57:57 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z71ct-0001om-00; Thu, 13 Aug 1998 10:57:27 -0700 Date: Thu, 13 Aug 1998 10:57:25 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: More PCI Slots... (fwd) 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, 13 Aug 1998, The Hermit Hacker wrote: > On Thu, 13 Aug 1998, Tom wrote: > > > > > On Thu, 13 Aug 1998, The Hermit Hacker wrote: > > > > > Sorry, I couldn't think of anywhere else more appropriate...but, is this > > > restricted to only Sun's, or has anyone looked at similar under an > > > Intel/PCI environment? > > > > PCI extender boxes have been available for a long time. Not long ago > > there was a mention of someone who hooked several of these up to a FreeBSD > > system. > > The OS doesn't need to do anything special to recognize them? Are > there any limitations? It is part of the PCI standard. PCI-PCI bridging. > At work, we are looking at a Sparc Enterprise 450, which has 10PCI > slots spread over something like 3-4 PCI busses...do the extende do > something like that, or is it all one big bus? I belive each extender is considered a separate bus, but of course is linked back to whatever bus it is plugged into. However, some x86 motherboards have their PCI slots slit over two buses too. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 14:52:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25819 for freebsd-current-outgoing; Thu, 13 Aug 1998 14:52:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25812 for ; Thu, 13 Aug 1998 14:52:21 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id QAA05271 for ; Thu, 13 Aug 1998 16:50:24 -0400 (EDT) Date: Thu, 13 Aug 1998 16:50:23 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: freebsd-current@FreeBSD.ORG Subject: diskslice.h 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 Line 103 of src/sys/sys/diskslice.h has the 3rd arg ("cmd") as an int, but src/kern/subr_diskslice.c line 387 has the same as a ulong. Which is it? My kernel won't compile. ----------------------------+----------------------------------------------- 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 Aug 13 17:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19795 for freebsd-current-outgoing; Thu, 13 Aug 1998 17:46:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19781; Thu, 13 Aug 1998 17:46:11 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id CAA05986; Fri, 14 Aug 1998 02:40:08 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id CAA13310; Fri, 14 Aug 1998 02:46:45 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id CAA10173; Fri, 14 Aug 1998 02:45:46 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Fri, 14 Aug 1998 02:45:46 +0200 (CEST) From: Stefan Bethke To: freebsd-stable@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <1682190.3111854089@d254.promo.de> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1089576808-903055546=:9883" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII [ please followup technical discussions to -current. ] On Tue, 11 Aug 1998, Stefan Bethke wrote: > On Die, 11. Aug 1998 13:33 Uhr +0200 Thomas Gellekum > wrote: > > > I have run this program five times and it finished once. The other > > four occasions I got > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x18 > > fault code = supervisor write, page ot present > > instruction pointer = 0x8:0xf0126d21 > > stack pointer = 0x10:0xefbffe50 > > frame pointer = 0x10:0xefbffe74 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 395 (crashbsd) > > interrupt mask = > > kernel: type 12 trap, code=0 > > Stopped at _sosend+0x391: movl $0, 0x18(%ebx) > > > > After saving the core dump and recompiling a few object files with -g: > > > #9 0xf01c0a37 in trap (frame={tf_es = -2147483632, tf_ds = -272695280, > > tf_edi = -272630136, tf_esi = -2147483648, tf_ebp = -272630156, > > tf_isp = -272630212, tf_ebx = 0, tf_edx = 2147483647, > > tf_ecx = -1073277766, tf_eax = 0, tf_trapno = 12, tf_err = 2, > > tf_eip = -267227871, tf_cs = 8, tf_eflags = 66198, tf_esp = 0, > > tf_ss = 1}) at ../../i386/i386/trap.c:324 > > #10 0xf0126d21 in sosend (so=0xf0937f00, addr=0x0, uio=0xefbffeb0, > > top=0x0, control=0xf06fff00, flags=0) at ../../kern/uipc_socket.c:432 > > Looking at kern/uipc_socket.c:sosend(), one can easily spot the problem > Because sosend() expects a MGET(m, M_WAIT, MT_DATA) to always succeed, it > pagefaults while trying to manipulate the non-allocated mbuf > (m->m_pkthdr.len at 0+0x18). > The solution would be either to make MGET() and MGETHRD() to always succeed > (or sleep indefinitly), or check the result of any of those calls (as many > callers already do). > This in both -stable and -current. I've made a simple patch to uipc_mbuf.c that makes sure M_GET() and M_GETHDR() always succeed when called with M_WAIT. The patch (attached) is against -current about 48 hrs ago. I've done a little testing (slightly modified version of the test program, also attached). It *seems* to work. I'd really appreciate comments from those more knowledgable... Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="m_retry.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: SW5kZXg6IHVpcGNfbWJ1Zi5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpS Q1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2tlcm4vdWlwY19tYnVmLmMs dg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjM3DQpkaWZmIC11IC1yMS4zNyB1 aXBjX21idWYuYw0KLS0tIHVpcGNfbWJ1Zi5jCTE5OTgvMDcvMjcgMDM6NTk6 NDgJMS4zNw0KKysrIHVpcGNfbWJ1Zi5jCTE5OTgvMDgvMTQgMDA6MzQ6NTMN CkBAIC0yNTAsNiArMjUwLDcgQEANCiAJaW50IGksIHQ7DQogew0KIAlyZWdp c3RlciBzdHJ1Y3QgbWJ1ZiAqbTsNCisJc3RhdGljIGludCBoYXZlX3dhcm5l ZCA9IDA7DQogDQogCS8qDQogCSAqIE11c3Qgb25seSBkbyB0aGUgcmVjbGFp bSBpZiBub3QgaW4gYW4gaW50ZXJydXB0IGNvbnRleHQuDQpAQCAtMjY0LDkg KzI2NSwzMCBAQA0KIAl9IGVsc2Ugew0KIAkJaWYgKGkgPT0gTV9ET05UV0FJ VCkNCiAJCQltYnN0YXQubV9kcm9wcysrOw0KLQkJZWxzZQ0KLQkJCXBhbmlj KCJPdXQgb2YgbWJ1ZiBjbHVzdGVycyIpOw0KKwkJZWxzZSB7DQorCQkJaWYg KCFoYXZlX3dhcm5lZCkgew0KKwkJCQlwcmludGYgKCJPdXQgb2YgbWJ1ZnMg LS0gaW5jcmVhc2UgTUFYVVNFUlNcbiIpOw0KKwkJCQloYXZlX3dhcm5lZCA9 IDE7DQorCQkJfQ0KKwkJCS8qDQorCQkJICogQmVjYXVzZSB0aGUgY2FsbGVy IHBhc3NlZCBNX1dBSVQsIHdlJ3JlIGFsbG93ZWQgdG8NCisJCQkgKiB0c2xl ZXAoKS4NCisJCQkgKi8NCisJCQl3aGlsZSAobSA9PSBOVUxMKSB7DQorCQkJ CSh2b2lkKXRzbGVlcCgoY2FkZHJfdCkmbW1iZnJlZSwgUFNPQ0ssICJtbWJm cmVlIiwgMTAwKTsNCisJCQkJLyogWFhYIHdlIHNob3VsZCBkbyBzb21ldGhp bmcgd2l0aCB0aGUgcmV0dXJuIHZhbHVlPyAqLw0KKwkJCQltX3JlY2xhaW0o KTsNCisJCQkJTUdFVChtLCBpLCB0KTsNCisJCQl9DQorCQl9DQogCX0NCisN CisJLyogU2hvdWxkIGFub3RoZXIgY2FsbGVyIGNvbWUgYnkgYW5kIG1fcmVj bGFpbSgpIGFjdHVhbGx5DQorCSAqIGZyZWUnZCBzb21lIG1idWZzLCB3YWtl IHVwIHRoZSBvdGhlcnMgc2xlZXBpbmcuDQorCSAqLw0KKwlpZiAobW1iZnJl ZSkNCisJCXdha2V1cCAoJm1tYmZyZWUpOw0KKw0KIAlyZXR1cm4gKG0pOw0K IH0NCiANCkBAIC0yNzgsNiArMzAwLDcgQEANCiAJaW50IGksIHQ7DQogew0K IAlyZWdpc3RlciBzdHJ1Y3QgbWJ1ZiAqbTsNCisJc3RhdGljIGludCBoYXZl X3dhcm5lZCA9IDA7DQogDQogCS8qDQogCSAqIE11c3Qgb25seSBkbyB0aGUg cmVjbGFpbSBpZiBub3QgaW4gYW4gaW50ZXJydXB0IGNvbnRleHQuDQpAQCAt MjkyLDkgKzMxNSwzMCBAQA0KIAl9IGVsc2Ugew0KIAkJaWYgKGkgPT0gTV9E T05UV0FJVCkNCiAJCQltYnN0YXQubV9kcm9wcysrOw0KLQkJZWxzZQ0KLQkJ CXBhbmljKCJPdXQgb2YgbWJ1ZiBjbHVzdGVycyIpOw0KKwkJZWxzZSB7DQor CQkJaWYgKCFoYXZlX3dhcm5lZCkgew0KKwkJCQlwcmludGYgKCJPdXQgb2Yg bWJ1ZnMgLS0gaW5jcmVhc2UgTUFYVVNFUlNcbiIpOw0KKwkJCQloYXZlX3dh cm5lZCA9IDE7DQorCQkJfQ0KKwkJCS8qDQorCQkJICogQmVjYXVzZSB0aGUg Y2FsbGVyIHBhc3NlZCBNX1dBSVQsIHdlJ3JlIGFsbG93ZWQgdG8NCisJCQkg KiB0c2xlZXAoKS4NCisJCQkgKi8NCisJCQl3aGlsZSAobSA9PSBOVUxMKSB7 DQorCQkJCSh2b2lkKXRzbGVlcCgoY2FkZHJfdCkmbW1iZnJlZSwgUFNPQ0ss ICJtbWJmcmVlIiwgMTAwKTsNCisJCQkJLyogWFhYIHdlIHNob3VsZCBkbyBz b21ldGhpbmcgd2l0aCB0aGUgcmV0dXJuIHZhbHVlPyAqLw0KKwkJCQltX3Jl Y2xhaW0oKTsNCisJCQkJTUdFVChtLCBpLCB0KTsNCisJCQl9DQorCQl9DQog CX0NCisNCisJLyogU2hvdWxkIGFub3RoZXIgY2FsbGVyIGNvbWUgYnkgYW5k IG1fcmVjbGFpbSgpIGFjdHVhbGx5DQorCSAqIGZyZWUnZCBzb21lIG1idWZz LCB3YWtlIHVwIHRoZSBvdGhlcnMgc2xlZXBpbmcuDQorCSAqLw0KKwlpZiAo bW1iZnJlZSkNCisJCXdha2V1cCAoJm1tYmZyZWUpOw0KKw0KIAlyZXR1cm4g KG0pOw0KIH0NCiANCg== --0-1089576808-903055546=:9883 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="bsdbug.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: LyogY3Jhc2hic2QuYw0KKioNCioqIFRISVMgUFJPR1JBTSBDQVVTRVMgS0VS TkVMIFBBTklDIE9OIFNPTUUgU1lTVEVNUw0KKioNCioqIFVzYWdlOiBjcmFz aG1lIFstLWhhcmRlcl0NCioqDQoqKiAtLWhhcmRlciBvcHRpb24gY2F1c2Vz IHRoaXMgcHJvZ3JhbSB0byBsZWF2ZSBvcGVuZWQgZmlsZSBkZXNjcmlwdG9y cyBoYW5naW5nDQoqKiB0aHVzIGluY3JlYXNpbmcgdGhlIHByb2JhYmlsaXR5 IG9mIHRoZSBjcmFzaC4NCioqDQoqLw0KDQojaW5jbHVkZSA8c3RkaW8uaD4N CiNpbmNsdWRlIDxmY250bC5oPg0KI2luY2x1ZGUgPHVuaXN0ZC5oPg0KI2lu Y2x1ZGUgPGVycm5vLmg+DQojaW5jbHVkZSA8c3lzL3R5cGVzLmg+DQojaW5j bHVkZSA8c3lzL3VuLmg+DQojaW5jbHVkZSA8c3lzL3Vpby5oPg0KI2luY2x1 ZGUgPHN5cy9zb2NrZXQuaD4NCiNpbmNsdWRlIDxzeXMvd2FpdC5oPg0KDQpp bnQgbWFpbihpbnQgYXJnYyxjaGFyICoqYXJndikgew0KCWludCBoYXJkZXI9 MCwgcCwgbnByb2MsIGgsIGksIHNvY2tldGZkc1syXTsNCgljaGFyIGFbMTBd Ow0KCXN0cnVjdCBpb3ZlYyBpb3YxPXthLDF9Ow0KCXN0cnVjdCBjbXNnaGRy ICpjbTsNCglzdHJ1Y3QgbXNnaGRyIG1zZzsNCgljaGFyIGJidWZmZXJbc2l6 ZW9mKHN0cnVjdCBjbXNnaGRyKStzaXplb2YoaW50KSoyNF07DQoNCglpZihh cmdjPj0yJiYhc3RyY21wKGFyZ3ZbMV0sIi0taGFyZGVyIikpIGhhcmRlcj0x Ow0KDQoJbnByb2M9LTE7DQoJZm9yKGk9MDtpPDYwO2krKykgew0KCQlpZiAo KHA9Zm9yaygpKT09MCkgew0KCQkJaWYgKHNvY2tldHBhaXIoQUZfVU5JWCxT T0NLX1NUUkVBTSwwLHNvY2tldGZkcykpIHsNCgkJCQlwZXJyb3IoInNvY2tl dHBhaXIiKTsNCgkJCX0gZWxzZSB7DQoJCQkJY209KHN0cnVjdCBjbXNnaGRy KiliYnVmZmVyOw0KCQkJCWNtLT5jbXNnX2xldmVsPVNPTF9TT0NLRVQ7DQoJ CQkJY20tPmNtc2dfdHlwZT1TQ01fUklHSFRTOw0KCQkJCWNtLT5jbXNnX2xl bj1zaXplb2Yoc3RydWN0IGNtc2doZHIpK3NpemVvZihpbnQpOw0KCQkJCW1z Zy5tc2dfbmFtZT0oY2FkZHJfdCkwOw0KCQkJCW1zZy5tc2dfbmFtZWxlbj0w Ow0KCQkJCW1zZy5tc2dfZmxhZ3M9MDsNCgkJCQltc2cubXNnX2lvdj0maW92 MTsNCgkJCQltc2cubXNnX2lvdmxlbj0xOw0KCQkJCW1zZy5tc2dfY29udHJv bD0oY2FkZHJfdCljbTsNCgkJCQltc2cubXNnX2NvbnRyb2xsZW49Y20tPmNt c2dfbGVuOw0KCQkJCWlmICgocD1mb3JrKCkpID4gMCkgew0KCQkJCQljbG9z ZShzb2NrZXRmZHNbMF0pOw0KCQkJCQkqKGludCopKGJidWZmZXIrc2l6ZW9m KHN0cnVjdCBjbXNnaGRyKSk9b3BlbigiL2Rldi9udWxsIixPX1JET05MWSk7 DQoJCQkJCWZvcihpPTA7aTwyMDQ4O2krKykgew0KCQkJCQkJZnByaW50Zihz dGRvdXQsIiVkPiAiLGkrMSk7DQoJCQkJCQl3aGlsZShzZW5kbXNnKHNvY2tl dGZkc1sxXSwmbXNnLDApIT0xKSB7DQoJCQkJCQkJaWYoZXJybm8hPUVBR0FJ Tikgew0KCQkJCQkJCQlwZXJyb3IoIlxuc2VuZG1zZyIpOw0KCQkJCQkJCX0N CgkJCQkgCQl9DQoJCQkJIAl9DQoJCQkJfSBlbHNlIHsNCgkJCQkJaWYgKHAg PCAwKSB7DQoJCQkJCQlwZXJyb3IoImZvcmsiKTsNCgkJCQkJCWV4aXQgKDAp Ow0KCQkJCQl9DQoJCQkJCWNsb3NlKHNvY2tldGZkc1sxXSk7DQoJCQkJCWZv cihpPTA7aTwyMDQ4O2krKykgew0KCQkJCQkJKihpbnQqKShiYnVmZmVyK3Np emVvZihzdHJ1Y3QgY21zZ2hkcikpPS0xOw0KCQkJCQkJZnByaW50ZihzdGRv dXQsIj4lZCAiLGkrMSk7DQoJCQkJCQljbT0oc3RydWN0IGNtc2doZHIqKWJi dWZmZXI7DQoJCQkJCQljbS0+Y21zZ19sZXZlbD1TT0xfU09DS0VUOw0KCQkJ CQkJY20tPmNtc2dfdHlwZT1TQ01fUklHSFRTOw0KCQkJCQkJY20tPmNtc2df bGVuPXNpemVvZihzdHJ1Y3QgY21zZ2hkcikrc2l6ZW9mKGludCkqMjQ7DQoJ CQkJCQltc2cubXNnX25hbWU9KGNhZGRyX3QpMDsNCgkJCQkJCW1zZy5tc2df bmFtZWxlbj0wOw0KCQkJCQkJaW92MS5pb3ZfbGVuPTEwOw0KCQkJCQkJbXNn Lm1zZ19pb3Y9JmlvdjE7DQoJCQkJCQltc2cubXNnX2lvdmxlbj0xOw0KCQkJ CQkJbXNnLm1zZ19jb250cm9sPShjYWRkcl90KWNtOw0KCQkJCQkJbXNnLm1z Z19jb250cm9sbGVuPWNtLT5jbXNnX2xlbjsNCg0KCQkJCQkJaWYocmVjdm1z Zyhzb2NrZXRmZHNbMF0sJm1zZywwKSE9MSl7DQoJCQkJCSAJCXBlcnJvcigi XG5yZWN2bXNnIik7DQoJCQkJCSAJfSBlbHNlIHsNCgkJCQkJIAkJZnByaW50 ZihzdGRvdXQsIiglZCkgIiwqKGludCopKGJidWZmZXIrc2l6ZW9mKHN0cnVj dCBjbXNnaGRyKSkpOw0KCQkJCQkJIAlpZighaGFyZGVyKSB7DQoJCQkJCQkJ CWNsb3NlKCooaW50KikoYmJ1ZmZlcitzaXplb2Yoc3RydWN0IGNtc2doZHIp KSk7DQoJCQkJCQkJfQ0KCQkJCQkJfQ0KCQkJCQl9DQoJCQkJCWV4aXQoMCk7 DQoJCQkJfQ0KCQkJCXdhaXQoJmgpOw0KCQkJfQ0KCQkJZXhpdCgwKTsNCgkJ fSBlbHNlIHsNCgkJCWlmKHA8MCkgew0KCQkJCW5wcm9jPWk7DQoJCQkJYnJl YWs7DQoJCQl9DQoJCX0NCgl9DQoJaWYobnByb2M8MCkNCgkJbnByb2M9NjA7 DQoJZm9yKGk9MDtpPG5wcm9jO2krKykgDQoJCXdhaXQoJmgpOw0KCWZwcmlu dGYoc3RkZXJyLCJcbiVkIHByb2Nlc3NlcyBmaW5pc2hlZFxuIixucHJvYyk7 DQoJcmV0dXJuIDA7DQp9DQo= --0-1089576808-903055546=:9883-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 19:44:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05791 for freebsd-current-outgoing; Thu, 13 Aug 1998 19:44:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05786 for ; Thu, 13 Aug 1998 19:44:44 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA29919 for ; Thu, 13 Aug 1998 19:44:17 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd029888; Thu Aug 13 19:44:08 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA26443 for current@freeBSD.org; Thu, 13 Aug 1998 19:44:08 -0700 (MST) From: Terry Lambert Message-Id: <199808140244.TAA26443@usr02.primenet.com> Subject: Tentative fix for VM bug To: current@FreeBSD.ORG Date: Fri, 14 Aug 1998 02:44:08 +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 A posting about NFS problems to the -hackers list gave me the clue I needed. I believe I have a fix for the VM bug. Would people running -current *AND* experiencing: o zeroed pages that shouldn't be o process hangs sleeping in "vmopar" o nfs client instability when executing programs or accessing files from the server (ie: mailboxes, etc., using lockfiles) o parts of files getting written to other files (that's me) o file corruption when accessing files via two routes (either two processes, or one process that both mmap's and extends the file via a descriptor). Please try this patch? Thanks... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ========================================================================= *** vm_object.c Thu May 21 07:47:58 1998 --- vm_object.c.good Fri Aug 14 02:08:15 1998 *************** *** 1348,1353 **** --- 1348,1354 ---- } } } else { + s = 0; while (size > 0) { if ((p = vm_page_lookup(object, start)) != 0) { *************** *** 1356,1361 **** --- 1357,1363 ---- vm_page_protect(p, VM_PROT_NONE); start += 1; size -= 1; + s = 1; continue; } *************** *** 1363,1376 **** * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) goto again; if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; continue; } } --- 1365,1381 ---- * The busy flags are only cleared at * interrupt -- minimize the spl transitions */ ! if (vm_page_sleep(p, "vmopar", &p->busy)) { ! start -= s; goto again; + } if (clean_only && p->valid) { vm_page_test_dirty(p); if (p->valid & p->dirty) { start += 1; size -= 1; + s = 1; continue; } } *************** *** 1381,1386 **** --- 1386,1392 ---- } start += 1; size -= 1; + s = 1; } } vm_object_pip_wakeup(object); ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 20:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13432 for freebsd-current-outgoing; Thu, 13 Aug 1998 20:56:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13427 for ; Thu, 13 Aug 1998 20:56:27 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA19898; Thu, 13 Aug 1998 20:56:00 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd019838; Thu Aug 13 20:55:50 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA00642; Thu, 13 Aug 1998 20:55:48 -0700 (MST) From: Terry Lambert Message-Id: <199808140355.UAA00642@usr06.primenet.com> Subject: Re: Tentative fix for VM bug To: tlambert@primenet.com (Terry Lambert) Date: Fri, 14 Aug 1998 03:55:48 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199808140244.TAA26443@usr02.primenet.com> from "Terry Lambert" at Aug 14, 98 02:44:08 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 > A posting about NFS problems to the -hackers list gave me the clue > I needed. > > I believe I have a fix for the VM bug. > > Would people running -current *AND* experiencing: > > o zeroed pages that shouldn't be > > o process hangs sleeping in "vmopar" > > o nfs client instability when executing programs or accessing > files from the server (ie: mailboxes, etc., using lockfiles) > > o parts of files getting written to other files (that's me) > > o file corruption when accessing files via two routes (either > two processes, or one process that both mmap's and extends > the file via a descriptor). Note: If I have lost my mind, there are two other places where this could be happening instead. If I have lost my mind, then I expect an increase in the occurance "vm_page_free: freeing free page", and I will have to go back to the other places (which are vastly more complicated to fix). 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 Aug 13 22:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22247 for freebsd-current-outgoing; Thu, 13 Aug 1998 22:21:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22242 for ; Thu, 13 Aug 1998 22:21:17 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-94.ix.netcom.com [209.109.232.94]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA29838; Thu, 13 Aug 1998 22:20:41 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id WAA12851; Thu, 13 Aug 1998 22:20:38 -0700 (PDT) Date: Thu, 13 Aug 1998 22:20:38 -0700 (PDT) Message-Id: <199808140520.WAA12851@silvia.hip.berkeley.edu> To: tom@uniserve.com CC: scrappy@hub.org, freebsd-current@FreeBSD.ORG In-reply-to: (message from Tom on Thu, 13 Aug 1998 10:57:25 -0700 (PDT)) Subject: Re: More PCI Slots... (fwd) From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * > > PCI extender boxes have been available for a long time. Not long ago * > > there was a mention of someone who hooked several of these up to a FreeBSD * > > system. That was probably me. We daisy-chained couple of the Bit3 boxes (7 slots each) and put a twin-channel SCSI adapter at the far end. It worked on some of our machines. * > The OS doesn't need to do anything special to recognize them? Are * > there any limitations? The BIOS needs to set up the bridge chips correctly. Note that there can be a full tree of these things hooked up to each other, so it has to recurse into the buses correctly to set up the PCI bus ID registers and such. Obviously there is some point it will stop working if you keep daisy-chaining the boxes because there is only a limited amount of memory the BIOS can use. At the time we tested (more than 3 years ago), Award BIOS didn't work with more than one level of bridging. All of them worked with twin-channel adapters (one bridge in there too) in the host PCI bus though, so they did know about bridge chips. * It is part of the PCI standard. PCI-PCI bridging. I think the chip has to be recognized correctly. Stefan added ours (the IBM chip) to the list. * > At work, we are looking at a Sparc Enterprise 450, which has 10PCI * > slots spread over something like 3-4 PCI busses...do the extende do * > something like that, or is it all one big bus? * * I belive each extender is considered a separate bus, but of course is * linked back to whatever bus it is plugged into. However, some x86 * motherboards have their PCI slots slit over two buses too. There are usually 4 or 5 slots per bus. And the host-expansion cable is also a separate bus. So, for instance, a 7-slot expansion box (which actually only adds 6 slots because one of the host PCI slots is taken) plugged into a 4-slot host will look like this (`*'s are the bridge chips): host | bus 0 bus 2 bus 3 +-+-+-+ +-+-+-+ * +-+-+-+ | | | | | | | | | | | | * * +---------+ bus 1 ^ | this slot is for the host interface card only Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 13 22:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25786 for freebsd-current-outgoing; Thu, 13 Aug 1998 22:54:57 -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 WAA25775 for ; Thu, 13 Aug 1998 22:54:53 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id QAA03218; Fri, 14 Aug 1998 16:02:23 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808140602.QAA03218@cimlogic.com.au> Subject: Re: 3.0 Schedule, ELF and CAM In-Reply-To: from Alex at "Aug 13, 98 10:40:19 pm" To: garbanzo@hooked.net (Alex) Date: Fri, 14 Aug 1998 16:02:23 +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 Alex wrote: > So when can we see some more ELF progress? We need to be sure that people aren't going to hose themselves by moving to elf. I'm working on the build end of the aout to elf transition. Testing this requires lots of big builds, and in my case, reinstalling 2.2.6 before each one to ensure that the procedure works from a system which doesn't know about elf tools. So far it is looking like a `make aout_to_elf' will be all that is required to make the switch. You can expect this to be available by about September 1st allowing 6 weeks before 3.0 is shipped. -- 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 Thu Aug 13 23:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26550 for freebsd-current-outgoing; Thu, 13 Aug 1998 23:01:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26545; Thu, 13 Aug 1998 23:01:02 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id CAA09249; Fri, 14 Aug 1998 02:02:02 -0400 (EDT) Date: Fri, 14 Aug 1998 02:02:02 -0400 (EDT) From: Mark turpin To: FreeBSD hackers , FreeBSD Current Subject: UDF Filesystem 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 Is any body working on implementing UDF on FreeBSD? I looked in the archives and didn't see anything about it? Thanks Mark Turpin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 00:19:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09280 for freebsd-current-outgoing; Fri, 14 Aug 1998 00:19:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09257; Fri, 14 Aug 1998 00:19:48 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id DAA00487; Fri, 14 Aug 1998 03:19:17 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Mark turpin cc: FreeBSD hackers , FreeBSD Current Reply-To: freebsd-fs@FreeBSD.ORG From: "Gary Palmer" Subject: Re: UDF Filesystem In-reply-to: Your message of "Fri, 14 Aug 1998 02:02:02 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 03:19:17 -0400 Message-ID: <483.903079157@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark turpin wrote in message ID : > > Is any body working on implementing UDF on FreeBSD? I looked in the > archives and didn't see anything about it? URL with details? (reply-to set to the correct list) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 01:17:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18302 for freebsd-current-outgoing; Fri, 14 Aug 1998 01:17:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18297 for ; Fri, 14 Aug 1998 01:17:27 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id JAA07829; Fri, 14 Aug 1998 09:16:58 +0100 (BST) Date: Fri, 14 Aug 1998 09:16:58 +0100 (BST) From: Doug Rabson To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: diskslice.h 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, 13 Aug 1998, Chuck Robey wrote: > Line 103 of src/sys/sys/diskslice.h has the 3rd arg ("cmd") as an int, > but src/kern/subr_diskslice.c line 387 has the same as a ulong. Which > is it? My kernel won't compile. I forgot to commit the header file, sorry. Fixed now. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 04:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10459 for freebsd-current-outgoing; Fri, 14 Aug 1998 04:49:15 -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 EAA10454 for ; Fri, 14 Aug 1998 04:49:13 -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 EAA23470; Fri, 14 Aug 1998 04:48:52 -0700 (PDT) Message-Id: <199808141148.EAA23470@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Tentative fix for VM bug In-reply-to: Your message of "Fri, 14 Aug 1998 03:55:48 -0000." <199808140355.UAA00642@usr06.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Aug 1998 04:48:52 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Note: If I have lost my mind, there are two other places where this >could be happening instead. > >If I have lost my mind, then I expect an increase in the occurance >"vm_page_free: freeing free page", and I will have to go back to >the other places (which are vastly more complicated to fix). You've lost your mind a long time ago, Terry. :-) -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 Fri Aug 14 07:12:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00705 for freebsd-current-outgoing; Fri, 14 Aug 1998 07:12:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00700 for ; Fri, 14 Aug 1998 07:12:04 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id KAA02008 for ; Fri, 14 Aug 1998 10:12:20 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 10:12:20 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: Funky DEVFS stuff. 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 posted a while back about devfs not being able to find my scsi disk, i'm posting some info that might be useful. i think this is a problem because i did some funky stuff when i labled it, however, mount CAN find the disk in a non-devfs system. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #8: Sun Aug 9 14:52:17 EST 1998 perlsta@server.local.sunyit.edu:/usr/src/sys/compile/K6233 Timecounter "i8254" frequency 1193182 Hz cost 3794 ns Timecounter "TSC" frequency 232961751 Hz cost 104 ns CPU: AMD-K6tm w/ multimedia extensions (232.96-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 94851072 (92628K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x23 on pci0.0.0 chip1: rev 0x27 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 chip2: rev 0x02 int d irq 11 on pci0.7.2 ahc0: rev 0x01 int a irq 9 on pci0.8.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 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 1812MB (3711990 512 byte sectors) ed3: rev 0x00 int a irq 12 on pci0.9.0 ed3: address 00:00:21:4e:29:c3, type NE2000 (16 bit) vga0: rev 0x41 on pci0.11.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 flags 0x4 on motherboard sc0: VGA color <16 virtual consoles, flags=0x4> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 at 0x220 irq 10 drq 3 flags 0x15 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 4028MB (8249472 sectors), 8184 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): , removable, intr, dma, iord y wcd0: 343/3445Kb/sec, 382Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked npx0 on motherboard npx0: INT 16 interface ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 DEVFS: ready to run IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled sd0: probing for MBR.. nope sd0: probing for disklabel.. fd0: probing for MBR.. wd0: probing for MBR.. part 1, start=63, size=8249409 wd0s1: attaching disklabel.. part a, start=0, size=96001 part b, start=96001, size=384000 part e, start=480001, size=192000 part f, start=672001, size=3788704 part g, start=4460705, size=3788704 fd0: hard error, block 0 (No status) WOULD SELECT /wd0a but it doesn't exist /wd0s1a exists, I'll use that right here i get prompt for single user mode because it can't find this entry in fstab now: /dev/sd0s1c /scsi ufs rw 1 1 ------ info from sd0 via disklable and such: # disklabel -r /dev/rsd0 | less # /dev/rsd0: type: SCSI disk: sd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 231 sectors/unit: 3711990 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 3711990 0 unused 0 0 # (Cyl. 0 - 231*) ------- fdisk ------ # fdisk /dev/rsd0 ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=3711990 heads=1 sectors/track=1 (1 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3711990 heads=1 sectors/track=1 (1 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 3711990 (1812 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 231/ sector 30/ head 15 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: # ok, heh :) now what? i know i musta done something icky for me to be able to mount it normally but DEVFS not being able to. thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Fri Aug 14 07:16:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01340 for freebsd-current-outgoing; Fri, 14 Aug 1998 07:16:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01331 for ; Fri, 14 Aug 1998 07:16:08 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id KAA02015 for ; Fri, 14 Aug 1998 10:16:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 10:16:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: new compiler? 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 wondering, the gcc freebsd uses is nice, but several people have reported succsess building world with newer versions of gcc (maybe ecgs too) to support more recent C++ standards by default, do any core team members have a "favorite" compiler? i'm kinda interested in seeing if i can do anything to have 3.0 come out with a more current compiler and would like to know which to look at. (also considering the alpha port) gcc 2.8.1? (i've heard masses of people complain it's buggy) ecgs (not heard much... but i know it has some interesting optimizations for i386, and better C++ support) anything else? thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- 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 Fri Aug 14 07:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06139 for freebsd-current-outgoing; Fri, 14 Aug 1998 07:49:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06134 for ; Fri, 14 Aug 1998 07:49:50 -0700 (PDT) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id JAA09013; Fri, 14 Aug 1998 09:49:14 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma008982; Fri, 14 Aug 98 09:48:48 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id JAA24748; Fri, 14 Aug 1998 09:47:47 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Fri, 14 Aug 1998 09:47:46 -0500 (CDT) From: Kyle Mestery To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: new compiler? 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, 14 Aug 1998, Alfred Perlstein wrote: > to support more recent C++ standards by default, do any core team members > have a "favorite" compiler? i'm kinda interested in seeing if i can do > anything to have 3.0 come out with a more current compiler and would like > to know which to look at. (also considering the alpha port) > I would also like to see this happen, and would be willing to help make it happen. > gcc 2.8.1? (i've heard masses of people complain it's buggy) > ecgs (not heard much... but i know it has some interesting optimizations > for i386, and better C++ support) > anything else? > I have heard the opposite. I have heard that egcs is buggy.:) On one of the NetBSD lists, someone said the latest egcs release only compiles decent code on ix86 and sparc platforms. And Terry has said before that the way they handle threads is broken, because you must compile thread support into the compiler. I haven't heard as many bad things about gcc-2.8.1. So, what are the chances of things happening along this front? Also, if we do bring a new compiler into the tree, should we try and bring FreeBSD's shared library mechanism along with it for compatability reasons, or just go strictly elf? -- Kyle Mestery StorageTek's Network Systems Group "I'll take what you're willing to give, and I'll teach myself to live, with a walk-on part of a background shot from a movie I'm not in." - Blink 182, "Apple Shampoo" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 09:14:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17071 for freebsd-current-outgoing; Fri, 14 Aug 1998 09:14:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17063 for ; Fri, 14 Aug 1998 09:14:49 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA13442; Fri, 14 Aug 1998 11:14:21 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA01061; Fri, 14 Aug 1998 11:14:21 -0500 (CDT) Message-ID: <19980814111421.45977@mcs.net> Date: Fri, 14 Aug 1998 11:14:21 -0500 From: Karl Denninger To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Tentative fix for VM bug References: <199808140244.TAA26443@usr02.primenet.com> <199808140355.UAA00642@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199808140355.UAA00642@usr06.primenet.com>; from Terry Lambert on Fri, Aug 14, 1998 at 03:55:48AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 03:55:48AM +0000, Terry Lambert wrote: > > A posting about NFS problems to the -hackers list gave me the clue > > I needed. > > > > I believe I have a fix for the VM bug. > > > > Would people running -current *AND* experiencing: > > > > o zeroed pages that shouldn't be > > > > o process hangs sleeping in "vmopar" > > > > o nfs client instability when executing programs or accessing > > files from the server (ie: mailboxes, etc., using lockfiles) > > > > o parts of files getting written to other files (that's me) > > > > o file corruption when accessing files via two routes (either > > two processes, or one process that both mmap's and extends > > the file via a descriptor). > > Note: If I have lost my mind, there are two other places where this > could be happening instead. > > If I have lost my mind, then I expect an increase in the occurance > "vm_page_free: freeing free page", and I will have to go back to > the other places (which are vastly more complicated to fix). I can confirm that the propounded fix doesn't, at least not for the case of a Diablo news server which gets files whacked with either zeros or random trash contents from time to time. With the "fix" in I see no change of significance in behavior. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 09:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18538 for freebsd-current-outgoing; Fri, 14 Aug 1998 09:22:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18533 for ; Fri, 14 Aug 1998 09:22:33 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id MAA12846 for ; Fri, 14 Aug 1998 12:21:24 -0400 (EDT) Date: Fri, 14 Aug 1998 12:21:24 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: ELF problems to occur 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 The transition from a.out to ELF will not be easy; I see some definite potential hangups: gdb - the gdb for a.out will not recognize ELF binaries, and the gdb for ELF will not recognize the current format of core dumps /usr/{X11R6,local}/lib etc. - what will be the new format? Will there be a /usr/X11R6/lib/{elf,aout} (unlikely) or should all old a.out shlibs be moves to /usr/lib/aout, and /usr/lib/aout shall also take over for /usr/lib/compat?Will I have to recompile all my many libraries for ELF or will objcopy work in all cases? I've had pretty good luck with objcopy, and if it works very well, I'll go ahead and write a shell script to help transition libraries. crunch, Modula-3, ldconfig, lkms/kernel - are these all going to be ready? M3 should already be ELF-compilable, crunch should probably still work, will ldconfig be necessary anymore, or is this just wishful thinking? I don't see how ldconfig is in its present state ready for ELF. And supposedly the ELF kernel is bootable nowadays with a few patches; do lkm's work? Just some nice things to trip us up! Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 09:26:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19550 for freebsd-current-outgoing; Fri, 14 Aug 1998 09:26:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19543 for ; Fri, 14 Aug 1998 09:26:45 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id MAA02130; Fri, 14 Aug 1998 12:26:55 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 12:26:55 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Kyle Mestery cc: current@FreeBSD.ORG Subject: Re: new compiler? 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 this will be something quite new to me. i think simplifing it by going elf is a good idea, as the move to elf is expected in the next week anyhow. -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 14 Aug 1998, Kyle Mestery wrote: > On Fri, 14 Aug 1998, Alfred Perlstein wrote: > > > to support more recent C++ standards by default, do any core team members > > have a "favorite" compiler? i'm kinda interested in seeing if i can do > > anything to have 3.0 come out with a more current compiler and would like > > to know which to look at. (also considering the alpha port) > > > I would also like to see this happen, and would be willing to help make it > happen. > > > gcc 2.8.1? (i've heard masses of people complain it's buggy) > > ecgs (not heard much... but i know it has some interesting optimizations > > for i386, and better C++ support) > > anything else? > > > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. > > So, what are the chances of things happening along this front? Also, if > we do bring a new compiler into the tree, should we try and bring > FreeBSD's shared library mechanism along with it for compatability > reasons, or just go strictly elf? > > -- > Kyle Mestery > StorageTek's Network Systems Group > > "I'll take what you're willing to give, and I'll teach myself to live, > with a walk-on part of a background shot from a movie I'm not in." > - Blink 182, "Apple Shampoo" > > > > 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 Fri Aug 14 09:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23912 for freebsd-current-outgoing; Fri, 14 Aug 1998 09:45:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23892 for ; Fri, 14 Aug 1998 09:45:39 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA13138; Fri, 14 Aug 1998 09:43:55 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808140943.JAA13138@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: Funky DEVFS stuff. In-reply-to: Your message of "Fri, 14 Aug 1998 10:12:20 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 09:43:54 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ------ info from sd0 via disklable and such: > > # disklabel -r /dev/rsd0 | less > # /dev/rsd0: > type: SCSI > disk: sd0s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 231 > sectors/unit: 3711990 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 3711990 0 unused 0 0 # (Cyl. 0 - > 231*) You can't do this. Make an 'a' partition that matches the 'c' partition and use that instead. -- \\ 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 Fri Aug 14 10:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28557 for freebsd-current-outgoing; Fri, 14 Aug 1998 10:08:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28538; Fri, 14 Aug 1998 10:08:26 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id TAA00337; Fri, 14 Aug 1998 19:07:06 +0200 (CEST) (envelope-from sos) Message-Id: <199808141707.TAA00337@sos.freebsd.dk> Subject: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: current@FreeBSD.ORG (FreeBSD current), hackers@FreeBSD.ORG (FreeBSD hackers) Date: Fri, 14 Aug 1998 19:07:06 +0200 (CEST) From: SЬren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A workable snapshot is available on: ftp;//sos.freebsd.dk/pub/ATAPI/* >From the README: This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. Please dont distribute this, only use it for testing, as it is alpha level code which is undergoing rapid changes. The main use of this snap is to test the support for ATAPI CD burners, and the driver has been adapted to the old ATAPI system to serve only this purpose. Both ATAPI CD-R & CD-RW drives are supported, and it has been tested with a HP7200i and a BTC BCE621E (also sold under the KISS name). The driver might scribble various messages on the console, but most should be harmless diagnostics. As always YMMV. Install the new driver files new-files.tgz and apply the patches in sys-diff, make a new entry in your configfile for the new "acd" atapi device, config & make a new kernel. The acd driver uses the same devicemajor as the old wcd driver, so you can reuse the /dev/*wcd* devices. However if you use DEVFS it will register itself under the name /dev/*acd*. I have includes a modified version of "wormcontrol" that can talk to the acd driver. It has two new commands "nextwriteable" that tells the driver the next writeable block on a CDR/CDRW, used when burning more that 1 track (for audio mostly). Example scripts for burning data & audio CD's are also included. The cd ripper program "cdd" is also here in a modified version that can talk to the acd driver. Enjoy and let me know the results... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 10:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02715 for freebsd-current-outgoing; Fri, 14 Aug 1998 10:31:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02709 for ; Fri, 14 Aug 1998 10:31:51 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id LAA06318; Fri, 14 Aug 1998 11:31:14 -0600 (MDT) Message-Id: <199808141731.LAA06318@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Kyle Mestery cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: new compiler? In-reply-to: Your message of "Fri, 14 Aug 1998 09:47:46 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Aug 1998 11:31:14 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > On Fri, 14 Aug 1998, Alfred Perlstein wrote: > > > to support more recent C++ standards by default, do any core team members > > have a "favorite" compiler? i'm kinda interested in seeing if i can do > > anything to have 3.0 come out with a more current compiler and would like > > to know which to look at. (also considering the alpha port) > > > I would also like to see this happen, and would be willing to help make it > happen. > > > gcc 2.8.1? (i've heard masses of people complain it's buggy) > > ecgs (not heard much... but i know it has some interesting optimizations > > for i386, and better C++ support) > > anything else? > > > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. > ... We have a fairly complex system running with 2.2.6, FreeBSD pthreads and g++28. We tried both the standard compiler and egcs, but neither would compile the complete project, let alone run. The biggest problem is in the area of c++ templates, g++28 will eat things the other 2 barfed on. We had to make one patch to gcc28 b4 building, and turn on the "GCC28_THREAD_AWARE" define in libc_r to fix the problem with dynamic chain handling. After this exceptions seem to work properly. My vote would be for gcc28. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 11:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09250 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:04: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 LAA09245; Fri, 14 Aug 1998 11:04:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17762; Fri, 14 Aug 1998 11:00:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdp17758; Fri Aug 14 18:00:30 1998 Date: Fri, 14 Aug 1998 11:00:27 -0700 (PDT) From: Julian Elischer To: Mark turpin cc: FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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 what's UDF? On Fri, 14 Aug 1998, Mark turpin wrote: > > Is any body working on implementing UDF on FreeBSD? I looked in the > archives and didn't see anything about it? > > > Thanks > > Mark Turpin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 11:04:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09344 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:04:46 -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 LAA09327 for ; Fri, 14 Aug 1998 11:04:43 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17747; Fri, 14 Aug 1998 11:00:03 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda17727; Fri Aug 14 18:00:00 1998 Date: Fri, 14 Aug 1998 10:59:57 -0700 (PDT) From: Julian Elischer To: David Greenman cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Tentative fix for VM bug In-Reply-To: <199808141148.EAA23470@implode.root.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 yes, but is it a bug that he's reporting? On Fri, 14 Aug 1998, David Greenman wrote: > >Note: If I have lost my mind, there are two other places where this > >could be happening instead. > > > >If I have lost my mind, then I expect an increase in the occurance > >"vm_page_free: freeing free page", and I will have to go back to > >the other places (which are vastly more complicated to fix). > > You've lost your mind a long time ago, Terry. :-) > > -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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 11:25:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13104 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:25:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13093 for ; Fri, 14 Aug 1998 11:25:24 -0700 (PDT) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id NAA16067; Fri, 14 Aug 1998 13:24:45 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma016045; Fri, 14 Aug 98 13:24:30 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id NAA28909; Fri, 14 Aug 1998 13:23:29 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Fri, 14 Aug 1998 13:23:28 -0500 (CDT) From: Kyle Mestery To: Steve Passe cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: new compiler? In-Reply-To: <199808141731.LAA06318@Ilsa.StevesCafe.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 Fri, 14 Aug 1998, Steve Passe wrote: > We have a fairly complex system running with 2.2.6, FreeBSD pthreads and > g++28. We tried both the standard compiler and egcs, but neither would > compile the complete project, let alone run. The biggest problem is in > the area of c++ templates, g++28 will eat things the other 2 barfed on. > We had to make one patch to gcc28 b4 building, and turn on the > "GCC28_THREAD_AWARE" define in libc_r to fix the problem with dynamic > chain handling. After this exceptions seem to work properly. > > My vote would be for gcc28. > My reason's for wanting gcc-2.8.1 also lie along these lines, as we are using a cross development environment at work that is complex and utilizes a mix of gcc-2.8.1 front end and back-end linker/assembler from WRS, targeting arm-wrs-vxworks. It works quite well, and we have no problems with the compiler so far. -- Kyle Mestery StorageTek's Storage Networking Group "I'll take what you're willing to give, and I'll teach myself to live, with a walk-on part of a background shot from a movie I'm not in." - Blink 182, "Apple Shampoo" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 11:32:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14844 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:32:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14811; Fri, 14 Aug 1998 11:32:37 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id OAA02613; Fri, 14 Aug 1998 14:32:54 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 14 Aug 1998 14:32:54 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: SЬren Schmidt cc: FreeBSD current , FreeBSD hackers Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808141707.TAA00337@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id LAA14817 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does this code have a watchdog to prevent ATAPI proccesses from tsleeping forever? (i don't have a burner, but i will test it if does) -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Fri, 14 Aug 1998, SЬren Schmidt wrote: > > A workable snapshot is available on: > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > >From the README: > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > Please dont distribute this, only use it for testing, as it is > alpha level code which is undergoing rapid changes. > > The main use of this snap is to test the support for ATAPI CD burners, > and the driver has been adapted to the old ATAPI system to serve only > this purpose. > > Both ATAPI CD-R & CD-RW drives are supported, and it has been tested > with a HP7200i and a BTC BCE621E (also sold under the KISS name). > The driver might scribble various messages on the console, but > most should be harmless diagnostics. As always YMMV. > > Install the new driver files new-files.tgz and apply the patches > in sys-diff, make a new entry in your configfile for the new > "acd" atapi device, config & make a new kernel. > > The acd driver uses the same devicemajor as the old wcd driver, so > you can reuse the /dev/*wcd* devices. However if you use DEVFS it > will register itself under the name /dev/*acd*. > > I have includes a modified version of "wormcontrol" that can talk > to the acd driver. It has two new commands "nextwriteable" that > tells the driver the next writeable block on a CDR/CDRW, used when > burning more that 1 track (for audio mostly). > > Example scripts for burning data & audio CD's are also included. > > The cd ripper program "cdd" is also here in a modified version > that can talk to the acd driver. > > Enjoy and let me know the results... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > 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 Fri Aug 14 11:36:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16077 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:36:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16055; Fri, 14 Aug 1998 11:36:36 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id OAA10077; Fri, 14 Aug 1998 14:37:38 -0400 (EDT) Date: Fri, 14 Aug 1998 14:37:38 -0400 (EDT) From: Mark turpin To: Julian Elischer cc: FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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 Universal Disk Format... It's how DVDs and some CD-Rs store data.. On Fri, 14 Aug 1998, Julian Elischer wrote: > what's UDF? > > > On Fri, 14 Aug 1998, Mark turpin wrote: > > > > > Is any body working on implementing UDF on FreeBSD? I looked in the > > archives and didn't see anything about it? > > > > > > Thanks > > > > Mark Turpin > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 11:53:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20115 for freebsd-current-outgoing; Fri, 14 Aug 1998 11:53:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19979; Fri, 14 Aug 1998 11:52:41 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id UAA00605; Fri, 14 Aug 1998 20:50:59 +0200 (CEST) (envelope-from sos) Message-Id: <199808141850.UAA00605@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: from Alfred Perlstein at "Aug 14, 98 02:32:54 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Fri, 14 Aug 1998 20:50:59 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: SЬren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Alfred Perlstein who wrote: > does this code have a watchdog to prevent ATAPI proccesses from tsleeping > forever? No, this is only to test ATAPI burners, prober timeout & error handeling is part of the new atapi subsystem, but that is not ready for primetime yet. Why are you especially interested in that ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 12:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23890 for freebsd-current-outgoing; Fri, 14 Aug 1998 12:16:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23793 for ; Fri, 14 Aug 1998 12:16:34 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA07416; Fri, 14 Aug 1998 12:16:01 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd007394; Fri Aug 14 12:15:56 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA29937; Fri, 14 Aug 1998 12:15:54 -0700 (MST) From: Terry Lambert Message-Id: <199808141915.MAA29937@usr05.primenet.com> Subject: Re: Tentative fix for VM bug To: karl@mcs.net (Karl Denninger) Date: Fri, 14 Aug 1998 19:15:53 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <19980814111421.45977@mcs.net> from "Karl Denninger" at Aug 14, 98 11:14:21 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 > > Note: If I have lost my mind, there are two other places where this > > could be happening instead. > > > > If I have lost my mind, then I expect an increase in the occurance > > "vm_page_free: freeing free page", and I will have to go back to > > the other places (which are vastly more complicated to fix). > > I can confirm that the propounded fix doesn't, at least not for the case of > a Diablo news server which gets files whacked with either zeros or random > trash contents from time to time. > > With the "fix" in I see no change of significance in behavior. John assures me that the fix will only mask a couple of the bugs I was aiming for (including the EOF bug). Your results are good (at least the "vm_page_free: freeing free page" isn't calling me a total idiot). But it's bad, in that it means the problem with the page aliases is most likely in vm_object.c, unless the code John Dyson sent me is correct (I have reservations; there is an order of operation discepancy between one part and the other of the patch, and I need John to tell me which was intended). To get the gist of why this is bad, do this: cd /sys/vm grep -5 busy *.c | more 8-(. In any case, there could be (and probably is) a seperate file extension with mmap bug. In theory, in a unified VM and buffer cache, it should never be necessary to have non-null msync() code. 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 Fri Aug 14 12:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26419 for freebsd-current-outgoing; Fri, 14 Aug 1998 12:32:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (congo-99.ppp.hooked.net [206.169.227.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26402 for ; Fri, 14 Aug 1998 12:32:38 -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 MAA04507; Fri, 14 Aug 1998 12:31:33 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 14 Aug 1998 12:31:33 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Kyle Mestery cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: new compiler? 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, 14 Aug 1998, Kyle Mestery wrote: [...] > > gcc 2.8.1? (i've heard masses of people complain it's buggy) > > ecgs (not heard much... but i know it has some interesting optimizations > > for i386, and better C++ support) > > anything else? > > > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. Well, I've tried a really recent egcs from their anoncvs server, and tried gcc 2.8 from the ports tree. egcs wouldn't even link when I tried to make a shared Qt lib, but worked nicely with static libs (albeit while eating up a few hundred megs of disk space..). gcc 2.8 nicely linked everything (Qt+various KDE stuff I'm working on), but when I tried to actually run everything.. I got seg faults or bus errors. Too bad Qt won't build with TenDRA... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 14:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20711 for freebsd-current-outgoing; Fri, 14 Aug 1998 14:53:39 -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 OAA20701 for ; Fri, 14 Aug 1998 14:53:37 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA11783; Fri, 14 Aug 1998 17:53:02 -0400 (EDT) Date: Fri, 14 Aug 1998 17:53:02 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF problems to occur 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, 14 Aug 1998, Brian Feldman wrote: > The transition from a.out to ELF will not be easy; I see some definite > potential hangups: Perhaps someone who experienced Linux's switchover can warn us of some likely 'issues'. 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 Aug 14 15:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23933 for freebsd-current-outgoing; Fri, 14 Aug 1998 15:06:38 -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 PAA23913 for ; Fri, 14 Aug 1998 15:06:35 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA26190; Fri, 14 Aug 1998 14:39:35 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdP26182; Fri Aug 14 21:39:28 1998 Date: Fri, 14 Aug 1998 14:39:24 -0700 (PDT) From: Julian Elischer To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: Funky DEVFS stuff. 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 *whack* *whack* *whack* DON'T DO THAT! The 'c' partition is "Magic" (for now) add an 'a' partition with teh same values next to the 'c' part and change the fstab to use it instead (leave the 'c' one there.. you always (for now) need a 'c' just don't USE it for filesystems etc. just use disklabel -er /dev/rsd0s1 to do this. On Fri, 14 Aug 1998, Alfred Perlstein wrote: > i posted a while back about devfs not being able to find my scsi disk, i'm > posting some info that might be useful. > > i think this is a problem because i did some funky stuff when i labled it, > however, mount CAN find the disk in a non-devfs system. > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #8: Sun Aug 9 14:52:17 EST 1998 > perlsta@server.local.sunyit.edu:/usr/src/sys/compile/K6233 > Timecounter "i8254" frequency 1193182 Hz cost 3794 ns > Timecounter "TSC" frequency 232961751 Hz cost 104 ns > CPU: AMD-K6tm w/ multimedia extensions (232.96-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x562 Stepping=2 > Features=0x8001bf > real memory = 100663296 (98304K bytes) > avail memory = 94851072 (92628K bytes) > DEVFS: ready for devices > Probing for devices on PCI bus 0: > chip0: rev 0x23 on > pci0.0.0 > chip1: rev 0x27 on pci0.7.0 > ide_pci0: rev 0x06 on > pci0.7.1 > chip2: rev 0x02 int d irq 11 on pci0.7.2 > ahc0: rev 0x01 int a irq 9 on > pci0.8.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 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 1812MB (3711990 512 byte sectors) > ed3: rev 0x00 int a irq 12 on > pci0.9.0 > ed3: address 00:00:21:4e:29:c3, type NE2000 (16 bit) > vga0: rev 0x41 on pci0.11.0 > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 flags 0x4 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x4> > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > pcm0 at 0x220 irq 10 drq 3 flags 0x15 on isa > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 4028MB (8249472 sectors), 8184 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > wdc1: unit 0 (atapi): , removable, intr, > dma, iord > y > wcd0: 343/3445Kb/sec, 382Kb cache, audio play, 255 volume levels, > ejectable tray > wcd0: 120mm audio disc loaded, unlocked > npx0 on motherboard > npx0: INT 16 interface > ppc0 at 0x378 irq 7 on isa > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > nlpt0: on ppbus 0 > nlpt0: Interrupt-driven port > ppi0: on ppbus 0 > plip0: on ppbus 0 > DEVFS: ready to run > IP packet filtering initialized, divert enabled, rule-based forwarding > disabled, > logging disabled > sd0: probing for MBR.. nope > sd0: probing for disklabel.. fd0: probing for MBR.. wd0: probing for MBR.. > part > 1, start=63, size=8249409 > wd0s1: attaching disklabel.. > part a, start=0, size=96001 > part b, start=96001, size=384000 > part e, start=480001, size=192000 > part f, start=672001, size=3788704 > part g, start=4460705, size=3788704 > fd0: hard error, block 0 (No status) > WOULD SELECT /wd0a but it doesn't exist > /wd0s1a exists, I'll use that > > right here i get prompt for single user mode because it can't find this > entry in fstab now: > /dev/sd0s1c /scsi ufs rw 1 1 > > ------ info from sd0 via disklable and such: > > # disklabel -r /dev/rsd0 | less > # /dev/rsd0: > type: SCSI > disk: sd0s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 231 > sectors/unit: 3711990 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 3711990 0 unused 0 0 # (Cyl. 0 - > 231*) > > ------- fdisk ------ > > # fdisk /dev/rsd0 > ******* Working on device /dev/rsd0 ******* > parameters extracted from in-core disklabel are: > cylinders=3711990 heads=1 sectors/track=1 (1 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=3711990 heads=1 sectors/track=1 (1 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 3711990 (1812 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 0; > end: cyl 231/ sector 30/ head 15 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > # > > > ok, heh :) now what? > i know i musta done something icky for me to be able to mount it normally > but DEVFS not being able to. > > thank you, > Alfred Perlstein > -- > > Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] > |-- There are operating systems, and then there's BSD. > \-- http://www.freebsd.org/ > > > 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 Fri Aug 14 15:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25218 for freebsd-current-outgoing; Fri, 14 Aug 1998 15:12:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25198 for ; Fri, 14 Aug 1998 15:12:07 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA07262; Fri, 14 Aug 1998 15:11:35 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd007239; Fri Aug 14 15:11:34 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA20997; Fri, 14 Aug 1998 15:11:32 -0700 (MST) From: Terry Lambert Message-Id: <199808142211.PAA20997@usr04.primenet.com> Subject: Re: new compiler? To: mestery@winternet.com (Kyle Mestery) Date: Fri, 14 Aug 1998 22:11:31 +0000 (GMT) Cc: bright@hotjobs.com, current@FreeBSD.ORG In-Reply-To: from "Kyle Mestery" at Aug 14, 98 09:47:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. Specifically, if you want to be able to use threads, you will need to link non-threaded applications against the threaded libc so that you aren't missing the per thread exception stack references. The way Jeremy Allison fixed this in 2.8.1 is the correct way (the code registers a callout routine in a list that doesn't break by default if no callouts are registered). This lets you choose at application link-time, rather than at compiler link-time, whether or not you have to link with a thread-safe libc. The overhead is less immense with kernel threads, but pure kernel threads are a bad model unless you have CPU affinity and choose to allocate only one thread per CPU; for large threaded applications, you end up paying thread context switch overhead if your threaded app if it's the only thing on the machine, and process context switch overhead if it's not (there is no clustering such that you context switch to another thread in your process when you give up the CPU, and putting sclustering in is wrong because you would starve the other processes). The best implementation is cooperative kernel and user space schedulers. And then you are back to having more libc overhead for the threaded libc. So a compiler that forces you to eat the overhead for all programs on the system, instead of eating the overhead only for programs that benefit from threads (ie: a conscious trade) is a bad compiler. > So, what are the chances of things happening along this front? Also, if > we do bring a new compiler into the tree, should we try and bring > FreeBSD's shared library mechanism along with it for compatability > reasons, or just go strictly elf? The a.out shared libraries have to be supported so long as there are dynamically linked commercial programs out there. FreeBSD can't afford to burn bridges when there are so few commercial products available on FreeBSD (IMO). 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 Fri Aug 14 15:14:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25776 for freebsd-current-outgoing; Fri, 14 Aug 1998 15:14:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25720; Fri, 14 Aug 1998 15:14:38 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA06086; Fri, 14 Aug 1998 15:14:06 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd006051; Fri Aug 14 15:14:04 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA21199; Fri, 14 Aug 1998 15:14:02 -0700 (MST) From: Terry Lambert Message-Id: <199808142214.PAA21199@usr04.primenet.com> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. To: sos@FreeBSD.ORG Date: Fri, 14 Aug 1998 22:14:02 +0000 (GMT) Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199808141707.TAA00337@sos.freebsd.dk> from "S?ren Schmidt" at Aug 14, 98 07:07:06 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 > A workable snapshot is available on: > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > From the README: > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > Please dont distribute this, only use it for testing, as it is > alpha level code which is undergoing rapid changes. I didn't see CAM in there; are you making it fit under CAM? NetBSD has unified their device model this wat, with apparently good results... 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 Fri Aug 14 15:19:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27052 for freebsd-current-outgoing; Fri, 14 Aug 1998 15:19:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from beavis.inetdirect.net (beavis.inetdirect.net [204.120.164.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26970 for ; Fri, 14 Aug 1998 15:18:53 -0700 (PDT) (envelope-from timsarver@netdirect.net) From: timsarver@netdirect.net Received: from tim (tech6.netdirect.net [204.120.164.16]) by beavis.inetdirect.net (8.8.5/8.7.3) with SMTP id RAA10342 for ; Fri, 14 Aug 1998 17:18:22 -0500 (EST) Message-Id: <199808142218.RAA10342@beavis.inetdirect.net> X-Sender: timsarver@netdirect.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 14 Aug 1998 17:19:23 -0500 To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-questions subscribe freebsd-announce END To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 15:36:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02160 for freebsd-current-outgoing; Fri, 14 Aug 1998 15:36:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01986 for ; Fri, 14 Aug 1998 15:35:35 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA21955; Fri, 14 Aug 1998 15:35:02 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd021938; Fri Aug 14 15:35:00 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA22151; Fri, 14 Aug 1998 15:34:56 -0700 (MST) From: Terry Lambert Message-Id: <199808142234.PAA22151@usr04.primenet.com> Subject: Re: new compiler? To: mestery@winternet.com (Kyle Mestery) Date: Fri, 14 Aug 1998 22:34:56 +0000 (GMT) Cc: smp@csn.net, bright@hotjobs.com, current@FreeBSD.ORG In-Reply-To: from "Kyle Mestery" at Aug 14, 98 01:23:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We have a fairly complex system running with 2.2.6, FreeBSD pthreads and > > g++28. We tried both the standard compiler and egcs, but neither would > > compile the complete project, let alone run. The biggest problem is in > > the area of c++ templates, g++28 will eat things the other 2 barfed on. > > We had to make one patch to gcc28 b4 building, and turn on the > > "GCC28_THREAD_AWARE" define in libc_r to fix the problem with dynamic > > chain handling. After this exceptions seem to work properly. > > > > My vote would be for gcc28. > > My reason's for wanting gcc-2.8.1 also lie along these lines, as we are > using a cross development environment at work that is complex and utilizes > a mix of gcc-2.8.1 front end and back-end linker/assembler from WRS, > targeting arm-wrs-vxworks. It works quite well, and we have no problems > with the compiler so far. To add more fuel to this fire, Whistle also made this dynamic chain change; I believe it's part of the FreeBSD gcc2.8 port, in fact. The Cygnus (egcs) guys didn't want the change because they had "solved" the problem by making you choose at compile time (per my other post), and Jeremy didn't want to submit the change to FSF because he didn't want to drive divergence between the two code bases. FWIW, I think Jeremy made the wrong decision, and I would be pleased if the FSF people would ask him for the change, under the terms of the GPL. 8-) 8-). The ACAP code makes heavy use of exceptions and threads; as far as I know, we are the only people who have brought it up using a g++ derived compiler; there were a number of changes having to do with g++ parsing of the :: namespace escape (ie: it demanded whitespace changes... bletch 8-)), but that is the only issue I have found so far with the 2.8.1 compiler. Most of the other changes were bad link order assumptions on the part of the ACAP authors and STL pthreads compliance level (Draft 4 vs. standard) assumptions in the Moscow Center for SPARC computing's STL (this is the best STL. Use it. It is more portable than the others, and is derived from the SGI and HP code). 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 Fri Aug 14 16:38:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15536 for freebsd-current-outgoing; Fri, 14 Aug 1998 16:38:57 -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 QAA15489; Fri, 14 Aug 1998 16:38:41 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA03368; Fri, 14 Aug 1998 19:38:08 -0400 (EDT) Date: Fri, 14 Aug 1998 19:38:08 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Mark turpin cc: Julian Elischer , FreeBSD hackers , FreeBSD Current Subject: Re: UDF Filesystem 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, 14 Aug 1998, Mark turpin wrote: > Universal Disk Format... It's how DVDs and some CD-Rs store data.. Whatever happened to ISO9660? Or is this a superset thereof? 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 Aug 14 17:07:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20226 for freebsd-current-outgoing; Fri, 14 Aug 1998 17:07:10 -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 RAA20213 for ; Fri, 14 Aug 1998 17:06:47 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id TAA02281 for ; Fri, 14 Aug 1998 19:04:03 -0500 (CDT) Message-ID: <35D4D073.C4D05089@webwizard.org.mx> Date: Fri, 14 Aug 1998 19:04:03 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Make Release Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else seeing this? Thanks ed sh -e /usr/src/release/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 160000 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 9. /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 2880 sectors 1.4MB in 1 cyl groups (9 c/g, 12.66MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 17:46:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25534 for freebsd-current-outgoing; Fri, 14 Aug 1998 17:46:47 -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 RAA25417 for ; Fri, 14 Aug 1998 17:45:05 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id KAA10489; Sat, 15 Aug 1998 10:51:49 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808150051.KAA10489@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: from Brian Feldman at "Aug 14, 98 12:21:24 pm" To: green@zone.syracuse.net (Brian Feldman) Date: Sat, 15 Aug 1998 10:51:48 +1000 (EST) Cc: 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 Brian Feldman wrote: > The transition from a.out to ELF will not be easy; I see some definite > potential hangups: We are not burning support for aout - just planning to change the default to elf. The answers to some of the points you raise depend on work being completed by various people. If none of this work is completed, 3.0 will ship with everything installed elf except the kernel, lkms, boot objects. I say this based on the state of what support is in the tree now plus patches that exist but haven't been committed. -- 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 Aug 14 18:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27439 for freebsd-current-outgoing; Fri, 14 Aug 1998 18:04:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27261 for ; Fri, 14 Aug 1998 18:02:58 -0700 (PDT) (envelope-from shmit@natasya.kublai.com) Received: from natasya.kublai.com (natasya.kublai.com [207.172.25.236]) by coleridge.kublai.com (8.8.8/8.8.8) with ESMTP id VAA12665; Fri, 14 Aug 1998 21:01:12 -0400 (EDT) (envelope-from shmit@natasya.kublai.com) Received: (from shmit@localhost) by natasya.kublai.com (8.8.8/8.8.8) id VAA28280; Fri, 14 Aug 1998 21:01:10 -0400 (EDT) Message-ID: <19980814210110.48283@kublai.com> Date: Fri, 14 Aug 1998 21:01:10 -0400 From: Brian Cully To: ben@rosengart.com, Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF problems to occur Reply-To: shmit@kublai.com Mail-Followup-To: ben@rosengart.com, Brian Feldman , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Snob Art Genre on Fri, Aug 14, 1998 at 05:53:02PM -0400 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 05:53:02PM -0400, Snob Art Genre wrote: > On Fri, 14 Aug 1998, Brian Feldman wrote: > > > The transition from a.out to ELF will not be easy; I see some definite > > potential hangups: > > Perhaps someone who experienced Linux's switchover can warn us of some > likely 'issues'. I wrote one of the docs for it, and my only warning is that it sucks if you have to do it all yourself. Being able to `make world' and be converted will be really nice. The only major concern (at the time) was with underscores in assembler files, but I think most of those problems have been fixed by now. -- Brian Cully ``And when one of our comrades was taken prisoner, blindfolded, hung upside-down, shot, and burned, we thought to ourselves, `These are the best experiences of our lives''' -Pathology (Joe Frank, Somewhere Out There) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 18:08:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28103 for freebsd-current-outgoing; Fri, 14 Aug 1998 18:08:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xalapa.lania.mx (xalapa.lania.mx [192.100.158.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA28046 for ; Fri, 14 Aug 1998 18:08:16 -0700 (PDT) (envelope-from horacio@xalapa.lania.mx) Received: from perote.lania.mx by xalapa.lania.mx (4.1/SMI-4.1) id AA03821; Fri, 14 Aug 98 20:08:22 CST Date: Fri, 14 Aug 98 20:08:22 CST From: horacio@xalapa.lania.mx (Horacio Diaz Requejo) Message-Id: <9808150208.AA03821@xalapa.lania.mx> To: ben@rosengart.com Subject: Re: UDF Filesystem Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Universal Disk Format... It's how DVDs and some CD-Rs store data.. > > Whatever happened to ISO9660? Or is this a superset thereof? > try http://www.soundblaster.com/mmuk/pcdvd/background.html It has a little description about de DVD technology and UDF file system format. Regards, Horacio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 18:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02357 for freebsd-current-outgoing; Fri, 14 Aug 1998 18:46:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02339 for ; Fri, 14 Aug 1998 18:46: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 SAA22621; Fri, 14 Aug 1998 18:43:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Edwin Culp cc: freebsd-current@FreeBSD.ORG Subject: Re: Make Release In-reply-to: Your message of "Fri, 14 Aug 1998 19:04:03 CDT." <35D4D073.C4D05089@webwizard.org.mx> Date: Fri, 14 Aug 1998 18:43:58 -0700 Message-ID: <22618.903145438@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, -current release builds are broken because of this. On hold until I either shrink the kernel or figure out some other way of reclaiming a few bytes. - Jordan > Anyone else seeing this? > > Thanks > > ed > > sh -e /usr/src/release/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std > 160000 fd1440 > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 9. > /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 2880 sectors > 1.4MB in 1 cyl groups (9 c/g, 12.66MB/g, 32 i/g) > super-block backups (for fsck -b #) at: > 32, > cpio: write error: No space left on device > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > > > 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 Fri Aug 14 19:03:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03392 for freebsd-current-outgoing; Fri, 14 Aug 1998 19:03:36 -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 TAA03384 for ; Fri, 14 Aug 1998 19:03:34 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id VAA03349; Fri, 14 Aug 1998 21:01:35 -0500 (CDT) Message-ID: <35D4EBFF.95B0312A@webwizard.org.mx> Date: Fri, 14 Aug 1998 21:01:35 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-current@FreeBSD.ORG Subject: Re: Make Release References: <22618.903145438@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks ed Jordan K. Hubbard wrote: > Yeah, -current release builds are broken because of this. On hold > until I either shrink the kernel or figure out some other way of > reclaiming a few bytes. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 20:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11089 for freebsd-current-outgoing; Fri, 14 Aug 1998 20:52:56 -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 UAA11084 for ; Fri, 14 Aug 1998 20:52:52 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id NAA31759 for ; Sat, 15 Aug 1998 13:22:21 +0930 (CST) Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA04204; Sat, 15 Aug 1998 13:22:20 +0930 Date: Sat, 15 Aug 1998 13:22:20 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: Softupdates patches 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 The recent softupdates patches committed by Julian solve the problem case I pointed out, and things have been running smoothly in the softupdates department. Thanks, Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 21:50:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15481 for freebsd-current-outgoing; Fri, 14 Aug 1998 21:50:05 -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 VAA15436 for ; Fri, 14 Aug 1998 21:49:59 -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 VAA10900; Fri, 14 Aug 1998 21:49:15 -0700 (PDT) (envelope-from jdp) Message-Id: <199808150449.VAA10900@austin.polstra.com> To: kgor@ksg.com Subject: Re: Is 3.0 going to be a.out? In-Reply-To: <199808110116.UAA03006@soccer.ksg.com> References: <199808110116.UAA03006@soccer.ksg.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 14 Aug 1998 21:49:15 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808110116.UAA03006@soccer.ksg.com>, Kent S. Gordon wrote: > Is the conversion from a.out to elf going to happen before or > after the release of 3.0 (~ Oct. 15)? Yes. ;-) Sorry, I couldn't resist. We are doing our best to make it happen before the release. -- 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 Fri Aug 14 22:55:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21157 for freebsd-current-outgoing; Fri, 14 Aug 1998 22:55: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 WAA21143 for ; Fri, 14 Aug 1998 22:55: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 PAA20785; Sat, 15 Aug 1998 15:54:24 +1000 Date: Sat, 15 Aug 1998 15:54:24 +1000 From: Bruce Evans Message-Id: <199808150554.PAA20785@godzilla.zeta.org.au> To: bright@www.hotjobs.com, mike@smith.net.au Subject: Re: Funky DEVFS stuff. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> c: 3711990 0 unused 0 0 # (Cyl. 0 - >> 231*) > >You can't do this. Make an 'a' partition that matches the 'c' >partition and use that instead. He just did. It should work. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 14 23:30:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26132 for freebsd-current-outgoing; Fri, 14 Aug 1998 23:30:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26027; Fri, 14 Aug 1998 23:29:48 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id IAA03408; Sat, 15 Aug 1998 08:25:14 +0200 (CEST) (envelope-from sos) Message-Id: <199808150625.IAA03408@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808142214.PAA21199@usr04.primenet.com> from Terry Lambert at "Aug 14, 98 10:14:02 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 15 Aug 1998 08:25:13 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: SЬren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Terry Lambert who wrote: > > A workable snapshot is available on: > > > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > > > From the README: > > > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > > Please dont distribute this, only use it for testing, as it is > > alpha level code which is undergoing rapid changes. > > I didn't see CAM in there; are you making it fit under CAM? NetBSD > has unified their device model this wat, with apparently good results... There is no CAM in there. There might be a hook in the ata driver to register the ATAPI devices through CAM later. Acessing ATA disk devices through CAM is not planned. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 05:42:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24537 for freebsd-current-outgoing; Sat, 15 Aug 1998 05:42:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24479 for ; Sat, 15 Aug 1998 05:42:17 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:2UM7UUQ+o2+haUI1peBcAi3I51u6Cqxw@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id OAA13942 for ; Sat, 15 Aug 1998 14:41:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808151241.OAA13942@gratis.grondar.za> To: current@FreeBSD.ORG Subject: NFS and AMD status? Date: Sat, 15 Aug 1998 14:41:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Is it just me, or are others seeing failures in NFS and the AMD? NFS sometimes hangs and/or fails to dismount, and the AMD simply does not work. All this on a very recent current. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 08:27:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06556 for freebsd-current-outgoing; Sat, 15 Aug 1998 08:27:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.NET (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06551 for ; Sat, 15 Aug 1998 08:27:37 -0700 (PDT) (envelope-from green@zone.syracuse.NET) Received: from localhost (green@localhost) by zone.syracuse.NET (8.8.8/8.8.7) with SMTP id LAA03361; Sat, 15 Aug 1998 11:25:51 -0400 (EDT) Date: Sat, 15 Aug 1998 11:25:51 -0400 (EDT) From: Brian Feldman To: John Birrell cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808150051.KAA10489@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 No, of course we're not going to be removing support for the FreeBSD a.out format, I would never expect us to! However, we really do need to start coordinating a bit with everyone working specifically with ELF. Perhaps temporarily hub should have another mailing list, freebsd-elf? Cheers, Brian Feldman green@unixhelp.org On Sat, 15 Aug 1998, John Birrell wrote: > Brian Feldman wrote: > > The transition from a.out to ELF will not be easy; I see some definite > > potential hangups: > > We are not burning support for aout - just planning to change the default > to elf. The answers to some of the points you raise depend on work being > completed by various people. If none of this work is completed, 3.0 will > ship with everything installed elf except the kernel, lkms, boot objects. > I say this based on the state of what support is in the tree now plus > patches that exist but haven't been committed. > > -- > 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 Sat Aug 15 10:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13513 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:05:49 -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 KAA13508 for ; Sat, 15 Aug 1998 10:05:47 -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 KAA17832 for ; Sat, 15 Aug 1998 10:05:17 -0700 (PDT) (envelope-from jdp) Message-Id: <199808151705.KAA17832@austin.polstra.com> To: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Date: Sat, 15 Aug 1998 10:05:16 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The transition from a.out to ELF will not be easy; I see some definite > potential hangups: We are aware of these things and are doing our best to solve the most important problems in time for the release. Please understand, there are going to be many small-to-medium problems and things that don't work quite right at first. We are trying to get the a.out->ELF transition done in -current as soon as possible, so that there will be time to work out the worst problems before 3.0 is released. John Birrell is putting in a heroic effort toward that end. Being uniprocessor humans, we can't work on ELF and reply to the mailing lists at the same time. To those who keep whining, "When will ELF be ready?" the answer is: another 10 minutes later, thanks to you. > Will I have to recompile all my many libraries for ELF > or will objcopy work in all cases? Objcopy doesn't understand a.out shared libraries. A special converter will be necessary. I've got it started, but have serious doubts about whether it will be ready in time for 3.0. > M3 should already be ELF-compilable I'm the maintainer of the M3 port, and I think it will take some work to get it to generate ELF. No major problems, just some work. It's one of the lower priorities, as far as I'm concerned. You will probably have to continue to use it as a.out at first. The same undoubtedly holds for a number of other ports. Remember, things that don't work under ELF can still be built as a.out programs until they are fixed. > I don't see how ldconfig is in its present state ready for ELF. For the short term, you may have to simply ensure that LD_LIBRARY_PATH is set properly. It's on my list to fix the ELF dynamic linker so that it can also get its search path from the ldconfig hints file. "ldconfig -r" or something like it will also have to be fixed for ELF, because the ports system relies on it to determine whether shared library dependencies are already installed or not. > And supposedly the ELF kernel is bootable nowadays with a few > patches; do lkm's work? I doubt we'll have time to switch the kernel to ELF before 3.0 release. -- 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 Sat Aug 15 10:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13962 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:09:53 -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 KAA13951 for ; Sat, 15 Aug 1998 10:09:51 -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 KAA17856; Sat, 15 Aug 1998 10:09:20 -0700 (PDT) (envelope-from jdp) Message-Id: <199808151709.KAA17856@austin.polstra.com> To: julian@whistle.com Subject: Re: Funky DEVFS stuff. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sat, 15 Aug 1998 10:09:20 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The 'c' partition is "Magic" (for now) Is 'd' still magic too? I seem to recall that it was magic once upon a time. But not any more, right? Also, 'b' used to be magic (reserved for swap) in some Unix variants. Not for us, right? -- 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 Sat Aug 15 10:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17277 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:45:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17271 for ; Sat, 15 Aug 1998 10:45:30 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id KAA00827; Sat, 15 Aug 1998 10:43:32 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808151043.KAA00827@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-reply-to: Your message of "Sat, 15 Aug 1998 10:05:16 MST." <199808151705.KAA17832@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 10:43:31 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And supposedly the ELF kernel is bootable nowadays with a few > > patches; do lkm's work? > > I doubt we'll have time to switch the kernel to ELF before 3.0 > release. The lkm system will not be ported for ELF, we will be using kld instead. Since this is close to my work on the bootstrap, and loading ELF kernels is about all that it's not getting right, I'm reasonably optomistic that this will indeed be ready at least as an option if not the default. -- \\ 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 Sat Aug 15 10:50:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18057 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:50:48 -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 KAA18048 for ; Sat, 15 Aug 1998 10:50:46 -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 KAA18030; Sat, 15 Aug 1998 10:50:09 -0700 (PDT) (envelope-from jdp) Message-Id: <199808151750.KAA18030@austin.polstra.com> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-reply-to: Your message of "Sat, 15 Aug 1998 10:43:31 -0000." <199808151043.KAA00827@word.smith.net.au> Date: Sat, 15 Aug 1998 10:50:09 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I doubt we'll have time to switch the kernel to ELF before 3.0 > > release. > > The lkm system will not be ported for ELF, we will be using kld > instead. Since this is close to my work on the bootstrap, and > loading ELF kernels is about all that it's not getting right, I'm > reasonably optomistic that this will indeed be ready at least as an > option if not the default. That's good news! -- 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 Sat Aug 15 10:59:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18764 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:59:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18759 for ; Sat, 15 Aug 1998 10:59:39 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA00497; Sat, 15 Aug 1998 09:44:28 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808150944.JAA00497@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: NFS and AMD status? In-reply-to: Your message of "Sat, 15 Aug 1998 14:41:34 +0200." <199808151241.OAA13942@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Aug 1998 09:44:28 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > Is it just me, or are others seeing failures in NFS and the AMD? > > NFS sometimes hangs and/or fails to dismount, and the AMD simply does > not work. All this on a very recent current. No. But aren't you supposed to be reviewing Harlan's contribified am-utils? -- \\ 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 Sat Aug 15 10:59:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18818 for freebsd-current-outgoing; Sat, 15 Aug 1998 10:59:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles334.castles.com [208.214.167.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18770; Sat, 15 Aug 1998 10:59:42 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.8) with ESMTP id JAA00459; Sat, 15 Aug 1998 09:36:59 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808150936.JAA00459@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: tlambert@primenet.com (Terry Lambert), current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-reply-to: Your message of "Sat, 15 Aug 1998 08:25:13 +0200." <199808150625.IAA03408@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 15 Aug 1998 09:33:09 +0000 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA18792 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > > > Please dont distribute this, only use it for testing, as it is > > > alpha level code which is undergoing rapid changes. > > > > I didn't see CAM in there; are you making it fit under CAM? NetBSD > > has unified their device model this wat, with apparently good results... > > There is no CAM in there. There might be a hook in the ata driver > to register the ATAPI devices through CAM later. Acessing ATA disk > devices through CAM is not planned. You've changed your mind *again*? For what it's worth, I don't see much value in treating ATA disks as though they were SCSI disks; the overhead in translation is probably too high. On the other hand, I'm less sure about things that use the ATAPI packet protocol. Still, and more importantly, you're the one doing the work. -- \\ 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 Sat Aug 15 11:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23187 for freebsd-current-outgoing; Sat, 15 Aug 1998 11:40:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23113 for ; Sat, 15 Aug 1998 11:40:01 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id TAA01962; Sat, 15 Aug 1998 19:39:32 +0100 (BST) Date: Sat, 15 Aug 1998 19:39:32 +0100 (BST) From: Doug Rabson To: Mike Smith cc: John Polstra , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808151043.KAA00827@word.smith.net.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 Sat, 15 Aug 1998, Mike Smith wrote: > > > And supposedly the ELF kernel is bootable nowadays with a few > > > patches; do lkm's work? > > > > I doubt we'll have time to switch the kernel to ELF before 3.0 > > release. > > The lkm system will not be ported for ELF, we will be using kld > instead. Since this is close to my work on the bootstrap, and loading > ELF kernels is about all that it's not getting right, I'm reasonably > optomistic that this will indeed be ready at least as an option if not > the default. Loading an ELF kernel with the new bootstrap is pretty easy. I did it today on the alpha. It should be possible to use the same ELF loader for i386 with some extra work. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 11:48:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24156 for freebsd-current-outgoing; Sat, 15 Aug 1998 11:48:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24132; Sat, 15 Aug 1998 11:48:47 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA05540; Sat, 15 Aug 1998 11:30:51 -0700 (PDT) Message-Id: <199808151830.LAA05540@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Mike Smith Cc: sos@FreeBSD.ORG, tlambert@primenet.com (Terry Lambert), current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 15 Aug 1998 11:30:50 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998 09:33:09 +0000 Mike Smith wrote: > You've changed your mind *again*? > > For what it's worth, I don't see much value in treating ATA disks as > though they were SCSI disks; the overhead in translation is probably > too high. On the other hand, I'm less sure about things that use the > ATAPI packet protocol. Considering that even SCSI command passthrough works on many ATAPI disks and CD-ROMS, it really is the right thing to do, and we have had a LOT of success doing it this way in NetBSD. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 12:04:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26126 for freebsd-current-outgoing; Sat, 15 Aug 1998 12:04:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26102; Sat, 15 Aug 1998 12:04:43 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id VAA08482; Sat, 15 Aug 1998 21:02:53 +0200 (CEST) (envelope-from sos) Message-Id: <199808151902.VAA08482@sos.freebsd.dk> Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. In-Reply-To: <199808150936.JAA00459@word.smith.net.au> from Mike Smith at "Aug 15, 98 09:33:09 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 15 Aug 1998 21:02:53 +0200 (CEST) Cc: sos@FreeBSD.ORG, tlambert@primenet.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG From: SЬren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Mike Smith who wrote: > > > > There is no CAM in there. There might be a hook in the ata driver > > to register the ATAPI devices through CAM later. Acessing ATA disk > > devices through CAM is not planned. > > You've changed your mind *again*? No :) > For what it's worth, I don't see much value in treating ATA disks as > though they were SCSI disks; the overhead in translation is probably > too high. On the other hand, I'm less sure about things that use the > ATAPI packet protocol. The ATA driver with lowlevel ATAPI support _must_ be implemented in all cases, the difference is if the ATAPI device are registered under CAM (scsi) or if there are nataive ATAPI drivers instead. Since I've allready written an ATAPI tape driver, and now an ATAPI CD-R/RW driver (which doesn't exist for CAM), I see no reason why not to have them. There is nothing hindering a CAM hook too, for those wanting that, but that will be up in the future until CAM gets "serious" enough. I se NO reason to bloat an ATA/ATAPI only system with all the CAM stuff though, but in a mixed ATA/ATAPI/SCSI system it might have some merit. > Still, and more importantly, you're the one doing the work. Exactly, and as long as its my spare time, I'll do the deciding :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 12:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26709 for freebsd-current-outgoing; Sat, 15 Aug 1998 12:08:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26649 for ; Sat, 15 Aug 1998 12:07:55 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:gxr9bmOkalwJvBMdxZHcwyNUhls7SSwL@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA14913; Sat, 15 Aug 1998 21:06:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808151906.VAA14913@gratis.grondar.za> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: NFS and AMD status? Date: Sat, 15 Aug 1998 21:06:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Is it just me, or are others seeing failures in NFS and the AMD? > > > > NFS sometimes hangs and/or fails to dismount, and the AMD simply does > > not work. All this on a very recent current. > > No. But aren't you supposed to be reviewing Harlan's contribified > am-utils? YeahYeahYeah! In my Copious Free Time(tm) I'm working flat-out on Perl5 and K5. Somewhere, I was hoping that someone had a Quick-fix(tm). :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 12:12:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27782 for freebsd-current-outgoing; Sat, 15 Aug 1998 12:12:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from owlnet.rice.edu (owlnet.rice.edu [128.42.49.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27777 for ; Sat, 15 Aug 1998 12:12:57 -0700 (PDT) (envelope-from jpc@rice.edu) Received: from ural.owlnet.rice.edu (ural.owlnet.rice.edu [128.42.48.100]) by owlnet.rice.edu (8.9.0/8.9.0) with ESMTP id OAA14758 for ; Sat, 15 Aug 1998 14:12:26 -0500 (CDT) Received: from rice.edu (swb3-asyn-45.rice.edu [128.42.176.152]) by ural.owlnet.rice.edu (8.8.5/8.8.5) with ESMTP id OAA00239 for ; Sat, 15 Aug 1998 14:12:25 -0500 (CDT) Message-ID: <35D5DEA2.6EE9E85B@rice.edu> Date: Sat, 15 Aug 1998 19:16:50 +0000 From: John Paul Campbell X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: make world error in libstdc++ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the following from sources I cvsup'd on 8/13/98: ===> libstdc++ /usr/obj/usr/src/gnu/lib/libstdc++ created for /usr/src/gnu/lib/libstdc++ cd /usr/src/secure/lib && /usr/obj/usr/src/tmp/usr/bin/make depend && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all install cleandir obj cd /usr/src/secure/lib && install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ---- The file I used to cvsup the sources was: *default host=cvsup.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs delete use-rel-suffix compress *default delete use-rel-suffix *default compress src-all cvs-crypto Any help would be appreciated. My current kernel is 2.2.5-RELEASE. Thanks, John jpc@rice.edu john.campbell@wcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 12:56:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02269 for freebsd-current-outgoing; Sat, 15 Aug 1998 12:56: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 MAA02257 for ; Sat, 15 Aug 1998 12:56:47 -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 FAA24483; Sun, 16 Aug 1998 05:56:13 +1000 Date: Sun, 16 Aug 1998 05:56:13 +1000 From: Bruce Evans Message-Id: <199808151956.FAA24483@godzilla.zeta.org.au> To: jdp@polstra.com, julian@whistle.com Subject: Re: Funky DEVFS stuff. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The 'c' partition is "Magic" (for now) > >Is 'd' still magic too? I seem to recall that it was magic once upon >a time. But not any more, right? No. At least not in FreeBSD (versions >= 2.0.5). 'c' isn't as magic as it used to be. It mainly has conventional uses that might cause problems for programs and users that blindly believe that the convensions are followed. E.g., the bootblocks default to 'a' and may give stray results unless you specify 'c'. If 'c' isn't the only partition with a nonzero size, then you don't want to use it for anything (except disk labeling and bad144 data) since it overlaps the other partitions. You don't really want to use it for labelling or bad144 data either. Normally the 'a' partition overlaps the label, and if 'a' is used for an ffs filesystem or swap then the label won't be overwritten. Foreign newfs's (run on 'a') will probably attempt to overwrite the label and fail because the label is write protected. >Also, 'b' used to be magic (reserved for swap) in some Unix variants. >Not for us, right? It is conventionally reserved for swap in FreeBSD too. It is a bit more than conventionally reserved for kernel dumps in FreeBSD - dumps are not permitted on devices whose minor is 1 modulo 8 (see kern_shutdown.c:dumpsys() and autoconf.c:setdumpdev()). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 12:57:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02528 for freebsd-current-outgoing; Sat, 15 Aug 1998 12:57:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02523 for ; Sat, 15 Aug 1998 12:57:49 -0700 (PDT) (envelope-from bright@www.hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id PAA05061; Sat, 15 Aug 1998 15:57:04 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 15 Aug 1998 15:57:04 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mark Murray cc: Mike Smith , current@FreeBSD.ORG Subject: Re: NFS and AMD status? In-Reply-To: <199808151906.VAA14913@gratis.grondar.za> 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 working on perl5 a bit, i'm kinda busy, but i got libperl.* setup already (easy) the odd part is handling the documentation "generation" if you want to ask/help me about anything i'm looking too. -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Sat, 15 Aug 1998, Mark Murray wrote: > Mike Smith wrote: > > > Is it just me, or are others seeing failures in NFS and the AMD? > > > > > > NFS sometimes hangs and/or fails to dismount, and the AMD simply does > > > not work. All this on a very recent current. > > > > No. But aren't you supposed to be reviewing Harlan's contribified > > am-utils? > > YeahYeahYeah! > > In my Copious Free Time(tm) I'm working flat-out on Perl5 and K5. > > Somewhere, I was hoping that someone had a Quick-fix(tm). > > :-) > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > 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 Aug 15 13:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02943 for freebsd-current-outgoing; Sat, 15 Aug 1998 13:01:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02929 for ; Sat, 15 Aug 1998 13:01:21 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:LzXKHlKuPxNmeOv6Gyn/kItBYg0EKd50@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id WAA15064; Sat, 15 Aug 1998 22:00:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808152000.WAA15064@gratis.grondar.za> To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: NFS and AMD status? Date: Sat, 15 Aug 1998 22:00:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > i'm working on perl5 a bit, i'm kinda busy, but i got libperl.* setup > already (easy) the odd part is handling the documentation "generation" I've done most of it - I am just tidying up and making sure it doesn't break virgin systems. The documentation stuff was easy :-) > if you want to ask/help me about anything i'm looking too. Send it over - I'll plagiarise^wuse any good ideas :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 13:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09687 for freebsd-current-outgoing; Sat, 15 Aug 1998 13:49:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09680 for ; Sat, 15 Aug 1998 13:49:21 -0700 (PDT) (envelope-from root@pozo.com) Received: from localhost (root@localhost) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id NAA07904 for ; Sat, 15 Aug 1998 13:48:40 -0700 (PDT) (envelope-from root@pozo.com) Date: Sat, 15 Aug 1998 13:48:39 -0700 (PDT) From: Manfred Antar To: current@FreeBSD.ORG Subject: make world today 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 >From current sources 8/15/98 while doing a make world i get cc -O2 -pipe -m486 -Wall -DXPG4 -I/usr/src/lib/libxpg4/../libc/locale -c /usr/src/lib/libxpg4/../libc/locale/big5.c -o big5.o /usr/src/lib/libxpg4/../libc/locale/big5.c:64: parse error before `u_int' /usr/src/lib/libxpg4/../libc/locale/big5.c:64: warning: data definition has no type or storage class /usr/src/lib/libxpg4/../libc/locale/big5.c: In function `_BIG5_sgetrune': /usr/src/lib/libxpg4/../libc/locale/big5.c:79: warning: implicit declaration of function `_big5_check' /usr/src/lib/libxpg4/../libc/locale/big5.c:85: `u_int' undeclared (first use this function) /usr/src/lib/libxpg4/../libc/locale/big5.c:85: (Each undeclared identifier is reported only once /usr/src/lib/libxpg4/../libc/locale/big5.c:85: for each function it appears in.) *** Error code 1 Stop. big5.c was recently changed Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 14:01:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11079 for freebsd-current-outgoing; Sat, 15 Aug 1998 14:01:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11071 for ; Sat, 15 Aug 1998 14:01:16 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id NAA18734 for ; Sat, 15 Aug 1998 13:59:24 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 15 Aug 1998 13:58:17 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: current@FreeBSD.ORG Subject: x11amp port on current.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed, x11amp port doesnt work on current......I am useiong kernel sound...is there a fix for this? --------------------- William Woods Date: 15-Aug-98 / Time: 13:57:18 --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 14:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13369 for freebsd-current-outgoing; Sat, 15 Aug 1998 14:19:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13363 for ; Sat, 15 Aug 1998 14:19:07 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA10586; Sat, 15 Aug 1998 14:18:32 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd010557; Sat Aug 15 14:18:25 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA22828; Sat, 15 Aug 1998 14:18:19 -0700 (MST) From: Terry Lambert Message-Id: <199808152118.OAA22828@usr01.primenet.com> Subject: Re: NFS and AMD status? To: mark@grondar.za (Mark Murray) Date: Sat, 15 Aug 1998 21:18:16 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199808151241.OAA13942@gratis.grondar.za> from "Mark Murray" at Aug 15, 98 02:41:34 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 > Is it just me, or are others seeing failures in NFS and the AMD? > > NFS sometimes hangs and/or fails to dismount, and the AMD simply does > not work. All this on a very recent current. See David Greenman's patches on the -hackers list, in reply to my "back up one after a sleep and run at it again" patch. They appear to stabilize NFS PAGE_BUSY problems. Also, I will post a patch a little later that result in a dianostic panic on a page stomp, and a better fix for vm_object_page_remove() based on discussion with John Dyson about my previous patch. I'm pretty sure the panic won't be hit (the result of a stomp is an orphan page, not a page alias), unless you are seeing the "magically zeroed page" bug. You will need to compile *with* DIAGNOSTIC and *without* MAX_PERF to test them, so be forewarned. 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 Aug 15 14:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14230 for freebsd-current-outgoing; Sat, 15 Aug 1998 14:24:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14218 for ; Sat, 15 Aug 1998 14:24:25 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA23943; Sat, 15 Aug 1998 14:23:55 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd023915; Sat Aug 15 14:23:54 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA23045; Sat, 15 Aug 1998 14:23:51 -0700 (MST) From: Terry Lambert Message-Id: <199808152123.OAA23045@usr01.primenet.com> Subject: Re: Funky DEVFS stuff. To: jdp@polstra.com (John Polstra) Date: Sat, 15 Aug 1998 21:23:51 +0000 (GMT) Cc: julian@whistle.com, current@FreeBSD.ORG In-Reply-To: <199808151709.KAA17856@austin.polstra.com> from "John Polstra" at Aug 15, 98 10:09:20 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 'c' partition is "Magic" (for now) The c partition is magic for hysterical raisons of spanning the whole disk. It's there fore cruft like disklabel and partitioning programs that operate on the whole disk, but don't use ioctl()'s to do it (obviously, if a label is useful, the kernel already has a model of it, and user space code dependent on c is just duplicating effort). > Is 'd' still magic too? I seem to recall that it was magic once upon > a time. But not any more, right? The d partition was magic because it used to span the whole FreeBSD area. Now we trust the DOS parittion table (or ourselves, if we are in "dangerously without a second stage boot record" mode. > Also, 'b' used to be magic (reserved for swap) in some Unix variants. > Not for us, right? See the disklabel. The use of swap is dictated by the "partition" type field. 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 Aug 15 14:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14540 for freebsd-current-outgoing; Sat, 15 Aug 1998 14:25:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14533 for ; Sat, 15 Aug 1998 14:25:42 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA13358; Sat, 15 Aug 1998 14:25:11 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd013317; Sat Aug 15 14:25:06 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA23138; Sat, 15 Aug 1998 14:25:02 -0700 (MST) From: Terry Lambert Message-Id: <199808152125.OAA23138@usr01.primenet.com> Subject: Re: ELF problems to occur To: dfr@nlsystems.com (Doug Rabson) Date: Sat, 15 Aug 1998 21:25:01 +0000 (GMT) Cc: mike@smith.net.au, jdp@polstra.com, current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Aug 15, 98 07:39:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Loading an ELF kernel with the new bootstrap is pretty easy. I did it > today on the alpha. It should be possible to use the same ELF loader for > i386 with some extra work. Was this a NetBSD ELF kernel or a FreeBSD ELF kernel? 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 Aug 15 14:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17043 for freebsd-current-outgoing; Sat, 15 Aug 1998 14:41:11 -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 OAA17020 for ; Sat, 15 Aug 1998 14:41:05 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA13299; Sun, 16 Aug 1998 07:48:58 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808152148.HAA13299@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: <199808152125.OAA23138@usr01.primenet.com> from Terry Lambert at "Aug 15, 98 09:25:01 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 16 Aug 1998 07:48:58 +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 Terry Lambert wrote: > > Loading an ELF kernel with the new bootstrap is pretty easy. I did it > > today on the alpha. It should be possible to use the same ELF loader for > > i386 with some extra work. > > Was this a NetBSD ELF kernel or a FreeBSD ELF kernel? 8-). FreeBSD/Alpha is now using a native kernel. I'm about to remove all the NetBSD kludges from libc that provided the NetBSD syscall interface we've used until now. -- 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 Sat Aug 15 15:29:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22979 for freebsd-current-outgoing; Sat, 15 Aug 1998 15:29:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA22946 for ; Sat, 15 Aug 1998 15:29:47 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 5644 invoked by uid 1000); 15 Aug 1998 23:31:59 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 15 Aug 1998 19:31:59 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: Where is my error? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In ``make buildworld'' as of this morning: cc -O -pipe -Wall -DXPG4 -I/usr/src/3.0/src/lib/libxpg4/../libc/locale -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c -o big5.o /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: parse error before `u_int' /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: warning: data definition has no type or storage class /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c: In function `_BIG5_sgetrune': /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:79: warning: implicit declaration of function `_big5_check' /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: `u_int' undeclared (first use this function) /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: (Each undeclared identifier is reported only once /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: for each function it appears in.) *** Error code 1 Me thinks may be a problem there... Sincerely Yours, Shimon@Simon-Shapiro.ORG Simon Shapiro 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 15:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26856 for freebsd-current-outgoing; Sat, 15 Aug 1998 15:55:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26848 for ; Sat, 15 Aug 1998 15:55:50 -0700 (PDT) (envelope-from lickyou@ein-hashofet.co.il) Received: from host41-68.mishkei.org.il (host41-68.mishkei.org.il [62.0.68.41]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id BAA13231; Sun, 16 Aug 1998 01:53:56 +0300 Date: Sun, 16 Aug 1998 01:51:57 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@localhost.my.domain Reply-To: rom_glsa@ein-hashofet.co.il To: William Woods cc: current@FreeBSD.ORG Subject: Re: x11amp port on 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 Yes. Incase you havent noticed, the X11AMP port requires OSS. I believe it even says that if you try running it without OSS installed. What you can do, is download the statically-linked linux version from the website, and run it using the linux emulator. works great. Make sure you use luigi's, voxware doesnt seem to like it, or vice-versa. Gilad. On Sat, 15 Aug 1998, William Woods wrote: > I just noticed, x11amp port doesnt work on current......I am useiong kernel > sound...is there a fix for this? > > --------------------- > William Woods > Date: 15-Aug-98 / Time: 13:57:18 > --> FreeBSD 3.0 CURRENT <-- > > 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 Aug 15 15:59:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27575 for freebsd-current-outgoing; Sat, 15 Aug 1998 15:59:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27566 for ; Sat, 15 Aug 1998 15:59:46 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA04779; Sat, 15 Aug 1998 18:59:07 -0400 (EDT) Date: Sat, 15 Aug 1998 18:59:06 -0400 (EDT) From: "Matthew N. Dodd" To: John Polstra cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808151705.KAA17832@austin.polstra.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, 15 Aug 1998, John Polstra wrote: > For the short term, you may have to simply ensure that LD_LIBRARY_PATH > is set properly. It's on my list to fix the ELF dynamic linker so > that it can also get its search path from the ldconfig hints file. Whats wrong with specifying the search path with the '-R' flag when the program is linked? Just because Linux didn't get this right doesn't mean we have to follow suit. As a rule, on Solaris, I dislike having LD_LIBRARY_PATH set at all. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 16:12:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29615 for freebsd-current-outgoing; Sat, 15 Aug 1998 16:12:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29610 for ; Sat, 15 Aug 1998 16:12:51 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id TAA04900; Sat, 15 Aug 1998 19:12:11 -0400 (EDT) Date: Sat, 15 Aug 1998 19:12:10 -0400 (EDT) From: "Matthew N. Dodd" To: John Birrell cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808152148.HAA13299@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 Sun, 16 Aug 1998, John Birrell wrote: > FreeBSD/Alpha is now using a native kernel. I'm about to remove all the > NetBSD kludges from libc that provided the NetBSD syscall interface we've > used until now. If they're non-intrusive for native FreeBSD systems, why not leave them in. It would make bootstrapping another port from NetBSD that much easier. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 16:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29781 for freebsd-current-outgoing; Sat, 15 Aug 1998 16:14:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29776 for ; Sat, 15 Aug 1998 16:14:24 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id AAA06186 for ; Sun, 16 Aug 1998 00:13:52 +0100 (BST) Message-ID: <35D61631.47D5DACA@tdx.co.uk> Date: Sun, 16 Aug 1998 00:13:53 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Can't build kernel with 15/08/98 @ 23:17 source Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I can't seem to build a kernel with the latest sources... It falls over with: " caladan# make loading kernel cd.o: Undefined symbol `_scsi_device_register' referenced from text segment cd.o: Undefined symbol `_scsi_open' referenced from text segment cd.o: Undefined symbol `_scsi_ioctl' referenced from text segment cd.o: Undefined symbol `_scsi_close' referenced from text segment cd.o: Undefined symbol `_scsi_minphys' referenced from text segment cd.o: Undefined symbol `_scsi_strategy' referenced from text segment cd.o: Undefined symbol `_extend_get' referenced from text segment cd.o: Undefined symbol `_extend_get' referenced from text segment cd.o: Undefined symbol `_extend_get' referenced from text segment cd.o: Undefined symbol `_extend_get' referenced from text segment (heaps of more like the above) " Can anybody suggest anything? - I have the following lines in the kernel config: " controller ahc0 controller ahc1 controller ahc2 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows " I've made sure to do a 'make clean; make depend; make'... I have a horrible feeling that this is pilot error, but I'm stumped... ;-( Regards, Karl Pielorz ---------------------------------------------------------------------------- Karl Pielorz 'mailto:kpielorz@tdx.co.uk' This system runs http://freebsd.org ~ - Any opinions in this posting are my own and not those of my employer - ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 16:15:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29983 for freebsd-current-outgoing; Sat, 15 Aug 1998 16:15:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29967 for ; Sat, 15 Aug 1998 16:15:13 -0700 (PDT) (envelope-from chat.ru!osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id DAA22362; Sun, 16 Aug 1998 03:14:37 +0400 (MSD) Received: by sunny.aha.ru id DAA08959; (8.8.8/vak/1.9) Sun, 16 Aug 1998 03:14:03 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma008942; Sun Aug 16 03:13:50 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id DAA20847; (8.9.1/vak/1.9) Sun, 16 Aug 1998 03:16:47 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.0/8.9.0) with ESMTP id DAA23650; Sun, 16 Aug 1998 03:14:05 +0400 (MSD) Date: Sun, 16 Aug 1998 03:14:04 +0400 (MSD) From: oZZ!!! X-Sender: osa@localhost To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is my error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R X-MIME-Autoconverted: from 8bit to quoted-printable by serv.etrust.ru id DAA20847 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id QAA29974 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Aug 1998, Simon Shapiro wrote: > In ``make buildworld'' as of this morning: > > cc -O -pipe -Wall -DXPG4 -I/usr/src/3.0/src/lib/libxpg4/../libc/locale > -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c -o big5.o > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: parse error before > `u_int' > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: warning: data > definition has no type or storage class > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c: In function > `_BIG5_sgetrune': > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:79: warning: implicit > declaration of function `_big5_check' > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: `u_int' undeclared > (first use this function) > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: (Each undeclared > identifier is reported only once > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: for each function it > appears in.) > *** Error code 1 > > Me thinks may be a problem there... > > > > Sincerely Yours, > Shimon@Simon-Shapiro.ORG > Simon Shapiro 770.265.7340 > > Now I cvsuped my source-tree & too have this problem. Rgdz, Осокин Сергей aka oZZ, osa@chat.ru FreeBSD - Да пребудет с нами сила! http://www.chat.ru/~osa/main.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 16:37:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02984 for freebsd-current-outgoing; Sat, 15 Aug 1998 16:37:45 -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 QAA02979 for ; Sat, 15 Aug 1998 16:37:44 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA08257; Sat, 15 Aug 1998 19:37:12 -0400 (EDT) Date: Sat, 15 Aug 1998 19:37:12 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is my error? 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 added "#include " to my copy of big5.c and everything compiled. However, the make world died installing in usr.bin/mklocale with this: install: mkstemp: /usr/share/locale/zh_TW.BIG5/INS@4350 for /usr/share/locale/zh _TW.BIG5/LC_CTYPE: No such file or directory On Sat, 15 Aug 1998, Simon Shapiro wrote: > In ``make buildworld'' as of this morning: > > cc -O -pipe -Wall -DXPG4 -I/usr/src/3.0/src/lib/libxpg4/../libc/locale > -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c -o big5.o > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: parse error before > `u_int' > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:64: warning: data > definition has no type or storage class > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c: In function > `_BIG5_sgetrune': > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:79: warning: implicit > declaration of function `_big5_check' > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: `u_int' undeclared > (first use this function) > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: (Each undeclared > identifier is reported only once > /usr/src/3.0/src/lib/libxpg4/../libc/locale/big5.c:85: for each function it > appears in.) > *** Error code 1 > > Me thinks may be a problem there... > > > > Sincerely Yours, > Shimon@Simon-Shapiro.ORG > Simon Shapiro 770.265.7340 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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 Sat Aug 15 16:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04879 for freebsd-current-outgoing; Sat, 15 Aug 1998 16:50:25 -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 QAA04874 for ; Sat, 15 Aug 1998 16:50:23 -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 QAA20449; Sat, 15 Aug 1998 16:49:26 -0700 (PDT) Message-Id: <199808152349.QAA20449@implode.root.com> To: Julian Elischer cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Tentative fix for VM bug In-reply-to: Your message of "Fri, 14 Aug 1998 10:59:57 PDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 15 Aug 1998 16:49:26 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >yes, but is it a bug that he's reporting? I don't see anything wrong with vm_object_page_remove(). We'd have far more serious problems if there was something wrong with it (the system wouldn't last for more than a few seconds, if that), and further, the problem wouldn't be specific to just NFS. My thinking at the moment is that the problem is caused by the lack of NFSnode locking; we depend on VOP_LOCK actually doing something in many parts of the code, and with nfs_lock() being a noop, it just doesn't happen. There might be a way to fix this without messing with nfs_lock(), but the exact failure scenario will need to be looked at carefully before this can be determined. -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 Aug 15 17:14:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07452 for freebsd-current-outgoing; Sat, 15 Aug 1998 17:14:50 -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 RAA07436 for ; Sat, 15 Aug 1998 17:14:45 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA16120; Sat, 15 Aug 1998 20:14:02 -0400 (EDT) (envelope-from wollman) Date: Sat, 15 Aug 1998 20:14:02 -0400 (EDT) From: Garrett Wollman Message-Id: <199808160014.UAA16120@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: John Polstra , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: References: <199808151705.KAA17832@austin.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Whats wrong with specifying the search path with the '-R' flag when the > program is linked? The person doing the linking doesn't necessarily know where the libraries are going to be installed. -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 Aug 15 17:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09125 for freebsd-current-outgoing; Sat, 15 Aug 1998 17:28:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09120 for ; Sat, 15 Aug 1998 17:28:48 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id UAA05566; Sat, 15 Aug 1998 20:28:09 -0400 (EDT) Date: Sat, 15 Aug 1998 20:28:09 -0400 (EDT) From: "Matthew N. Dodd" To: Garrett Wollman cc: John Polstra , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808160014.UAA16120@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 On Sat, 15 Aug 1998, Garrett Wollman wrote: > < said: > > Whats wrong with specifying the search path with the '-R' flag when the > > program is linked? > > The person doing the linking doesn't necessarily know where the > libraries are going to be installed. In the case of system binaries, they do know where the libraries will be installed. Other things have fiarly standard places to live (/usr/local/lib, /usr/X11/lib etc). If an end user does not like the defaults they are free to recompile the software in question. I would be interested in a utility that lets you edit the compiled in search paths. This would seem to be a far better solution than LD_LIBRARY_PATH. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 17:49:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10952 for freebsd-current-outgoing; Sat, 15 Aug 1998 17:49:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10947 for ; Sat, 15 Aug 1998 17:49:08 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id UAA09677; Sat, 15 Aug 1998 20:48:10 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: Karl Pielorz cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Can't build kernel with 15/08/98 @ 23:17 source In-reply-to: Your message of "Sun, 16 Aug 1998 00:13:53 BST." <35D61631.47D5DACA@tdx.co.uk> Date: Sat, 15 Aug 1998 20:48:10 -0400 Message-ID: <9673.903228490@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote in message ID <35D61631.47D5DACA@tdx.co.uk>: > Hi All, > > I can't seem to build a kernel with the latest sources... It falls over with: > > " > caladan# make > loading kernel > cd.o: Undefined symbol `_scsi_device_register' referenced from text segment > cd.o: Undefined symbol `_scsi_open' referenced from text segment > cd.o: Undefined symbol `_scsi_ioctl' referenced from text segment > cd.o: Undefined symbol `_scsi_close' referenced from text segment > cd.o: Undefined symbol `_scsi_minphys' referenced from text segment > cd.o: Undefined symbol `_scsi_strategy' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > (heaps of more like the above) > " > > Can anybody suggest anything? - I have the following lines in the kernel conf > ig: > > " > controller ahc0 > controller ahc1 > controller ahc2 > options AHC_TAGENABLE > options AHC_SCBPAGING_ENABLE > options AHC_ALLOW_MEMIO > > device sd0 > device st0 > device cd0 #Only need one of these, the code dynamically grows > " Do you have: controller scbus0 at ahc0 controller scbus1 at ahc1 controller scbus2 at ahc2 Also? You could actually cut this down do: controller ahc0 controller scbus0 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO device sd0 device st0 device cd0 Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 18:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13778 for freebsd-current-outgoing; Sat, 15 Aug 1998 18:14:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13772 for ; Sat, 15 Aug 1998 18:14:17 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA20250; Sat, 15 Aug 1998 18:13:45 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd020209; Sat Aug 15 18:13:37 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA17303; Sat, 15 Aug 1998 18:13:34 -0700 (MST) From: Terry Lambert Message-Id: <199808160113.SAA17303@usr07.primenet.com> Subject: Better VM patches (was Tentative fix for VM bug) To: dg@root.com Date: Sun, 16 Aug 1998 01:13:33 +0000 (GMT) Cc: current@FreeBSD.ORG, karl@mcs.net In-Reply-To: <199808152349.QAA20449@implode.root.com> from "David Greenman" at Aug 15, 98 04:49:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >yes, but is it a bug that he's reporting? > > I don't see anything wrong with vm_object_page_remove(). We'd have > far more serious problems if there was something wrong with it (the system > wouldn't last for more than a few seconds, if that), and further, the > problem wouldn't be specific to just NFS. My thinking at the moment is that > the problem is caused by the lack of NFSnode locking; we depend on VOP_LOCK > actually doing something in many parts of the code, and with nfs_lock() > being a noop, it just doesn't happen. There might be a way to fix this > without messing with nfs_lock(), but the exact failure scenario will need > to be looked at carefully before this can be determined. Let me prefix this by saying that your NFS fixes are correct, and that my "backup patch" apparently only masks the EOF bug that results from bogus invalidations, and there's a better fix. The problem with vm_object_page_remove() is that in the clean_only != 0 case, the page is marked invalid. This will result in orphaned pages. This is not the problem we have been seeing, because these would be lost. This may be the source of the: * XXX: sometimes we get pages which aren't wired down or on any queue - * we need to put them on the inactive queue also, otherwise we lose * track of them. Paul Mackerras (paulus@cs.anu.edu.au) 9-Jan-93. comment in vm_page.c, and it may be the source of the zero page phenomenon. John provided the fix, but inverted the clearing of valid and the vm_page_protect call. I corrected this. Another problem in the mmap code is that when the vnode_pager object is created, it is set to be the number of pages times the page size in length; but also in vnode_pager, the setsize on the object sets the length to the actual file length. This discrepancy opens a window in which some changes may be lost. I have narrowed this window, but it's still there; other than adding an actual size parameter to vnode_pager_object_allocate, I couldn't fully close off the window. I would appreciate it if people with mmap news server problems and the zero'ed page problems would try these patches. John also suggested another change for detecting a case where page orphans can be created. in vm_page.c, it's possible that an object entry in the page insert function will overwrite an existing entry; I added a DIAGNOSTIC panic to catch this when it happens. Finally, there were three cases in which a lock was being acquired, but not being logged by MAP_LOCK_DIAGNOSTIC. I've added a vm_map_lock_try macro calling a _vm_map_lock_try inline similar to others in vm_map.h to track this. There are now now cases of lockmgr() being called directly, yet the lock released by a macro encapsulation. Patches (against Whistle's working copy of -current) follow my signature.... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ============================================================================= *** vm_fault.c Mon May 4 03:01:43 1998 --- vm_fault.c.new Sat Aug 15 22:45:59 1998 *************** *** 590,597 **** */ (fs.lookup_still_valid || (((fs.entry->eflags & MAP_ENTRY_IS_A_MAP) == 0) && ! lockmgr(&fs.map->lock, ! LK_EXCLUSIVE|LK_NOWAIT, (void *)0, curproc) == 0))) { fs.lookup_still_valid = 1; /* --- 590,596 ---- */ (fs.lookup_still_valid || (((fs.entry->eflags & MAP_ENTRY_IS_A_MAP) == 0) && ! vm_map_lock_try(fs.map) == 0))) { fs.lookup_still_valid = 1; /* *** vm_glue.c Wed Mar 4 10:27:00 1998 --- vm_glue.c.new Sat Aug 15 22:47:13 1998 *************** *** 452,460 **** * do not swapout a process that is waiting for VM * data structures there is a possible deadlock. */ ! if (lockmgr(&vm->vm_map.lock, ! LK_EXCLUSIVE | LK_NOWAIT, ! (void *)0, curproc)) { vmspace_free(vm); continue; } --- 452,459 ---- * do not swapout a process that is waiting for VM * data structures there is a possible deadlock. */ ! if (vm_map_lock_try(&vm->vm_map)) { ! /* failed to obtain lock*/ vmspace_free(vm); continue; } *** vm_map.h Thu Jan 22 17:30:38 1998 --- vm_map.h.new Sat Aug 15 23:22:14 1998 *************** *** 242,247 **** --- 242,261 ---- #endif static __inline__ int + _vm_map_lock_try(vm_map_t map, struct proc *p) { + int rv; + + rv = lockmgr(&(map)->lock, LK_EXCLUSIVE | LK_NOWAIT, (void *)0, p); + #if defined(MAP_LOCK_DIAGNOSTIC) + if( !rv) + printf("locking map LK_EXCLUSIVE: 0x%x\n", map); + #endif + return rv; + } + + #define vm_map_lock_try(map) _vm_map_lock_try(map, curproc) + + static __inline__ int _vm_map_lock_upgrade(vm_map_t map, struct proc *p) { #if defined(MAP_LOCK_DIAGNOSTIC) printf("locking map LK_EXCLUPGRADE: 0x%x\n", map); *** vm_mmap.c Sun Aug 16 00:09:32 1998 --- vm_mmap.c.new Sun Aug 16 00:33:06 1998 *************** *** 929,934 **** --- 929,935 ---- vm_ooffset_t objsize; int docow; struct proc *p = curproc; + struct vattr vat; if (size == 0) return (0); *************** *** 972,978 **** type = OBJT_DEVICE; handle = (void *)vp->v_rdev; } else { - struct vattr vat; int error; error = VOP_GETATTR(vp, &vat, p->p_ucred, p); --- 973,978 ---- *************** *** 990,995 **** --- 990,1002 ---- handle, OFF_TO_IDX(objsize), prot, foff); if (object == NULL) return (type == OBJT_DEVICE ? EINVAL : ENOMEM); + /* + * XXX we are in a race here. If the file is extended + * between the time we get the object and the time + * we set the size, then we lose... + */ + if (!(flags & MAP_ANON) && vp->v_type != VCHR) + object->un_pager.vnp.vnp_size = vat.va_size; } /* *** vm_page.c Sat Aug 15 20:26:27 1998 --- vm_page.c.new Sat Aug 15 22:10:23 1998 *************** *** 388,393 **** --- 388,400 ---- register vm_pindex_t pindex; { register struct pglist *bucket; + #ifdef DIAGNOSTIC + register vm_page_t dm; + + dm = vm_page_lookup(object, pindex); + if (dm) + panic("vm_page_insert: insertion overwrites existing entry"); + #endif #if !defined(MAX_PERF) if (m->flags & PG_TABLED) *************** *** 1071,1076 **** --- 1078,1085 ---- /* * helper routine for vm_page_free and vm_page_free_zero + * + * must be at splhigh */ static int vm_page_freechk_and_unqueue(m) *** vm_pageout.c Mon Mar 30 09:56:58 1998 --- vm_pageout.c.new Sat Aug 15 22:45:37 1998 *************** *** 530,536 **** vm_map_entry_t tmpe; vm_object_t obj, bigobj; ! if (lockmgr(&map->lock, LK_EXCLUSIVE | LK_NOWAIT, (void *)0, curproc)) { return; } --- 530,537 ---- vm_map_entry_t tmpe; vm_object_t obj, bigobj; ! if (vm_map_lock_try(map)) { ! /* failed to obtain lock */ return; } *** vnode_pager.c Mon Mar 16 01:56:03 1998 --- vnode_pager.c.new Sun Aug 16 00:05:12 1998 *************** *** 137,142 **** --- 137,147 ---- object = vm_object_allocate(OBJT_VNODE, size); object->flags = 0; + /* + * The object is allocated to a page boundary. This is + * incorrect if page is only partially backed by the vp; + * we must fix this up in the caller. + */ object->un_pager.vnp.vnp_size = (vm_ooffset_t) size * PAGE_SIZE; object->handle = handle; *** vm_object.c Sun Aug 16 00:55:33 1998 --- vm_object.c.new Sun Aug 16 00:54:15 1998 *************** *** 1324,1330 **** if (all || ((start <= p->pindex) && (p->pindex < end))) { if (p->wire_count != 0) { vm_page_protect(p, VM_PROT_NONE); ! p->valid = 0; continue; } --- 1324,1331 ---- if (all || ((start <= p->pindex) && (p->pindex < end))) { if (p->wire_count != 0) { vm_page_protect(p, VM_PROT_NONE); ! if (!clean_only) ! p->valid = 0; continue; } *************** *** 1352,1359 **** if ((p = vm_page_lookup(object, start)) != 0) { if (p->wire_count != 0) { - p->valid = 0; vm_page_protect(p, VM_PROT_NONE); start += 1; size -= 1; continue; --- 1353,1361 ---- if ((p = vm_page_lookup(object, start)) != 0) { if (p->wire_count != 0) { vm_page_protect(p, VM_PROT_NONE); + if (!clean_only) + p->valid = 0; start += 1; size -= 1; continue; ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 19:49:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20158 for freebsd-current-outgoing; Sat, 15 Aug 1998 19:49:43 -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 TAA20153 for ; Sat, 15 Aug 1998 19:49:41 -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 TAA20839; Sat, 15 Aug 1998 19:49:04 -0700 (PDT) (envelope-from jdp) Message-Id: <199808160249.TAA20839@austin.polstra.com> To: "Matthew N. Dodd" cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-reply-to: Your message of "Sat, 15 Aug 1998 18:59:06 EDT." Date: Sat, 15 Aug 1998 19:49:04 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Whats wrong with specifying the search path with the '-R' flag when > the program is linked? Nothing, provided you know where the libraries are going to be. Actually, I like this idea. It makes a lot of sense, especially for ports. -- 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 Sat Aug 15 20:04:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21552 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:04:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21547 for ; Sat, 15 Aug 1998 20:04:52 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id XAA06693; Sat, 15 Aug 1998 23:04:17 -0400 (EDT) Date: Sat, 15 Aug 1998 23:04:17 -0400 (EDT) From: "Matthew N. Dodd" To: John Polstra cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808160249.TAA20839@austin.polstra.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, 15 Aug 1998, John Polstra wrote: > > Whats wrong with specifying the search path with the '-R' flag when > > the program is linked? > > Nothing, provided you know where the libraries are going to be. > Actually, I like this idea. It makes a lot of sense, especially for > ports. Exactly. '-R' is the easy way for us to keep track of dependancies on libraries; the binary keeps track of its search path, not the administrator of the system. If the administrator wants to move things from their default locations, he should be able to recompile the binary, edit the search path in the binary (is this possiable? I've not been able to find a way to do this in Solaris.) or at last resort, use LD_LIBRARY_PATH. Its too easy for users to subvert LD_LIBRARY_PATH and dig themselves gopher holes to trip up in. In addition, relying on LD_LIBRARY_PATH complicates the use of multiple versions of a library with different binaries. At the site I work at, we use a commercial version of Kerberos, installed in say /usr/kerberos/{bin,lib,etc}. I compile and install MIT kerberos in $HOME/opt/krb5/{bin,lib,etc}. I neglect to modify the build process to add the proper '-R' and decide to use LD_LIBRARY_PATH; both the commercial and the MIT versions of kerberos call their libraries the same thing (libkrb5.so for short.). Running the original binaries out of /usr/kerberos/bin results in an error as the LD_LIBRARY_PATH lets the binary load the wrong library. Long winded but this is one of the reasons I dislike relying on LD_LIBRARY_PATH. Using it for temporary situations is fine; installed programs have no business using it. If anyone knows if it is feasible to modify the compiled in search paths I'd like to know about it. This is the best solution for the desire to allow libraries to be moved. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 20:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23300 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:21:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23290 for ; Sat, 15 Aug 1998 20:21:03 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.58.132]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id XAA20372; Sat, 15 Aug 1998 23:20:27 -0400 (EDT) Message-ID: <35D6500F.7F1149BA@acm.org> Date: Sat, 15 Aug 1998 23:20:47 -0400 From: Jim Bloom X-Mailer: Mozilla 4.04 [en]C-MOENE (Win95; U) MIME-Version: 1.0 To: "Matthew N. Dodd" CC: current@FreeBSD.ORG Subject: Re: ELF problems to occur References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG '-R' is nice when you have source. If you are software vendor distributing binaries only, your example show why LD_LIBRARY_PATH is nice. The system administrator can configure the loading to match the local environment without requiring supporting libraries to be installed in one precise place. The exact same problem arises when one buys a binary only package. I agree that editting a binaries search list is one of the better solutions, but I don't believe it is feasible on Solaris. Jim Bloom bloom@acm.org Matthew N. Dodd wrote: > > Exactly. '-R' is the easy way for us to keep track of dependancies on > libraries; the binary keeps track of its search path, not the > administrator of the system. > > If the administrator wants to move things from their default locations, he > should be able to recompile the binary, edit the search path in the binary > (is this possiable? I've not been able to find a way to do this in > Solaris.) or at last resort, use LD_LIBRARY_PATH. > > Its too easy for users to subvert LD_LIBRARY_PATH and dig themselves > gopher holes to trip up in. In addition, relying on LD_LIBRARY_PATH > complicates the use of multiple versions of a library with different > binaries. At the site I work at, we use a commercial version of Kerberos, > installed in say /usr/kerberos/{bin,lib,etc}. I compile and install MIT > kerberos in $HOME/opt/krb5/{bin,lib,etc}. I neglect to modify the build > process to add the proper '-R' and decide to use LD_LIBRARY_PATH; both the > commercial and the MIT versions of kerberos call their libraries the same > thing (libkrb5.so for short.). Running the original binaries out of > /usr/kerberos/bin results in an error as the LD_LIBRARY_PATH lets the > binary load the wrong library. > > Long winded but this is one of the reasons I dislike relying on > LD_LIBRARY_PATH. Using it for temporary situations is fine; installed > programs have no business using it. > > If anyone knows if it is feasible to modify the compiled in search paths > I'd like to know about it. This is the best solution for the desire to > allow libraries to be moved. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 20:26:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23863 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:26:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from falcon.inetnebr.com (falcon.inetnebr.com [199.184.119.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23858 for ; Sat, 15 Aug 1998 20:26:20 -0700 (PDT) (envelope-from cradek@in221.inetnebr.com) Received: from hoser.inetnebr.com (in221.inetnebr.com [199.184.119.221]) by falcon.inetnebr.com (8.8.8/8.8.8) with ESMTP id WAA05858 for ; Sat, 15 Aug 1998 22:25:45 -0500 (CDT) Received: from insight.inetnebr.com (localhost [127.0.0.1]) by hoser.inetnebr.com (8.8.8/8.8.8) with ESMTP id WAA20242 for ; Sat, 15 Aug 1998 22:26:17 -0500 (CDT) (envelope-from cradek@insight.inetnebr.com) Message-Id: <199808160326.WAA20242@hoser.inetnebr.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: STB TV/PCI - every other scanline? Date: Sat, 15 Aug 1998 22:26:17 -0500 From: Chris Radek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using the bktr driver with an STB TV/PCI and Matrox Millenium II, I am getting a nice picture but with only every other line showing. Every once in a while, the intermediate lines will be displayed at the top 1/4 (or so) of the picture and "freeze" there. So after this happens, every other line is a frozen (wrong) picture on the top part of the window. Hitting "refresh" on my window manager menu clears out the frozen lines and I get my picture back with every other line black. Is anyone else seeing this behavior? Under L***x, the card works properly. (I just nuked it and installed FreeBSD... Trying to get everything working again now!) Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 20:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24194 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:29:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp1718.on.bellglobal.com [206.172.249.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24189 for ; Sat, 15 Aug 1998 20:29:24 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id XAA05658; Sat, 15 Aug 1998 23:28:11 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 15 Aug 1998 23:28:11 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: John Polstra cc: "Matthew N. Dodd" , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808160249.TAA20839@austin.polstra.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, 15 Aug 1998, John Polstra wrote: > Actually, I like this idea. It makes a lot of sense, especially for > ports. So long as no one's suggesting removing LD_LIBRARY_PATH... -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 20:40:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25046 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:40:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25040 for ; Sat, 15 Aug 1998 20:40:38 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id XAA06950; Sat, 15 Aug 1998 23:40:07 -0400 (EDT) Date: Sat, 15 Aug 1998 23:40:06 -0400 (EDT) From: "Matthew N. Dodd" To: Jim Bloom cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <35D6500F.7F1149BA@acm.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 On Sat, 15 Aug 1998, Jim Bloom wrote: > '-R' is nice when you have source. If you are software vendor > distributing binaries only, your example show why LD_LIBRARY_PATH is > nice. The system administrator can configure the loading to match the > local environment without requiring supporting libraries to be > installed in one precise place. The exact same problem arises when one > buys a binary only package. So we only care about LD_LIBRARY_PATH when the following conditions exist: 1. We wish to install and run a package for which we do not have the source. 2. We wish to install the package in a location other than the default. Given these conditions, I do not think it unrealistic for us to attempt to do everything in our power to limit the need for LD_LIBARARY_PATH for normal system operation. This means the base system and ports. The alternative is to watch -questions become deluged with "I can't find my libraries but they are listed in /etc/ld.so.conf. Help!!" (Obviously, this won't happen unless 3.0 is still partially an a.out system when it releases.) > I agree that editting a binaries search list is one of the better > solutions, but I don't believe it is feasible on Solaris. It should be feasible on FreeBSD given the premise that "everything is possiable in software." The question now is if it is practical for someone to spend the time to add support. -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 20:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25540 for freebsd-current-outgoing; Sat, 15 Aug 1998 20:45:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25535 for ; Sat, 15 Aug 1998 20:45:51 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id XAA07008; Sat, 15 Aug 1998 23:45:12 -0400 (EDT) Date: Sat, 15 Aug 1998 23:45:12 -0400 (EDT) From: "Matthew N. Dodd" To: Tim Vanderhoek cc: John Polstra , current@FreeBSD.ORG Subject: Re: ELF problems to occur 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 Sat, 15 Aug 1998, Tim Vanderhoek wrote: > On Sat, 15 Aug 1998, John Polstra wrote: > > Actually, I like this idea. It makes a lot of sense, especially for > > ports. > > So long as no one's suggesting removing LD_LIBRARY_PATH... Of course not. Please don't let my verbose postings against LD_LIBRARY_PATH be intrepreted as a call for it's removal. LD_LIBRARY_PATH is an adaquet tool for a limited case of problems. I am trying to point out that the use of LD_LIBRARY_PATH does not belong in the system as provided by the FreeBSD Project (base, X11, ports etc). -- | Matthew N. Dodd |This space | '78 Datsun 280Z | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net |is for rent| '84 Volvo 245DL | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 15 21:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29139 for freebsd-current-outgoing; Sat, 15 Aug 1998 21:30:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29134 for ; Sat, 15 Aug 1998 21:30:49 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA21488; Sat, 15 Aug 1998 23:30:15 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA17489; Sat, 15 Aug 1998 23:30:15 -0500 (CDT) Message-ID: <19980815233015.14991@mcs.net> Date: Sat, 15 Aug 1998 23:30:15 -0500 From: Karl Denninger To: Terry Lambert Cc: dg@root.com, current@FreeBSD.ORG Subject: Re: Better VM patches (was Tentative fix for VM bug) References: <199808152349.QAA20449@implode.root.com> <199808160113.SAA17303@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199808160113.SAA17303@usr07.primenet.com>; from Terry Lambert on Sun, Aug 16, 1998 at 01:13:33AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has had an effect, in that it has changed behavior. It has not completely made the problem go away, as I managed to provoke it about an hour after I loaded these patches. However, it has had a significantly positive effect. I am NOT running with DIAGNOSTIC, so I won't get the panic (I don't want it!) More on this tomorrow when its been up for a day or so. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Sun, Aug 16, 1998 at 01:13:33AM +0000, Terry Lambert wrote: > > >yes, but is it a bug that he's reporting? > > > > I don't see anything wrong with vm_object_page_remove(). We'd have > > far more serious problems if there was something wrong with it (the system > > wouldn't last for more than a few seconds, if that), and further, the > > problem wouldn't be specific to just NFS. My thinking at the moment is that > > the problem is caused by the lack of NFSnode locking; we depend on VOP_LOCK > > actually doing something in many parts of the code, and with nfs_lock() > > being a noop, it just doesn't happen. There might be a way to fix this > > without messing with nfs_lock(), but the exact failure scenario will need > > to be looked at carefully before this can be determined. > > Let me prefix this by saying that your NFS fixes are correct, and > that my "backup patch" apparently only masks the EOF bug that > results from bogus invalidations, and there's a better fix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message